Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-plugins fusiondirectory-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 63
    • Issues 63
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Wiki
  • deployment features

deployment features · Changes

Page history
Update deployment features authored Sep 20, 2017 by MCMic's avatar MCMic
Hide whitespace changes
Inline Side-by-side
deployment-features.md
View page @ 71df98af
...@@ -20,15 +20,16 @@ For instance if boundaries are 8PM -> 10PM ...@@ -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. 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. 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 * ping
* System.halt * System.halt
* System.reboot * System.reboot
* Deployment.reboot * **Deployment.reboot**
* Deployment.reinstall * **Deployment.reinstall**
* Deployment.update * **Deployment.update**
* Deployment.wake * **Deployment.wake**
* OPSI.update_or_insert * OPSI.update_or_insert
* OPSI.delete * OPSI.delete
* OPSI.host_getObjects * OPSI.host_getObjects
...@@ -36,8 +37,6 @@ Existing actions are: ...@@ -36,8 +37,6 @@ Existing actions are:
* OPSI.get_localboots * OPSI.get_localboots
* OPSI.get_product_properties * OPSI.get_product_properties
I think the forbidden actions should be Deployment.\*, but maybe System.\* as well?
#### Changes #### 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. 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.
......
Clone repository
  • FusiondirectoryIPAM
  • LSC
  • LdapAlias
  • Modifying group member types
  • RestWebservice
    • addUpdateUser
    • addUpdateUserMultivaluated
    • createUser
    • deleteUser
  • SupannSupport
  • UserReminder
  • deployment features
  • fd lsc backend
  • fd lsc zimbra
  • filters acl
View All Pages