Difference between revisions of "Ops-telecom-nfv"
Serverascode (talk | contribs) |
Serverascode (talk | contribs) (→FAQ) |
||
| Line 30: | Line 30: | ||
#Wasn't there a telecom related working group previously? | #Wasn't there a telecom related working group previously? | ||
| − | ## 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. See this email message: http://lists.openstack.org/pipermail/openstack-operators/2016-April/010169.html | + | ## 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: http://lists.openstack.org/pipermail/openstack-operators/2016-April/010169.html |
| − | # Telecom operators versus OpenStack Operators | + | ## Further, this group is related to OpenStack Operators and helping them to manage OpenStack clouds with telecommunication and/or NFV use cases. |
| − | ## In telecommunications, the word "operators" has a different connotation than in OpenStack. In OpenStack, and operator is essentially 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 cloud, be it in test or production. Usually they have requirements to operate the cloud over time, such as performing upgrades. | + | # Telecom "operators" versus OpenStack "Operators" |
| + | ## In telecommunications, the word "operators" has a different connotation than in OpenStack. In OpenStack, and operator is essentially 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 cloud, be it in test or production. Usually they have requirements to operate the cloud over time, such as performing upgrades. I don't see either group changing their use of the word any time soon, so we will just have to deal with the occasional confusion. | ||
[[Category: Working_Groups]] | [[Category: Working_Groups]] | ||
[[Category:UserCommittee]] | [[Category:UserCommittee]] | ||
Revision as of 16:46, 27 July 2016
Status: Active
Organizers:
- Curtis Collicutt <curtis@serverascode.com>
- Your name here?
Contents
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) 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.
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
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: https://wiki.opnfv.org/display/COM/OpenStack
FAQ
- Wasn't there a telecom related working group previously?
- 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: http://lists.openstack.org/pipermail/openstack-operators/2016-April/010169.html
- Further, this group is related to OpenStack Operators and helping them to manage OpenStack clouds with telecommunication and/or NFV use cases.
- Telecom "operators" versus OpenStack "Operators"
- In telecommunications, the word "operators" has a different connotation than in OpenStack. In OpenStack, and operator is essentially 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 cloud, be it in test or production. Usually they have requirements to operate the cloud over time, such as performing upgrades. I don't see either group changing their use of the word any time soon, so we will just have to deal with the occasional confusion.
