Closed patchsmyle closed 1 year ago
You would be correct; however, assuming you are using cache, large data sets which will be invalid following a restart (this includes anything with a registry provider such as bios or smart storage). Cache-less activities, sure. We could consider an optional argument added to the logout command (technically available for all commands), which would do this; however, if you use cache, then it is strongly advised to refresh when the system has finished POST (or later).
Understood it is strongly advised. In my use case I am setting up a new server and updating Firmware from the CLI, not a database automation system. I am not worried about the data (cache) already collected.
Would it also not be wise to give an option in the tool/system then to allow to purge cache without needing to log-out?
This will be available in version 4.1. Additional Option --nologout will be introduced.
ilorest when sending any form of a reboot command, 'PowerOn', 'PushPowerButton', etc force the API connection to be disconnected.
Powering on a server should not force the API to disconnect, as it is sending a command to change the server state, not the ILO state. If this was a reboot of the ILO I would understand.
I am able to safely power off the server via the GUI or another method and the API does not loose a connection. An example of this is from HPE's own documentation: https://developer.hpe.com/blog/master-the-redfish-server-states-to-improve-your-monitoring-and-manageme