Map Service Elements to Existing Resources

DZS Cloud Orchestration allows users the capability to add existing resources into a running NS during instantiation. When you are instantiating the workflow is specific to the NSD from which the service is created.

Note: While an audit is in progress, do not attempt to add existing resources into a running NS.

The process of discovering resources and mapping them to service elements during instantiation changes depending on how you build your service. An operator can map existing resources during instantiation with CNFs or with SOL003 based VNFs.

Map Service Elements to Existing Resources during Instantiation

Note: The NSD in the below instantiation workflow is a ping_pong_nsd with VNFs.

  1. On the Launchpad menu, click SERVICES.

  2. Click the   button to edit a service.

    An account wizard appears. Fill in the appropriate details for the specific service. The right side of the wizard screen displays what can be changed using this edit option.

    Note: You cannot navigate forward without filling in required fields (*). The Next >> button will not function if the previous required field isn’t populated. The Save button allows you to save your NSR config content and edit it later if you are not ready to Instantiate.

  3. Provide the following details in the Service Instantiation step:

    • *Name - Name of the service

    • Description - Details about this service

    • Map Existing Resources - Service elements will be mapped to existing resources. Choose True from the drop-down menu in this field to map existing service elements to existing resources.

    The steps to instantiate a service that will use existing resources mapped to elements defined in the service are customized for your NSD. The Network Service Instantiation section includes more information on designing and editing specific variables in an NS prior to instantiation. Two of the steps specific to this process are Element Selection and Preexisting VLDs.

    Note: There are steps to configure each VNF elected in the Element selection step.

  4. Click Next>> to provide the following details in the Element Selection step:

    • CNFs or VNFs - Selected cnfds or vnfs to which an existing resource will be attached. You can select an option for each CNFD or VNFD that is part of the NSD. The CNFs/VNFs drop-down menu only displays available resources after running discovery in the datacenter. Click DISCOVER RESOURCES in the Instantaiton Wizard.

      Note: The Discovery Status changes to discovering and the discover process can take several minutes. An operator can continue to perform other functions such as save, close, etc. while the discovery process takes place. Once discovery is complete, continue with the steps to instantiate.

  5. Click Next>> to provide the appropriate details in the VLDs step. The fields in this page correspond to the segment profiles set up in Profile Configuration.

  6. Click Next>> to provide following details in the CNFD/VNFD step. The CNFD and/or VNFD that you choose is associated with the discovered set of resources.

    • *VM Resource Name - Name of existing VM. There is a section in this step for each VDU defined in the VNFD.

    • *VM Delete On Terminate - Should remove VM on terminate. (True or False)

    • *Interface Resource Name - Name of existing Interface.

    • *Interface Delete On Terminate - Should remove interface on terminate. (True or False)

      Note: If the vdu in your service has volumes defined, then they will appear in this ping_vnfd details page.

Map Service Elements to Existing Resources during Instantiation with CNFs

DZS Cloud Orchestration supports the ability to map existing resources during instantiation with CNFs. A user can run Discovery on a Kubernetes Datacenter account to identify existing resources. An existing resource can then be mapped to an appropriate CNF that is part of a Network Service being instantiated by DZS.

Prior to mapping service element to existing resources, an operator must import a helm chart to automatically create CNFDs and create a service.

  1. On the Launchpad menu, select CATALOG > NSD LIST. The NSD CATALOG page opens.

  2. Select a network service descriptor from the catalog and click to the left of the descriptor to edit parameters for the NSD.

  3. Click Update.

  4. Next, click to create the Service.

  5. On the Configuration page, click and the Service Instantiation wizard appears. Fill in the appropriate details for the specific service.

  6. Provide the following details in the Service Instantiation step:

    • *Name: Name of the service

    • Description: Details about this service

    • Map Existing Resources: Service elements will be mapped to existing resources. Choose True from the drop-down menu in this field to map service elements to existing resources.

    The steps to instantiate a service that will use existing resources mapped to elements defined in the service are customized for your NSD. The Network Service Instantiation section includes more information on designing and editing specific variables in an NS prior to instantiation. The required steps are to discover resources and then select the NFs to which an existing resource will be attached. Once a NF is selected a new step will be added to the Service Instantiation Wizard for each NF. When you get to this step you will identify the preexisting release name and determine if the release is removed when terminating the service.

    Note: There are steps to configure each CNF elected in the Element selection step.

  7. Click Next >> and provide appropriate details for each step. Once you reach the Element Selection Step, provide the following details for your service.

    • NFs: Selected nfs to which an existing helm release will be attached. You can select an option for each CNFD that is part of the NSD. The drop-down menu will only show available resources if you run discovery on a datacenter.

    • In the Resources Discovery section click and the Discovery Status changes to discovering. The discover process can take several minutes. An operator can continue to perform other functions such as save, close, etc. while the discovery process takes place. If the Kubernetes resources under the preexisting release are not ready, then the CNF instantiation fails.

      • Note: If discovery is already done at the Datacenter level, then you can skip this step.

  8. After selecting an NF, a NF section appears in the Service Instantiation Wizard. On that screen, provide the following details:

    • *Preexisting Release Name: Name of the existing helm release.

    • Delete On Terminate: Select True or False to identify if the helm releases are deleted when you terminate the Network Service.

  9. Click Save.

