Deploying the Mashery Local OVF Template

To deploy the Mashery Local OVF Template:

Procedure

  1. Start the vSphere Client application on a computer that has access to the target ESX server.
  2. Select File >Deploy OVF Template.
    The vSphere Source window appears.

  3. Navigate to and select the .ova file you received from Mashery.

    Note: To complete this step, you will need to have previously downloaded the .ova file and stored it in a location that is accessible to the computer running vSphere.
    vSphere displays the OVF template’s details. For Mashery Local, the details are as follows:
    • Version: 4.1.0 (or later)
    • Download size: 877.4 MB
    • Size on disk: 2.2 GB (thin provisioned), 50 GB (thick provisioned)
  4. Click Next.
    The End User License Agreement appears.

  5. Read and accept the End User License Agreement and click Next.
    The vSphere Name and Location window appears.
  6. Run the following command to start the installation:
    Enter a name that is meaningful to your managing your virtual environment. This name has no relevance to what your users and partners will see in Mashery products but is meaningful to your administration of your ESX environment. Your operations team likely has naming conventions that should be followed. Then, click Next.
    The Datastore window appears.

  7. Select the appropriate VM datastore, and then click Next.

    Note: Ensure that you pick a datastore with enough free space. See Hardware and Software Requirements for guidance.
    The Disk Format window appears.
  8. Select the Thin provisioned format or Thick provisioned format option for Disk Format according to your needs and best practices, and then click Next. See this VMware performance study for guidance. Thin clients, although faster, need to be monitored closely to ensure you do not run out of space and sometimes require attention to shrink them back down. Remember also that a large number of thin provisioned VMs can affect performance due to frequent metadata updates.

    The Network Mapping window appears.
  9. Select the appropriate Network Mapping for your environment, and then click Next.

    The Ready to Complete window appears.
  10. Click Finish to complete the provisioning.

    The vSphere Client reports as follows when the deployment is complete. Click Finish.

  11. Select the Power On icon for the instance to boot the instance.

  12. You need to get the IP addresses of the instance for use when performing further configuration steps within the Mashery Local appliance. Select the instance and then click View All to find the IP address and make a note of them.

    A recommended best practice is to select IP addresses as follows:
    • eth0: use as a public interface where API calls would be coming in from the developers.
    • eth1: use as an internal interface for the nodes to talk to each other and where nodes can interface with the backend systems.

    This scheme allows you to deal with your firewall rules more easily and keep services on different subnets if needed for security reasons. Typically, the Admin UI would be handled via eth1 as it most likely would be from the internal subnet. The Slave would also be connecting to the Master on eth1 as it is internal traffic.

    You are now ready to configure the Mashery Local instance. You may optionally create a number of slave instances before proceeding by repeating the previous steps for each.