Skip to content

GitLab

  • Menu
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 501
    • Issues 501
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 53
    • Merge requests 53
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #394

Closed
Open
Created Jan 14, 2019 by Marcin Siodelski@marcinDeveloper

Recalculate statistics when server configuration is changed as a result of a command

While reviewing !197 (merged) we found a general issue that statistics needs to be recalculated when incremental changes are applied to the configuration. The specific case discussed in !197 (merged) was that when new subnet is added to the database and the server detects this change, it will fetch the subnet data and merge the subnet into the configuration it is currently running. Because, it bypasses the staging/commit phase, the statistics is not recalculated.

We also checked that subnet_cmds doesn't deal with this problem either. We may need to find some generic solution for it.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking