Allow devstack to be modular and independent of each others.
This is a followup from a discussion Jesse and Chmouel had on https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Dean Troyer
- Completed by
- Dean Troyer
Related branches
Related bugs
Sprints
Whiteboard
A use case :
I am thinking to remove the swift-remakerings and swift-startmain and put them directly in stack.sh
Adding them directly to devstack would make it a big bigger and at certain time and it probably get bigger and bigger in the future (which would make harder to read for the sysadmin.
So what do you think if I move all the swift code to :
services.d/swift.sh
where we can source all of swift things from there.
[dtroyer]
I've prototyped a breakdown of stack.sh by service, creating a set of functions for each service that configure, initialize, start, stop, etc. This lets us segregate the details of each service into one place. All of the dependency logic remains in stack.sh so it is in one place; it should be more readable after factoring out the details of each service.
https:/
[dtroyer]
cinder, ceilometer and heat have all been added to devstack in this format.
https:/
[dtroyer]
https:/
https:/
https:/
Remaining:
* quantum
* swift
