Alexis,
In Casablanca release, SO has introduce new building block for MACRO VNF
instantiation orchestration via SDN-C generic resource api.
SO new process flows for instantiation includes:
· Macro Service Assign – pause
o NOTE: Enables the operations user the ability to review cloud params
resources prior for triggering create and activate
· Macro Service Activate (Create and Activate) – resume
OR
· Macro Service Create (Assign, Create and Activate)
o NOTE: Fully automated flows.
The SO macro instantiation flow is a generic standard building block that can
be used for any VNF orchestration.
The changes that are mainly need to enable the netbox capability is to
integrate the main generic resource api dg in SDNC to execute the netbox
capability sub dg when the controller blueprint information is returned and it
contains meta data related to the capability of netbox.
The generic-resource-api is used to assign cloud parameter assignment during
instantiation flow. The vf-module instantiation flow begins with the main DG,
self-serve-vfmodule-assign, when the svc-action = assign in the rpc request.
The main DG will call a series of sub-DGs according to the execution order of
all the predefined capability components, such as generate-name,
vlan-tag-assignment, netbox-ip-assignment.(new for Casablanca release)
Let's step through the swim lane diagrams on today's CDS call.
"capability-name": "netbox-ip-assignment",
"key-mapping": [
{
"payload": [
{
"param-name": "service-instance-id",
"param-value": "${service-instance-id}"
},
{
"param-name": "prefix-id",
"param-value": "${prefix-id}"
},
{
"param-name": "vf-module-id",
"param-value": "${vf-module-id}"
}
],
"output-key-mapping": [
{
"resource-name": "protected_private_net_cidr",
"resource-value": "${address}"
}
]
}
-----Original Message-----
From: Alexis de Talhouët [mailto:[email protected]]
Sent: Wednesday, August 22, 2018 4:23 PM
To: onap-discuss <[email protected]>
Cc: FREEMAN, BRIAN D <[email protected]>; TIMONEY, DAN <[email protected]>; MALAKOV,
YURIY <[email protected]>
Subject: [SDNC][SO] How to provision service-data within GENERIC-RESOURCE-API
Team,
In order for the self serve initiative to provide the vf-module-parameters
along with the capability-name, the service-data needs to be filled through
some mechanism (
restconf/config/GENERIC-RESOURCE-API:services/service/$serviceInstanceId/service-data)
Reason this needs to be done is so the sub-dg that will be created for
assign/unassign will be able to, based on the capability name, select the
proper plugin and trigger the right action.
I envisioned this being done at design time or an SO flow to take care of that;
and looking at current SO flows, it currently seems to be done in groovy
through SDNCAdapterWorkflowRequest.
Is that the route we want to pursue for our current initiative? If yes, does it
means I create a new BPMN subprocess specifically for this, e.g.
DoCreateVfModuleSelfServe, where the param and capability are passed through SO
request?
Or should I be using the new freshly added building block, such as
SDNCAssignTasks? but I’m very un-clear how to use it.
Could please shed some light on how should I proceed?
Thanks,
Alexi
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12031): https://lists.onap.org/g/onap-discuss/message/12031
Mute This Topic: https://lists.onap.org/mt/24923559/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
