| ... | ... | @@ -20,15 +20,16 @@ For instance if boundaries are 8PM -> 10PM |
|
|
|
This should be checked by both FusionDirectory at the time of scheduling and Argonaut Server at the time of deploying.
|
|
|
|
|
|
|
|
We need to establish which actions would be forbidden outside of the time frame.
|
|
|
|
Existing actions are:
|
|
|
|
|
|
|
|
The forbidden Argonaut actions are in bold:
|
|
|
|
|
|
|
|
* ping
|
|
|
|
* System.halt
|
|
|
|
* System.reboot
|
|
|
|
* Deployment.reboot
|
|
|
|
* Deployment.reinstall
|
|
|
|
* Deployment.update
|
|
|
|
* Deployment.wake
|
|
|
|
* **Deployment.reboot**
|
|
|
|
* **Deployment.reinstall**
|
|
|
|
* **Deployment.update**
|
|
|
|
* **Deployment.wake**
|
|
|
|
* OPSI.update_or_insert
|
|
|
|
* OPSI.delete
|
|
|
|
* OPSI.host_getObjects
|
| ... | ... | @@ -36,8 +37,6 @@ Existing actions are: |
|
|
|
* OPSI.get_localboots
|
|
|
|
* OPSI.get_product_properties
|
|
|
|
|
|
|
|
I think the forbidden actions should be Deployment.\*, but maybe System.\* as well?
|
|
|
|
|
|
|
|
#### Changes
|
|
|
|
|
|
|
|
This means a new generic deployment tab will be needed on systems to store this information (along with an LDAP schema). This tab should be dynamically available in groups of systems and should be inherited.
|
| ... | ... | |
