Page Comparison

Table of Contents

maxLevel	2

Excerpt

hidden	true

This page describes how to manage virtual data centers in private cloud and how to onboard virtual resources from public clouds in the hybrid cloud platform

Info
This page section 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 virtual datacentersin myCloud view you can manage your virtual compute, network, and storage resources. Each virtual datacenter (VDC) is a separate cloud environment in a single datacenter or public cloud region. In private cloud a virtual datacenter is on a single rack so that a private network has one network tag, such as a VLAN tag, in the switch on the same rack.

To access Virtual datacenters view, click the myCloud button in the main menu and then click the cloud virtual datacenters button at the top left of the screen.

...

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.

...

In Azure, before you create a virtual datacenter, Create create a resource group and optionally Create you can also create an availability set. See Manage resource groups and Manage availability sets
In Google Cloud Platform, before you create a virtual datacenter, Create create a global network and Create create a subnet See Manage global networks and subnets

To create a new virtual datacenter:

Panel

bgColor	#FFFAE6

Privileges: Manage virtual datacenters

Go to myCloud

...

view → Virtual datacenters

...

Below the V. datacenters list, click the + add button
Select Create a new virtual datacenter from the pull-down menu

...

Complete the dialog as described below

...

Click Save

For the General information:

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

...

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

...

1. For the Location select the datacenter or public cloud region to use
2. For the Network select from:
  1. Default: The platform creates a private network using the platform settings (from Configuration view → Network) and assigns the default network (from the enterprise or platform settings)
  2. None: The platform does not create a private network or assign the default network. This option is not available in Azure or OCI.
  3. Custom Private: The platform creates a custom private network (see details below) and assigns the default network (from the enterprise or platform settings)
    Image Added
3. If your environment uses NAT, you can select:
  1. NAT network: to use for the default SNAT rule
  2. Default NAT IP

...

1. 1. : for the default SNAT rule
Click Save

...

Create a virtual datacenter with no network

When you create a virtual datacenter with the None option for the Network, the platform does not create a default private network or assign the default network of the enterprise or platform.

If there is no default network in the virtual datacenter, and the user tries to deploy a VM without a NIC, then the deploy will fail because the platform cannot automatically assign an IP address.

...

Create a virtual datacenter with a default or custom

...

network

When you create a virtual datacenter with Default selected for the Network, the platform always creates a private network. This private network and it counts as part of your VLAN network allocation limits, even if the default network for the enterprise in the datacenter is another type of network, such as an external network.

The private network can be the "Automatically-created private VLAN"network, which is called "default_private_network", or a custom private network, which will be set as the default network.you can define with the Custom private option. The platform will assign the private network as the default network if there is no other enterprise default network.

...

Create a virtual datacenter with a custom private network

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

...

Field	Description
Name	The name of the

...

network 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

...

network
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

...

network
DNS suffix	The DNS suffix for the

...

network

To manage the VLANs or other networks of your virtual datacenter or to change its default network, 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.

...

Property	Description
Edge cluster name	Name of the NSX-T Edge Cluster used to create Tier-1 VPCs. NSX-T UI path is: Policy - System - Fabric - Nodes - Edge Clusters
Allow snat destinations public	Allow traffic to internet.
Allow dnat sources	Allow traffic from the Tier-0 specified networks. List of IPs or CIDRs in CSV format, or the name of a single NSX-T group that already exists.
Allow dnat sources public	Allow traffic from internet.
Tier0 name	Name of the NSX-T Tier-0 used to create the Tier-1 VPCs. NSX-T UI path is: Policy - Networking - Tier-0 Gateway
Allow snat destinations	Allow traffic to the Tier-0 specified networks. List of IPs or CIDRs in CSV format, or the name of a single NSX-T group that already exists.
Transport zone name	Name of the NSX-T Transport Zone (overlay) used to create segments / networks. NSX-T UI path is: Policy - System - Fabric - Transport Zones
Dhcp conf name	Name of the NSX-T DHCP Profile used to create Tier-1 VPCs. NSX-T UI path is: Policy - Networking - IP Management - DCHP

...

Manage resource allocation limits for a virtual datacenter

You can set hard limits and soft limits to control resource usage in the virtual datacenter.

A Hard hard limit is the maximum amount of a virtual resource (e.g. RAM) that an entity will be allowed to consume.
A Soft soft limit warns users and administrators that the entity is running out of a resource.

...

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

...

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
networks that may be defined.
Note that a private
VLAN
network 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.

Expand

