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.
The structure of the user committee is currently being defined. Tim Bell, Jon Proulx and Subbu Allamaraju have been nominated by the management board and technical committee to work with the community and determine the by-laws and scope. 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:
|Telco||Active||Steve Gordon||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>||Action plans to solve Enterprise Private Cloud needs and issues.|
|Application Ecosystem Working Group||Active||Bill Franklin, Tom Fifield||To create an environment where a diverse array of applications built for OpenStack can thrive.|
|API Working Group||Active||Jay Pipes, Christopher Yeoh, Everett Toews||To propose, discuss, review, and advocate for API guidelines for all OpenStack Programs to follow.|
|Large Deployment Team||Active||Matt Van Winkle||To discuss the needs and issues of those running large OpenStack deployments|
|Log Rationalisation||Active||Rochelle Grober, Jay Pipes|
|Ops Tools||Sporadic Activity||Debbo Dutta, Joe Topjian||To discover and detail best practices in ops monitoring and tools, and facilitate tool sharing|
|Packaging||Sporadic Activity||None yet||To be determined|
|Product Working Group||Active||Carol Barrett||To listen and aggregate feedback on the desired capabilities for the OpenStack platform|
|Ops Tags Team||Active||Tom Fifield, Tim Bell, Subbu Allamaraju, Jon Proulx||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, Tim Bell, Subbu Allamaraju, Jon Proulx, Lauren Sell||The traditional group of people (user committee+foundation staff) who run the user survey.|
|HPC/HTC Working Group||Sporadic Activity||Tim Bell||To gather and promote OpenStack use cases and best practices in an HPC/HTC environment.|
|Upgrades Working Group||Sporadic Activity||TBC||To ease the pain of OpenStack upgrades.|