VID instantiation flow
Use VID to trigger instantiation of an infrastructure service and its components using the following order:
- Create a service instance container
- Add a Network associated with the service (if part of service composition)
- Add a VNF associated with the service
- Add a volume group (where required)
- Add a VF module (where required)
Verify that prerequisite configuration is in the cloud and inventory
The cloud organization creates a tenant associated with a service. The VID user may want to verify that a tenant was created as well as confirm other cloud-related information prior to instantiating an infrastructure service.
customer and subscriptions for infrastructure services
For information about tenant creation, see Pre-Onboarding.
- Upload component-specific information
- Determine VID input
- Validate entitlements
Convert spreadsheet data
Convert each spreadsheet to a format that is acceptable to SDNC (.csv).
- Navigate to the directory that contains the spreadsheet.
- Use a conversion tool to convert the spreadsheet to .csv format.
- Provide the data to the SDNC administrator for upload.
Upload conversion output to SDNC
Upload the converted preload spreadsheets to SDNC. The spreadsheets contain information about the infrastructure service and/or network being instantiated.
- Navigate to the SDNC Admin Portal.
- Click the Preload Tools tab and select Preload VNF Network Data.
- Scroll to the bottom of the page and click Browse to select the converted spreadsheet created in Convert spreadsheet data.
- After selecting the spreadsheet, click Upload Network Worksheet CSV files.The GUI displays the uploaded data.
Trigger instantiation of an infrastructure service using VID
The service instance may contain multiple VNFs, and VNFs may contain one or more volume groups and/or VF modules.
- Log into the VID Home page.
- Click Browse SDC Service Models and search for the service to instantiate.The view displays service models in a DISTRIBUTED state.
- Select a service and click Deploy.A dialog box displays.
- Complete the fields indicated by the red star and click Confirm:
For the Instance Name field, for resources that are orchestrated into the cloud, such as Volume Group, VF Module, and Network, the Instance Name field is the heat stack name. Only alphanumeric characters and underscore "_" are allowed. The name must begin with an alphabetic character. Spaces are not allowed and must be replaced with the underscore "_" character.A status message displays that shows the MSO instantiation progress as well as any messages associated with the process.
- For the Subscriber Name, select the internal customer requesting the service. The subscriber name maps to the ID of the customer that owns this infrastructure service.
- For the Service Type, select the type required.
- All other input fields are derived from the TOSCA model associated with the service model being instantiated. These fields can vary from one service model to another.
The View/Edit Service screen displays the instantiated service model.
- Click Add VNF and select the appropriate VNF from the dropdown list.After selecting the VNF, the Add VNF dialog box displays.
- Complete all required fields in the dialog box and click Confirm:
A status message shows the MSO instantiation progress as well as any exceptions.
- Provide a name for the VNF
- Select the product family
- Select the cloud region to locate the VNF.
- Select the tenant available to the subscriber in the selected region
- In the View/Edit Service Instance view, click one of the following (where required) and select the appropriate option:
These options only display if the SDC Model permits VF modules or volume groups. Only add these options according to the SDC service model.For VF modules with supporting volume groups, create the volume groups first. Also make sure that the volume group name matches to the name of the VF module that supports it.The Add Volume Group or Add VF Module dialog box displays.
- Add Volume Group
- Add VF Module
- Complete the required fields and click Confirm.A status message shows the MSO instantiation progress as well as any exceptions.
- Repeat step 7 and step 8 to add another volume group or VF module.To create another VNF associated with this service, repeat steps 5 to 9 depending on the component requirements of this service.
VID instantiation errors
The service instance was successfully created.
The request has been accepted for processing, but the processing has not been completed.
The request may or may not be acted upon; it might be disallowed when processing actually takes place.
Many possible reasons not specified by the other codes, such as missing required parameters or incorrect format. The response body may include a further exception code and text.
HTTP 400 errors may be mapped to:
Authentication failed or was not provided. HTTP 401 errors may be mapped to:
The server has not found anything matching the Request-URI.
No indication is given of whether the condition is temporary or permanent.
Method Not Allowed
A request was made of a resource using a request method not supported by that resource, such as using PUT on a REST resource that only supports POST.
The request could not be completed due to a conflict with the current state of the resource.
Internal Server Error
The server encountered an internal error or timed out; please retry (general catch-all server-side error).
HTTP 500 errors may be mapped to:
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay.
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream process.