Page Comparison

...

...

5) BBS Policy calls SDN-C GR-API to create new AccessConnectivity VF [Needs to find out which Access SDN M&C to use, how?]

...

6) BBS Policy calls SDN-C GR-API to update InternetProfile VF

...

7) BBS Policy updates  {{bbs-cfs-service-instance-UUID}} orchestration-status [ assigned --> created ]

...

Basic steps (CPE Authentication):

8) BBS policy triggered by DMaaP message from BBS uS: topicName=unauthenticated.DCAE_CL_OUTPUT, policyName=CPE_Authentication, policyScope=policyScopeCpeAuth

[
    "{\"closedLoopEventClient\":\"DCAE.BBS_event_processor_mSInstance\",\"policyVersion\":\"1.0.0.5\",\"policyName\":\"CPE_Authentication\",\"policyScope\":\"policyScopeCpeAuth\",\"target_type\":\"VM\",\"AAI\":{\"cpe.old-authentication-state\":\"outOfService\",\"cpe.new-authentication-state\":\"inService\",\"cpe.swVersion\":\"1.2.3\",\"service-information.hsia-cfs-service-instance-id\":\"1923eaa8-8ab7-49ef-b4c2-e185efbbe832\"},\"closedLoopAlarmStart\":1552997462,\"closedLoopEventStatus\":\"ONSET\",\"closedLoopControlName\":\"clControlNameCpeAuth\",\"version\":\"1.0.2\",\"target\":\"vserver.vserver-name\",\"requestID\":\"d76541f3-7f55-4c80-b0a0-ec5dee2a56cb\",\"from\":\"DCAE\"}"
]

9) If swVersion is present in the VES message's Additional information "swVersion", the BBS policy updates the PNF instances swVersion field. [not needed for demo]

10) The BBS policy changes the CFS service instance's orchestration status [ created --> active ]

...

curl -X GET \
 'https://aai.api.simpledemo.openecomp.org:30233/aai/v11/business/customers/customer/{{business-customer-UUID}}/service-subscriptions/service-subscription/{{bbs-cfs-service-type}}/service-instances/service-instance/{{bbs-cfs-service-instance-UUID}}?depth=all' \
 -H 'Accept: application/json' \
 -H 'Authorization: Basic TW9kZWxMb2FkZXI6TW9kZWxMb2FkZXI=' \
 -H 'Content-Type: application/json' \
 -H 'Postman-Token: f799a782-ce93-4179-8739-71174aeb1028' \
 -H 'X-FromAppId: AAI' \
 -H 'X-TransactionId: jimmy-postman' \
 -H 'cache-control: no-cache'

Response:

{
 "service-instance-id": "535ee766-09ea-4815-a186-a316c393e849",
 "resource-version": "1553614797867",
 "orchestration-status": "assigned",
 "relationship-list": {
	 "relationship": [
		 {
		 "related-to": "pnf",
		 "relationship-label": "org.onap.relationships.inventory.ComposedOf",
		 "related-link": "/aai/v14/network/pnfs/pnf/pnf",
		 "relationship-data": [
		 	{
		 		"relationship-key": "pnf.pnf-name",
		 		"relationship-value": "pnf"
		 	}
	 		]
	 	}
	 ]
 },
 "metadata": {
 	"metadatum": [
 		{
 			"metaname": "cvlan",
 			"metaval": "1005",
			"resource-version": "1553614797883"
 		},
 		{
			"metaname": "svlan",
 			"metaval": "100",
			"resource-version": "1553614797909"
 		}
 	]
 }	
}

4) BBS Policy calls SDN-C GR-API to delete AccessConnectivity VF ID

5) BBS Policy calls SDN-C GR-API to create new AccessConnectivity VF [Needs to find out which Access SDN M&C to use, how?]

6) BBS Policy calls SDN-C GR-API to update InternetProfile VF

7) BBS Policy updates  {{bbs-cfs-service-instance-UUID}} orchestration-status [ assigned --> created ]

Basic steps (CPE Authentication):

8) BBS policy triggered by DMaaP message from BBS uS: topicName=unauthenticated.DCAE_CL_OUTPUT, policyName=CPE_Authentication, policyScope=policyScopeCpeAuth

[
    "{\"closedLoopEventClient\":\"DCAE.BBS_event_processor_mSInstance\",\"policyVersion\":\"1.0.0.5\",\"policyName\":\"CPE_Authentication\",\"policyScope\":\"policyScopeCpeAuth\",\"target_type\":\"VM\",\"AAI\":{\"cpe.old-authentication-state\":\"outOfService\",\"cpe.new-authentication-state\":\"inService\",\"cpe.swVersion\":\"1.2.3\",\"service-information.hsia-cfs-service-instance-id\":\"1923eaa8-8ab7-49ef-b4c2-e185efbbe832\"},\"closedLoopAlarmStart\":1552997462,\"closedLoopEventStatus\":\"ONSET\",\"closedLoopControlName\":\"clControlNameCpeAuth\",\"version\":\"1.0.2\",\"target\":\"vserver.vserver-name\",\"requestID\":\"d76541f3-7f55-4c80-b0a0-ec5dee2a56cb\",\"from\":\"DCAE\"}"
]

9) If swVersion is present in the VES message's Additional information "swVersion", the BBS policy updates the PNF instances swVersion field. [not needed for demo]

10) The BBS policy changes the CFS service instance's orchestration status [ created --> active ]

• newState: InService → orchestration status: Active
• newState: OutofService → orchestration status: Inactive (assigned)
  
  

Deploying the BBS Policy in APEX

At the moment, the BBS policy is included as an example under APEX in the Policy Framework. This means that every time the policy is changed, if the example deployment packed in APEX is used, there is a need to re-release the APEX image to pick up the use case changes. For example, some last minute changes have been raised in the JIRA below:

Image AddedPOLICY-1831 - BBS Apex Policy vendor --> manufacturer Submitted

Now that the new Policy Framework architecture is released, the BBS policy can be deployed using the new Policy architecture, see The ONAP Policy Framework and TO BE DELETED - refer to Dublin Documentation. Rather than having to update the APEX image every time the BBS policy changes, we should use the ONAP Policy Framework infrastructure to deploy the policy.

Pamela Dragosh David Perez CaparrosFormer user (Deleted) Let's discuss this.