Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Brigade Lead:

  • Patrick Liu

Brigade Members:

  • Madan Jampani                (Configuration Store - ON.LAB)*
    • Aaron Kruglikov                (Configuration Store - Fujitsu)
    • Sithara Punnassery          (Configuration Store - Huawei)
    • 2 more developers required in this area.
    • 1-2 testing engineers required, who will develop the testing script for functionality and stress test, setup the environment, and add the testing case to ONOS daily automation testing tools.
  • VinodS Kumar                  (YMS - Huawei)*
    • Henry Yu                (RestCONF Server    - Huawei)
  • Gaurav Agrawal               (YANG Utils  - Huawei)*
  • Jiang, chuncheng (Samuel)    (SB Driver - Huawei)*
    • we need 3-5 vendors to provide their devices with their own device model, and do the integration work with our SB driver mechanism.  
  • Lu, Kai                                     (Use Case  - L3VPN  - Huawei)*
  • Hongtao Yin                             (Use Case  - L3VPN  - Huawei)
  • Xu, Shiping                              (Use Case - L3VPN - Huawei) 

Contact the brigade:

Project Goal:

  • On SB, we will build a service and vendor agnostic driver. This driver provides a mechanism for operator, integrator, vendor, and so on to quickly hook a new device to ONOS controller through modifying the driver configuration file (.xml)  rather than modifying JAVA code. This provides an agile way to enable and activate a NETCONF enabled devices.   
  • On NB, based on a YANG defined network service(e.g. L3VPN), we will build an corresponding application and provide configuration interface for user to install/update/remove configuration dynamically. 
  • In ONOS Core, we will build a Configuration Store as a storage for app's configuration with read/write/update/delete operation. This is a distributed data store, which will provide transactional operation to application. 

Demo


  • Use ONOS YANG Utils to translate IETF L3SM L3VPN model to JAVA application framework
  • Enable and disable L3VPN service on ONOS controller through dynamic configuration
  • Add a new device through modifying ONOS driver configuration (.xml) file.   

 

 Scope     

Build a model driven architecture in ONOS to dynamically install/update/remove the configuration for NETCONF enabled devices. In the first release, we will use L3VPN as a use case and build related applications on top of this architecture to demonstrate how this architecture works.  This project will be based on and integrate the results from existing projects (e.g. YANG Utils,  YMS, etc) and create new several components when necessary. In the demo, we plan to use multi-vendor devices as network element in our demo setup.


Short-term focus in 2016

Use IETF L3SW model in building both network layer application and network element layer application

Use 3-5 devices from different Vendors as network elements in the Demo setup

New components to be built

L3VPN Application.  This is an external application (off-platform) that handle network model. 

Ne L3VPN App.  This is an ONOS internal application that processes device model. Its north bound interface is defined by IETF.

Configuration Store. This is used to store configuration of device. 

Driver Mechanism. This is an service and device agonistic mechanism

Long-term focus in 2017

    • Performance Assessment and do the enhancement if necessary
    • Transactional Operation on Configuration Store

How to get involved

Help needed

  • 1-2 developer for configuration Store, who is/are required to work with ONOS distributed core team to implement Store Mechanism, Application API, and advanced store features etc. Location can be local or remote. 
  • 1-2 QA engineer, whose responsibility will be setup related testing environment in ON.LAB, design stress and regression testing plan and testing cases, write automation script, work with developer on any issues by stress and regression test. Local resources are preferred.
  • Invite 3 (at least) vendors to join the brigade. These vendors will provide one or two L3 devices with NETCONF and device model ready. Engineers are required to work with Brigade team to integrate their devices into the demo environment. They are required to know their device model and is able to help brigade team to debug any issue seen during the integration.      


  • No labels