Documentation

Skip to end of metadata
Go to start of metadata

Create a Datacenter

API Documentation

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

To create a datacenter, you will require the Manage datacenter privilege.

To create a datacenter, in Infrastructure view, click on the Datacenters tab.

 

Then click on the add button at the top of the Datacenters list. 

The Create datacenter popup will open.

Enter the name and location of the datacenter.

  • When Abiquo creates the Datacenter, it will use this location to plot the Datacenter on the Infrastructure view map.

 

  • Enter the connection details of the remote services
    • To speed up remote services data entry:
      • Type the first IP address then copy it to the other boxes by clicking on the Duplicate IP addresses link
      • If you are reusing remote services already created for another datacenter, type the first number of the IP address to open a selection list
        • Remember that you cannot reuse the Appliance manager or Business process manager remote services
  • Click Check for each remote service or Check all to ensure that the Abiquo orchestrator can connect to the remote services
  • To go straight into the new datacenter and add racks, machines, etc., mark the checkbox to Automaticallly open datacenter after creation
  • Click Save

 

  • Remember to
    • Edit your enterprises to add the new datacenter to the Allowed datacenters list so users can deploy in the datacenter
    • Edit your administration scopes to allow administrators to manage the datacenter

 

Remote Service Connection Details

  • Protocol: the protocol used to connect to the remote service
  • Address: the address of the remote service
  • Port: the port used to connect to the remote service. The default port for HTTP is 8009 and for DHCP it is 7911
  • Context: the context where the remote service is published
Required Remote Services

The remote services required for a datacenter are marked with a tick in the following table. For a full description of each remote service, see  Infrastructure View#Abiquo uses Remote Services to manage infrastructure.

Remote serviceDC

Virtualization manager

(tick) (blue star)

Monitor manager

(tick) (blue star)

Appliance manager

(tick) (info)

Discovery manager

(tick)

Storage manager

(tick)

Business process manager

(tick) (info)

DHCP service

(tick) (star)
DHCPv6 service(tick) (star)
Cloud provider proxy

(tick) for OpenStack Neutron
(green star) for other datacenters

Optional DHCP Servers

(star) You can configure virtual machines on unmanaged networks to receive their configuration from a DHCP Server outside the Abiquo Platform. These machines can run in a datacenter without a DHCP Server for the Abiquo platform. On all other types of private cloud tenant networks, the DHCP Server is essential to the proper functioning of virtual machine networking.

Optional Cloud Provider Proxy Remote Service

(green star) The Cloud Provider Proxy remote service is required to use the OpenStack Neutron integration but it is optional for other private cloud datacenters. After you create the datacenter, if you do not require this remote service, you can remove it from the location. 

Shared remote services

(info) - Individual remote services required for each datacenter: these remote services CANNOT BE SHARED and each Appliance Manager remote service requires a separate NFS repository to hold the Datacenter Apps Library

(blue star) - To reuse these remotes services, they will all require access to a single shared remote service Redis instance

Troubleshooting Remote Services

If your remote services cannot be found, check which port the remote services are listening on. Also check that remote services can connect correctly to the Abiquo API, with a correct abiquo.server.api.location in the abiquo.properties file. If you receive a repository error, for example, that the .abiquo_repository file cannot be found, you should check that the NFS repository is properly mounted.




Create a Public Cloud Region

To create a new OpenStack public cloud region, see #CreateOpenStackRegions or #Create OpenStack Regions

To create a new public cloud region, in Infrastructure view click on the Public cloud regions tab.

The click the add button at the top of the Public cloud regions list.

The Create public cloud region popup will open. 

  • Enter the base name of the public cloud region
    • Note that you can change this later
  • Select the provider
  • Select the region(s)
    • Abiquo will create the first region with the name you enter and the others with a suffix of "_1", "_2", and so on
      • Abiquo creates the regions in order and if a region cannot be created, then Abiquo will try to create the next region on the list
  • Click Next

  • Enter the connection details of the remote services
    • To speed up remote services data entry:
      • type the first IP address then copy it to the other boxes by clicking on the Duplicate IP addresses link
      • if you are reusing remote services already created for another datacenter, type the first number of the IP address to open a selection list
  • Click Check for each remote service or Check all to ensure that the Abiquo orchestrator can connect to the remote service
  • Click Save

  • Remember to 
    • Edit your enterprises to add credentials and add the new region to the Allowed datacenters list so users can deploy in the region
      • You will require one separate AWS account for each enterprise using an AWS public cloud region, i.e. one account per enterprise
    • Edit your administration scopes to allow administrators to manage the public cloud region

