...
Gather what you need:
Deck of Cards id prerequisite Card label instantiation Have the HEATtemplate along with the HEATenvironment file.
Card label post-instantiation Have the configuration template to apply on the VNF.
- XML for NETCONF
- JSON / XML for RESTCONF
- not supported yet - CLI
- Identify which values are static and dynamic
Create and fill-in the a table for all the dynamic values
Card label instantiation Here are the information to capture for each dynamic cloud parameters
Cloud Parameter name How to resolve Input for resolution Output of resolution Name as in the HEAT environment file Deck of Cards id how to resolve Card label Input Value will be given as input in the request.
Card label Default Value will be defaulted in the model.
Card label REST Value will be resolved by sending a query to the REST system
Auth URL URI Payload VERB Supported Auth type
Deck of Cards id auth Card label Token Use token based authentication
- token
Card label Basic Use basic authentication
- username
- password
Card label SSL Use SSL basic authentication
- keystore type
- truststore
- truststore password
- keystore
- keystore password
http(s)://<host>:<port> /xyz JSON formatted payload HTTP method Card label SQL Value will be resolved by sending a SQL statement to the DB system
Type URL Query Username Password Only maria-dbsupported for nowSQL statement Deck of Cards id input Card label REST List of placeholders used for
- URI
- Payload
Card label DB List of placeholders used for
- SQL statement
This is the expected result from the system, and you should know what value out of the response is of interest for you.
If it's a JSON payload, then you should think about the json path to access to value of interest.
Data dictionary
...
Workflows
The following workflows are contracts established between SO, SDNC and CDS to cover the instantiation and the post-instantiation use cases.
...