Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #9082] Runtime configuration for the API #2912

Closed
icinga-migration opened this issue Apr 17, 2015 · 5 comments
Closed

[dev.icinga.com #9082] Runtime configuration for the API #2912

icinga-migration opened this issue Apr 17, 2015 · 5 comments

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Apr 17, 2015

This issue has been migrated from Redmine: https://dev.icinga.com/issues/9082

Created by gbeutner on 2015-04-17 12:30:01 +00:00

Assignee: (none)
Status: Closed (closed on 2015-09-23 16:17:05 +00:00)
Target Version: 2.4.0
Last Update: 2015-09-24 20:08:50 +00:00 (in Redmine)

Backport?: No
Include in Changelog: 1

  • Support for creating, removing single objects (no transactions)
  • Allow cascading removes (i.e. removing an object and all other objects which depend on this object, e.g. all services/notifications/… when removing a host)
  • Dependency tracking: Trying to remove an object must either fail (when cascading removes are not used) or cause all of their dependant objects to be removed as well)
  • All existing modules must be updated to support creating and removing objects at runtime (IDO, checker, …)
  • Optional: Update the objects.cache file
  • Configuration changes are persistent
  • Dynamic configuration changes are persisted using the Icinga 2 configuration format
    • Object definitions
    • Function calls for the attribute change log
  • Dynamic configuration API must be aware of zones
  • Dynamic configuration changes must be synced to other Icinga 2 instances
    • The instance which has an authoritative copy of the zone's config is responsible for persisting the configuration for dynamically configured objects
  • Automatically generated configuration files end up in /var/lib/…

Changesets

2015-08-18 06:22:14 +00:00 by (unknown) 60a30d5

Don't allow users to delete objects that weren't created using the API

refs #9082

2015-08-18 14:53:30 +00:00 by (unknown) 71dc682

Implement support for "." in attributes when creating objects

refs #9082

2015-08-18 17:39:10 +00:00 by (unknown) da7d045

Add missing attributes for dependent objects

refs #9082

2015-08-18 18:25:06 +00:00 by (unknown) b3db2ee

Fix crash in ConfigObjectUtility::CreateObject

refs #9082

Subtasks:

Relations:

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented May 19, 2015

Updated by mfriedrich on 2015-05-19 08:21:51 +00:00

  • Blocked set to 9077
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jul 30, 2015

Updated by gbeutner on 2015-07-30 06:05:18 +00:00

  • Blocks set to 9777
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jul 30, 2015

Updated by mfriedrich on 2015-07-30 17:08:12 +00:00

Idea from a discussion this week: When adding a new object being located in a specific zone, we'll need to ensure that it gets put somewhere the cluster config sync also reads from (e.g. by registering a new directory for this zone being already implemented).

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Sep 23, 2015

Updated by mfriedrich on 2015-09-23 16:17:05 +00:00

  • Status changed from New to Closed

The remaining tasks are tracked inside the modified attributes issues. I'm therefore closing the parent task for these issues being resolved.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Sep 24, 2015

Updated by mfriedrich on 2015-09-24 20:08:50 +00:00

  • Backport? changed from TBD to No
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.