Deploy the Linux Appliance Instance

Create an application instance from a template that will be used as the NFV.

  1. In the left navigation menu of the ThinkAgile CP Cloud Controller, click Organization Templates.
  2. Click New Instance next to the CentOS 7.5 (64-bit) - Lenovo Template.
    Figure 1. CentOS 7.5 (64-bit) Template
    Screenshot showing the CentOS 7.5 (64–bit) Lenovo template
    Note:

    If the template is not displayed in Organization Templates, you can download it from the Lenovo Cloud Marketplace. For more information, see the following topic:

    Create a new instance from a template

  3. Enter a name in the Instance Name field under the Properties section (for example, VNET-01-NFV).
    Figure 2. New Instance Name
    Screenshot showing the Instance Name field
  4. In the Virtual Datacenter section, select the virtual datacenter where the application instance will run. This selection determines the migration zone and storage pool resources available for the application instance. Use the virtual datacenter (VDC-test) that was assigned to the VNET VNET-ID-01 when it was created.
    Figure 3. Virtual Datacenter assignment
    Screenshot showing the assignment of a virtual datacenter to the application instance
  5. In the Storage section, select the storage pool for this application instance.
  6. In the Compute section, select the migration zone for this application instance.
  7. Configure the network as follows:
    1. Assign vNIC 0 to the Hypervisor VLAN (for example: Default 4091).
    2. Add a second vNIC by clicking Add vNIC.
    3. Assign vNIC 1 to VNET-ID-01.
    Figure 4. Modify Network Settings
    Image showing the Modify Network Settings option
  8. Click Create Instance.

    Once the instance starts you will be taken back to the Application Instances page.

  9. In the list of instances, click the application instance that was just created (VNET-01-NFV).
  10. Click the Profile tab and navigate to the Networking section. Click the Actions menu (Actions menu icon) next to each vNIC and click Edit Name.
    Figure 5. vNIC Edit Name
    Image showing the vNIC Edit Name option
    1. Rename vNIC 0 to be outside.
    2. Rename vNIC 1 to be inside.
    Figure 6. vNIC after renaming
    Image showing the vNICs after renaming them
  11. Record the MAC addresses for both vNICs for later use, as well as the IP address that was allocated to the outside vNIC.
    Figure 7. IP and MAC Addresses
    Image showing the IP and MAC Addresses fields