...
| Expand | ||
|---|---|---|
| ||
To create an enterprise for a cloud tenant to consume cloud resources:
|
When creating a new enterprise, the Cloud Admin can define exactly how that enterprise can use the infrastructure. So while the enterprise will have a self-service experience, the Cloud Admin remains in control and defines the boundaries of what the enterprise can do.
At the heart of controlled self service are Allocation limits. These define how much of the compute, storage and networking resources the Enterprise can consume. The Cloud Admin can also exert granular control by defining allocation limits at the level of a datacenter, or even a virtual datacenter. Tenant Admins can also set limits for virtual datacenters.
The Soft Limit defines the point where the platform can issue a warning. In a self-service world this will be a decision point for the user. Do they need to request more resources, or will they look at the resources they are consuming and realize that there are environments that are no longer being used. Perhaps these can be undeployed and those resources made available for new environments.
...
| Expand | ||
|---|---|---|
| ||
To set limits based on the business agreement with the enterprise holder: The platform will display a warning when the tenant reaches a Soft limit and enterprise users will not be able to deploy VMs after the tenant reaches the Hard limits. You can create an integration with the event streaming API to perform additional actions when tenants reach either limit. An example of a basic integration is an event notifier. |
...
| Expand | ||
|---|---|---|
| ||
To set limits based on the business agreement with the Enterprise holder
|
Within an enterprise, Admins create users with roles. Roles can have over 100 granular privileges and you can base them on the Abiquo default roles for Cloud Admin, Enterprise Admin (tenant admin), and User. The Cloud Admin can therefore delegate as much, or as little administration as they require. Or they can create roles for specific administrative functions (e.g a Network Admin). You can link Abiquo roles to those in an external directory system such as LDAP, AD, or OpenID.
...
| Expand | ||
|---|---|---|
| ||
To create an enterprise Admin user do these steps:
An Enterprise Admin user will be available. This user can manage template libraries and users for the enterprise. |
...
| Expand | ||
|---|---|---|
| ||
To create a custom user role:
|
The Admin can also define Administration scopes. These define groups of enterprises or data centers (Abiquo datacenters or public cloud regions) that can be administered by a user. This allows for more control over the infrastructure and it enables service providers to support a reseller model. Each reseller can manage a scope that is a list of their own customers. Admins can also create a scope hierarchy for sharing resources, such as VM templates and application blueprints, down a "tree branch" that includes the Admin's resellers, their customers and the customers' departments, and so on.