Versions Compared

Old Version 10

changes.mady.by.user Hesam Rahimi

Saved on

compared with

New Version Current

changes.mady.by.user Henry Yu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Test Case NumberTest CaseStatusOwner
1Physical network discoveryPASSEDHesam
2(a)Create single CLL instance which accesses single cloud.PASSEDHesam
2(b)Repeat 2(a), and verify closed-loop actions:  (1) SDNC establish yang-push SSE session with PNC; (2) SDNC receives bandwidth live updates from PNC; (3) SDNC updates bandwidth in AAI; (3) SDNC sends VES notification to DCAE; PASSEDHesam 
2(c)Repeat 2(b), and increase bandwidth and verify: (1) DCAE checks bandwidth received from SDNC against the threshold and calls Policy if needed; (5) Policy calls SO modify-bandwidth API; (6) SO calls SDNC for modify-bandwidthPENDINGPASSEDDecheng
2c.1pm-mock (bandwidth-generator) increases the bandwidth data pushing to PNCs-"performance-monitor", verify that PNC can get latest data. (The bandwidth usage data are expected to exceed the network-policy threshold , so that bandwidth adjustment can be triggered)PASSEDDecheng
2c.2Assuming a SSE subscription had been established, SDNC SSE, upon receiving yang-push notification, sends VES msg to DCAE-VES-Collector through publishing msg to VES_NOTIFICATION topicPASSEDDecheng
2c.3DCAE-Slice-analysis-ms listened and received the notification, saved the data to in-memory datastorePASSEDDecheng
2c.4DCAE-Slice-analysis-ms getting bandwidth data from A&AI network policy object whose network-policy-fqdn equals to cll-IdPASSEDDecheng
2c.5DCAE-Slice-analysis-ms triggered periodic service-state check after pre-configured interval, if condition is met, sends request to Policy through publishing msg to DCAE_CL_OUTPUT topicPASSEDDecheng
2c.6Policy listened and received DCAE_CL_OUTPUT topic, upon receiving request, calls SO modify-bandwidth APIPENDING – need to turn on Policy, and maybe confirm with China Telecom PASSEDDecheng
2c.7When SO received request from Policy, calls SDNC for bandwidth adjustmentPENDING PASSEDDecheng
2c.8After SDNC and SO complete bandwidth adjustment, check if DCAE update target ServiceState from UNDER_MAINTENANCE to RUNNINGPENDING PASSEDDecheng
2c.9After SDNC and SO complete bandwidth adjustment, check PNCs, see if eth-svc has new CIR and EIR PENDING PASSEDDecheng
2c.10Repeat 2c, stopping the pm-mock, and rerun with new baseline parameters, see if another adjustment can be triggeredPENDING PASSED Decheng
2(d)Delete single CLL instance which accesses single cloud. Verify that E-TRE is deleted on the PNCs.PASSEDHesam
2(e)Repeat 2(d) and verify:  SDNC calls terminate-subscription RPC to stop yang-push streamingPASSED - Need to fix our RESTCONF server to properly handle unsubscribe and terminate SSE connections. Fixed. 

Hesam

Henry

3(a)Create single CLL instance which access multiple clouds.PASSEDHesam
3(b)Repeat 3(a), and verify closed-loop actions:  (1) SDNC establish yang-push SSE session with PNC; (2) SDNC receives bandwidth live updates from PNC; (3) SDNC updates bandwidth in AAI; (3) SDNC sends VES notification to DCAE; PASSEDHesam
3(c)Repeat 3(b), and increase bandwidth and verify: (1) DCAE checks bandwidth received from SDNC against the threshold and calls Policy if needed; (5) Policy calls SO modify-bandwidth API; (6) SO calls SDNC for modify-bandwidthPASSEDDecheng
3(d)Delete single CLL instance which access multiple clouds.PASSEDHesam
3(e)Repeat 3(d) and verify:  SDNC calls terminate-subscription RPC to stop yang-push streamingPASSED 

Hesam

Henry

4Create and delete multiple CLL instances which access single cloud, and monitor if the closed-loop call flow is getting triggered.PASSEDHesam
5Create and delete multiple CLL instances which access multiple clouds, and monitor if the closed-loop call flow is getting triggered.PASSEDHesam
6Create a CLL instance which have connection links with different bandwidth, and monitor if the closed-loop call flow is getting triggered.PASSEDHesam
7Modify the bandwidth of a connection link of an existing CLL instance, and monitor if the closed-loop call flow is getting triggered.PASSEDHesam
8Modify an existing CLL instance by add a new connection link, and monitor if the closed-loop call flow is getting triggered.PASSEDHesam
9UUI actively modifies an existing IBN service-instance, the request is sending to AAI, DCAE, POLICY, SOPASSEDDecheng
9(a)UUI modify IBN service-instance, verify an AAI-EVENT is published and received by DCAEPASSEDDecheng
9(b)When DCAE received AAI-EVENT, it should verify the serivice bw, if adjustment needed, sending OnSetMessage to PolicyPASSEDDecheng
9(c)Upon receiving OnSetMessage, Policy invokes predefined operator and sending request to SOPASSEDDecheng
9(d)SO sends down request to SDNC to reflect on User's intent.PASSEDDecheng


Test Plan

The Transport Slicing integration tests consist of eight (8) test cases.  Each test case is broken down into a sequence of measurable checkpoints. These checkpoints are RESTful APIs, each of which has a specific set of input and output parameters that can be measured against.  The checkpoints are illustrated below.

...

#Test caseSDNC-DCAEDCAE-POLICYPOLICY-SO
1topology discoveryN/AN/AN/A
2test case #2 - #8
  1. Check whether SDNC calls DCAE upon receiving a performance monitoring notification event
1.  Check whether DCAE calls POLICY to read the notification events data.
  1. Check whether POLICY calls SO to adjust the monitored value.


#Test caseUUI-AAIAAI-DCAEDCAE-POLICYPOLICY-SO
3test case #9
  1. When user tries to modify service setup, UUI modify service-instance attributes
1. Upon receiving the AAI-EVENT, DCAE check the service state and start service modification process1. Upon receiving service modification request, POLICY sends down request to SO.
  1. Upon receiving modification request, SO sends down service modification request to downstream controllers.