Name of Use Case:
vFW/vDNS
...
| Expand |
|---|
|
cl @startuml
title vFW Closed Loop
participant vPG
participant vFW
participant vSN
vPG -> vFW : traffic
vFW -> vSN : traffic sink
|||
note left: vPG automatically \nincreases traffic based on script
vFW -> DCAE : VES Telemetry
DCAE -> Policy : Threhold Crossing (High)
Policy -> Policy : pattern-match-replace vFW to vPG data
Policy -> APPC : ModifyConfig (lower PG traffic)
APPC -> vPG : Netconf modify config
note right : reduce number of traffic streams
vPG -> vFW : lower traffic
vFW -> DCAE : VES Telemetry
DCAE -> Policy : Event cleared (lower traffic)
@enduml
|
1.4 Close Loop vDNS
This flow has the APPC to AAI query which moves the query from Policy to APPC.
There are no changes in the vDNS flow for R1. Originally we looked at moving the query from Policy to APPC but there were design details on executing the dnsscaling API call and whether APPC should call SO or MultiVIM directly that were not able to work out in time for R1. So we will continue with the original flow.
vDNS Flow (R1)
Image Added
Future Flow to be considered (After R1)
| Expand |
|---|
|
@startuml
title vDNS Closed Loop
participant vPG
participant vLB
participant vDNS1
participant vDNS2
vPG -> vLB : traffic (high)
vLB -> vDNS1 : traffic sink
|||
note left: vPG automatically \nincreases traffic based on script
vLB -> DCAE : VES Telemetry (Traffic/vDNS)
DCAE -> Policy : Threhold Crossing (High)
Policy -> APPC: Scale VNF
APPC -> AAI : Named Query to map vLB to dnsscaling data
APPC -> SO : dnsscaling instantiate
SO -> AAI : inventory update
SO -> SDNC : Generic VNF API\n(reserved)
SO -> Multi_VIM: dnsscaling Heat template + ENV file
Multi_VIM -> OS_Heat : dnsscaling Heat template + ENV file
OS_Heat -> KVM : vDNS Infrastructure instantiation
KVM -> vDNS2 : Nova/Neutron Instantiation
KVM -> OS_Heat : complete
OS_Heat -> Multi_VIM : complete
Multi_VIM -> SO : complete
note right : SO may poll for completion
SO -> SDNC: Generic VNF API\n(activated)
note right : on failure from Openstack SO issues rollback to SDNC
SDNC -> AAI : L3 Network resource update
|||
note right : Alternative with TOSCA based dnsscaling
APPC -> AAI : inventory update
APPC -> SDNC : Generic VNF API\n(reserved)
APPC -> Multi_VIM : scale out request (Need to confirm since vFW/vDNS do not have VNFM)
Multi_VIM -> OS_Heat : dnsscaling Heat template + ENV file
OS_Heat -> KVM : vDNS Infrastructure instantiation
KVM -> vDNS2 : Nova/Neutron Instantiation
KVM -> OS_Heat : complete
OS_Heat -> Multi_VIM : complete
Multi_VIM -> APPC : complete
note right : APPC may poll for completion
APPC -> SDNC: Generic VNF API\n(activated)
note right : on failure from Openstack APPC issues rollback to SDNC
SDNC -> AAI : L3 Network resource update
|||
vLB -> DCAE : VES Telemetry
DCAE -> Policy : Event cleared (lower traffic)
@enduml |
...
1.5 CLAMP creation of control loops (new in R1)
Image Removed
Image Added
| Expand |
|---|
|
@startuml
title CLAMP Closed Loop Design for vFW and vDNS \nvFW and vDNS use the same flows but they are separate VNFs/Services
participant ONAP_User
participant CLAMP
participant SDC
ONAP_User -> CLAMP : Create Control Loop from Template
CLAMP -> SDC : Query for Services and VNFs
ONAP_User -> CLAMP : Choose Service and VNF
CLAMP -> SDC : Query for Alarm data from VNFs
ONAP_User -> CLAMP : Create Operational Policy\nChooses Chain of Actions\nSave Policy
ONAP_User -> CLAMP : SelectString matcher Select TCA box,\nclicks and creates one or more \nassociated signature rules.\nAssociates them with the operational policy \ncreated earlier
ONAP_User -> CLAMP : Repeat as Operational Policy/Signature as needed\n(total 1 vFW, 1 vDNS)
CLAMP -> Policy : Create Operational Policies (DROOLS)
CLAMP -> Policy : Create String Matcher to Policy association
note right: executed for both vFW and vDNS policies
CLAMP -> SDC : Distribute Blueprint
ONAP_User -> SDC : check in, test, certify, distribute Blueprint
SDC -> DMaaP : Distribute control loop for DCAE
DMaaP -> DCAE : Control Loop Blueprint
CLAMP -> DMaaP : Poll for distribution complete
@enduml |
Image Removed
| Expand |
|---|
|
@startuml
title CLAMP Closed Loop Design (Option A) for vFW and vDNS \nvFW and vDNS use the same flows but they are separate VNFs/Services\n Uses Policy GUI
participant ONAP_User
participant CLAMP
participant SDC
ONAP_User -> CLAMP : Create Control Loop from Template
CLAMP -> SDC : Query for Services and VNFs
ONAP_User -> CLAMP : Choose Service and VNF
CLAMP -> SDC : Query for Alarm data from VNFs
ONAP_User -> CLAMP : Create Operational Policy\nChooses Chain of Actions\nSave Policy
CLAMP -> PolicyGUI : Redirect to Policy GUI
ONAP_User -> PolicyGUI : SelectString matcher box,\nclicks and creates one or more \nassociated signature rules.\nAssociates them with the operational policy \ncreated earlier
note right : DCAE Design Template has default policies already defined/expressed
ONAP_User -> PolicyGUI : Repeat as Operational Policy/Signature as needed\n(total 1 vFW, 1 vDNS)
PolicyGUI -> Policy : Create Policies
PolicyGUI -> Policy : Create String Matcher to Policy association
note right: executed for both vFW and vDNS policies
CLAMP -> SDC : Distribute Blueprint
ONAP_User -> SDC : check in, test, certify Blueprint
note right: this could take quite a while (minutes to days) due to user interactions
ONAP_User -> SDC : Distribute Blueprint
|||
SDC -> DMaaP : Distribute control loop for DCAE
DMaaP -> DCAE : Control Loop Blueprint
CLAMP -> DMaaP : Poll for distribution complete
@enduml |
...
Override the default ssh key in the env file to be able to ssh to any of the 3 VMs instantiated by the demo.
...