Heatbridge is currently a manual step that is executed after a VNF and its vfModules have been instantiated. What happens is that AAI is updated with details about the workload running in the cloud (e.g. vserver details, interface details, images, flavors).
There is interest in providing for this update to AAI to happen automatically instead of manually.
It is also of interest to provide this functionality generically for other cloud types. Let's call it something like 'AAI Workload Update' instead of 'heatbridge'.
Preferred approach
A couple possible approaches are shown below. Approach 1 is a bit more complex and attempts to enable support for other things like auditing (assume that means comparision of AAI configuration vs actual cloud configuration). Approach 2 - based on Bin Yang comments on Approach 1 - is simpler.
The preference here is for Approach 2. Perhaps the way to go is look at auditing as another feature which will need to be supported by Multicloud.
Approach 1
Following is a proposal for how the functionality could be done.
Step 1 (referring to diagram above)
In this step, a new SO workflow step makes a call to query the details about a workload. Based on details in SO's cloud site DB, a choice will be made to invoke 2a or 2b
Step 2a
This gerrit ( https://gerrit.onap.org/r/#/c/78155/ ) proposes a code change to perform Openstack specific AAI Workload Update functionality within the SO openstack adapter implementation. In this path, the workload detail query is handled by this code in SO.
Step 2b
Alternatively, for cloud sites that are set up to talk to Multicloud, the workload detail query is sent to Multicloud via an API (see below for more details). Multicloud has plugins for various cloud types, so the appropriate plugin will be selected to perform the query.
Step 3
The workload detail query result is returned. Regardless of path or cloud type, the detail is returned in a normalized format. Suggest this be in conformance with the AAI schema.
Step 4
The workload detail results can be passed along the workflow to the next step which performs the update to AAI. (other uses can be supported by separating query from AAI update, such as auditing)
Step 5
Perform the actual update to AAI. Logic could be supported in the workflow to determine whether this step must be performed and whether failure affects the success of the workload creation or not.
Notes on updates to the Multicloud API
The SO-MC infrastructure GET API (https://onap.readthedocs.io/en/casablanca/submodules/multicloud/framework.git/docs/specs/multicloud_infra_workload.html) needs to be extended to include the workload query details
- GET http://msb-iag.onap:80/api/multicloud/v1/<cloud-owner>/<cloud-region>/infra_workload/<workload-id>
- add the workload details to the response
- Or, since it's probably time consuming/expensive to query the workload details, maybe it's better to add a new query to the API
- What's best?
- GET http://msb-iag.onap:80/api/multicloud/v1/<cloud-owner>/<cloud-region>/infra_workload/<workload-id>?depth=all
- GET http://msb-iag.onap:80/api/multicloud/v1/<cloud-owner>/<cloud-region>/infra_workload_details/<workload-id>
- GET http://msb-iag.onap:80/api/multicloud/v1/<cloud-owner>/<cloud-region>/infra_workload/<workload-id>/details
- something else?
Approach 2
Here is another variation - taking into account Bin Yang's comments.
Along the 2b-3b sequence, SO invokes via a POST to Multicloud to trigger an AAI Update. SO can invoke a GET along step 6 to query the status of the AAI Update.
Note, in this approach AAI update is either performed via sequence 1,2a,3a,4a using SO Openstack adapter. Or, via sequence 1, 2b, 3b, 4b, 5, 6 using SO Multicloud adapter.
Other points
In addition to creating the workload details in AAI, there will need to be corresponding delete and update functions as well.