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 is an RFE to provide a command-set to replace one running host's current (or future, specific cloud) schedule with a replacement host. The real-world usage of this would occur if hardware issues or supplanting one model with a more preferred model in an active or future assignment would occur.
Due to the potentially disruptive nature of this command if it were typo'd or used incorrectly we should consider confirmation if we are operating on a currently-running cloud.
NOTE The replacement host must not conflict with the schedule from the old host being replaced, this must be checked in all occasions.
NOTE For using --replace-host against currently-running assignments shorten the schedule, do not remove it - that way we have the record on books for partial usage of the system before it was swapped.
There are two scenarios here that come to mind:
1A) Replacing a host with another host in a currently-running cloud, confirm
Check the schedule entered on oldhost for the first future occurence of it being in cloud02, and replicate this to anotehr host to swap it, checking availability
The text was updated successfully, but these errors were encountered:
sadsfae
changed the title
(RFE) Add --replace-host functionality to replace host schedule with another host within an assignment
(RFE) Add --replace-host functionality
Nov 10, 2020
This is an RFE to provide a command-set to replace one running host's current (or future, specific cloud) schedule with a replacement host. The real-world usage of this would occur if hardware issues or supplanting one model with a more preferred model in an active or future assignment would occur.
Due to the potentially disruptive nature of this command if it were typo'd or used incorrectly we should consider confirmation if we are operating on a currently-running cloud.
NOTE The replacement host must not conflict with the schedule from the old host being replaced, this must be checked in all occasions.
NOTE For using
--replace-host
against currently-running assignments shorten the schedule, do not remove it - that way we have the record on books for partial usage of the system before it was swapped.There are two scenarios here that come to mind:
1A) Replacing a host with another host in a currently-running cloud, confirm
1B) Replacing a host with another host in a currently-running cloud, no confirmation via --force
2A) Replace host in the next occurring future cloud assignment specified
The text was updated successfully, but these errors were encountered: