* rpower for redfish support
* rsetboot for redfish support
* recover
* modify depending on discussion and comments
* refine test case xcatd_start (#5932)
* Update small text in the diskful support example for cuda_power9_setup
Fix small issue mentioned in 5852
* rsetboot for redfish support
* Fix issue 5933: xCAT-openbmc-py build failed
* Fix remoteshell compatibility with custom Match (#5936)
If a user has a custom Match directive, remoteshell would
create an invalid configuration. Fix by ensuring we are
outside of a match context by doing Match all explicitly.
* fix issue PR #5936 resulted in remoteshell failed in rhels6.10 #5944
* refine xcat-inventory backend testcase (#5946)
* add test case for issue 3602: confignetwork cannot work when regular expression is used in nics table
* add lsdef to get more debug info
* Revert "fix issue PR #5936 resulted in remoteshell failed in rhels6.10 #5944"
* revert PR Fix remoteshell compatibility with custom Match #5936
* [go-xcat] Revise debug log, in order to make debugging go-xcat and bug reporting easier.
* [go-xcat] Revise the prompt messages
* [go-xcat] In yum/zypper repo file, use gpgcheck=1
* [go-xcat] Bump version number
* [go-xcat] Revise the help messages
* [go-xcat] xCAT uninstallation
* [go-xcat] Fix kill command error messages
* [go-xcat] Simplify command line argument processing
* [go-xcat] When do a `check', only run update_repo
* Update document of xCAT uninstallation - use `go-xcat uninstall`
* [go-xcat] Handle goconserver in trash_xcat()
* [go-xcat] Add goconserver to the uninstallation package list
* Add goconserver to the uninstallation package list
* [go-xcat] Fix debug_logger
* [go-xcat] xCAT can be completely uninstalled
You can't install NVML anymore. NVML has been part of CUDA since CUDA version 8. See: https://developer.nvidia.com/gpu-deployment-kit
```
The GPU Deployment Kit is part of the CUDA Toolkit, in versions 8 and later, and is no longer available as a separate download.
```
The package is called: `cuda-nvml-dev-9-2.ppc64le`
The entry in the passwd table has to use the key `switch`, otherwise the sshusername and password is not detected.
See `man switches` page:
```
sshusername
The remote login user name. It can be for ssh or telnet. If it is for telnet,
set protocol to "telnet". If the sshusername is blank, the username, password
and protocol will be retrieved from the passwd table with "switch" as the key.
sshpassword
The remote login password. It can be for ssh or telnet. If it is for telnet, set
protocol to "telnet". If the sshusername is blank, the username, password and
protocol will be retrieved from the passwd table with "switch" as the key.
```
See `man passwd` page:
```
key
The type of component this user/pw is for. Valid values: blade (management module),
ipmi (BMC), system (nodes), omapi (DHCP), hmc, ivm, cec, frame, switch.
```
