As the number of production OpenStack deployments increase and more ecosystem partners add support for OpenStack clouds, it becomes increasingly important that the communities building services around OpenStack guide and influence the product evolution. The user committee's role is to represent the needs of the diverse range of OpenStack users.
The user committee mission is to:
- Consolidate user requirements and present these to the management board and technical committee
- Provide guidance for the development teams where user feedback is requested
- Track OpenStack deployments and usage, helping to share user stories and experiences
- Work with the user groups worldwide to keep the OpenStack community vibrant and informed
How to Engage?
The committee co-ordinates via the user-commitee mailing list - feel free to join and post your ideas.
Consider looking at the working groups and teams below and joining their activities.
If you are interested in volunteering to help with User Committee efforts, please complete this form.
Planning for Austin:
The User Committee will have a session during the Austin Summit. We are using this etherpad to plan our agenda. Please add your proposals to it!
Attend our fortnightly IRC meetings, alternating between times convenient for US and APAC attendees:
Next US meeting: Monday, March 14th, 2016 at 1900 UTC in (freenode) #openstack-meeting Next APAC meeting: Wednesday, March 8th, 2016 at 0300 UTC in (freenode) #openstack-meeting Proposed Agenda: * Next steps for Survey analysis - Let's review where we are * Operators recognition next steps * Discuss where we want to take the UC and what we can change
Logs from past meetings: * http://eavesdrop.openstack.org/meetings/user_committee/2015/ * http://eavesdrop.openstack.org/meetings/uc/2016/ Subscribe to the Mailing List Mailing List Archives
The structure of the user committee is currently being defined. Jon Proulx, Subbu Allamaraju and Shilla Saebi have been nominated by the management board and technical committee to work with the community. This process is ongoing and your assistance is welcome - consider the following:
- initial structure ideas document for review.
- more recent ideas Scaling out the User Committee
- Ideas from Vancouver: https://etherpad.openstack.org/p/uc-2015
and post your thoughts on the user-committee mailing list.
Working Groups and Teams
The user committee is currently looking at a structure that involves working groups to conduct specific packages of tasks. The Working Groups have a defined purpose and goal, and produce work to meet their stated aims. Working Groups will have their own leadership, which will be responsible for finding volunteers in the community to complete the work. Working Groups should be allowed to form naturally and easily where a need arises, without unnecessary bureaucratic burden. However, some controls should be enacted to ensure effort is best placed, and not duplicated, so please consider the procedure below:
|Group/Team||Status||Organisers||WG Tag||Expected Outcomes|
|Telco||Meetings subsumed into Product Working Group and OpenNFV collaboration||Steve Gordon||#Telco-WG||Define the use cases and identify and prioritise the requirements which are needed to deploy, manage, and run telecommunication services on top of OpenStack.|
|Enterprise Working Group||Active||Carol Barrett <firstname.lastname@example.org>||#Enterprise-WG||Action plans to solve Enterprise Private Cloud needs and issues.|
|Application Ecosystem Working Group||Active||John Callaghan, David Flanders||#AppEco-WG||To create an environment where a diverse array of applications built for OpenStack can thrive.|
|API Working Group||Active||Jay Pipes, Everett Toews||#API-WG||To propose, discuss, review, and advocate for API guidelines for all OpenStack Programs to follow.|
|Fault Genes Working Group #FaultGenes-WG||Active||Nemat Bidokhti||#Fault-WG||To create a failure mode taxonomy for Operators and Application Developers. To understand the DNA of failure in OpenStack.|
|Large Deployment Team||Active||Matt Van Winkle||#Deploy-WG||To discuss the needs and issues of those running large OpenStack deployments|
|Log Rationalisation||Active||Rochelle Grober, Jay Pipes||#Log-WG|
|Non-ATC Recognition||Active||Shamail Tahir, Maish Saidel-Keesing||#Recognition-WG||To assist the User Committee with defining its constituency|
|Ops Meetups Team||Active||Tom Fifield||#OpsMeet-WG||An open team for those who are passionate about ops meetups to discuss and create the next successful events.|
|Osops (formerly Ops Tools)||Active||Joseph Bajin||#Monitor-WG||To discover and detail best practices in ops monitoring and tools, and facilitate tool sharing|
|Packaging||Sporadic Activity||None yet||Package-WG||To be determined|
|Product Working Group||Active||Carol Barrett, Shamail Tahir||#Product-WG||To aggregate user stories from market-oriented work groups, partner with the development community on resources, and help gather data to generate a multi-release roadmap.|
|Ops Tags Team||Active||Tom Fifield, Subbu Allamaraju, Jon Proulx, Shilla Saebi||#OpsTags-WG||A team to define tags for ops, allowing users to make better decisions by providing useful information about OpenStack software projects.|
|User Survey Team||Active||Tom Fifield, Subbu Allamaraju, Jon Proulx, Shilla Saebi, Lauren Sell, Heidi Joy Tretheway||#UserSurvey-WG||The traditional group of people (user committee+foundation staff) who run the user survey.|
|Upgrades Working Group||Sporadic Activity||TBC||#Upgrade-WG||To ease the pain of OpenStack upgrades.|
|scientific working group||Active||Stig Telfer & Blair Blethwaite||#Scientific-WG||see wiki page|