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

Compare with Current View Page History

« Previous Version 5 Next »


CCVPN Close Loop Fow

  1. SDC/CLAMP Portal design and activate policy.
  2. SDC/CLAMP config and activate the policy.
  3. SDC/CLAMP distribute the DCAE config.
  4. SDC/CLMAP distribute the alarm correlation rules to Holmes.
  5. 3rd party SOTN controller report link down alarm to DCAE
  6. DCAE will do data cleaning and filtering for the alarms
  7. DCAEk keep track the datas.
  8. Holmes do analysis for the alarms.
  9. Holmes notify the reroute event.
  10. Policy matching the reroute rules.
  11. Policy call SO to delete the old services and create the new services. For the creation flow, a variable route will be recalculated.

CLAMP  (TBD)

DCAE

DCAE  Flow

  1. RestConf Collector (RC)subscribes for remote failure alarm to SOTN Controller (SC) 
  2. RC requests to set up a long term tunnel with the 3rd party SC
  3. SC responses with OK upon successful tunnel setting
  4. SC pushes service route status data to the collector
  5. RC receives alarm data, converts it into JSON format and publishes on DMAAP with topic of ROUTE_ALARM_OUTPUT
  6. UVA consumes the alarm message
  7. UVA requests the RestConf2VES mapping
  8. UVA converts json alarm into VES  event
  9. UVA publishes the VES event on DMAAP for further correlation 

APIs to SOTN Controller (Restconf)

Subscribe Notification

Functionality

             Collector (Client) and SOTN Controller establishes subscription relationship. 

Method

             POST

Request-URL

             /restconf/operations/ietf-subscribed-notifications:establish-subscription

Request-Body

            {

               "ietf-subscribed-notifications:input": {

                                 "encoding": "encode-json"

               }

            }

Response-Body

           {

                "ietf-subscribed-notifications:output": {

                       "identifier": "1"

                }

           }

Establish Long Term

Functionality

           Collector establishes long term connectivity with SOTN Controller and the controller will continuously Push the subscribed notification over. 

Method

           GET

Request-URL

           /restconf/streams/yang-push-json

Request-Body

          (TBD)

Response-Body

          {  

             "ietf-notification:notification": {

                     "eventTime": {eventTime},

                     "ietf-yang-push: push-change-update ": {

                             "subscription-id ": {subscription-id },

                              " datastore-changes ": {

                                      "ietf-yang-patch:yang-patch": {

                                             "patch-id": {patch-id},

                                             "edit": [

                                                  {

                                                  "edit-id" : {edit-id }, 

                                                  "operation" : {operation }, 

                                                  "target" : {target },

                                                  "value": {value}

                                                 }

                                              ]

                                       }

                              }

                      }

                }

          }

HOLMES


POLICY


  • No labels