Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel3

...

To create a new private cloud datacenter:

  1. Go to Infrastructure view

    Image RemovedImage Added
  2. Go to the Private tab, click the + add button

  3. Enter the Name of the datacenter and the Location. Click Next

    Image RemovedImage Added
  4. Enter the IP address of the monolithic Abiquo server, and click Duplicate IP addresses to copy the remote service locations

  5. Click Accept to use this remote services configuration for the datacenter.

    Image RemovedImage Added

Expected results: A new Abiquo datacenter is created with resources managed by Abiquo.

...

  1. Open the Infrastructure view and select Private and the datacenter name. If you are not on the Infrastructure details tab (with Servers, Network, etc.), open it by clicking the server button.

  2. On the DATACENTERS list, click the plus button

  3. Select Create Rack

  4. Enter details of the Rack 

    Image RemovedImage Added
  5. Click Network and enter details for your switch and environment. The platform will use these settings to create a pool of VLAN tags to assign to private networks

    Image RemovedImage Added
  6. Click Save

Expected results: The rack will be available in the datacenter to add hypervisors to the physical infrastructure.

...

  1. In the Infrastructure view, click the Datastore tiers tab, and click + Add to create a datastore tier.

    Image RemovedImage Added
  2. On the Enterprise access tab, allow all enterprises to access the tier.

...

  1. Use the + button to create a new physical machine. For example, for a vCenter host (note: you can also add vCenter clusters as hosts).

    Image RemovedImage Added


    Select the hosts to add to Abiquo and configure them as described here.

    1. For each hypervisor host, you must enable a network interface (by assigning a Network Service Type). This is the network interface that is listening on VLANs.

      Image RemovedImage Added
    2. For each hypervisor host, you must enable at least one datastore (mark the checkbox). 
      (minus) Do not enable the vm_repository for use as a datastore.

      Image RemovedImage Added

Repeat the process of adding the physical machine for additional hypervisor hosts. Add the datastores to a datastore tier.

...

  1. Select the data center and edit. Select the Allocation Rules tab

  2. Add a new DATACENTER rule on the right pane with the + icon. Select the Rule type such as 'Compute load level' as below. This rule can be used for oversubscription of CPU. For example, in a test system with small VM templates, you could set RAM to 100% and CPU to 400%. You can also set a storage load level rule for datastore usage.

    Image RemovedImage Added


    Note: If you are adding a "vCenter cluster" directly as a physical machine, use the server rule not the cluster rule.

    Image RemovedImage Added

This rule can be used for oversubscription of CPU. For example, in a test system with small VM templates, you could set RAM to 100% and CPU to 400%. You can also set a storage load level rule for datastore usage.

...

  1. From the Infrastructure view, select Datacenter, Network tab, and select the Public sub-tab.

  2. Click the + icon to add a network

  3. Fill in the necessary information and click Save

    Image RemovedImage Added
  4. Create IPs as required. Click Accept

  5. Review the list of available IPs and make unavailable any IPs that are required for administration purposes. Use the arrow button to move selected IPs from available to unavailable. Use the double arrow buttons to move all IPs.

    Image RemovedImage Added
  6. You can quarantine a public IP if it is misued. Enterprises cannot use IPs that are in quarantine. Select the IP and Click the quarantine button to make an IP unavailable to enterprises.

...

  1. Go to Infrastructure → Public

  2. Click the + add button

  3. Enter the Name for the region, select the public cloud Provider and mark the checkboxes for the Region(s) you wish to use. Click Next.

    Image RemovedImage Added
  4. Enter the IP address of the monolithic Abiquo server. Click Duplicate IP addresses to copy the remote service location.

    Image RemovedImage Added
  5. Click Save to use this remote services configuration for the datacenter.

...

  1. In the bottom left-hand corner of the screen, click on the user icon.

  2. From the dropdown menu, select Edit credentials

  3. Select the cloud provider

  4. Enter the Access key ID and the Secret access key

  5. Click Add account

    Image RemovedImage Added
  6. Click Close

Expected results: The credentials will be added to the tenant's account

...

  • ACME Hosting {root level – Reseller (corporate or service provider level)}

    1. Local Bank {Enterprise}

    2. Wernham Hogg {Enterprise}

    3. Dundler Mifflin {Enterprise}

...

  1. Go to Users

  2. Go to Scopes and for the reseller, create a reseller scope

    1. Name the scope with the same name as the reseller, e.g. ResellerEnterpriseScope

    2. Select an appropriate Parent scope, for example, the Global scope or no parent scope

      Image RemovedImage Added
  3. Create an enterprise and select the Reseller checkbox to make it a reseller enterprise

    1. For the Default scope of the enterprise, select the reseller scope for the enterprise. Abiquo will automatically add the enterprise to its Default scope

      1. Note that if you change the default scope of an enteprise, Abiquo will not remove the enterprise from its previous scope

        Image RemovedImage Added
    2. Go to the Datacenters tab and drag datacenters and/or public cloud regions into the Allowed pane

      Image RemovedImage Added

