Page tree
Skip to end of metadata
Go to start of metadata

The next step in the process is to check and adjust the resources you'll need to stand up a Lumeta Command Center or Scout image on a VMware ESXi vSphere hypervisor.

You'll need: 

  • VMware vSphere (or comparable) for use as your client
  • Sufficient resources on your VMware ESXi vSphere hypervisor to run a virtual Lumeta with standard resource requirements.

If your hypervisor doesn’t have enough memory or enough free space in its datastore, you’ll need to reallocate resources (i.e., delete or reconfigure existing virtual machines), or switch to another hypervisor that has more available resources. To avoid over-subscribing a datastore, you can set up an alarm in vSphere that notifies you when provisioned space reaches a threshold.

  1. Launch the VMware vSphere client and select Inventory from the View menu.
  2. Select the Configuration tab.
  3. Select Storage from the Hardware sidebar to check the configuration of the datastore you will be using for your virtual Lumeta. A VMFS-2 datastore requires a 2MB block size; VMSF-3 requires a 4MB block size; VMSF-5 requires a block size of at least 1MB.
    Note: A datastore's block size is not easily changed; its version, however, can be. If an Upgrade to VMFS-5 link is available, opt to do so.
  4. Ensure that your datastore meets the minimum required free space for a thin-provisioned virtual Lumeta Command Center.
  5. Select Memory from the Hardware sidebar and ensure that you will be able to allocate the required GB to the new virtual Lumeta Command Center.
  6. Select Processors from the Hardware sidebar and ensure you can allocate the required cores to the new virtual Lumeta.

That's it!  You have successfully allocated computing resources for Lumeta. Next, open the OVA.

  • No labels