Test Report of `goconserver` - xcat2/xcat-core GitHub Wiki

Introduction

This document explains the various activities performed as part of Testing of "gocnserver Function Verification Test". It contains the results of tests, which were executed during the testing.

Refer the Test Design

Testing Scope

Function Verification Test

Scenario 1 - Normal console functionality

Test if the console can work normally in the following conditions

Console against OpenPOWER machine via OpenBMC

Run the following command, see if it works.

congo create tz001 driver=ssh ondemand=false --params user=root,host=10.3.1.9,port=22,password=cluster
congo console tz001

+ PASS

Console against OpenPOWER machine via IPMI

Run the following command, see if it works.

congo create tz002 driver=cmd ondemand=false --params cmd="ipmitool -I lanplus -H 50.3.17.1 -U '' -P PASSW0RD sol activate"
congo console tz002

See issue #6

congo create tz003 driver=cmd ondemand=false --params cmd="/opt/xcat/share/xcat/cons/ipmi tz003"
congo console tz003

There is no proper solution for this scenario yet.

- NOT APPLICABLE

Console against KVM guest via ssh to KVM host

Run the following command, see if it works.

congo create tz004 driver=cmd ondemand=false --params cmd="/opt/xcat/share/xcat/cons/kvm tz004"
congo console tz004

There is no proper solution for this scenario yet.

- NOT APPLICABLE

Console against x86-64 machine via IPMI

Run the following command, see if it works.

congo create tz005 driver=cmd ondemand=false --params cmd="/opt/xcat/share/xcat/cons/ipmi tz005"
congo console tz005

There is no proper solution for this scenario yet.

- NOT APPLICABLE

Console against IBM PowerVM LPAR via HMC

Run the following command, see if it works.

congo create tz006 driver=cmd ondemand=false --params cmd="/opt/xcat/share/xcat/cons/hmc tz006"
congo console tz006

There is no proper solution for this scenario yet.

- NOT APPLICABLE

Scenario 2 - Recovery

Restart a compute node

+ PASS

Restart the OpenBMC on a OpenPOWER machine with OpenBMC

This test is performed by connect to a regular ssh host. And reboot the remote ssh host. See if goconserver can do the retry and reconnect properly after the remote ssh host restart.

congo create tz001 driver=ssh ondemand=false --params user=root,host=10.3.1.9,port=22,password=cluster
congo console tz001

+ PASS

Restart the BMC on a OpenPOWER machine with IPMI

  NOT APPLICABLE

Disconnect the network between the console server and the OpenBMC/BMC

+ PASS

Scenario 3 - Multiplex

Multiple user connect to the console of the same compute node at the same time

This test is performed by connect to a regular ssh host. And use two or three congo console sessions from different terminal to access it. See if all these setup can work properly.

congo create tz001 driver=ssh ondemand=false --params user=root,host=10.3.1.9,port=22,password=cluster
congo console tz001

+ PASS

Scenario 4 - Stability

Leave a compute node with no console outputs for a quite long period of time, say 10 days

See issue #8

- FAILED

Performance Test

VSZ RSS OFD Nodes
203776 9792 13 0 node
205632 9792 14 1 node
208064 9792 15 2 nodes
209216 9792 18 5 nodes
284032 9792 23 10 nodes
285120 9792 33 20 nodes
287232 9792 63 50 nodes
365184 14080 113 100 nodes
1286080 24512 213 200 nodes
724480 72192 513 500 nodes
785600 120512 1013 1000 nodes
... ... ... ...
?? ?? n + 13 n nodes
  • VSS - Virtual memory size of the process in KiB (1024-byte units). Device mappings are currently excluded; this is subject to change.
  • RSS - Resident set size, the non-swapped physical memory that a task has used (in kiloBytes).
  • OFD - Opened file descriptors.

Performance Testing was not done for goconserver yet.

Conclusion

It is not suggested goconserver to "Go Live" at this time.

⚠️ **GitHub.com Fallback** ⚠️