The deployment location for the target VNFM can be added in the TNC-O UI, supplying the following information for infrastructure properties.
{
"vnfmServerUrl": "http://vnfm-test-harness:8297",
# Authentication details
"authenticationType": "BASIC",
"username": "xxx",
"password": "yyy"
}
{
"authenticationType": "BASIC",
"username": "xxx",
"password": "yyy"
}
{
"authenticationType": "OAUTH2",
"accessTokenUri": "https://vnfm:port/oauth2/token",
"client_id": "",
"client_secret": "",
"grant_type": "", # Optional
"scope": "" # Optional
}
{
"authenticationType": "COOKIE",
"authenticationUrl": "",
"username": "xxx",
"password": "yyy",
"usernameTokenName": "", # Optional (default: IDToken1)
"passwordTokenName": "" # Optional (default: IDToken2)
}
In order for the driver to receive lifecycle notifications from the VNFM, the following command should be run.
NOTES:
- It is important that the command is run from a location where the VNFM can be reached
- The address (for the driver) used in the content of the message below should be considered from the point of view of the VNFM itself (in cases where addresses or ports may be subject to NAT or proxying)
curl -X POST \
http://vnfm-address:port/vnflcm/v2/subscriptions \
-H 'Content-Type: application/json' \
-d '{
"callbackUri" : "https://sol003-lifecycle-driver:8296/vnflcm/v2/notifications",
"filter" : {
"notificationTypes" : [ "VnfLcmOperationOccurrenceNotification" ],
"operationStates" : [ "COMPLETED", "FAILED", "FAILED_TEMP", "ROLLED_BACK" ]
}
}'