Versions Compared

Key

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

Table of Contents

...

As the basic functional map shows, Abiquo adds a thin unintrusive management layer to the existing cloud infrastructure and providers. There is no impact on any VMs that are already running. The Cloud Admins can add the physical and virtual infrastructure to Abiquo in a controlled way on their own timescales.


Abiquo does more than just cloud provisioning!

In addition to the basic concepts, the following diagram shows some of the specialized feature sets that Abiquo can provide as part of a cloud service! For example, with Abiquo you can:

  • Manage costs with budgets, pricing estimates, dashboards displaying usage and bills, and allocation limits. Synchronize price books from Amazon and Azure. Control your cloud costs.
  • Automatically scale out or in to adjust your workloads (and cloud bills) to your application requirements on any cloud. Save on cloud costs.
  • Manage automation on any cloud, using guest tools or the cloud-init standard. Save system administrators' time.
  • Automate your infrastructure using Abiquo integrations with Terraform and Chef, or using standard tools such as Ansible and Puppet. Save system administrator time.
  • Create your own integrations using the complete Abiquo REST API, with Java and Python libraries. Use the Java stream client to follow activity on the platform. Customize your cloud platform to implement your business objectives.
      

...

This section describes the platform from the administrator's point of view. On the Abiquo multi-cloud IaaS platform, Cloud Administrators manage resources, and grant give users controlled access to users for controlled self-service resources. Cloud administrators perform tasks such as the following.

  • Register physical resources and public cloud services in the platform, then grant virtual resources to usersAdministrators allow users to have self-service in the cloud. Administrators , while Administrators remain in control of the physical resources and public cloud services. 
  • Create Enterprises, which are the basic cloud tenants, and tenant hierarchies. Administrators allocate resources to enterprises and use policy to control access to resources, including user roles and privileges.  Cloud Administrators can automate management tasks and delegate tasks them to manage the platform to resellers, for example.
  • Create the Apps library, which contains VM templates and application blueprints. The Apps library is the key to self-service on the platform, enabling users to easily consume the cloud resources in the virtual datacenters. Administrators can share templates and blueprints using tenant access control lists. This enables you to provide Software as a Service (SaaS) on top of Infrastructure as a Service (IaaS). And you can allow tenant administrators to upload their own templates or create their own blueprints.
  • Create Virtual Datacenters (VDCs) where users will consume their cloud resources. VDCs are logical groups of resources bound to a single Abiquo datacenter and virtualization backend, or public cloud provider. The Cloud Administrator can provide different service levels by using different technology stacks for different VDCs. Administrators can apply policies to VDCs using allocation limits (controlling compute, network and storage) or defining the users within an enterprise who can work with each VDC, and their level of access. For example, read only access in public cloud.
  • Administrators create pricing models. They Administrators enter pricing information for billing that also enables them to offer pricing estimates to users.

...