Difference between revisions of "Kosmos"
Graham Hayes (talk | contribs) |
|||
| Line 7: | Line 7: | ||
== Overview == | == Overview == | ||
| − | Kosmos is a new project, formed initially from members of Designate and | + | Kosmos is a new project, formed initially from members of Designate and Octavia, to provide global server load-balancing for OpenStack clouds. |
This is separate from both LBaaS and Designate, but heavily leverages both. | This is separate from both LBaaS and Designate, but heavily leverages both. | ||
| Line 13: | Line 13: | ||
Our long term aim is to create a global service (like Designate / Keystone) that allows cloud users to balance their traffic across multiple regions, or multiple cloud providers. | Our long term aim is to create a global service (like Designate / Keystone) that allows cloud users to balance their traffic across multiple regions, or multiple cloud providers. | ||
| − | Both | + | Both Octavia and Designate will be first class citizens - the default install for Kosmos will use both, but we are adopting a plugin architecture that allows for different integrations, while maintaining a consistent API. |
A standard setup may look like this: | A standard setup may look like this: | ||
| − | Customer Applications running behind | + | Customer Applications running behind Octavia in multiple regions. |
Kosmos will constantly monitor these endpoints, and the LBaaS Status API, and update DNS records in Designate to move traffic between the endpoints. | Kosmos will constantly monitor these endpoints, and the LBaaS Status API, and update DNS records in Designate to move traffic between the endpoints. | ||
| Line 28: | Line 28: | ||
|- | |- | ||
| IRC | | IRC | ||
| − | | #openstack- | + | | #openstack-lbaas on OFTC |
|- | |- | ||
| Milestones | | Milestones | ||
Revision as of 15:57, 20 February 2024
Kosmos will provide self-service global server load-balancing for OpenStack clouds.
Overview
Kosmos is a new project, formed initially from members of Designate and Octavia, to provide global server load-balancing for OpenStack clouds.
This is separate from both LBaaS and Designate, but heavily leverages both.
Our long term aim is to create a global service (like Designate / Keystone) that allows cloud users to balance their traffic across multiple regions, or multiple cloud providers.
Both Octavia and Designate will be first class citizens - the default install for Kosmos will use both, but we are adopting a plugin architecture that allows for different integrations, while maintaining a consistent API.
A standard setup may look like this:
Customer Applications running behind Octavia in multiple regions.
Kosmos will constantly monitor these endpoints, and the LBaaS Status API, and update DNS records in Designate to move traffic between the endpoints.
Resources
| Meetings | Meetings/Kosmos |
| IRC | #openstack-lbaas on OFTC |
| Milestones | https://launchpad.net/kosmos/+milestones |
| Mailing List | OpenStack dev list, prefix with [kosmos] or [gslb] |
| Bug tracker | https://bugs.launchpad.net/kosmos |
| Blueprints | [1] |
