Jump to: navigation, search

Difference between revisions of "Large Deployment Team"

Line 3: Line 3:
 
'''Organisers''': Matt Van Winkle <mvanwink@rackspace.com>
 
'''Organisers''': Matt Van Winkle <mvanwink@rackspace.com>
  
'''Page is a work in progress'''
 
  
As the first paragraph, give a clear statement on the purpose of your working group, including specific, detailed outcomes.
 
  
 
==Scope==
 
==Scope==
Line 11: Line 9:
  
 
==How to Join==
 
==How to Join==
Give some simple instructions on how a prospective new member could join the activity.
+
# Sign up to the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators openstack-operators] mailing list and look for posts with "[Large deployments]" in the subject
 +
# Email Matt Van Winkle <mvanwink@rackspace.com> to get patched in
  
 
==Structure==
 
==Structure==
Is your group a single group, or are there multiple groups? Is it time based with multiple phases?
+
* Mailing List:  [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators openstack-operators] mailing list with "[Large deployments]" in the subject line
 
+
* Regular Monthly meetings announced on the mailing list, in addition to sessions at the mid-cycle ops meetup and design summit
 
+
** Minutes from Monthly Meetings: https://etherpad.openstack.org/p/Large-Deployment-Team-Meetings
For each part of your structure, ensure you list organisers and the main participants.
+
** Results from Philadelphia Ops Meetup https://etherpad.openstack.org/p/PHL-ops-large-deployments
 +
** Results from Paris Summit https://etherpad.openstack.org/p/kilo-summit-ops-large-deployments

Revision as of 13:24, 29 March 2015

Status: Active

Organisers: Matt Van Winkle <mvanwink@rackspace.com>


Scope

Specify which items are in and out of scope for this working group. It it important to avoid overlap and duplication of efforts with other working groups.

How to Join

  1. Sign up to the openstack-operators mailing list and look for posts with "[Large deployments]" in the subject
  2. Email Matt Van Winkle <mvanwink@rackspace.com> to get patched in

Structure