Notification and Central Agent using centrally stored pipeline
The Notification Agent and Central Agent will now optionally using the centrally stored pipeline.yaml as part of the configuration as data store effort.
The Agent will check the existence of a valid pipeline in the DB and if that is available will use it, otherwise will push the one available in the default location or passed as parameter to the agent.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Fabio Giannetti
- Direction:
- Approved
- Assignee:
- Fabio Giannetti
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Blocked
- Milestone target:
- None
- Started by
- gordon chung
- Completed by
- gordon chung
Related branches
Related bugs
Sprints
Whiteboard
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
changing to not started as the bp isn't merge... and i think there's implementation details regarding this that need to be discussed. see https:/
-- gordc [10.03.15]
Punting to Liberty as agreed -- eglynn [12.03.15]
using just file based approached for now -- gordc 17.06.2015
abandoning, this should target oslo or openstack-specs -- gord (10.07.15)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
