Multi-region Implementation
You may want to manage multiple regions using one management node. Each region will have essentially its own /etc/kolla config. So it would be nice to support a config flag to specify where /etc/kolla is for alternates. like /etc/kolla/region1, /etc/kolla/region2, /etc/kolla/
Blueprint information
- Status:
- Complete
- Approver:
- Jeffrey Zhang
- Priority:
- Undefined
- Drafter:
- Kevin Fox
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Radosław Piliszek
Related branches
Related bugs
Sprints
Whiteboard
I am for this, but this blueprint needs an assignee to be approved. --SamYaple
I think we need a little more R before the D on this one. Can we discuss how multi-region is supposed to be configured? I would consider taking this on in mitaka-2 possibly - I think multiregion would be cool, but I don't know precisely what it entails. --sdake
Basically its multiple seperate clouds, each setting region name to something different in each region, and sharing a keystone. The keystone may be read only to the region admin wise, so maybe we have the ansible scripts spit out the cli commands for setting up the service users if thats the case so the keystone admins can preregister them? - kfox1111
what's the status of this bp, seem patch is merged. is this implemented? (jeffrey4l, 06-15)