This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Test Design of rinv
python version
Introduction
This document provides an overview of test of command rinv 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
Overview of xCAT FVT
Test Software Requirements
Operating System :Red Hat Enterprise Linux Server release 7.4
Other Softwares
xCAT 2.13.11
Test Hardware Requirements
MN: any machines with latest xcat installed
CN: Witherspoon node (p9)
xCAT Test Detail Section
Test environment preparation
-
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:
Test cases
Automation cases
We have rinv automation cases in file cases0, cases2 under /opt/xcat/share/xcat/tools/autotest/testcase/rinv. After you install xcat-test, you will find the file.
[root@briggs01 rinv]# pwd
/opt/xcat/share/xcat/tools/autotest/testcase/rinv
[root@briggs01 rinv]# ls
cases0 cases2
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 rinv cases bundle file by yourself.
[root@briggs01 bundle]# pwd
/opt/xcat/share/xcat/tools/autotest/bundle
[root@briggs01 bundle]# cat rinv.bundle
rinv_h
rinv_v
rinv_help
rinv_errorcommand
rinv_serial
rinv_model
rinv_firm
rinv_all
rinv_mixnode
rinv_cpu
rinv_dimm
rinv_check_active_fw_count
rinv_check_active_fw_count_verbose
rinv_wrongbmcpasswd
- Run following commands to start your test.
[root@briggs01 testcase]# XCATTEST_CN=mid05tor12cn05 xcattest -b rinv.bundle
- Check the result under following directory
[root@briggs01 result]# pwd
/opt/xcat/share/xcat/tools/autotest/result
[root@briggs01 result]# vi xcattest.log.20180204054757
Manual cases (Notice: by 2.13.11, the automation cases cover all the options in following help information. FVT doesn't need to run manual cases at the moment)
The test cases is given according to the rinv' help information for machines managed by openbmc.
OpenPOWER (OpenBMC) server specific: rinv [model|serial|firm|cpu|dimm|all] [-V|--verbose]
Test case 1
Check if rinv -h or --help could display help information for openbmc.
- Run rinv -h or rinv --help
- Expected output should be help information.
Test case 2
Check if rinv noderange model could retrieves the machine's model number.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rinv nodegrange model
- Expected output should be the node's model information.
Test case 3
Check if rinv noderange serial could retrieves the machine's serial number.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rinv nodegrange serial
- Expected output should be the node's serial information.
Test case 4
Check if rinv noderange firm could retrieves the machine's firmware version.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rinv nodegrange firm
- Expected output should be the node's firmware version.
Test case 5
Check if rinv noderange cpu could retrieves the machine's firmware version.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rinv nodegrange firm
- Expected output should be the node's firmware version.
Test case 6
Check if rinv noderange dimm could retrieves the machine's dual in-line memory module information.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rinv nodegrange dimm
- Expected output should be the node's dual in-line memory module information.
Test case 7
Check if rinv noderange all could retrieves the machine's all information include cpu, memory, power etc.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rinv nodegrange all
- Expected output should be the node's all information.
Test case 8
Check if rinv noderange all -V / --verbose could retrieves the machine's all information in verbose format.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rinv nodegrange all -V/ --verbose
- Expected output should be the node's verbose information.
Test case 9
Check if rinv noderange false_value.
- Define node. The node's definition should have bmc's ip. BMC should work correctly.
- Run rinv nodegrange false_value
- Expected output should be warning message.
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.