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

« Previous Version 104 Next »

This page describes how to manage virtual datacenters in private cloud and public cloud
For details of how to onboard virtual datacenters and resources from public cloud, see Onboard from public cloud


Introduction to virtual datacenters

In the Virtual datacenters in myCloud view you can manage your compute, network and storage resources.

Each virtual datacenter (VDC) is a separate cloud environment in a single datacenter or public cloud region. 

To access Virtual datacenters view, click the myCloud button in the main menu and then click the cloud virtual datacenters button.

Virtual appliances in virtual datacenter view

To display all the virtual datacenters in specific providers, click the funnel filter button at the top of the list and select one or more providers.


Create a virtual datacenter

Before you begin:

To create a new virtual datacenter:

Privileges: Manage virtual datacenters

  1. Go to myCloud Virtual datacenters view

  2. Above the V. datacenters list, click the + add button

  3. Select Create a new virtual datacenter from the pull-down menu

  4. Complete the dialog as described below

  5. Click Save

General information

This section describes the basic details to enter when creating a virtual datacenter. The following sections describe further configuration.

Create virtual datacenter

Field

Description

Name

The name of the virtual datacenter

Location

The datacenter or public cloud region where virtual appliances will be deployed. You can select any of your allowed locations

Hypervisor

The type of the hypervisor for the virtual datacenter. This option will not display if there is only one choice.

Network

  • Default: Create a VLAN (default private or external) in the pre-configured range

  • Custom Private: Create a custom private VLAN (see form below)

If your environment supports NAT you may also be able to select the IP address for the default SNAT rule

Field

Description

NAT network

Optionally, select the NAT network to use for the default SNAT rule

Default NAT IP

Optionally, select the NAT IP address for the default SNAT rule for the virtual datacenter


Create a virtual datacenter with custom networks

When you create a virtual datacenter, the platform always creates a private network and it counts as part of your VLAN allocation limits, even if the default network is another type of network.

The private network can be the "Automatically-created private VLAN", which is called "default_private_network", or a custom private network, which will be set as the default network.

To create a Custom private network, complete the Network section of this dialog.

Create virtual datacenter - general information
 Click here to display details of create virtual datacenter general information custom private network PCR

Field

Description

Name

The name of the VLAN to create

Netmask

The network mask CIDR

Network address

The network address

Address range

The address space that the virtual datacenter can use in CIDR format.
This space will define the virtual network and the private networks will be subnets within this address space.

Gateway

The IP of the gateway of the VLAN

Availability zone

The availability zone where VMs attached to this network will deploy

Primary DNS

The primary DNS of the network

Secondary DNS

The secondary DNS of the VLAN

DNS suffix

The DNS suffix for the VLAN

To manage the VLANs or other networks of your virtual datacenter, go to Virtual datacenters → Network. See Manage networks.

  • For information about changing the default network of the VDC, see Manage networks


Create a virtual datacenter for NSX-T

If you are using NSX-T and the tenant may have more than one tier0 configuration, you may enter NSX-T parameters when you are creating a virtual datacenter.


Manage resource allocation limits for a virtual datacenter

  • Hard limit is the maximum amount of a virtual resource (e.g. RAM) that an entity will be allowed to consume. 

  • Soft limit warns users and administrators that the entity is running out of a resource.

The rules for creating allocation limits are as follows:

  • You cannot have a hard limit only

  • Soft limits must always be less than or equal to hard limits

  • When a limit is equal to 0, it means that there is no limit to resource usage at this level

  • When editing limits, you cannot set the hard limits below the existing resource usage, except for Local hard disk

Create virtual datacenter - allocation limits

Limit

Checked at

Description

Memory

Deployment

Total amount of RAM that may be used by VMs including hardware profiles assigned to VMs

Virtual CPUs

Deployment

Total number of virtual CPU cores that may be used by VMs including hardware profiles assigned to VMs

Local hard disk

Deployment

Total size of hard disk that may be used by VMs on hypervisor datastores and in public cloud providers

External storage

Configuration

Total size of external storage that may be created for VMs

VLANs

Configuration

Total number of private VLANs that may be defined. Note that a private VLAN is automatically created for every VDC, so this limit may restrict the number of VDCs that users can create

Public /floating/NAT IPs

Configuration

Total number of public IPs, floating IPs (in public cloud), and NAT IPs that may be used

Virtual machines

Deployment

Total number of VMs that users can deploy in the location using their allowed resources

DR protected VMs

Configuration

Total number of VMs that may be protected with the disaster recovery service.
In public cloud regions, the platform does not use DRaaS features or limits.

 Click here to show/hide allocation limit message details

Consider a virtual datacenter with a soft limit of 1 virtual CPU and a hard limit of 4 virtual CPUs.

  • The user will exceed the soft limit if they deploy a virtual appliance with more than 1 CPU in the virtual datacenter.

  • The user will exceed the hard limit if they attempt to deploy a virtual appliance with more than 4 CPUs in the virtual datacenter.

