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 10 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:

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:


  • No labels