project_proposals:enfv
This is an old revision of the document!
Table of Contents
Project Name:
- Proposed name for the project: edge nfv
- Proposed name for the repository: enfv
- Project Categories: Requirements
Project description:
- The NFV movement is largely focused gaining the efficiencies of large data centre compute infrastructure. This is sensible, however to paraphrase the old switching/routing saying … centralize what you can, distribute what you must. Some applications naturally belong at the edge: WAN Acceleration, Content Cacheing, and depending on your philosophy, Firewalling all fall into that category. Other more specialized test applications also need to be at the edge to exercise the portions of the network under test. Similarly many business applications are most efficiently delivered at the edge.
- The purpose of this Requirements Project is to articulate the capabilities and behaviours needed in Edge NFV platforms, and how they interact with centralized NFVI and MANO components of NFV solutions
- Appropriate Tunneling for User Traffic across WAN (Ethernet, IP/MPLS) links
- Appropriate Tunneling for Management Traffic across WAN links
- Including reachability requirements to the compute platform
- Extending Multi-DC management to address many small "DC" locations
- Monitoring Capabilities required for a remote Compute Node
- Squaring Bare Metal with remote survivability and whether IaaS is more appropriate for remote locations
- Include any architecture diagrams or specifications, reference to OPNFV requirements list.
Scope:
- This is a requirements project, therefore it is proposed to develop use cases, requirements, as well as upstream project blue prints.
- Describe the problem being solved by project
- Specify any interface/API specification proposed,
- Specify testing and integration:
- Debugging and Tracing
- Unit/Integration Test plans
- Client tools developed for status shows etc.
- Identity a list of features and functionality will be developed.
- Identify what is in or out of scope. So during the development phase, it helps reduce discussion.
- Describe how the project is extensible in future
Testability: ''(optional, Project Categories: Integration & Testing)''
- Specify testing and integration like interoperability, scalability, high availablity
- What QA and test resources will be available?
Documentation: ''(optional, Project Categories: Documention)''
- API Docs
- Functional block description
Dependencies:
- Identify similar projects is underway or being proposed in OPNFV or upstream project
- Pharos project
- Identify any open source upstream projects and release timeline.
- OpenStack
- Identify any specific development be staged with respect to the upstream project and releases.
- Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications.
- If project is an integration and test, identify hardware dependency.
Committers and Contributors:
- Names and affiliations of the committers
- Names and affiliations of any other contributors
Planned deliverables
- Described the project release package as OPNFV or open source upstream projects.
- If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.
Proposed Release Schedule:
- When is the first release planned?
- Will this align with the current release cadence
project_proposals/enfv.1433200167.txt.gz · Last modified: 2015/06/01 23:09 by James Buchanan
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
