Difference between revisions of "ProductTeam/User Stories/HA VMs"
< ProductTeam | User Stories
Adam Spiers (talk | contribs) (→User Story Overview: it's the whole user story, not an overview) |
Adam Spiers (talk | contribs) (→High Availability for VMs: add more detail about recent work) |
||
Line 1: | Line 1: | ||
== High Availability for VMs == | == High Availability for VMs == | ||
− | + | ||
− | ==== [http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html | + | === User story === |
+ | |||
+ | The [http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html official user story] explains the high-level motivation and requirements for this feature. | ||
+ | |||
+ | === History === | ||
+ | |||
+ | Initially, various factions within the OpenStack community built solutions mostly independently from each other. The architectural challenges and several of these solutions were presented in [https://www.openstack.org/videos/video/high-availability-for-pets-and-hypervisors-state-of-the-nation a talk at the Austin summit]. However, around the time of the [[Mitaka Release Schedule|Mitaka]] Design Summit in Tokyo, an OpenStack HA community was formed with [[Meetings/HATeamMeeting|weekly IRC meetings]]. Since then, the community has been working towards converging on a single solution. In Austin, many long meetings were held, and minuted in [http://etherpad.openstack.org/p/newton-instance-ha this etherpad]. | ||
+ | |||
+ | === Current work === | ||
+ | |||
+ | In Austin the following key points were agreed: | ||
+ | |||
+ | * All stakeholders wanted to converge on a unified upstream solution. | ||
+ | * That solution should consist of modular components with clearly-defined interfaces. This will give a clean separation of concerns, and facilitate gradual transition of all existing vendor-specific implementations to a unified upstream one, by incrementally replacing custom code with upstream components. | ||
+ | ** These modular components are described in [http://etherpad.openstack.org/p/newton-instance-ha this etherpad]. | ||
+ | * Specs should be written for each component, to ensure consensus on the feature sets and high-level implementation plan. | ||
+ | |||
+ | This work has started, but is still in its early stages. | ||
=== Meeting Information === | === Meeting Information === |
Revision as of 23:20, 5 September 2016
Contents
High Availability for VMs
User story
The official user story explains the high-level motivation and requirements for this feature.
History
Initially, various factions within the OpenStack community built solutions mostly independently from each other. The architectural challenges and several of these solutions were presented in a talk at the Austin summit. However, around the time of the Mitaka Design Summit in Tokyo, an OpenStack HA community was formed with weekly IRC meetings. Since then, the community has been working towards converging on a single solution. In Austin, many long meetings were held, and minuted in this etherpad.
Current work
In Austin the following key points were agreed:
- All stakeholders wanted to converge on a unified upstream solution.
- That solution should consist of modular components with clearly-defined interfaces. This will give a clean separation of concerns, and facilitate gradual transition of all existing vendor-specific implementations to a unified upstream one, by incrementally replacing custom code with upstream components.
- These modular components are described in this etherpad.
- Specs should be written for each component, to ensure consensus on the feature sets and high-level implementation plan.
This work has started, but is still in its early stages.
Meeting Information
Team Members
Name | Company | IRC Handle |
---|---|---|
Pete Chadwick (user story owner within PWG) | SUSE | pchadwick |
Adam Spiers | SUSE | aspiers |
Andrew Beekhof | Red Hat | beekhof |
Dawid Deja | Intel | ddeja |
Sampath Priyankara | NTT | samP |
Additional Artifacts
- https://etherpad.openstack.org/p/newton-instance-ha contains design work started in Austin
- Minutes of all HA meetings
- https://etherpad.openstack.org/p/automatic-evacuation summarises all known existing approaches
- Subscribe to the PWG Mailing List
- PWG Mailing List Archives