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 563
    • Issues 563
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 69
    • Merge requests 69
  • 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
  • #512
Closed
Open
Issue created Feb 28, 2019 by Francis Dupont@fdupontDeveloper

remote-network4-del update

You asked me what the code should do with the subnets when the shared network is being deleted. I updated the CB design doc: https://gitlab.isc.org/isc-projects/kea/wikis/designs/configuration-in-db-design#remote-network4-del

with two variants that differ by "subnets-action" parameter. We need to add support for this parameter to explicitly control whether the subnets are kept or deleted. This idea is derived from the subnets_cmds hook and I believe that's the best option here too.

Note that the variant that removes a shared network but keeps subnets requires to update shared_network_name column for all these subnets to null. Perhaps the easiest way to do it via an SQL trigger.

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