Ops-telecom-nfv

OpenStack Operators Telecom/NFV Functional Team

Status: Active

Organizers:

Curtis Collicutt <curtis@serverascode.com>
Your name here?

Mission Statement

The OpenStack Operators Telecom and NFV Team will work with the OpenStack community and ecosystem to benefit operators specifically running telecommunication services and Network Function Virtualization (NFV) systems utilizing OpenStack.

To achieve this, with each release the group identifies requirements most commonly raised by the telecommunications and NFV operator community and ensures action is being taken to address the requirements in an appropriate way, including, but not limited to, liaising with developers, raising and highlighting bug reports, and generating reports or documentation. As well, in situations when a larger requirement is identified, occasionally the team will develop a mid to long term plan to shepherd said requirement through the OpenStack community.

For each release the Working Group will produce a record of issues identified, what is being done to resolve them and an expected timeline.

How to Join

Sign up to the openstack-operators mailing list and look for posts with "[telecom-nfv]" in the subject
Attend bi-weekly meetings: http://eavesdrop.openstack.org/#OpenStack_Operators_Telco_and_NFV_Working_Group

Structure

Currently we have bi-weekly meetings. Please see the meeting page for more information on time and place. Like most OpenStack meetings, they take place on IRC. Logs from previous meetings can be found online.

OPNFV

As our team crosses several areas, from OpenStack to telecommunications, we also work with the Open Platform for Network Function Virtualization organization (OPNFV).

The OPNFV has a wiki page dedicated to related OpenStack projects.

Mid to Long Term Project

Currently we are working to determine a project to work on over a mid-to-long term time frame. There is an etherpad page with some ideas listed. If you have requirements you think would be good for this functional team to work on, please feel free to add them to that page. Projects could vary from performance testing to working with OpenStack projects to add requirements.

FAQ

Do I have to be an "OpenStack Operator" to be part of this functional team?
1. No. While certainly the goal is to ensure that OpenStack Operators have all the tools, requirements, and functionality they need to do their work, there are many different facets to operating OpenStack clouds, and all opinions are welcome. Further, this team will be required to interact with many parts of the OpenStack ecosystem, not just other OpenStack Operators.
Wasn't there a telecom related working group previously?
1. Yes there was. However, it seems they met their goal of creating telecom/NFV related user stories, and those stories were moved into the product working group. With that completed the working group meetings were suspended. See this email message for more information.
2. Further, this group, the "OpenStack Operators Telecom/NFV Functional Team" is related to OpenStack Operators and helping them to manage OpenStack clouds with telecommunication and/or NFV use cases, so has a somewhat narrower scope.
Telecom "operators" versus OpenStack "Operators"
1. In telecommunications, the word "operator" has a different connotation than in OpenStack. Generally speaking, an "operator" in telecommunications context is some kind of communication service provider. Usually a telecommunications company.
2. In OpenStack, an operator is someone who runs an OpenStack cloud...someone who is responsible for deploying, and/or designing, and/or maintaining an OpenStack cloud. Usually they have day to day responsibility for an OpenStack deployment. Typically their job is to operate the cloud over time, which includes tasks such as performing upgrades, managing scalability, and making other operational decisions.
3. It is unlikely that either group will change their use of the word any time soon, so we will just have to deal with the occasional confusion.