* Hw/sw proposal by Intel to get started …

* Hardware

• Intel® Server Board 2U
• 2-way with top bin CPUs (versions with 10 or 14 cores)
• 240GB SSD (8x2.5 SATA)
• 64GB RAM (8x8GB DDR3 or DDR4)
• Integrated 1GbE x4
• PCIe x16 Gen 3
• NICS (PCI-Express)
  • 2x Intel® 82599 10 GbE
  • Other vendors NICS
• Accelerators (PCI-Express)
  • Intel® Communications Chipset 8920
  • Other vendors accelerators

* Software (compute node)

• Fedora 20 (3.15 kernel) with KVM
• Ubuntu 14.04
• Open vSwitch v 2.1.2 (ovs.org)

* Software (VIM)

• Fedora 20 (3.15 kernel) with KVM
• Ubuntu 14.04
• Open Stack (Ice House)
• Open Daylight (Hydrogen) - there are 3 flavours, use carrier grade version

• Proposed name for the project: Reference community platform definition
• Proposed name for the repository: repo-name
• Project Categories: (Documentation, Requirements, Integration & Testing, Collaborative Development)

• Provide high level description of intended project and OPNFV use case and benefit, if needed.
• Include any architecture diagrams or specifications, reference to OPNFV requirements list.

• 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

• Specify testing and integration like interoperability, scalability, high availablity
• What QA and test resources will be available?

• API Docs
• Functional block description

• Identify similar projects is underway or being proposed in OPNFV or upstream project
• Identify any open source upstream projects and release timeline.
• 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.

• Name of and affiliation of the maintainer: Trevor Cooper (Intel)
• Names and affiliations of the committers:
• Any other contributors

• 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.

• When is the first release planned?
• Will this align with the current release cadence