title	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 let the user to to acknowledge the message and continue with the operationtheir action.
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.Image Removed
...
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 operationbut the platform will stop the user action.
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.Image Removed
...
The platform will also display this type of message when the users exceed soft hard 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.
...
Field
Description
Default datastore tier
Select the default disk service level for
your non-persistent virtual machine
VM disks on the hypervisor datastore.
This is the default datastore tier for the virtual datacenter.
To use
your
the cloud provider's default tier, select
"
Configured by location
"
Or select
a default
another 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 be able to deploy VMs if you do not manually configure an IP address.
After you create the virtual datacenter, you can edit it to change the default values.
Note that Abiquo will use the enterprise’s default network in the cloud location as To set the default network for the new a virtual datacenter, see the section below.
...
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 standard cloud users).
For example, you can give users read-only access. You can only apply restricted roles to users that can have their VDCs restricted, which are users without the No VDC restriction privilege.
Panel
Privileges: Manage roles, No VDC restriction
To limit access to a VDC virtual datacenter for cloud users:
Go to myCloud → Virtual datacenters
Create, edit, or onboard a virtual datacenter
Go to Roles
...
Image Added
For the Role, select a more restrictive role to replace user roles within this
...
virtual datacenter.
For example, to give cloud users read-only access, select the ENTERPRISE_VIEWER role
To create exceptions to the VDC role:
Select a Username and an exception Role for the user
Click Add
When you finish creating or editing the virtual datacenter, click Save
The exception will enable activate 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.
...
The platform will create the virtual datacenter and the default private VLAN and display it in the Virtual datacenters view (and any selected private network) and you can work with its virtual resources.
...
Create a virtual datacenter using the API
Tip
API Documentation
For the Abiquo API documentation of this feature, see Abiquo API Resources and https://wiki.abiquo.com/api/latest and the page for this resource VirtualDatacentersResource.
...
To set a default firewall for the virtual datacenter:
Go to Virtual datacenters → Edit → Defaults
For the Default firewall, select an appropriate
...
firewall
...
Image Added
To manage tags for a virtual datacenter:
Go to Virtual datacenters → Edit a virtual datacenter → Tags
Add tags
...
Image Added
For more details see Edit resource tags.
...
Set
...
the default network for
...
all virtual
...
datacenters
By default, the platform automatically creates a default private network for each virtual datacenter. So if you deploy a VM without assigning a NIC, the platform will add one from the default network.You can
To configure the default networks before you create a virtual datacenter:
To define the default private network
...
for all virtual datacenters in the platform, go to Configuration view → Network
To set the default network for all virtual datacenters in an enterprise: edit the enterprise and go to Datacenters, edit a datacenter and go to Default network. You can select the platform’s default private network or an external network of the enterprise
When you change these values, the new values will apply to new virtual datacenters.
...
Set a default network after you create a virtual datacenter
After you create a virtual datacenter, you can configure the default network to be a private network, an external network, or a public network.
To set a network as the default, you will require privileges to access this network in the virtual infrastructure.
:closed_lock_with_key:
Panel
panelIconId 1f510
panelIcon
panelIconText 🔐
bgColor #FFFAE6
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:
Go to Virtual datacenters
...
Select a virtual datacenter
...
and go to Network
Select the network type, such as Private, External, or Public
Create a new private network or edit
...
any network
Select the Default
...
network checkbox
...
The new default
...
network will replace any previous default network
The new default network will apply to all VMs deployed after you set it
For a public network
...
, obtain IP addresses
...
before you deploy a VM
For an external network
...
, your administrator must create IP addresses in infrastructure for your VMs before you deploy a VM
The platform will mark the default network with a star symbol.
...
Onboard from public cloud
...
Administration of virtual datacenters:
Manage networks
Manage firewalls
Manage load balancers
Administer and troubleshoot VMsManage persistent storage and VMs
How users can work with VMs
Manage virtual machines
Configure virtual machines
Manage scaling groups
Manage virtual appliances
...

Versions Compared

Old Version 103

New Version Current

Key

Introduction to virtual datacenters

Create a virtual datacenter with no network

Create a virtual datacenter with a default or custom

network

Create a virtual datacenter with a custom private network

Create a virtual datacenter for NSX-T

Manage resource allocation limits for a virtual datacenter

Soft limits message

Hard limits message

Set virtual datacenter defaults

Set a virtual datacenter role to limit user access

Create a virtual datacenter using the API

Set

the default network for

all virtual

datacenters

Set a default network after you create a virtual datacenter

Onboard from public cloud

network 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.