Then create a customer of your reseller:

...

  1. Log in as SysAdmin

  2. Select a specific enterprise

  3. Go to the Users pane and click + to add the new user

  4. Select the default role ENTERPRISE_ADMIN

  5. For the Scope, select the enterprise scope

    Image RemovedImage Added
  6. Go to the Advanced tab and enter user details as required. The public key is required for remote access to VMs

    Image RemovedImage Added
  7. Click Save

Expected results: An Enterprise Admin will be available. This user can manage template libraries and users for the enterprise.

...

  1. Log in as SysAdmin

  2. In Users view, select a specific enterprise

  3. Select Edit and go to Reservations

  4. Select a datacenter and rack where a server will be reserved for this enterprise

  5. Move one of the available servers to add the server to the Reserved servers list.

    Image RemovedImage Added
  6. Log in as ANY user NOT in this enterprise (note rack reserved servers should not be available).

  7. Log in as ANY user in the enterprise with the reserved server.

...

  1. Go to Virtual datacenters view. Click the + add button and select Synchronize public cloud.

  2. Select the public cloud region

  3. Select the virtual datacenter to synchronize from the list.

    Image RemovedImage Added
  4. Click Synchronize

...

  1. Login as Cloud Admin or Enterprise Admin

  2. Select the enterprise

  3. Go to the "Users" pane click + to add the new user

  4. For the Role, select USER and for the Scope, select the "Enterprise scope" and fill in necessary info

    Image RemovedImage Added
  5. Optionally restrict the user to a set of VDCs

    Image RemovedImage Added
  6. Enter public key for remote access to VMs

    Image RemovedImage Added

Expected results: An Enterprise user is created and they can log in and deploy VMs in the selected enterprise.

...

  1. Login as SysAdmin

  2. Select UsersRoles

  3. Select the USER role and click the Clone button (or click + to add the new role)

  4. Fill in the necessary info. (Do not enter External roles now, but you can enter them later to provide AD support)

    Image RemovedImage Added
  5. Save the role

  6. Select the role again and select the required privileges, then click Save. See Manage Roles#Privileges table

  7. Create a new user and assign the new role to this user

...

  1. Open the cloud Virtual datacenters view. It should open at the Virtual appliances tab

  2. Select the virtual datacenter you want to deploy a virtual appliance in

  3. Click the + add button at the bottom of the the Virtual Appliances tab

  4. Enter the details of the virtual appliance

    Image RemovedImage Added
  5. Click on Open or the virtual appliance Name to enter the virtual appliance editor. A virtual appliance will not do anything unless you add at least one VM template to it

  6. Click the Create virtual machine button. You can now select from the VM templates that are ready to be deployed.
    Simply double-click a template to create a VM with the default label, or click once and enter your own friendly name for the your VM

    Image RemovedImage Added

Expected results: A virtual appliance is created with a VM template available from the Apps library (Catalogue).

...

  1. To change VM settings, from the VM options menu, select Edit.

  2. The VM edit dialog will open. On the General tab, enable remote access, obtain the password and optionally increase CPU and/or RAM. Also make a note of the SSH user and password if they are available.

  3. On the Network tab, go to Private and select the default_private_network or another network

    Image RemovedImage Added
  4. Add an IP address or add the Auto-generated IP tag to the VM

  5. If the original IP is in the same network, remove the original IP, so as to not have two IP addresses in the same network

  6. On the Storage tab, add a hard disk by clicking the + add button at the bottom of the page

    Image RemovedImage Added
  7. Enter appropriate values for a disk in your environment and click Save.

...

  1. Select the virtual datacenter

  2. Click the + add button

  3. Enter the details as described below.

    Image RemovedImage Added
  4. Total size, where the minimum size is as follows:

    1. AWS and Azure: 1 GB

    2. GCP: 10 GB

    3. OCI: 50 GB

  5. Tier is the service level. Some tiers may not be available in all regions, for example, the AWS "io2" service level.

  6. Availability zone, for AWS and GCP. This must be the same Availability zone as for the VM network

  7. Controller type for OCI: PARAVIRTUALIZED or SCSI. Note that in OCI, volumes may onboard as IDE but the platform will later update them.

  8. Controller: In public cloud, the platform does not apply the Controller

  9. Encrypted: Available in AWS and OCI

...

Info

Prerequisites

  • A cloud environment with a datacenter plus a public cloud region (or another datacenter)

  • Abiquo Server

  • V2V Services in datacenter (for conversion)

  • Two private cloud datacenters or one private cloud datacenter and a public cloud region

    • Check tenant is allowed to use the physical datacenter and the public cloud region

    • For public cloud region, you will need a compatible template and you must prepare it according to provider instructions (see VM Template Mobility)

