Test Design of rcons based goconserver

Function Verification Test

Scenario 0 - Installation and basic setup

• Install goconserver along with xCAT, and make it running.
  • Shutdown conserver
  • Run makegocons

Scenario 1 - Normal console functionality

Test if the console can work normally in the following conditions

• Console against OpenPOWER machine via OpenBMC
  • Create a node definition with openbmc as its cons attribute
  • Run makegocons against this node
  • Run rcons against this node
• Console against OpenPOWER machine via IPMI
  • Create a node definition with ipmi as its cons attribute
  • Run makegocons against this node
  • Run rcons against this node* Console against KVM guest via ssh to KVM host
• Console against x86-64 machine via IPMI
  • Create a node definition with ipmi as its cons attribute
  • Run makegocons against this node
  • Run rcons against this node
• Console against IBM PowerVM LPAR via HMC
  • Create a node definition with hmc as its cons attribute
  • Run makegocons against this node
  • Run rcons against this node

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

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

Scenario 4 - Stability

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