Jump to: navigation, search

Difference between revisions of "ProductTeam/User Stories/HA VMs"

(→‎History: add history of user story)
m (put other links inline and swap section order)
Line 4: Line 4:
  
 
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.
 
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.
 +
 +
=== 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.
  
 
=== History ===
 
=== History ===
Line 16: Line 27:
  
  
−
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].
+
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]] ([http://eavesdrop.openstack.org/meetings/ha/ minutes of all HA meetings are available]). [https://etherpad.openstack.org/p/automatic-evacuation All known existing approaches were summarised and compared], and discussion on a best-of-breed solution commenced.
 +
 
 +
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].
  
 
Concurrently, the [https://wiki.openstack.org/wiki/ProductTeam OpenStack Product Working Group (PWG)] identified this feature as missing functionality in OpenStack which should be addressed with high priority.  As a result the user story was co-authored by the PWG and members of the OpenStack HA developer community.
 
Concurrently, the [https://wiki.openstack.org/wiki/ProductTeam OpenStack Product Working Group (PWG)] identified this feature as missing functionality in OpenStack which should be addressed with high priority.  As a result the user story was co-authored by the PWG and members of the OpenStack HA developer community.
−
 
−
=== 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 ===
Line 50: Line 52:
 
|}
 
|}
  
−
=== Additional Artifacts ===
+
=== Additional Artefacts ===
  
−
* https://etherpad.openstack.org/p/newton-instance-ha contains design work started in Austin
 
−
* [http://eavesdrop.openstack.org/meetings/ha/ Minutes of all HA meetings]
 
−
* https://etherpad.openstack.org/p/automatic-evacuation summarises all known existing approaches
 
 
* [http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg Subscribe to the PWG Mailing List]
 
* [http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg Subscribe to the PWG Mailing List]
 
* [http://lists.openstack.org/pipermail/product-wg/ PWG Mailing List Archives]
 
* [http://lists.openstack.org/pipermail/product-wg/ PWG Mailing List Archives]

Revision as of 23:41, 5 September 2016

High Availability for VMs

User story

The official user story explains the high-level motivation and requirements for this feature.

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.
  • 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.

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.

The code for three of these solutions can be found on github:


However, around the time of the Mitaka Design Summit in Tokyo, an OpenStack HA community was formed with weekly IRC meetings (minutes of all HA meetings are available). All known existing approaches were summarised and compared, and discussion on a best-of-breed solution commenced.

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.

Concurrently, the OpenStack Product Working Group (PWG) identified this feature as missing functionality in OpenStack which should be addressed with high priority. As a result the user story was co-authored by the PWG and members of the OpenStack HA developer community.

Meeting Information

See Meetings/HATeamMeeting

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 Artefacts

Retrieved from "https://wiki.openstack.org/w/index.php?title=ProductTeam/User_Stories/HA_VMs&oldid=132524"