Product Documentation

Manual Provisioning of NetScaler VPX Instance on OpenStack

Apr 24, 2017

In a few enterprise networks, NetScaler VPX instances cannot connect to Citrix license server to automatically download the licenses, for security reasons. In such a scenario, you need to manually deploy NetScaler VPX instances on OpenStack platform. Using the License Activation Code (LAC) received by you from Citrix, download the appropriate netScaler VPX license and save it on your local system.

To Manually Provision NetScaler VPX Instance on OpenStack

  1. Install the NetScaler Driver Software and Register NetScaler MAS on OpenStack
    1. In NetScaler MAS, navigate to Orchestration > Cloud Orchestration > OpenStack.
    2. Click Configure OpenStack Settings. In Configure OpenStack Settings page, you can set the parameters to configure OpenStack in NetScaler MAS. You have two options here - Default and Customized.
    3. Select Default, if the OpenStack services are running on default ports.
  2. Navigate to Orchestration > Cloud Orchestration > OpenStack, and click Deployment Settings.
    1. Management Network - select the management network on OpenStack, to which the auto-provisioned NetScaler VPX is connected.
    2. Profile Name - select the profile from the drop-down list. The NetScaler MAS uses the password contained in this profile to configure new auto-provisioned NetScaler VPX instances.
    3. NetScaler VPX Image in Glance - select the NetScaler VPX image available in the OpenStack Glance that is used to create a NetScaler VPX instance. The drop-down list will display only those images that are present on OpenStack Glance.
  3. In NetScaler MAS, navigate to Orchestration > Cloud Orchestration > OpenStack > Service Packages, and then click Add
  4. On the Service Package page specify the following parameters:
    1. Name - name for the service package. For example, enter SVC-PKG-GOLD.
    2. NetScaler Instance Allocation - select Dedicated or Partitioned as the type of instance allocation defined in the service package.  
    3. NetScaler Instance Provisioning - select Create Instance OnDemand to create NetScaler instances during the configuration itself.
    4. Auto Provision Platform - select OpenStack Compute. By default, NetScaler VPX will be selected as the instance type.
    5. Assign OpenStack Tenants/Placement Policies - section, under OpenStack Tenants, click Add, and select the tenant.
    6. Click Continue, and then click Done.
  5. Navigate to System > System Administration > Change System Settings and select http from the drop-down list.
  6. Navigate to Networks > Instances > NetScaler VPX
  7. In NetScaler VPX page, click Admin drop-down list and select Provision Device.
localized image

                    1.  On the Device Provisioning page, enter the name of the device, and select the service package that you created in the previous step. 

                    2.  Click OK.

localized image

        8.  Navigate to Orchestration Cloud Orchestration > OpenStack > Requests tab. Select the request and click Tasks to view the tasks. When the status of the task changes to Finished, it means that the NetScaler VPX is provisioned in NetScaler MAS.

        9.  Navigate to Networks Instances NetScaler VPX to check that the NetScaler VPX instance appears in NetScaler VPX page.

        10.  Click the NetScaler VPX instance. When the NetScaler VPX instnace opens in your browser window, log on to the instance. Navigate to Configuration > System > Licenses, and manually add the new license. For more information on how to add new license, see NetScaler Licensing Overview.

        11.  Restart the NetScaler VPX instance.

localized image

    12.  After a few minutes, you can log on to OpenStack and in System Instances, you can see that the NetScaler VPX instance is deployed on OpenStack.

          13.  LBaaS V2 API implementations are performed through Neutron LBaaS commands. Connect to any Neutron  client and execute the configuration tasks. For more information on how to execute configuration commands, see Configuring LBaaS V2 using Command Line.