EPIC:

  1. SDN-C support BBS Usecase

Story:

  1. Depends on the Data Model definition to expose the API for the resource in SDN-C
  2. Develop the new DGs for the PNF configuration during the PnP and Nomadic ONT.

Tasks:

  1. Until the DM defined. (Both Design Time and Runtime)


Reviewed by Stavros Kanarakis Weitao Gao Bryan Guo


Sub-UC1: Topology Discovery and Synchronization

CCSDK/SDNC-C Diagram

Flow Discription

1.User registers 3rd party controller information in ESR.

2. ESR triggers a 3rd party controller registration event to DMAAP

3. SDNC subscribes to the event and gets event ntification

4. SDNC queries topology from 3rd party Controller

5. SDNC decomposes and save topology to AAI

New Development

  1. Adapt existing DGs for sync topology to make a new BBS type, Each vendor will have a different API call and so we need a switch flag inside DG code to choose specific vendor sub-DG for the call
  2. Topology data model definition (optional, depends on whether we follow CCVPN model for topology). If new model is required, we need to adapt saving data to AAI DG.
  3. Make token authentication more generic

Query Topology API


Query Topology API 
URL:/v2/data/huwwei-nce-resource-inventory:ltps
get:



Topology Model


Topology Model 
PON-UNI
{


}


OLT-NNI
{


}



Sub-UC2: Service Creation and Activation

CCSDK/SDN-C Diagram

Flow Description

  1. Access SDN M&C notify ONT Register Event to DCAE

  2. DCAE Publishes an ONT Registration Event(pnf_registeration) to SO via DMaaP 

  3. SO Calls Generic Resource APIs of SDNC to trigger Access/Edge SDN M&C

  4. SDNC calls Access SDN M&C to configure RFS ONT

  5. SDNC calls Edge SDN M&C to configure IPAM and AAA

  6. Access SDN M&C notify RG Activated Event to DCAE

  7. DCAE Publishes an RG Activated Event to SO via DMaaP

New Development(Depends on the Modeling definition)

  1. Addition of new enumerations to generic-resource-api.yang for CreateAccessConnectivity, CreateInternetProfile.

  2. Addition of new resource to GenericResourceApiProvider.java (review it later)

  3. New DGs for the service creation

  4. Extending respective template for restapicall plugin in Network Adapters. We need to manually put the new template files for each vendor inside the SDN-C container

Configure RFS ONT

URL：

Configure RFS ONT Template


Configure  IPAM/AAA

URL：

Configure IPAM/AAA Template


Sub-UC3: Nomadic ONT Service

CCSDK/SDN-C Diagram

Flow Description

1.Access SDN M&C notify ONT Register Event to DCAE
2.DCAE notify SO ONT registration
3.SO Calls Generic Resource APIs of SDNC to trigger Access SDN M&C
4.SDNC calls Access SDN M&C to delete old RFS ONT;SDNC calls Access SDN M&C to configure new RFS ONT
5.SDNC calls Edge SDN M&C to configure  AAA

New Development

  1. Addition of new enumerations to generic-resource-api.yang forDeleteAccessConnectivity, DeleteInternetProfile.

  2. Addition of new resource to GenericResourceApiProvider.java (review it later)

  3. New DGs for the service deletion

  4. Extending respective template for restapicall plugin in Network Adapters. We need to manually put the new template files for each vendor inside the SDN-C container

  5. Creation DGs/templates/additions are mentioned in the Sub-UC2.

Delete old RFS ONT

URL:

Delete old RFS ONT Template


Configure new RFS ONT

URL:

Configure new RFS ONT Template


Configure AAA

URL:

Configure AAA Template
  • No labels

7 Comments

  1. michail salichos

    Looks good to me, one question though: in both Sub-UC2 and Sub-UC3 there is a connection between Edge SDN M&C and DCAE, what kind of VES messages are you expecting the Edge SDN M&C to send to DCAE?

    1. Bryan Guo

      Good question! Edge SDN M&C need not send  messages to DCAE,it has been corrected.

    2. Weitao Gao

      Michail,

         our discussion didn't cover this part.  I think we could list the VES message first then we could distinguish the Access and Edge part. I think we need to merge the Access and Edge message into one and reported by Access SDN M&C if needed since ONT is handled by Access SDN M&C.  Xin Miao any idea on this?

  2. Tim Carey

    Careful about merging Domain specific controllers - they do.... domain specific things. ONT events will come from the Access M&C. For the Edge we haven't identified any flows that need it at this time. I did start a discussion trying to decide from where the RGActivation event gets emitted - which could be the Edge but for now we don't have any needs for Edge to emit an event in our interactions.

    1. Weitao Gao

      I think we didn't try to merge the domain-specific controllers. can you help me point out this?

      1. Tim Carey

        It was in sub-UC2: SO Calls Generic Resource APIs of SDNC to trigger Access/Edge SDN M&C

        When I was reading it looked combined but that was my mistake - I would have said trigger Access and Edge SDN M&Cs.


        Also in sub-UC3: SO Calls Generic Resource APIs of SDNC to trigger Access SDN M&C - You meant Access and Edge SDN M&C's right?


        1. Xin Miao

          Weitao Gao

          David Perez Caparros

          Based on today's discussion in BBS meeting, we need to understand the interface defined between SDNC and Edge SDN M&C as well as those between DCAE and Edge SDN M&C. 

          In Case of DCAE, in the sub-UC2 and sub-UC3, the arrow from Edge SDN M&C to DCAE is missing. The message/notification from Edge SDN M&C, need to be either in Restconf JSON or VES format. 

          Please confirm.