-
Notifications
You must be signed in to change notification settings - Fork 173
Test Design of rsetboot python version
This document provides an overview of test of command rsetboot that is conducted on the IBM Witherspoon Physical Machine. This test plan is intended for the use of xCAT FVT team.
The test is against xCAT version 2.13.11. The build of xCAT will be picked up from the xcat.org
Operating System :Red Hat Enterprise Linux Server release 7.4
xCAT 2.13.11
MN: any machines with latest xcat installed
CN: Witherspoon node (p9)
-
new OpenBMC python version rpm installation steps:
- Use yum install gcc and python-devel.ppc64le:
yum install -y gcc python-devel.ppc64le
- Install pip refer to https://pip.pypa.io/en/stable/installing/. Use pip to install gevent, greenlet, certifi, chardet, idna, urllib3, requests:
pip install gevent greenlet certifi chardet idna urllib3 requests
- Download and install xCAT-openbmc-py-2.13.10-snap201801250418.noarch.rpm:
wget http://xcat.org/files/xcat/xcat-dep/2.x_Linux/beta/xCAT-openbmc-py-2.13.10-snap201801250418.noarch.rpm yum localinstall -y xCAT-openbmc-py-2.13.10-snap201801250418.noarch.rpm
- enable OpenBMC python version:
export XCAT_OPENBMC_PYTHON=YES
- Use yum install gcc and python-devel.ppc64le:
We have some rsetboot automation cases in file cases0 under /opt/xcat/share/xcat/tools/autotest/testcase/rsetboot. After you install xcat-test, you will find the file.
[root@briggs01 rsetboot]# pwd
/opt/xcat/share/xcat/tools/autotest/testcase/rsetboot
[root@briggs01 rsetboot]# ls
cases0
The steps to run automation cases.
- Install xcat-test on your testing nodes
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- create rsetboot cases bundle file by yourself.
[root@briggs01 bundle]# pwd
/opt/xcat/share/xcat/tools/autotest/bundle
[root@briggs01 bundle]# cat rsetboot.bundle
rsetboot_net_statcheck
rsetboot_cd_statcheck
rsetboot_default_statcheck
rsetboot_h
rsetboot_help
rsetboot_v
rsetboot_node_invalidnode
rsetboot_noderange_net
rsetboot_node_invalidaction
rsetboot_group_net
- Run following commands to start your test.
[root@briggs01 testcase]# XCATTEST_CN=mid05tor12cn05 xcattest -b rsetboot.bundle
- Check the result under following directory
[root@briggs01 result]# pwd
/opt/xcat/share/xcat/tools/autotest/result
[root@briggs01 result]# vi failedcases.20180201192605
The test cases is given according to the rsetboot' help information for machines managed by openbmc. -u is not realized in python version. Only -p is realized on python version.
Usage: rsetboot [net|hd|cd|floppy|def|stat] [-u] [-p] rsetboot [-h|--help|-v|--version]
Check if rsetboot -h or --help could display help information for openbmc.
- Run rsetboot -h or rsetboot --help
- Expected output should be help information.
Check if rsetboot -v or --version could display version information for openbmc.
- Run rsetboot -v or rsetboot --version
- Expected output should be version information.
Check if rsetboot noderange stat could display the current boot setting.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rsetboot noderange stat
- Expected output should be the node's current boot setting information.
Check if rsetboot noderange def or rsetboot noderange default could boot using the default set in BIOS
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Check the BIOS setting.
- Run rsetboot noderange def or rsetboot noderange default
- Run rpower noderange boot
- Check if the noderange boots from the BIOS setting.
Check if rsetboot noderange hd could boot from hard disk.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rsetboot noderange hd
- Run rpower noderange boot
- Check if the noderange boots from hard disk.
Check if rsetboot noderange net could boot from network.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rsetboot noderange net
- Run rpower noderange boot
- Check if the noderange boots from network.
Check if rsetboot noderange net -p could always boot from network.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rsetboot noderange net -p
- Run rpower noderange boot for several times.
- Check if noderange always boot from network.
Check if rsetboot noderange cd could boot from cd or dvd drive.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rsetboot noderange cd
- Run rpower noderange boot
- Check if the noderange boots from cd or dvd drive.
Check if rsetboot noderange false_value could give warning message.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rsetboot noderange false_value
- Check if the warning message is given.
- Nov 13, 2024: xCAT 2.17 released.
- Mar 08, 2023: xCAT 2.16.5 released.
- Jun 20, 2022: xCAT 2.16.4 released.
- Nov 17, 2021: xCAT 2.16.3 released.
- May 25, 2021: xCAT 2.16.2 released.
- Nov 06, 2020: xCAT 2.16.1 released.
- Jun 17, 2020: xCAT 2.16 released.
- Mar 06, 2020: xCAT 2.15.1 released.
- Nov 11, 2019: xCAT 2.15 released.
- Mar 29, 2019: xCAT 2.14.6 released.
- Dec 07, 2018: xCAT 2.14.5 released.
- Oct 19, 2018: xCAT 2.14.4 released.
- Aug 24, 2018: xCAT 2.14.3 released.
- Jul 13, 2018: xCAT 2.14.2 released.
- Jun 01, 2018: xCAT 2.14.1 released.
- Apr 20, 2018: xCAT 2.14 released.
- Mar 14, 2018: xCAT 2.13.11 released.
- Jan 26, 2018: xCAT 2.13.10 released.
- Dec 18, 2017: xCAT 2.13.9 released.
- Nov 03, 2017: xCAT 2.13.8 released.
- Sep 22, 2017: xCAT 2.13.7 released.
- Aug 10, 2017: xCAT 2.13.6 released.
- Jun 30, 2017: xCAT 2.13.5 released.
- May 19, 2017: xCAT 2.13.4 released.
- Apr 14, 2017: xCAT 2.13.3 released.
- Feb 24, 2017: xCAT 2.13.2 released.
- Jan 13, 2017: xCAT 2.13.1 released.
- Dec 09, 2016: xCAT 2.13 released.
- Dec 06, 2016: xCAT 2.9.4 (AIX only) released.
- Nov 11, 2016: xCAT 2.12.4 released.
- Sep 30, 2016: xCAT 2.12.3 released.
- Aug 19, 2016: xCAT 2.12.2 released.
- Jul 08, 2016: xCAT 2.12.1 released.
- May 20, 2016: xCAT 2.12 released.
- 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 OS And Hw Support Matrix
- 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.