Testing Assumptions
A single VES Collector will be pre-deployed for all flows
DCAE project will 'hand-craft' a blueprint for TCA deployment using Kubernetes
SDC (DCAE-Design Studio) will not generate the blueprint programmatically
CLAMP will deploy an instance of TCA microservice for each use case (vCPE, vFirewall, etc.)
CLAMP will create the initial configuration policy for TCA and make any subsequent updates to it through API to Policy
Initial TCA configuration policy and subsequent updates will be sent by policy to DCAE policy handler
TCA microservice will process updates to its configuration policy
TCA microservice will not be capable of processing multiple configuration policies
Preparation for Testing
DCAE
Deploy VES Blueprint to DCAE which will deploy the VES collector
Generate TCA Blueprint
Confirm validity of previously-generated (and uploaded to Policy) TCA Policy model
Policy
Make sure that policy model for TCA is already uploaded to Policy GUI - this should be done as part of initial Policy container deployment
CLAMP
Store policy model for TCA in local repository
Testing Flow
This sequence of flows below will be repated for all services being tested (vCPE, vFirewall, vDNS)
Flow 1: Design and Distribute First Control Loop
![](/download/attachments/23266662/Creating%20the%20service%20design%20in%20SDC%20and%20distributing%20design%20artifacts.png?version=1&modificationDate=1522948499000&api=v2)
Step Range | Description | Status | Notes |
---|
1-3 | Upload artifact and distribute | Tested |
|
4 | Process distribution in CLAMP | Tested |
|
5-6 | Process distribution in DCAE | Tested |
|
|
|
|
|
@startuml
title Creating the service design in SDC and distributing design artifacts
actor SDC_Tester
participant SDC
participant CLAMP
box "DCAE controller"
participant "Service Change Handler" as SCH
database Inventory
end box
autonumber
note over SDC_Tester: Closed loop 1
SDC_Tester -> SDC : Design vCPE service composed\nof one VNF resource
SDC_Tester -> SDC : Upload DCAE TCA blueprint\nas artifact
SDC_Tester -> SDC : Test, certify, distribute the service design
SDC -> CLAMP : Blueprint distribution
SDC -> SCH : Blueprint distribution
SCH -> Inventory : Save blueprint
@enduml
![](/download/attachments/23266662/Configure%20and%20Deploy%20First%20Control%20Loop.png?version=1&modificationDate=1522948627000&api=v2)
Step Range | Description | Status | Notes |
---|
1-3 | CLAMP Creates Policies | Tested |
|
4-11 | CLAMP Starts deployment in DCAE |
|
|
12-17 | CLAMP starts getting deployment status |
|
|
18-22 | DCAE gets and stores TCA policy |
|
|
23-30 | DCAE deploys TCA with config policy |
|
|
31-35 | CLAMP gets final status |
|
|
|
|
|
|
@startuml
title Configure and Deploy First Control Loop
actor CLAMP_Tester
participant CLAMP
participant Policy
box "DCAE controller"
database Inventory
participant "Deployment-handler" as DH
control "Cloudify+plugin" as Cloudify
participant "Policy-handler" as PH
database "Consul-kv" as consul
participant "Config-binding service" as CBS
control k8s
end box
participant TCA_Instance
autonumber
note over CLAMP_Tester: Closed loop 1
hnote right CLAMP_Tester: decided to install TCA
CLAMP_Tester -> CLAMP : Configure thresholds\n of control loop
CLAMP_Tester -> CLAMP : Configure actions\n of control loop
activate CLAMP
CLAMP -> Policy : Create Configuration\n and Operational Policies
CLAMP -> Inventory : Get DCAE Service Id\n based on Distributed Parameters
group install TCA_Instance
CLAMP -> DH : install instance of TCA with policy_id as input
activate DH
DH -> Inventory : get blueprint for TCA
Inventory --> DH : blueprint for TCA
DH -> Cloudify : install TCA_Instance
activate Cloudify
Cloudify --> DH : started: execution_id
DH --> CLAMP : started installation: url to get status
deactivate DH
CLAMP -> CLAMP : sleep
group CLAMP polling for installation status
CLAMP -> CLAMP : wake up
activate CLAMP #DarkSalmon
CLAMP -> DH : get status of installation
activate DH #DarkSalmon
DH -> Cloudify : get execution status
activate Cloudify #DarkSalmon
Cloudify --> DH : status: started
deactivate Cloudify
DH --> CLAMP : installation status: **processing**
deactivate DH
CLAMP -> CLAMP : sleep
deactivate CLAMP
end group
Cloudify -> PH : get policy\n by policy_id
PH -> Policy : /getConfig policy for policyName = policy_id
Policy --> PH : return found policy
PH --> Cloudify : policy by policy_id
Cloudify -> consul: store config with policies\n for TCA_Instance
Cloudify -> k8s: create instance of TCA
activate k8s
create TCA_Instance
k8s -> TCA_Instance: deploys
activate TCA_Instance
k8s --> Cloudify: created instance of TCA
deactivate k8s
deactivate Cloudify
TCA_Instance -> CBS: get Config\n and policies\n (**new API**)
CBS -> consul: get Config\n and policies
consul --> CBS: Config\n and policies
CBS --> TCA_Instance: Config and policies
TCA_Instance -->]: run
group CLAMP polling for installation status
CLAMP -> CLAMP : wake up
activate CLAMP #DarkSalmon
CLAMP -> DH : get status of installation
activate DH #DarkSalmon
DH -> Cloudify : get execution status
activate Cloudify #DarkSalmon
Cloudify --> DH : status: terminated
deactivate Cloudify
DH --> CLAMP : installation status: **succeeded**
deactivate DH
deactivate CLAMP
end group
hnote over CLAMP: installed TCA
deactivate CLAMP
end group
@enduml
Flow 3: Run Control Loop
![](/download/attachments/23266662/run_flow_cl.png?version=1&modificationDate=1522868126000&api=v2)
@startuml
title This is the flow that will be tested in Beijing
participant VNF
participant VES_Collector
participant TCA_Instance1
participant Policy
participant AppC
autonumber
VNF -> VES_Collector : VES Message\nmeasurementsForVfScaling
VES_Collector -> TCA_Instance1 : VES Message\nmeasurementsForVfScaling
TCA_Instance1 -> Policy : Signature ONSET Message
Policy -> AppC : Action
AppC -> VNF : Action
note left
VNF action taken which
corrects the condition
end note
VNF -> VES_Collector : VES Message\nmeasurementsForVfScaling
note left
Time passes until next
message
end note
VES_Collector -> TCA_Instance1 : VES Message\nmeasurementsForVfScaling
TCA_Instance1 -> Policy : Signature ABATE Message
@enduml
Flow 4: Update Control Loop by Reconfiguring TCA
![](/download/attachments/23266662/Update%20Control%20Loop%20by%20Reconfiguring%20TCA.png?version=1&modificationDate=1522948811000&api=v2)
@startuml
title Update Control Loop by Reconfiguring TCA
actor CLAMP_Tester
participant CLAMP
participant Policy
box "DCAE controller"
participant "Policy-handler" as PH
participant "Deployment-handler" as DH
control "Cloudify+plugin" as Cloudify
database "Consul-kv" as consul
participant "Config-binding service" as CBS
end box
participant TCA_Instance
autonumber
CLAMP_Tester -> CLAMP : Update control\n loop settings
CLAMP -> Policy: update policy
group policy update
Policy -> PH : notify about\n updated policy
activate PH
PH -> Policy : /getConfig for\n policyName
Policy --> PH : policy body
PH -> DH : policy updated
deactivate PH
activate DH
DH -> Cloudify : get components info
Cloudify --> DH : components
DH -> DH : find TCA_Instance\n by policy_id
DH -> Cloudify : policy updated\n on TCA_Instance
deactivate DH
activate Cloudify
Cloudify -> consul: store updated\n policies\n for TCA_Instance
deactivate Cloudify
end
==TCA is expected to periodically poll for latest policies==
group polling for policy changes
activate TCA_Instance
TCA_Instance <-]: wake up
activate TCA_Instance #DarkSalmon
TCA_Instance -> CBS: get Config\n and policies\n (**new API**)
activate CBS #DarkSalmon
CBS -> consul: get Config\n and policies
activate consul #DarkSalmon
consul --> CBS: Config\n and policies
deactivate consul
CBS --> TCA_Instance: Config and\n policies
deactivate CBS
hnote over TCA_Instance: check if policy\n changed
TCA_Instance -> TCA_Instance: act on\n changed\n policy
TCA_Instance -->]: run
deactivate TCA_Instance
end
@enduml
Run Control Loop Again
After the control loop is reconfigured, we test that the changes have taken effect. This is done by running the control loop again. For example, if the threshold value was increased, we would initiate an event with the old threshold value, and see that the signature is no longer produced.
Flow 5: Stop and Restart Control Loop
![](/download/attachments/23266662/flow6.png?version=1&modificationDate=1522358584000&api=v2)
@startuml
participant CLAMP
actor CLAMP_Tester
participant Policy
autonumber
CLAMP_Tester -> CLAMP : Stop operation\nof control loop
CLAMP -> Policy : Disable Operational Policy
participant VNF
participant VES_Collector
participant TCA_Instance1
participant AppC
autonumber
group Runtime Test
VNF -> VES_Collector : VES Message\nmeasurementsForVfScaling
VES_Collector -> TCA_Instance1 : VES Message\nmeasurementsForVfScaling
TCA_Instance1 -> Policy : Signature ONSET Message
end
CLAMP_Tester -> CLAMP : Restart operation\nof control loop
CLAMP -> Policy : Enable Operational Policy
participant VNF
participant VES_Collector
participant TCA_Instance1
participant AppC
autonumber
group Runtime Test
VNF -> VES_Collector : VES Message\nmeasurementsForVfScaling
VES_Collector -> TCA_Instance1 : VES Message\nmeasurementsForVfScaling
TCA_Instance1 -> Policy : Signature ONSET Message
Policy -> AppC : Action
AppC -> VNF : Action
VNF -> VES_Collector : VES Message\nmeasurementsForVfScaling
VES_Collector -> TCA_Instance1 : VES Message\nmeasurementsForVfScaling
TCA_Instance1 -> Policy : Signature ABATE Message
end
@enduml
Dashboard