Remote Service Connection Details

  • Protocol: the protocol used to connect to the remote service
  • Address: the address of the remote service
  • Port: the port used to connect to the remote service. The default port for HTTP is 8009
  • Context: the context where the remote service is published
Required Remote Services

The remote services required for a public cloud region are marked with a tick in the following table. For a full description of each remote service, see  Infrastructure View#Abiquo uses Remote Services to manage infrastructure.

Remote servicePCR

Virtualization manager

(tick) (blue star)

Monitor manager

(tick) (blue star)

Appliance manager

 

Discovery manager

(tick)

Storage manager

 

Business process manager

 

DHCP service

 
DHCPv6 service 
Cloud provider proxy(tick) (red star)

Shared remote services

(blue star) - To reuse these remotes services, they will all require access to a single shared remote service Redis instance

(red star) - OpenStack: to create a public cloud region for a public or private OpenStack cloud, you must have already registered a cloud provider proxy remote service in Abiquo

Reuse Remote Services

In the following screenshot, the black "i" symbol marks the reused remote services. Click on it to find out where the remote services are reused.

Abiquo can work with generic OpenStack clouds, for example, a private OpenStack deployment you may have in your labs, or even public OpenStack offerings. The feature is very similar to other Abiquo public cloud plugins, enabling you to deploy and configure virtual machines (including Chef features), manage their lifecycle, and manage networking and VDCs.

Configure networking with OpenStack Neutron

The administrator can configure networking with the same functionality as the Abiquo OpenStack Neutron Integration in private cloud. See OpenStack Neutron Integration for SDN and firewalls and load balancers

Configure networking for the generic OpenStack integration by setting the OpenStack Neutron properties. See Abiquo Configuration Properties#neutron.

When you create the OpenStack region, Abiquo will automatically configure the network infrastructure, so it is not necessary to create a device as in private cloud.

See Manage Networks

Add an OpenStack Cloud

There is a slight difference between the functionality for create OpenStack clouds and creating other public cloud regions. Because the OpenStack plugin is generic, the regions are not available to Abiquo before you add the cloud. Therefore you will need to create the Abiquo Cloud provider proxy remote service in order to retrieve the regions before you add the cloud.

Add the Cloud provider proxy

Abiquo now adds the Cloud provider proxy to private cloud datacenters by default, but it is an optional remote service. Abiquo uses it for SDN networking integrations and for the Generic OpenStack Integration. If it is not present on your platform or in your datacenter, you may need to add it.

To add the Cloud provider proxy, do the following steps: 

Open Infrastructure view, then Click on the Remote Services tab.

To add the new remote service, click the plus button in the top right-hand corner of the main Remote Services pane.

The Create remote service popup will open. Enter the IP address.

To ensure that the IP service is reachable, click Check. If the check result is positive (green indicator), click Save. 

Retrieve OpenStack regions

In Infrastructure view, open the Datacenters tab and click on the Add button. Select Create public cloud region.

Enter the name of the public cloud region and select the OpenStack provider.

Enter the URL of the OpenStack cloud endpoint and the OpenStack administrator credentials and click Retrieve regions.

 

The Cloud Provider Proxy you created will use the administrator credentials to retrieve the region information and register the regions.

Create OpenStack Regions

Select the desired region(s) from the list.

Then register the remote services, remembering to select the existing cloud provider proxy from the pull-down if you wish to use this specific remote service, or use another cloud provider proxy remote service.

Click Save to create the public cloud region.

Then you can edit Enterprises to allow tenants access and add tenant credentials in the usual way. Enter the credentials on the Credentials tab in the following format.

Access key ID: tenantName:userName

