project_proposals:armband
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
project_proposals:armband [2015/08/22 18:01] Bin Hu [Project Name: ARM Band] |
project_proposals:armband [2015/09/14 02:21] (current) Bob Monkman [Key Project Facts] |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| The Arno release was configured, built, validated, etc., without specific design on any particular underlying hardware, but, from a practical standpoint, was completed entirely on Intel Architecture-based servers in OPNFV labs available. This project, while adding support for ARM Architecture-based servers, will simultaneously identify platform dependencies that are necessary to modify to verify OPNFV independence of instruction set architecture at the silicon level, which is necessary for the industry. | The Arno release was configured, built, validated, etc., without specific design on any particular underlying hardware, but, from a practical standpoint, was completed entirely on Intel Architecture-based servers in OPNFV labs available. This project, while adding support for ARM Architecture-based servers, will simultaneously identify platform dependencies that are necessary to modify to verify OPNFV independence of instruction set architecture at the silicon level, which is necessary for the industry. | ||
| - | The full details of this work, including tasks and schedule, will be determined in the early phase of the project once underway. Working in close coordination with developers familiar with the process followed in building, installing, configuring, and testing the Arno release and beyond, this project will identify the list of tasks and schedule, available components, scripts, tools required etc., in order to accomplish the goal of this project. | + | The full details of this work, including tasks and schedule, will be determined in the early phase of the project once underway. Working in close coordination with other OPNFV projects and developers familiar with the process followed in building, installing, configuring, and testing the Arno release and beyond, this project will identify the list of tasks and schedule, available components, scripts, tools required etc., in order to accomplish the goal of this project. The steps of executing this project include: |
| + | * An analysis of what specifics of running OPNFV in ARM architecture are needed | ||
| + | * This step will produce a global view of critical path, and expected work in dependent projects, such as Pharos, Octopus, FuncTest, YardStick, Genesis, etc. | ||
| + | * According to the analysis and critical path, collaborate with those dependent projects through resource commitment and code contribution\\ | ||
| + | * ARM-specific code development in own repo for integration (e.g. with OVS). | ||
| + | |||
| + | **Please note that the spirit of this project focuses on collaborative development with other OPNFV projects in building, installing, configuring and testing, while develops ARM-specific code as necessary for integration purpose**. | ||
| The project will also necessitate the population of ARM-based servers in OPNFV Labs, which is discussion on several fronts, but will likely begin in an “incubation lab” of sorts, which is already underway since early in 2015. | The project will also necessitate the population of ARM-based servers in OPNFV Labs, which is discussion on several fronts, but will likely begin in an “incubation lab” of sorts, which is already underway since early in 2015. | ||
| Line 19: | Line 25: | ||
| This project will also add, in addition to all of the upstream projects planned for the Brahmaputra release, the upstream project OpenDataPlane for additional interfaces to underlying silicon platform. | This project will also add, in addition to all of the upstream projects planned for the Brahmaputra release, the upstream project OpenDataPlane for additional interfaces to underlying silicon platform. | ||
| - | It should be noted that the overall goal is to be able to demonstrate to the OPNFV community, ISVs, and all end users that OPNFV can be configured, build, deployed and run on any relevant silicon required by the industry. It is expected that some dependencies developed in the Arno release will naturally be discovered and will need to be adjusted to realize this goal. Once this goal is reached, there should be no further special projects required to address the ability to release OPNFV on multi-architectures identified as required for subsequent releases. | + | It should be noted that the overall goal is to be able to demonstrate to the OPNFV community, ISVs, and all end users that OPNFV can be configured, build, deployed and run on any relevant silicon required by the industry. It is expected that some dependencies developed in the Arno release will naturally be discovered and will need to be adjusted **through collaborative development** to realize this goal. Once this goal is reached, there should be no further special projects required to address the ability to release OPNFV on multi-architectures identified as required for subsequent releases. |
| ==== Dependencies ==== | ==== Dependencies ==== | ||
| Line 26: | Line 32: | ||
| * Octopus: necessary CI tools and scripts, if any, of integration and build for ARM-based servers | * Octopus: necessary CI tools and scripts, if any, of integration and build for ARM-based servers | ||
| * FuncTest: necessary test tools and scripts, if any, of integration with test framework for testing | * FuncTest: necessary test tools and scripts, if any, of integration with test framework for testing | ||
| + | * YardStick: necessary framework for verifying infrastructure compliance when running VNF | ||
| + | * Qtip: necessary platform benchmarking for ARM arcitecture | ||
| + | * Genesis: necessary ARM-specific requirement for installers | ||
| + | * Releng: build automation and tooling | ||
| ==== Committers and Contributors ==== | ==== Committers and Contributors ==== | ||
| Line 38: | Line 47: | ||
| * Joe Kidder (Enea) (joe.kidder@enea.com) | * Joe Kidder (Enea) (joe.kidder@enea.com) | ||
| * Bin Hu (AT&T) (bh526r@att.com) | * Bin Hu (AT&T) (bh526r@att.com) | ||
| + | * Aiguo Cui (Huawei) (ag.cui@huawei.com) | ||
| + | * Lauri Leukkenen (Huawei) (lauri.leukkunen@huawei.com) | ||
| * Additional contributors: | * Additional contributors: | ||
| Line 71: | Line 82: | ||
| ** Committers: ** \\ | ** Committers: ** \\ | ||
| * Bob Monkman (bob.monkman@arm.com) | * Bob Monkman (bob.monkman@arm.com) | ||
| + | * Rob Dimond (robert.dimond@arm.com) | ||
| * Jerin Jacob (Jerin.Jacob@caviumnetworks.com) | * Jerin Jacob (Jerin.Jacob@caviumnetworks.com) | ||
| * Vinita Gupta (Vinita.Gupta@caviumnetworks.com) | * Vinita Gupta (Vinita.Gupta@caviumnetworks.com) | ||
| Line 77: | Line 89: | ||
| * Joe Kidder (joe.kidder@enea.com) | * Joe Kidder (joe.kidder@enea.com) | ||
| * Bin Hu (bh526r@att.com) | * Bin Hu (bh526r@att.com) | ||
| + | * Aiguo Cui (ag.cui@huawei.com) | ||
| + | * Lauri Leukkenen (lauri.leukkunen@huawei.com) | ||
| \\ | \\ | ||
| - | ** Link to TSC approval: ** TBD \\ | + | ** Link to TSC approval: ** http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-09-08-13.59.html \\ |
| ** Link to approval of additional submitters: ** TBD \\ | ** Link to approval of additional submitters: ** TBD \\ | ||
project_proposals/armband.1440266476.txt.gz · Last modified: 2015/08/22 18:01 by Bin Hu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
