You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(This was originally @kambiz-aghaiepour suggestion, filing for him here)
Occasionally we might decommission systems instead of outright removing them from QUADS control and it might be useful to preserve the scheduling history and/or the interfaces or other data so it can be referenced later.
Some option like quads-cli --retire --host host01.example.com would help here, where it might:
tag a retired: yes flag onto the hosts mongodb collection
any host with retired: yes would not be schedulable or show up in the following returns:
not show up in --ls-hosts unless something like --retired-hosts is passed
not show up on wiki / visuals
not show up in any totals relying on --ls-hosts
not show up in --ls-available
If another approach involving CloudHistory is possible here perhaps that's ok too.
The text was updated successfully, but these errors were encountered:
(This was originally @kambiz-aghaiepour suggestion, filing for him here)
Occasionally we might decommission systems instead of outright removing them from QUADS control and it might be useful to preserve the scheduling history and/or the interfaces or other data so it can be referenced later.
Some option like
quads-cli --retire --host host01.example.com
would help here, where it might:retired: yes
flag onto the hosts mongodb collectionretired: yes
would not be schedulable or show up in the following returns:--ls-hosts
unless something like--retired-hosts
is passed--ls-hosts
--ls-available
If another approach involving
CloudHistory
is possible here perhaps that's ok too.The text was updated successfully, but these errors were encountered: