Table of Contents
- Introduction
- Testing Scope
- Function Verification Test
- Scenario 1 - Normal console functionality
- Console against OpenPOWER machine via OpenBMC
- Console against OpenPOWER machine via IPMI
- Console against KVM guest via ssh to KVM host
- Console against x86-64 machine via IPMI
- Console against IBM PowerVM LPAR via HMC
- Scenario 2 - Recovery
- Restart a compute node
- Restart the OpenBMC on a OpenPOWER machine with OpenBMC
- Restart the BMC on a OpenPOWER machine with IPMI
- Disconnect the network between the console server and the OpenBMC/BMC
- Scenario 3 - Multiplex
- Scenario 4 - Stability
- Performance Test
- Conclusion
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.
News
- Apr 22, 2016: xCAT 2.11.1 released.
- Mar 11, 2016: xCAT 2.9.3 (AIX only) released.
- Dec 11, 2015: xCAT 2.11 released.
- Nov 11, 2015: xCAT 2.9.2 (AIX only) released.
- Jul 30, 2015: xCAT 2.10 released.
- Jul 30, 2015: xCAT migrates from sourceforge to github
- Jun 26, 2015: xCAT 2.7.9 released.
- Mar 20, 2015: xCAT 2.9.1 released.
- Dec 12, 2014: xCAT 2.9 released.
- Sep 5, 2014: xCAT 2.8.5 released.
- May 23, 2014: xCAT 2.8.4 released.
- Jan 24, 2014: xCAT 2.7.8 released.
- Nov 15, 2013: xCAT 2.8.3 released.
- Jun 26, 2013: xCAT 2.8.2 released.
- May 17, 2013: xCAT 2.7.7 released.
- May 10, 2013: xCAT 2.8.1 released.
- Feb 28, 2013: xCAT 2.8 released.
- Nov 30, 2012: xCAT 2.7.6 released.
- Oct 29, 2012: xCAT 2.7.5 released.
- Aug 27, 2012: xCAT 2.7.4 released.
- Jun 22, 2012: xCAT 2.7.3 released.
- May 25, 2012: xCAT 2.7.2 released.
- Apr 20, 2012: xCAT 2.7.1 released.
- Mar 19, 2012: xCAT 2.7 released.
- Mar 15, 2012: xCAT 2.6.11 released.
- Jan 23, 2012: xCAT 2.6.10 released.
- Nov 15, 2011: xCAT 2.6.9 released.
- Sep 30, 2011: xCAT 2.6.8 released.
- Aug 26, 2011: xCAT 2.6.6 released.
- May 20, 2011: xCAT 2.6 released.
- Feb 14, 2011: Watson plays on Jeopardy and is managed by xCAT!
- xCAT Release Notes Summary
- xCAT OS And Hw Support Matrix
- xCAT Test Environment Summary
History
- Oct 22, 2010: xCAT 2.5 released.
- Apr 30, 2010: xCAT 2.4 is released.
- Oct 31, 2009: xCAT 2.3 released.
xCAT's 10 year anniversary! - Apr 16, 2009: xCAT 2.2 released.
- Oct 31, 2008: xCAT 2.1 released.
- Sep 12, 2008: Support for xCAT 2
can now be purchased! - June 9, 2008: xCAT breaths life into
(at the time) the fastest
supercomputer on the planet - May 30, 2008: xCAT 2.0 for Linux
officially released! - Oct 31, 2007: IBM open sources
xCAT 2.0 to allow collaboration
among all of the xCAT users. - Oct 31, 1999: xCAT 1.0 is born!
xCAT started out as a project in
IBM developed by Egan Ford. It
was quickly adopted by customers
and IBM manufacturing sites to
rapidly deploy clusters.