Contents

1   Description

This instruction describes how to instantiate a Virtualized Network Function (VNF) using Ericsson Orchestrator (EO).

Instantiation in EO consists of preparatory steps, during which HOT files, the VNF configuration file, and other Cloud infrastructure-related input are provided. The actual instantiation is done by EO triggering an instantiation workflow in VNF-LCM.

For more information about the VNF-LCM, see MTAS VNF Lifecycle Management.

2   Procedure

2.1   Instantiate a VNF

Prerequisites

• No tools are required.
• The following condition must apply:
  • The Onboard procedure is completed. For more information, see Onboard VNF Package on EO.
  • The user is logged on to EO.

Steps

1. In the EO, start a new Virtual Application (VAPP).
2. In Resources > Packages, select the package to deploy and click Deploy.
3. On the Search for Offers view, select values for the mandatory fields, and click Next.
4. On the Choose Offer view, select the VNF package to be used for instantiation, and click Next.
5. On the Set VIM Criteria view, click Next.
6. On the Choose VIM Zone view, select the desired VIM zone, and click Next.
7. On the Enter Attributes view, provide values for the fields of the VAPP Attributes tab:
   • Virtual Application Name, which is also the name of the Heat stack
   • VNF Manager - The VNF Manager chosen during onboarding is pre-selected.
   • Flavor - The virtual hardware configuration of the VNF, for example: number of vCPUs and memory size.

     Note:  

     The value provided for Flavor is not used at this point, but as it is a mandatory field, a dummy value must be provided.

     
     
8. On the Enter Attributes view, provide the VNFD_Wrapper.json file on the Configuration tab. It is possible to overwrite the VNFD_Wrapper.json file provided during onboarding either by uploading an updated file or by modifying the attribute values on the Configuration tab.
9. Click Submit Order to finalize instantiation.
   Result:
   On the opening window, click View Asset List to check the status of the instantiation order. EO triggers an instantiation workflow in VNF-LCM, and the VNF becomes visible in the used VNFM.

   Note:  

   If the EO and the VNF-LCM are in a mutually granting connection, the new instance appears in the VNF-LCM after a successful instantiation from the EO.

   
   

2.2   Troubleshooting

If the workflow execution fails, inspect the relevant logs to identify the cause of the failure.

Steps

1. Increase the log level from INFO to DEBUG. For information on how to change log level, see VNF-Lifecycle Manager System Administration Guide, 1543-APR 901 0578.
2. Inspect the following logs to identify the cause of the failure:
   • Jboss Server log: /ericsson/3pp/jboss/standalone/log/server.log
   • System log: /var/log/messages
   • Workflow log: the Workflow Log view in the VNF-LCM
3. If a problem cannot be solved, consult the next level of maintenance support and provide the logs. Further actions are outside the scope of this instruction.