Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Users can add, modify or delete a Virtual Datacenter (vDC). When modifying, changes to the vDC must be made within the defined min/max range values for the service. If the user tries to add a new VM or deploy a vApp that goes beyond the max value, it will fail to deploy.

*Note that this does not apply to a Pay-As-You-Go solution, which can be set to unlimited.

The vDC page is split into sub-sections:

  • vDC Information - Displays the name, type, and description of the vDC.  It also displays total usage and Min/Max values for the vDC resources.
  • vDC Management - Manage or modify the vDC, or check the audit logs for a history of all actions taken inside the vDC.

    • Resource Management - Users can deploy new vApps, set up networks, deploy NSX Edge Gateways, and upload templates or ISO disk images for their VMs.

    • Modify Services - Users can change the vDC's resources provided they are still within the defined Min/Max range.
    • Automator logs -  Display's all recorded tasks, whether successful or failed. If failed, the log will show a brief description of why the task failed.
  • vDC Details – Displays the details of each object in vDC.

Virtual Datacenter Management

This is the Apex of the vDC. Here, you can manage the following objects:

vApps


vApps are containers that can hold multiple VM's and Networks. You can deploy as many vApps as long as you meet the specs of the vDC's resources. You can deploy 3 types of vApps:

  • Empty vApp - An empty container which you can customize with VM's and Networks
  • Public vApp Templates - These are vApps that were created by the Provider that you can deploy into your vDC
  • Private vApp Templates - These are vApps that the user has uploaded themselves that can be deployed into the vDC (See "Catalogs")

You can also Power ON, OFF, or Restart the entire vApp which will apply to all VM's inside it.

Organization Networks

Organization Networks allows the user to create a private or public network within their vDC. They have 3 types of networks that they can deploy:

  • Isolated - This creates a private network within the vDC.
  • natRouted - A private/public network that works only with NSX Edge Gateways. You will need at least one NSX Edge Gateway to use this option (See NSX Edge Gateway Service for more details)
  • Bridged - Use the provider's public networks.

The Network table seen above will also show you the range of the networks Subnet and Allocations, which shows you which VM is assigned to what IP address.

NSX Edge Gateways

NSX Edge Gateways are software firewalls that you can use to manage network security behind it. See NSX Edge Gateway Service for more details in setting and managing one.

Storage Profiles

Storage policies show which policies the vDC can use when deploying vApps and VMs, or where uploaded vApp Templates and ISOs will go. Each policy displays how much storage space is used, the policy state, and the default policy.

Catalogs

Catalogs allow the user to add vApp templates (.ovf format) and media (.iso format). The catalog uses storage policy limits, so if the template or media exceeds storage capacity it will not upload.

Each type is displayed in a sub-section under the catalog and you can only add .ovf and .iso files via a URL hyperlink.


vApp Management

vApp Management allows the user to access all VM's within that vApp or Add vApp Networks. Each VM in the vApp shows the VM Name, Resource Specs  Guest OS Name, Hostname, and the current state of the VM (running or stopped). Clicking on a VM will open a page to allow the client to connect and manage a VM.

VApp networks allow the VM's to communicate with each other and to the outside world connect to Organization Networks. The vApp network is the only type that can be assigned to a VM Network Card. You can add more than one Organization Network to the vApp network.

If you’re connecting a VM to a routed network, the VM will have to abide by the rules of the Edge and its associated network.

Virtual Machine Management

The Virtual Management (VM) interface allows the client access to their Guest OS. They can modify resource power, change virtual peripherals, or take a virtual snapshot to back up the exact state of the VM at any given time. 

The VM page is split into three sub-sections:

  • VM Information – Displays the VM name, specs, and guest OS information.  It will also show if access is enabled to power on/off/restart the VM. There are a few options the user can perform here:
    • Power Options – The VM can be Powered ON, OFF, Rebooted or if the Guest supports it, you can also perform a graceful shutdown or graceful reboot.
    • Modify VM – Change the VM name, hostname, or CPU/RAM values
    • Console Access – Opens a new window with a GUI interface that allows the client to access the guest OS
    • Mount ISO – Mount an ISO uploaded by the client to their catalog 
    • Unmount ISO – Eject a mounted ISO and unmount it.
    • Delete – Delete the entire VM
  • VM Management – See which virtual peripherals are attached to the VM and view the logs for VM related tasks completed by Hyalto.
  • VM Details – See virtual peripheral details, add or remove virtual peripherals, and create or remove snapshots.

A user can also manage the VM's disks, Network cards, and snapshots. 

  • Networks - Clients can add or modify Virtual NICs (Network Interface Controller or Network Card). The NICs can be connected to vApp networks that bridge the VM to an org network. Each NIC will show the type, IP address, allocation type (Manual, Pool or DHCP), network IP, and a flag to indicate if this is the primary NIC. You can add 3 different allocation types:
    • DHCP – IP is determined by a DHCP server
    • Pool – The NIC is given the next available IP in the IP pool (as defined in the org network)
    • Manual – The client can enter a valid IP
  • Disks - Virtual disks store all the VM’s guest OS data. VMs can have multiple disks provided they are within the limits of the Org vDC storage policy. Each disk shows the index number (order of disks where 0 is the primary disk), total disk storage, and the storage policy being used.
  • Snapshots - Snapshots allow the client to take a copy of the current state of the VM, and back it up in case of a fatal error or requirement to revert to a previous version. Snapshots are stored using the storage policy. Once a snapshot is taken, the client can revert to that state at any time. The user can name the snapshot and give a brief description or reason for taking the snapshot, then click “Submit” to create the snapshot.


  • No labels