Secret access key: password




Manage Remote Services

The Remote Services tab of Infrastructure view shows the details of the remote services and the cloud locations they are used in. It also shows their Status in the last manual or automatic infrastructure check. 

The actions you can perform on this tab are:

ButtonAction
Create a new remote service and, as part of the creation process, assign it to a location
Edit an existing remote service, assign it to a location, or remove it from a location.
Delete a remote service if it is not in use in any location

Sometimes you may need to create an individual remote service, for example, before you create an OpenStack region, you must register a Cloud provider proxy remote service.

The Appliance manager and Business process manager must always be assigned to one and only one location. All other remote services can be created without assigning them to any existing location

To create a new remote service, click the Add button in the top right-hand corner of the Remote services pane.

The Create remote service popup will open. 

Select a remote service type, enter the IP address of the remote service and click the Check button.

To assign the remote service directly to a location during the creation process, click the Add location link.

Select an appropriate location that will require this remote service from the pull-down list. 

After you have added the remote service to a location, it will be displayed in the locations box. To remove the remote service from a location (but not delete it from the platform), click the red x button beside the location. 

Note: to change the location of the Appliance manager or the Business process manager, you must replace these remote services in the location. To do this, edit the remote service and enter the URL for the replacement remote service(s). If you change the Appliance manager, you must maintain the same NFS repository. The Appliance manager and Business process manager cannot be removed completely from a location without deleting the location itself. 

Shared Remote Services

Introduction to shared remote services

You can share remote services between more than one location (datacenter or public cloud region). This enables you to create more efficient datacenter environments for public cloud and datacenters in close physical proximity. 

Some remote services cannot be shared or have special requirements:

  • Appliance manager cannot be shared
  • Business process manager (V2V) cannot be shared
  • To share a VSM and Virtual Factory, the Remote Service must have access to the same remote services Redis instance. Discovery manager may use a separate remote services Redis instance.
Sample shared remote services configurations

These examples show some basic configurations of datacenters with shared remote services. 

In the second configuration the NFS folders for each datacenter are shown to highlight that a separate NFS share is required for each datacenter.





Modify a Datacenter or a Public Cloud Region

API Documentation

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

To modify a datacenter or public cloud region, click on the name, then click on the  configuration button at the bottom of the datacenter list.

To change the name (and location of a Datacenter), enter the new values on the General tab.

Modify Remote Services

To modify the remote services in an existing location, edit the datacenter or public cloud region and click on the Remote services tab.

You will see a list of the remote services that are already assigned to the location.

To add an existing remote service, click on the arrow to the right of the remote service and select it from the pull-down list.

To remove a remote service, click the black "x" beside it.

Remote services that cannot be shared are whited out if they are already assigned to a location.

  • The Appliance manager and Business process manager must always be associated with one and only one datacenter.
  • You can change these remote services as follows:
    • On the Remote Services tab, replace the remote service
      • Edit the remote service and change the URL to another URL with the same remote service available
      • Note: you can only change the appliance manager remote service if you retain the same NFS repository
    • Delete the datacenter
      • This will delete the remote service from the platform

The status of the remote service from the last manual or automatic infrastructure check is shown in the status indicator on the Check button. You should not save a remote service that is not in the AVAILABLE state in a location.

When you have selected all the Remote services, click Save.

 




Delete a Datacenter or Public Cloud Region

To delete a datacenter or public cloud region, first delete any virtual datacenters and storage volumes defined within it. For more information, see Manage Virtual Datacenters.
Then select the datacenter or public cloud region and click the Delete button in the button bar at the top right of the DATACENTERS screen.

When you delete a datacenter, the remote services that can be shared will be detached from the Datacenter, but not deleted from the platform.

To delete all the remote services, open the Remote services tab in Infrastructure view.

Some remote services that must always be assigned to only one datacenter. These are the Appliance manager and Business process manager. So when you delete a Datacenter, Abiquo automatically deletes these shared remote services when it deletes the datacenter.


Users with the Manage Datacenter privilege can create, edit and delete datacenters and public cloud regions. This page describes how to create, edit and delete datacenters and public cloud regions.