Jump to: navigation, search

LCOO

Revision as of 10:04, 16 March 2017 by Au3678 (talk | contribs) (Large Contributing OpenStack Operators (LCOO))

Large Contributing OpenStack Operators (LCOO)

Status: Regular Meetings and joint work in progress since August 2016. Introduced as Working Group to the User Committee at Barcelona Summit October 26, 2016. We meet as a coordination team at least twice monthly and run "deep dive/topical" sessions in between.

Co-Chairs:

 * Sundar Krishnamoorthy <sundar.krishnamoorthy@intel.com>
 * Jamey McCabe <jamemcc@gmail.com>

Roadmap Co-Chairs:

 * Andy Ukasick <andrew.ukasick@att.com>
 * Aditya Mani <aditya.mani@ril.com>

Organization Coordinators:

 * Abdelhadi Chari, Orange; <abdelhadi.chari@orange.com>
 * Andy Ukasick, AT&T; <andrew.ukasick@att.com>
 * Aditya Mani; Reliance Jio; <aditya.mani@ril.com>
 * Jaesuk Ahn; SK Telecom; <jay.ahn@sk.com>
 * Kunal Shah;  Reliance Jio; <kunal2.shah@ril.com>
 * Megan Rossetti; Walmart; <rossetti.megan18@gmail.com>
 * Shintaro Mizuno; NTT; <mizuno.shintaro@lab.ntt.co.jp>
 * Shilla Saebi; Comcast; <shilla.saebi@gmail.com>
 * Sundar Krishnamoorthy; Intel; <sundar.krishnamoorthy@intel.com>

Communications - Etherpads and Links: We run meetings via video-conference but also track all participants, proposals and agreements:

* https://etherpad.openstack.org/p/Large_Contributing_OpenStack_Operators_Master
* https://openstack-lcoo.atlassian.net/wiki/display/LCOO/The+Large+Contributing+OpenStack+Operators+%28LCOO%29+Working+Group

Mission and Scope

The Large Contributing OpenStack Operator (LCOO) is a body of OpenStack Community Contributors who have organized around their shared interest in accelerating the enterprise maturity and adoption of OpenStack and to drive Community awareness of platform enhancements necessary to address the unique use cases of network service providers and horizontally scaling, massively distributed cloud operators.

The working group aims to collaborate with the Product Working Group (PWG), other working groups and community-wide stakeholders to define the use cases and identify and prioritize the requirements which are needed to deploy, manage, and run services on top of OpenStack. This work includes identifying functional gaps, creating blueprints, submitting and reviewing patches to the relevant OpenStack projects, contributing to working on those items, tracking their completion. The LCOO will partner with the PWG, following their User Story Workflow in order to accomplish this.

Key Tenets

Drive Community Roadmap Awareness

The LCOO exists to drive Community awareness of platform enhancements necessary to meet the needs of Large “Multi-Clouds” Operators and Network Service Providers. Multi-Clouds is defined as multiple regions, availability zones and multi-tenant in OpenStack. LCOO does this through the publishing of its use cases and Roadmap as well as by participating in and contributing thought leadership to OpenStack community Working Groups, Project Teams and other OpenStack groups. The LCOO also leverages blogs, white papers, Summit presentations, Summit presence and any other practical means to carry its message to the broad community.

Drive Focused OpenStack Enhancements

The LCOO works openly, transparently and collaboratively within the OpenStack community to be engaged in continuous enhancement of the OpenStack platform. The LCOO’s coordinates the upstream software development activities of its member’s resources in order to advance the platform while ensuring that efforts align with the spirit and goals of the OpenStack Foundation.

Increase Upstream Contributions to OpenStack

The LCOO seeks to advance the OpenStack platform by building and growing a joint LCOO committed engineering team focused on a shared agenda of development that drives its overall mission forward, along a number of vectors:

  • Multisite Management and Operations including Upgradeability
  • Resiliency at Scale
  • Networking, SDN and NFV Infrastructure
  • Security, Policy and Operational Insights
  • Workload Enablement
  • Feature Requests and Bug fixes across all of the projects


Accelerate OpenStack Innovation

Through its multi-cultural, globally distributed and technologically diverse member companies, the LCOO creates an environment for its members that promotes far greater opportunity for innovation, learning, mentoring and accomplishment than would ever be possible by any member alone. This same large and diverse member coalition of community contributors is also able to engage much more deeply, broadly and effectively within the community in order to further its objectives of raising awareness and accelerating improvement.

Guiding Principles

Align with the OpenStack Foundation

The LCOO is dedicated to advancing the goals of the OpenStack community by aligning with the OpenStack Foundation using a two-pronged approach, both through centralized authorities and through grassroots engagement.

Working within established centralized channels, the LCOO informs, publishes, and solicits feedback on its engineering roadmap through the OpenStack Foundation’s Working Groups. This approach ensures that the engineering team works on the right features to advance the OpenStack platform for use by enterprise customers, as validated by the community. The LCOO engages with the OpenStack Foundation Board, Technical Committee and User Committee to draw attention to help drive coordination across projects. Finally, the LCOO also works with certain groups outside of OpenStack such as OPNFV whose work has critical impacts on the platform.From a grassroots standpoint, the LCOO member resources are engaged within numerous projects, organizations and user groups, collaborating, networking and discussing across the OpenStack Community.

Contribute Work Upstream

In the true spirit of open source, the LCOO is committed to furthering open standards and preventing vendor lock-in by ensuring that work is contributed upstream, working within the community to advance the collective state of the platform for the benefit of all.

How to Join

Member companies should meet these criteria:

  • Be a Multi-Cloud Operator and/or Network Service Provider
  • Participate equally with other members in the meetings and other activities of the coalition
  • Be a contributor to the OpenStack platform with at least 4 FTEs contributing regularly
  • Contribute 2 FTEs to upstream activities aligned to the LCOO roadmap

If a member should fail to continue to meet these minimum criteria after joining, their membership may be revoked through an action of the board.

Method of joining:

  1. 1. Contact or be contacted by an existing member and familiarize yourself with this charter and our current roadmap/goals.
  2. 2. Attend coordinators meeting and introduce your organization’s current OpenStack contributions and your ideas for how to contribute to the LCOO roadmap.
  3. 3. Be welcomed and begin to integrate your specific staff into the current LCOO activities in that Governance meeting.
  4. 4. Be added to LCOO communication tools, e.g. Slack, E-mail/invite distribution and roadmap tracking.

Governance

The LCOO is governed by a board consisting of equal representation from each of its member companies. The board will be led by an annually elected Meeting Chair and Co-Chair(s) from among its members. Each member company will have one vote. The board will operate by consensus. This composition underscores the LCOO’s true community spirit, ensuring a system of governance that relies on respect, equality, trust and transparency. In the event that consensus cannot be reached, the Chairperson may call for a vote.

The LCOO Governance Board:

  • Meets quarterly to produce, prioritize and publish a common OpenStack Roadmap
  • Meets quarterly to formulate Strategy for Roadmap delivery
  • Collaborates to drive Community awareness and acceptance of its Roadmap objectives
  • Directs member resources to upstream activities in alignment with its Roadmap and Strategy
  • Coordinates member participation in Working Groups
  • Coordinates engagement with the OpenStack Foundation Board, Technical Committee and User Committee
  • Meets at a minimum monthly to re-align on Strategy execution, review progress and (re)direct activities as needed
  • Meeting agenda’s published ahead of time for board meetings and meeting results published and open for all (members and non-members) to view.