onosfw
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
onosfw [2015/04/20 15:15] Ashlee Young [Contributors] |
onosfw [2015/11/28 02:47] (current) Tim Zhao [Project Status] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Project Name: ONOS Framework (ONOSFW) ====== | + | ====== Project Name: ONOSFW ====== |
| - | * Proposed name for the project: ONOS Framework (onosfw) | + | * Name for the project: Open Network Operating System Framework (ONOSFW) |
| * Proposed name for the repository: onosfw | * Proposed name for the repository: onosfw | ||
| - | * Project Categories: Collaborative Development | + | * Categories: Collaborative Development |
| + | ====== Project Status ====== | ||
| + | |||
| + | * Milestones A,B,C, and D met on time | ||
| + | * Currently working on Milestone D/E in parallel | ||
| + | * ML2/ML3 plugin has been posted for code review | ||
| + | * SFC support has been added for ONOS and pushed into Emu version of ONOS | ||
| + | * Fuel installer: in process | ||
| + | * JuJu installer: in process | ||
| + | * Compass installer: in process | ||
| + | * Apex installer: in process | ||
| + | * Milestone D Report: [[https://wiki.opnfv.org/releases/brahmaputra/release_plan/onosfw_milestone_d_report|ONOSFW Milestone D Report]] | ||
| + | ====== Primary Repo ====== | ||
| + | https://gerrit.opnfv.org/gerrit/p/onosfw.git | ||
| ====== Etherpad ====== | ====== Etherpad ====== | ||
| https://etherpad.opnfv.org/p/onosfw | https://etherpad.opnfv.org/p/onosfw | ||
| + | |||
| + | ====== Meetings ====== | ||
| + | |||
| + | Meeting details: \\ When: Bi-weekly Wednesday 17:00-17:30 am PDT (Thursday 00:00-00:30 UTC) \\ Goto Meeting, Meeting ID: 796-752-669 \\ **IRC channel: ''#onosfw'' @ Freenode** | ||
| + | |||
| + | Next meeting will be September 2, 2015. | ||
| + | |||
| + | Meeting Announcements & Minutes can be tracked at http://forum.onosfw.com/c/meeting-tracker. This allows us to capture the minutes from the meeting, but to then have a dialogue without modifying the recorded minutes. | ||
| ====== Discussion Forum ====== | ====== Discussion Forum ====== | ||
| http://forum.onosfw.com | http://forum.onosfw.com | ||
| ===== Project Proposal Slides: ===== | ===== Project Proposal Slides: ===== | ||
| + | {{:onosfw_cr_summary.pdf|}} | ||
| {{:onosfw_overview_v1_0.pdf|}} | {{:onosfw_overview_v1_0.pdf|}} | ||
| {{:onosfw_overview_v1.1.pdf|}} | {{:onosfw_overview_v1.1.pdf|}} | ||
| {{:onosfw_overview_v1.2.pdf|}} | {{:onosfw_overview_v1.2.pdf|}} | ||
| + | {{:onosfw_overview_v1_3.pdf|}} | ||
| ===== Project Description: ===== | ===== Project Description: ===== | ||
| - | A number of SDN/NFV technologies have been developed since the dawn of open networking. Each approach has demonstrated its unique value in specific application domains. As stated in the white paper, [[https://www.opnfv.org//sites/opnfv/files/pages/files/opnfv_whitepaper_103014.pdf]], OPNFV is to create a common platform that will encourage open source development for NFV and create a collaborative environment. | + | A number of SDN/NFV technologies have been developed since the dawn of open networking. Each approach has demonstrated its unique value in specific application domains. As stated in the white paper, [[https://www.opnfv.org//sites/opnfv/files/pages/files/opnfv_whitepaper_103014.pdf]], OPNFV is to create a common platform that will encourage open source development for NFV and to create a heterogeneous & collaborative environment. |
| - | This project addresses integrating an SDN controller of choice based on a target applications or use cases within the OPNFV defined NFVI and VIM framework. It aims to provide end user and open source community with greater flexibility to build service applications, and to help leverage corresponding open source development efforts and results as well. | + | This project addresses integrating an SDN controller of choice based on a target applications or use cases within the OPNFV defined NFVI and VIM framework. It aims to provide end user and open source community with greater flexibility to build service applications, and to help leverage corresponding open source development efforts and results as well. Furthermore, it will create some common framework elements to address multi tenancy support, integration between the network controller and a DPI engine for context-based flow policies. It will also provide driver integration to support the Neutron ML2 plugin. |
| This project uses ONOS as an SDN controller within the VIM. ONOS is designed and optimized for carriers’ operation environments. The intent framework of ONOS is an ideal match for separating abstraction concerns for deployment of underlay and overlay resources, besides policy-based projects such as Copper. Along with its precise flow control capability, ONOS provides users with greater freedom for controlling data traffic. ONOS represents a simple core plus rich extensible modular service utilities controller design paradigm. It enables developers to quickly create needed applications. Many OPNFV applications can be easily built by extending ONOS' support library. Several potential use cases are listed below: | This project uses ONOS as an SDN controller within the VIM. ONOS is designed and optimized for carriers’ operation environments. The intent framework of ONOS is an ideal match for separating abstraction concerns for deployment of underlay and overlay resources, besides policy-based projects such as Copper. Along with its precise flow control capability, ONOS provides users with greater freedom for controlling data traffic. ONOS represents a simple core plus rich extensible modular service utilities controller design paradigm. It enables developers to quickly create needed applications. Many OPNFV applications can be easily built by extending ONOS' support library. Several potential use cases are listed below: | ||
| Line 32: | Line 54: | ||
| {{ :onos.png |}} | {{ :onos.png |}} | ||
| * The phase 1 of this project is limited to the framework of ONOS for integrating with VIM as an SDN controller. There are three integral pieces of the work: NB DevOps framework, OPNFV service supporting library, and SB DevOps framework. | * The phase 1 of this project is limited to the framework of ONOS for integrating with VIM as an SDN controller. There are three integral pieces of the work: NB DevOps framework, OPNFV service supporting library, and SB DevOps framework. | ||
| + | * For ONOSFW's first release, will include integration of ONOS controller into CI, BGS, or OPNFV's Arno+ platform, driver work to add ONOS support to ML2 Neutron plugin, and some (TBD) multi tenancy support to address the various Linux Namespace issues with large scale virtualization infrastructure. Initially, using OpenStack: Security Beyond Firewalls [[http://www.slideshare.net/gpaterno1/open-stack-security-beyond-firewalls]] as a guiding point. | ||
| * NB DevOps framework comprises two components: ONOS Restful API and Openstack support module/VAS. Through the Restful API, L2DB and L3DB in ML2 and ML3 Plug-ins of Neutron are passed into ONOS for topology management and other virtual network support functions. The API will include the declaration of network, subnet, port, tunnel, etc. as other SDN controllers do. The Openstack support module/VAS includes interfaces to vSwitch topology management, VM to vSwitch bonding, UNIFV interface creation, VLAN provisioning, MAC and ARP table management, etc. The upstream to Neutron plug-in ensures seamlessness in operation, while VAS lib allows integration of different open source packages. | * NB DevOps framework comprises two components: ONOS Restful API and Openstack support module/VAS. Through the Restful API, L2DB and L3DB in ML2 and ML3 Plug-ins of Neutron are passed into ONOS for topology management and other virtual network support functions. The API will include the declaration of network, subnet, port, tunnel, etc. as other SDN controllers do. The Openstack support module/VAS includes interfaces to vSwitch topology management, VM to vSwitch bonding, UNIFV interface creation, VLAN provisioning, MAC and ARP table management, etc. The upstream to Neutron plug-in ensures seamlessness in operation, while VAS lib allows integration of different open source packages. | ||
| * Extensible service support utilities will initially include topology plug-in to Horizon, intent state management, and resource allocation modules. | * Extensible service support utilities will initially include topology plug-in to Horizon, intent state management, and resource allocation modules. | ||
| Line 40: | Line 63: | ||
| * Interaction and federation with other controller is out of scope phase 1 & 2 of this proposal | * Interaction and federation with other controller is out of scope phase 1 & 2 of this proposal | ||
| * Extension to Phase 1 will be adding more service supporting modules. | * Extension to Phase 1 will be adding more service supporting modules. | ||
| - | + | * Targeted installers currently include Compass, Foreman, Juju, and Docker (inclusion and prioritization is based on resource participation). | |
| + | ===== NFV Requirement: ===== | ||
| + | * Heterogeneous SDN controller support | ||
| + | * VIM-based network control | ||
| + | * Ability to provision physical network resources into virtual resources, and then to allocate virtual resources | ||
| ===== Testability: ‘‘(optional, Project Categories: Integration & Testing)'' ===== | ===== Testability: ‘‘(optional, Project Categories: Integration & Testing)'' ===== | ||
| Line 47: | Line 73: | ||
| * The interoperability, scalability, high availability will be left to other Projects in OPNFV and this project may provide Q&A and test advice to those projects (?) | * The interoperability, scalability, high availability will be left to other Projects in OPNFV and this project may provide Q&A and test advice to those projects (?) | ||
| * Any enhancement within the scope of this project will be under Octopus(CI) along with parser and other tools for testing both Openstack and SDN modules | * Any enhancement within the scope of this project will be under Octopus(CI) along with parser and other tools for testing both Openstack and SDN modules | ||
| + | === Function Test: === | ||
| + | Onosfw function test, see more in [[:functest_onos|Functest:ONOS test]] | ||
| ===== Documentation: ‘‘(optional, Project Categories: Documentation)'' ===== | ===== Documentation: ‘‘(optional, Project Categories: Documentation)'' ===== | ||
| Line 58: | Line 85: | ||
| * This project will support requirements proposed in OPNFV OCSAR, OCTOPUS, BGS, and upstream project(s) plug-ins in Openstack [like Neutron, Horizon, Keystone and corresponding python clients/agents/drivers]. | * This project will support requirements proposed in OPNFV OCSAR, OCTOPUS, BGS, and upstream project(s) plug-ins in Openstack [like Neutron, Horizon, Keystone and corresponding python clients/agents/drivers]. | ||
| - | * Release 1 will only include definition of requirements in open source upstream projects coinciding with April 23, 2015 and will be using Liberty release of Openstack for Release 2 OPNFV, Cordoba of OPNFV. | + | * Release 1 will only include definition of requirements in open source upstream projects coinciding with April 23, 2015 and will be using Liberty release of Openstack for Release 2 OPNFV, Cordinal of OPNFV. |
| * Still to completely identify any specific development to be staged with respect to the upstream project. | * Still to completely identify any specific development to be staged with respect to the upstream project. | ||
| * This project has dependencies on ONOS blackbird release (March 15, 2015) for core functionalities, and subsequent releases (May &August time frame) for NetConf/Multi-tenant support. Refer [[https://wiki.onosproject.org/display/ONOS/Releases]] | * This project has dependencies on ONOS blackbird release (March 15, 2015) for core functionalities, and subsequent releases (May &August time frame) for NetConf/Multi-tenant support. Refer [[https://wiki.onosproject.org/display/ONOS/Releases]] | ||
| - | * This project keystone package has dependencies on ONOS Blackbird/Cordoba release (May/August ) for Multi-tenancy inclusion in Blackbird/Cordoba Release and alternate would be this add-on a temporary plug-in for keystone ID management via a plug-in for OPNFV in upstream. | + | * This project keystone package has dependencies on ONOS Blackbird/Cordinal release (May/August ) for Multi-tenancy inclusion in Blackbird/Cordoba Release and alternate would be this add-on a temporary plug-in for keystone ID management via a plug-in for OPNFV in upstream. |
| ===== Committers and Contributors: ===== | ===== Committers and Contributors: ===== | ||
| ==== Project Lead: ==== | ==== Project Lead: ==== | ||
| - | * Michael Young: OPNFV Liaison, Site Tools, Forum, and Infrastructure (Huawei, michael.y@huawei.com) | + | * Ashlee Young (Huawei, ashlee@wildernessvoice.com) |
| ==== Committers ==== | ==== Committers ==== | ||
| * Zhao Kexue (Huawei, zhaokexue@huawei.com) | * Zhao Kexue (Huawei, zhaokexue@huawei.com) | ||
| * Patrick Liu (Huawei, patrick.liu@huawei.com) | * Patrick Liu (Huawei, patrick.liu@huawei.com) | ||
| - | * Michael Young (Huawei, michael.y@huawei.com) | + | * Ashlee Young (Huawei, ashlee@wildernessvoice.com) |
| + | * Prakash Ramchandran (Huawei, prakash.ramchandran@huawei.com) | ||
| + | * Daniel Smith (Ericsson, daniel.smith@ericsson.com) | ||
| + | * Brian O’Conner (ON.Lab, brian@onlab.us) | ||
| + | * Zhanghouyu (Huawei, zhanghaoyu7@huawei.com) | ||
| + | * Zhou Bob (Huawei, bob.zh@huawei.com) | ||
| + | * Lanqinglong (Huawei, lanqinglong@huawei.com) | ||
| + | * Jiangrui (Huawei, jiangrui1@huawei.com) | ||
| + | * Xuzhang (Huawei, xuzhang.xuzhang@huawei.com) | ||
| + | * Lishuai (Huawei, lishuai12@huawei.com) | ||
| + | * Jiangchunchen (Huawei, jiangchuncheng@huawei.com) | ||
| + | * Zhangyuanyou (Huawei, zhangyuanyou@huawei.com) | ||
| ==== Contributors ==== | ==== Contributors ==== | ||
| - | * Brian O’Conner (ON.Lab, brian@onlabs.us) | ||
| * Huangzhipeng (Huawei, huangzhipeng@huawei.com) | * Huangzhipeng (Huawei, huangzhipeng@huawei.com) | ||
| - | * Prakash Ramchandran (Huawei, prakash.ramchandran@huawei.com) | ||
| * Robert Tao (Huawei, roberttao@huawei.com) | * Robert Tao (Huawei, roberttao@huawei.com) | ||
| - | * Hongbo Tian (Huawei, tianhongbo@huawei.com) | + | * Hongbo Tian (Huawei, hongbo.tianhongbo@huawei.com) |
| * William Snow (ON.Lab, bill@onlab.us) | * William Snow (ON.Lab, bill@onlab.us) | ||
| * Wei Su (Huawei, su.wei@huawei.com) | * Wei Su (Huawei, su.wei@huawei.com) | ||
| Line 93: | Line 128: | ||
| * Jie Miao (China Unicom, miaojie9@chinaunicom.cn) | * Jie Miao (China Unicom, miaojie9@chinaunicom.cn) | ||
| * John Strassner (Huawei, john.sc.Strassner@huawei.com) | * John Strassner (Huawei, john.sc.Strassner@huawei.com) | ||
| + | * Harsha Alapati (Ericsson, harsha.alapati@ericsson.com) | ||
| + | * Mark Gray (Intel, mark.d.gray@intel.com) | ||
| + | * Eric Sindelar (Supermicro, erics@supermicro.com) | ||
| + | * Chris Beekman (Supermicro, chrisb@supermicro.com) | ||
| + | * Etay Nir (Palo Alto Software, etay@me.com) | ||
| + | * Tongjj (China Unicom, tongjj@dimpt.com) | ||
| + | * GanZhen (China Unicom, ganzhen1@chinaunicom.cn) | ||
| + | * Lijy (China Unicom, lijy@dimpt.com) | ||
| + | * Cathy (Huawei, wuwenbin2@huawei.com) | ||
| + | * Vikram Choudhary (Huawei, vikram.choudhary@huawei.com) | ||
| ===== Planned Deliverables ===== | ===== Planned Deliverables ===== | ||
| Line 111: | Line 156: | ||
| * Specification May 23 | * Specification May 23 | ||
| * Package release plan October 23 | * Package release plan October 23 | ||
| - | 4. Keystone | + | 5. Keystone |
| - | * Specification May 23 | + | |
| - | * Package release plan October 23 | + | |
| - | 5. Congress | + | |
| * Specification May 23 | * Specification May 23 | ||
| * Package release plan October 23 | * Package release plan October 23 | ||
onosfw.1429542926.txt.gz · Last modified: 2015/04/20 15:15 by Ashlee Young
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