...

  1. Go to Apps library → select the private cloud datacenter where the VM template is stored.

  2. Select the VM template and from its options menu, select Export

  3. For private cloud, select the datacenter

    Image RemovedImage Added
  4. For public cloud, select the public cloud region

    Image RemovedImage Added
  5. For public cloud, select one bootable system disk. For private cloud, select disks

    Image RemovedImage Added

Expected results: A compatible VM template can be exported (copied) to another private cloud datacenter or a public cloud region

...

Info

Prerequisites

  • A virtual appliance that is successfully deployed and powered on (smile).

  • Network connectivity between browser and hypervisor

    • Console is through the hypervisor, not directly to the VM

  • Remote access password set in the VM from the VM template, or with guest setup, and/or user SSH public key. See Guest setup

...

Info

Prerequisites

  • Abiquo installed and configured

  • Existing tools to manage the hypervisor hosts. 

    • E.g. VMware vCenter managing ESXi

  • VM running on hypervisor hosts

...

  1. Configure the Abiquo server to use LDAP authentication. See LDAP and active directory integration. Please review the documentation as you will need to manually edit the configuration files.

  2. Assign the LDAP groups or OpenID groups to User roles as external roles. A user in matching groups will be assigned the Abiquo Role

    • Example for OpenID:

      • id=admins,ou=group,o=qa,ou=services,dc=openam,dc=forgerock,dc=org

    • Examples for LDAP:

      • ldap_group_01

      • ldap_group_02

  3. Log in to Abiquo using the credentials of an LDAP or OpenID user in the Abiquo group.

...

Info

Prerequisites

  • A working Cloud Management Platform (CMP) and populated Apps library (Catalogue)

Steps:

  1. To create a cost code for resource pricing

    1. Go to Pricing → Cost codes

    2. Click the + add button

    3. Enter the details and initial prices

  2. Configure a VM template in the Catalogue.

  3. Edit the VM template and go to the Advanced tab

  4. Select the appropriate Cost codes for the VM template

    Image RemovedImage Added


    When you create or edit a hardware profile, you can also assign a cost code.

  5. When you create a VM you can also assign cost codes

  6. You can use the cost code to track a VM or hardware profile in the Abiquo database either for licensing or charge back.

...

Info

Prerequisites

  • Deployed VM(s)

  • User has added collectd as an OAuth application in Abiquo. See Authentication

  • Following the instructions at Use collectd plugin for custom metrics

    • Collectd is installed and running on the VM(s)

    • Abiquo collectd plugin is installed and running on the VM(s).

  • Privilege allowing the user to push own metrics must be assigned to the collectd OAuth application

...

Info

Prerequisites

  • Virtual Datacenter

    • In public cloud this can be onboarded and synchronized

  • Private cloud

    • Abiquo VMware NSX integration

    • Devices created for the enterprise in the cloud location

  • Public cloud

    • Credentials for public cloud provider with firewall support, for example, AWS

  • Logged in as cloud admin using this enterprise, or tenant admin

...

  1. Go to Virtual datacenters → select a virtual datacenterNetworkFirewalls

    Image RemovedImage Added
  2. Select the location or the virtual datacenter and click the double-arrow synchronize button in the top right-hand corner of the page

  3. Click the + button and enter firewall general information

    Image RemovedImage Added
  4. Click the synchronize button to synchronize firewall rules. You will probably see a default rule to allow all outbound traffic.

  5. Click the pencil edit button to edit firewall rules. Enter firewall rules, for example, to allow SSH and HTTP traffic

...

Info

Prerequisites

  • Virtual Datacenter  

    • In public cloud this can be onboarded; All public cloud virtual datacenters must be synchronized

  • Private cloud

    • Security group (firewall) if using Abiquo VMware NSX integration or other firewall and load balancer integration

  • Public cloud

    • Security group (firewall) if using public cloud provider with firewall support, for example, AWS

  • Linux template added to the Abiquo Apps library (Catalogue)

  • SSH public key added to Abiquo user account

  • Pre-purchase of two public IP addresses

...

  1. Select the location or the virtual datacenter and synchronize it (round arrow button beside the name)

  2. Go to Network → Load balancers

  3. Click the + button and enter load balancer general information. Select Public address and "An automatically created public address"

    Image RemovedImage Added
  4. Create routing rules. Add a routing rule with HTTP and port 8000 (unless you have certificates prepared for HTTPS)

    Image RemovedImage Added
  5. Enter a health check if required. AWS will automatically create one if you do not enter one. For the health check enter: Name, HTTP, 8000, Path: /index.html, interval (sec) e.g. 30, timeout (sec) e.g. 5 and attempts e.g. 3

  6. Select the firewall you created earlier

  7. Assign nodes, adding both instances

  8. Click Save

...