Difference between revisions of "Kosmos"
Graham Hayes (talk | contribs) |
Graham Hayes (talk | contribs) |
||
| Line 4: | Line 4: | ||
* [https://github.com/openstack/kosmos-specs Approved Specs] | * [https://github.com/openstack/kosmos-specs Approved Specs] | ||
* [https://launchpad.net/kosmos Launchpad] | * [https://launchpad.net/kosmos Launchpad] | ||
| + | |||
| + | == Overview == | ||
| + | |||
| + | Kosmos is a new project, formed initially from members of Designate and Neutron Lbaas, 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 Neutron LBaaS 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 Neutron LB 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 == | == Resources == | ||
Revision as of 17:02, 15 September 2015
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 Neutron Lbaas, 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 Neutron LBaaS 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 Neutron LB 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-gslb on Freenode |
| 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] |