Map Service Elements to Existing Resources during Instantiation with SOL003 based VNFs

DZS Cloud Orchestration now supports the ability to map existing resources, during service instantiation, to a functioning VNFM. This VNFM must support the Or-VNFM interface defined by the ETSI specs SOL003/IFA 007. At the time of instantiation, the VNFM account needs to be selected to manage an associated VNF. See Add a VNFM Account for specifics on creating an Or-VNFM Account. The Or-VNFM account name is specified as part of the instantiation process. After creating an account, an operator can run an account discovery on a VNFM account to identify resources and map the specific resources to a VNFM.

After adding an VNFM account, run an account discoveryto identify resources and map the specific resources to a VNFM. Click in the CONNECTORS section of the Launchpad menu for VNFM accounts.

Scroll down to the bottom of the screen to see the status and discovery details.

Note the vnf-instance-name from the Discovery Info. This name is necessary to add in the vnf-instance-id section in the Service Instantiation Wizard during Instantiation.

After discovery is complete, the VNFM instance only display the VNF instances that are present on the VNFM. Prior to instantiation, an operator must:

  1. On the Launchpad menu, select SERVICES > SERVICE LIST.

  2. Click to open a service and then click to edit the service.

    A Service Instantiation wizard appears. Fill in the appropriate details for the specific service. The right side of the wizard screen displays what can be changed using this edit option.

    Note: You cannot navigate forward without filling in required fields (*). The Next >> button will not function if required fields are not populated. The Save button allows you to save your NSR config content and edit it later if you are not ready to Instantiate.

  3. Provide the following details in the Service Instantiation step:

    • *Name: Name of the service.

    • Description: Details about this service.

    • Map Existing Resources: Service elements will be mapped to existing resources. Choose True from the drop-down menu in this field to map service elements to existing resources.

    The steps to instantiate a service that will use existing resources mapped to elements defined in the service are customized for your NSD. The Network Service Instantiation section includes more information on designing and editing specific variables in an NS prior to instantiation. The required steps are to discover resources and then select the NFs to which an existing resource will be attached. Once the NF is select, then the NF will appear in the Service Instantiation Wizard.

  4. Click Next >> to provide the default datacenter, the datacenter on which to instantiate the vnf and the VNFM account to use when instantiating the service VNF in the Placement step. The Placement step does not appear if there is only one Datacenter option in the Datacenter Account.

  5. Click Next >> to provide the following details in the Element Selection step:

    • NFs: Selected nfs to which an existing resource will be attached. You can select an option for each VNFD that is part of the NSD. The drop-down menu will only show available resources if you run discovery on a datacenter.

    • In the Resources Discovery section click and the Discovery Status changes to discovering. The discover process can take several minutes. An operator can continue to perform other functions such as save, close, etc. while the discovery process takes place.

  6. Click Next >> to provide the appropriate details in the pong_vnfd step. There are no changes to this step to instantiate on a VNFM account.

  7. Click Next >> to provide the following details in the WSG step:

    • *VNF Instance ID: ID of existing VNF. If the vnf instance id does not exist, then the instantiation fails. The VNF Instance ID maps to the vnf-instance-name value found in the VNFM Account details on the CONNECTORS tab. See the beginning of Map Service Elements to Existing Resources during Instantiation with SOL003 based VNFs.

    • Delete On Terminate: Select True or False to identify if the resources are deleted when you terminate the Network Service.

  8. Click Save.

Next steps

Return to the Instantiate the network service section in Create and Instantiate a Network Service