Soft limits message

A soft-limits message popup will allow the user to to acknowledge the message and continue with the operation.

By default, the message will provide details of the limits, used, and requested resources.

For example, the limits are 5 CPUs, the users have 2 CPUs in deployed VMs, and they have requested 3 more CPUs.

Soft limit exceeded

The platform will also display this type of message when the users exceed soft limits at another level, for example, enterprise, enterprise in provider, or enterprise in location.

Hard limits message

A hard-limits message pop-up will allow the user to acknowledge the message and terminate the operation.

By default, the message will provide details of the limits, used, and requested resources.

For example, the limits are 5 CPUs, the users have 5 CPUs in deployed VMs, and they have requested 1 more CPU. Because the user will exceed the hard limit, the platform will not allow the user to obtain 1 CPU.

Hard limit exceeded

The platform will also display this type of message when the users exceed soft limits at another level, for example, enterprise, enterprise in provider, or enterprise in location.


Set virtual datacenter defaults

When you create a virtual datacenter, you can set some defaults according to your platform configuration.

Create virtual datacenter - defaults

Field

Description

Default datastore tier

Select the default disk service level for your non-persistent virtual machine disks on the hypervisor. This is the default datastore tier for the virtual datacenter.

  • To use your cloud provider's default tier, select "Configured by location"

  • Or select a default tier, according to the available service levels

To clear the current tier, click the black x symbol beside the tier name

Subnet

In Google Cloud Platform you must select a default subnet to deploy VMs if you do not manually configure an IP address

After you create the virtual datacenter, you can edit it the default values.

Note that Abiquo will use the enterprise’s default network in the cloud location as the default network for the new virtual datacenter.


Set a virtual datacenter role to limit user access 

If you are able to manage user roles, you can limit user access to a virtual datacenter for users that can have their virtual datacenters restricted (usually ordinary cloud users).
For example, you can give users read-only access.

Privileges: Manage roles, No VDC restriction

To limit access to a VDC for cloud users:

  1. Go to myCloud → Virtual datacenters

  2. Create, edit, or onboard a virtual datacenter

  3. Go to Roles

    Create virtual datacenter
  4. For the Role, select a more restrictive role to replace user roles within this VDC.
    For example, to give users read-only access, select the ENTERPRISE_VIEWER role

  5. To create exceptions to the VDC role:

    1. Select a Username and an exception Role for the user

    2. Click Add

  6. When you finish creating or editing the virtual datacenter, click Save

The exception will enable all privileges that are included in both the user's role and the exception role. It is not possible to grant additional privileges using a VDC role.


After you have entered Allocation limits, Defaults, and Role, click Save.

The platform will create the virtual datacenter and the default private VLAN and display it in the Virtual datacenters view. 

Create a virtual datacenter using the API

API Documentation

For the Abiquo API documentation of this feature, see Abiquo API Resources and the page for this resource VirtualDatacentersResource.


Edit a virtual datacenter

When you edit a virtual datacenter, it is similar to creating a virtual datacenter, but you can also set a default firewall and edit tags.

To set a default firewall for the virtual datacenter: 

  1. Go to Virtual datacentersEdit → Defaults

  2. For the Default firewall, select an appropriate firewall 

Edit virtual datacenter - defaults

To manage tags for a virtual datacenter: 

  1. Go to Virtual datacenters → Edit a virtual datacenter → Tags

  2. Add tags

    Edit virtual datacenter - tags

    For more details see Edit resource tags


Set a default network for a virtual datacenter

Each virtual datacenter requires a default network. The platform automatically creates a default private network for each virtual datacenter.
You can configure the default network to be a private network, an external network, or a public network.
You can configure a default network for each enterprise in a datacenter.
If you deploy a VM without assigning a NIC, the platform will add one from the default network.

To set a network as the default, you will require privileges to access this network in the virtual infrastructure.

Privileges: Manage virtual datacenter network elements, Access public network tab,
Manage public network elements, Access external network tab, Manage external network elements

To assign a network as the default for a virtual datacenter do these steps:

  1. Go to Virtual datacenters → select virtual datacenter → Network

  2. Select the network type, such as Private, Public

  3. Create or edit a network

  4. Select the Default network checkbox

    • This default will override the platform default network and the network set for the enterprise in the datacenter

    • The new default network will apply to all VMs deployed after you set it

    • For a public network that is the virtual datacenter default, obtain IP addresses for your VMs before you deploy

    • For an external network that is the virtual datacenter default, your administrator must create IP addresses in infrastructure for your VMs before you deploy


Onboard from public cloud

See Onboard from public cloud


Pages related to virtual datacenters

The following pages are related to the management of virtual datacenters

  • No labels