Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 555
    • Issues 555
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 66
    • Merge requests 66
  • 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
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #905
Closed
Open
Issue created Sep 10, 2019 by Alan Clegg@knobeeContributor

Add ability to do a CB update at a specified time

With the current configuration backend model using config-fetch-wait-time, it is difficult if not impossible to synchronize changes across multiple servers, or to do "timed" deployments of changes.

I recommend the implementation of time-based config updates:

{
  "command": "remote-server-update-at",
  "arguments": {
    "server-tags": [ "headquarters" ]
    "reconfig-at": [
      { "time": "<timespec>",
        "date": "<datespec>"
      }
    ],

  "service": [ "dhcp4" ]
}

The provided JSON is probably illegal/syntactically incorrect. It is provided to give an idea of what's rattling around in my brain.

Third (and last!) issue created from #846 (closed)

Edited Sep 10, 2019 by Alan Clegg
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking