Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Gliffy Diagram
nameScaling Seq Diagram
pagePin1

...


Development Status

Here we will track the development status of each Requirement.  There should be a user story for every requirement within the project. 


 GoalProjectPTLJIRA Epic/User StoryRequirements

 Auto Scale Out

(High Priority)

 CLAMP Gervais-Martial Ngueko
 
Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCLAMP-189

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCLAMP-190

  1.  Create Threshold Crossing Alert (TCA) policies for Scaling of vDNS 
  2. Create Guard policies for Auto Scale Out 
 Policy Pamela Dragosh

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-842

  1. Create API call to SO with VNFInstanceID and VF_Module_Type as arguments
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyPOLICY-962
  2. Set up proper Guard Policies
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyPOLICY-963
  3. Compare number of instances to both Min and Max values
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyPOLICY-968
  4. Check Prov_Status = PROV
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyPOLICY-964
 SO Seshu Kumar Mudiganti

 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-677

  1. Create API for VID and Policy to call that will allow SO to scale a VNFC
  2. Create work flow to get all information needed to scale a VNFC
  3. Call existing OOF API for Homing and Capacity Checks (Low Priority)

Manual Scale Out Enhancements  

(High Priority)

AAI  New Customer Query to get IP Addresses of new VNFC Instance
APPC 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAPPC-431

  1. Process Healthcheck request from SO
  2. Process ConfigScaleOut action from SO
SDNC 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-235

  1. Process Healthcheck action from SO
  2. Import scaling changes from APPC so that all configuration changes may be done on VNFs controlled by SDNC
SO 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-677

 
 VID 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-248

  1. Update manual scaling use case to use the updated SO API for scaling
  2. Update GUI to get only the information needed for SO API
 VNFRQTS 

 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVNFRQTS-261

  1.  Update Scaling Documentation with any changes as well as more detailed requirements

Controller Type

(Medium Priority)

SO 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-677

  1.  Add a an editable table for mapping VNF_Controller _type to VNF_Type

Homing and Capacity 

(Low Priority)

OOF 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-295

  1.  If possible, reuse existing R2 process for Homing and Capacity check prior to instantiating new VF_Module
SO 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-677

  1.  Call existing OOF process for Homing and Capacity Check



Testing

Current Status

  1. Creating Test Plans 


End to End Flow To Be Tested



Test Cases and Status

Closed Loop Scaling

#Test Case

Status

101

DCAE Sends Policy a Scale Out Event when threshold is crossedNOT YET TESTED
102Policy checks Guard policies to see if it should tell SO to ScaleNOT YET TESTED
103Policy Sends Scale Out Request to SONOT YET TESTED

Healthcheck

#Test CaseStatus
201SO Sends Healthcheck request to DMaaPNOT YET TESTED
202APPC/SDNC picks up Healthcheck request from DMaaPNOT YET TESTED
203APPC/SDNC sends RESTCONF Healthcheck to vLBNOT YET TESTED
204vLB returns Healthcheck status to APPC/SDNCNOT YET TESTED
205SO receives Healtcheck resultsNOT YET TESTED

Instantiation

#

Test Case

Status
301SO sends CreateVF-Module to AAINOT YET TESTED
302SO Sends VFModule Resource Assignment Request to SDNCNOT YET TESTED
303SDNC does Heat and Resource AssignmentNOT YET TESTED
304SDNC writes information to AAINOT YET TESTED
305SO executes Create VF_Module via Heat NOT YET TESTED
306New instance of vDNS component is createdNOT YET TESTED
307So updates AAI with Heatstack IDNOT YET TESTED

Configuration


#Test CaseStatus
401

402

403

Healthcheck

#Test CaseStatus
1