Scale Out Use Case Tracking
- Scott Blandford
- Marco Platania
- Scott Seabolt
JIRA Development Status
Project | PTL | JIRA Epics | |
|---|---|---|---|
1 | AAI | @James Forsyth | |
2 | APPC | @Randa Maher | |
3 | MultiCloud | @Former user (Deleted) | NA |
4 | OOF | @Sarat Puthenpura | OPTFRA-34: OOF support for VNF auto scale out use caseClosed |
5 | SDC | @Michael Lando | |
6 | SDNC | @Dan Timoney | |
7 | SO | @Seshu Kumar Mudiganti | SO-391: SO should support scaling of Network services and VF modulesClosed |
8 | UUI | @Tao Shen | |
9 | VFC | @Yan Yang | |
10 | VID | @Ofir Sonsino | |
11 | VNFRQTS | @Steven wright | VNFRQTS-158: VNF Requirements improvements to support Beijing Functional RequirementsClosed |
12 | vLB/vDNS use case | @Marco Platania | INT-431: The vLB/vDNS use case should be updated to support the manual scale out use caseClosed |
Testing
Current Status
Major Blocker: APPC is not getting configuration data for the vLB (There was a requirements gap/conflict as to how this would work and there is not enough time to fix it in Beijing. This problem will be worked in Casablanca)
VID-230: VF Scaling workflow not triggeredClosed Payload to SO is not being configured properly. It could be a problem with the level of ModelInfo
VID-226: PROV_STATUS of VNFs are not being set to PROV. This was a process issue. Prov_status is supposed to be moved to PROV by an operator after NVT test. Since there is no operator in our test environment it never got changed. This was fixed by modifying "Robot" to update the field. (Currently working around issue by not applying PROV_STATUS filter on VID) VID-226: Manual scale out operation not scheduled/startedClosed
All other test cases are to be tested for Beijing Release.
End to End flow to be tested
Testing Components and Status
Test | Status | |
|---|---|---|
| 1 | Onboard vLB to APPC via CDT | Complete |
| 2 | Can configure Manual Scaling request in VID | Complete |
| 3 | VID Sends a Manual Scale Out Request to SO | Complete |
| 4 | SO Recieves Manual Scale Out request | Complete |
| 5 | SO Sends Healthcheck request to DMaaP | Not yet tested |
| 6 | APPC/SDNC pick up Healthcheck request from DMaaP | Not yet tested |
| 7 | APPC/SDNC sends RESTCONF Healthcheck to vLB | Not yet tested |
| 8 | vLB returns Healtcheck status to APPC/SDNC | Not yet tested |
| 9 | SO receives HealthCheck results | Not yet tested |
| 10 | SO sends CreateVF-Module() to A&AI | Complete |
| 11 | SO Sends VF-Module Resource Assignment Request to SDNC | Complete |
| 12 | SDNC does Heat & Resource assignment and sends to A&AI | Complete Not Adding IPADDR info |
| 13 | SO executes Create VF_Module via Heat | Complete |
| 14 | MultiCloud creates VM with vDNS on it | Complete |
| 15 | SO updates A&AI with Heatstack ID | Complete |
| 16 | SO sends ConfigScaleOut() to DMaaP | Complete |
| 17 | SDNC/APPC pick up ConfigScaleOut() from DMaaP | APPC Complete |
| 18 | SDNC/APPC will collect Configuration Data | Not yet tested |
| 19 | SDNC/APPC sends NETCONF Configuration Data to vLB | APPC Complete |
| 20 | APPC/SDNC sends Success Message to SO via DMaaP | APPC Complete |
| 21 | SO Sends HealthCheck Request to APPC/SDNC via DMaaP | Not yet tested |
| 22 | SDNC/APPC picks up HealthCheck from DMaaP | APPC COMPLETE (Manually by posting to DMaaP) |
| 23 | APPC/SDNC sends RESTCONF HealthCheck to vLB | APPC COMPLETE (Manually by posting to DMaaP) |
| 24 | vLB sends HealthCheck status to APPC/SDNC | APPC COMPLETE (Manually by posting to DMaaP) |
| 25 | SO receives HealthCheck Status | Not yet tested |