Page tree
Skip to end of metadata
Go to start of metadata

This page is used to capture the agreement the OPNFV 2.0 sub-committee reached. 

The page can only be edited by the chair of the sub-committee or anyone the chair assigned.


Mission Statement final proposal from the sub-committee call on Mar. 20th


Proposal for web statementOPNFV reduces time to integrate and deploy NFV infrastructure and onboard VNF/CNFs for those who supply components and those who operationalize these platforms. The OPNFV community does this by implementing, testing and deploying tools for conformance and performance of  NFV infrastructure, aligned with industry reference architectures

Proposal for the Charter

OPNFV reduces time to integrate and deploy NFV infrastructure and onboard VNF/CNFs for those who supply components and those who operationalize these platforms. The OPNFV community does this by:

(a) implementing, testing and deploying tools for conformance and performance of  NFV infrastructure, aligned with industry reference architectures,

(b) iterating on developing integrated, tested reference infrastructures (including interfaces to hardware) based on open source software, with tools of its own design and from upstream projects,

(c) contributing changes to and influencing upstream projects leveraging the reference infrastructures,

(d) building new open source components within the reference infrastructures where needed,

(e) leveraging open implementations to drive an open standards and open source based ecosystem for NFV solutions,

(f) supporting and maintaining the strategic framework of the Project through the technologies made available by the organization to make the Reference Infrastructure testing, certification, and deployment a success.

  • No labels

15 Comments

  1. Thanks Qiao Fu. This is coming along well. The only edit Id suggest is on the second sentence of the web statement because as currently written it's an incomplete sentence. Adding the "OPNFV does this by" (similar to the charter statement) should do the trick:

    "OPNFV is a project and community for Communication Service Providers (CSPs) and their supply chains focused on network transformation and collaboration to continuously improve the efficiency and predictability of consuming and deploying NFV infrastructure, VNFs, and CNFs. OPNFV does this by iterating through implementation of toolsets, automation, verification, conformance, and performance, aligned with normalized architectures, and enabling the community to drive down cost and time to revenue for network services."

    1. HI, Brandon. Thank you for that. I am OK with this, will edit the page accordingly.

    2. Hi, Brandon.  I just put up the final statement after discussion on Mar. 20. It was suggested on today's call for marketing guys to read the second sentence in the statement of the website, and see if grammer is right. Would you please help with that?

  2. Per the discussion in the last TSC call. IMHO Marketing statement and charter can be closely aligned. In addition, the above statements could be simplified - with shorter sentences used.

    Marketing: 
    OPNFV is an open source project and open community focused on improving NFV infrastructure, VNFs, and CNFs, striving to accelerate the success of NFV. OPNFV integrates and builds tests, creates tools and components for NFV infrastructure, VNFs and CNFs. OPNFV incorporates and leverages standards and normalized architectures.

    Charter:
    OPNFV is an open source project and open community focused on improving NFV infrastructure, VNFs, and CNFs, striving to accelerate the success of NFV. OPNFV is to integrate and build tests, create tools and components for NFV infrastructure, VNFs and CNFs. OPNFV is to incorporate and leverage standards and normalized architectures.

  3. One additional comment: Before we address the OPNFV 2.0 charter it would be good to see an answer to the key question articulated:

    "What is the technical problem that OPNFV 2.0 is to address that all parties agree to and that is in its very nature suitable for open source, i.e. everyone agrees to the problem, everyone benefits from the solution and the solution is low on IP?"

  4. RE: Technical Problem

    Maybe: Reduce the technical barriers to NFVI and VNF/CNF integration for those who supply components, and/or procure, operate, and maintain these platforms (at large scale).

    1. Thanks Al. This might be a good starting point for the charter.

  5. Proposal for web statement: OPNFV aims to significantly improve the efficiency and predictability of consuming and deploying NFV infrastructure, VNFs, and CNFs in order to drive down cost and time to revenue for network services. The community does this by implementing tools for NFV infrastructure deployment and testing the capabilities and performance of reference architectures.


    Proposal for the Charter

    OPNFV's mission is to continuously improve the efficiency and predictability of consuming and deploying NFV infrastructure, VNFs, and CNFs in order to drive down cost and time to revenue for network services. This is achieved by:

    (a) fostering close industry collaboration to integrate and build tests, automation tools and NFV reference infrastructures that can ensure predictable VNF and CNF behavior,

    (c) contributing changes to and influencing upstream projects from gaps exposed deploying and testing reference infrastructures,

    (d) building new open source components within reference infrastructures where needed,

    (e) leveraging reference infrastructures to drive an open-source-based ecosystem for NFV solutions,

    (f) implementing a program for testing commercial NFV infrastructures against reference infrastructures.

  6. OPNFV reduces time to integrate and deploy NFV infrastructure and onboard VNF/CNFs. The community does this by implementing tools for testing NFV infrastructure deployment and testing the conformance and performance of reference architectures

  7. OPNFV reduces time to integrate and deploy NFV infrastructure and onboard VNF/CNFs for those who supply components and those who operationalize these platforms. The OPNFV community does this by implementing, testing and deployment tools for conformance and performance of  NFV infrastructure, aligned with industry reference architectures

  8. OPNFV reduces time to integrate and deploy NFV infrastructure and onboard VNF/CNFs for those who supply components and those who operationalize these platforms. OPNFV does this by:

    (a) The OPNFV community does this by implementing, testing and deployment tools for conformance and performance of  NFV infrastructure, aligned with industry reference architectures,

    (b) iterating on developing an integrated, tested, and certified open software reference infrastructure (including interfaces to hardware), with tools of its own design and from upstream testing projects,

    (c) contributing changes to and influencing upstream projects leveraging the reference infrastructure,

    (d) building new open source components within the reference infrastructure where needed,

    (e) leveraging open implementations to drive an open standards and open-source-based ecosystem for NFV solutions,

    (f) supporting and maintaining the strategic framework of the Project through the technologies made available by the organization to make the Reference Infrastructure testing, certification, and deployment a success.

  9. OPNFV reduces time to integrate and deploy NFV infrastructure and onboard VNF/CNFs for those who supply components and those who operationalize these platforms. The OPNFV community does this by:

    (a) implementing, testing and deployment tools for conformance and performance of  NFV infrastructure, aligned with industry reference architectures,

    (b) iterating on developing an integrated, tested, and certified open software reference infrastructure (including interfaces to hardware), with tools of its own design and from upstream testing projects,

    (c) contributing changes to and influencing upstream projects leveraging the reference infrastructure,

    (d) building new open source components within the reference infrastructure where needed,

    (e) leveraging open implementations to drive an open standards and open-source-based ecosystem for NFV solutions,

    (f) supporting and maintaining the strategic framework of the Project through the technologies made available by the organization to make the Reference Infrastructure testing, certification, and deployment a success.

  10. ... minor note: IMHO it should read " ... does this by implementing, testing and deploying tools for conformance..." (i.e. s/deployment/deploying/)

    1. Modify accordingly. Thanks