Introduction to resource scopes
A resource scope is assigned to a resource, such as a VM template or a VApp spec, and it controls resource sharing. A VM template or VApp spec can have multiple scopes and these resource scopes work in conjunction with other access controls. For example, for administrators these are user role privileges, enterprise allowed datacenters, user datacenter scope, and in addition, for specs, access to the spec owner enterprise.
The administrator assigns the scopes to the resource itself and Abiquo gets the list of enterprises in the scopes and allows the users of those enterprises to access the resource. If the scopes are part of a hierarchy, then an administrator can share resources by selecting child scopes that are beneath their scope in the hierachy.
For example, for virtual machine templates, the template scopes define a list of tenants whose users can access a shared template, as well as the administrators who can manage it.
(The scopes applied to users are called user scopes, for more information about user scopes, see the Manage Scopes page)
Pricing scope for pricing models
Abiquo controls access to pricing models with a simple scope, according to these rules:
- When a user creates a pricing model, Abiquo automatically assigns the user's scope for tenants (which is a list of enterprises the user can manage). You cannot change this scope or display it in the UI
- Abiquo only allows users with the same tenant scope (who can administer exactly the same enterprises) to manage the user's pricing models
- All users with pricing privileges can view the pricing model assigned to their own tenant
Template scopes for virtual machine templates
Changes to scopes in 4.0
The administrator can manage shared templates and specs with scopes if they have the Allow user to switch enterprises privilege and administrator access to the resource. The administrator can save a template or spec with their own scope or a child scope in their hierarchy.
Administrators can use scopes for precise control over access to shared templates. In order to work with VM templates, administrators will require the appropriate Apps library privileges and full access to the datacenter with Datacenter scope and Allowed datacenter.
The cloud administrator can add one or more scopes to a template, including the global scope.The global scope means that users from all current and future enterprises can access this template.
Spec scopes for virtual appliance specs
Administrators can use scopes for precise control over access to VApp specs. In order to work with specs, administrators will require the appropriate Virtual appliance specs and Apps library privileges and full access to the datacenter (Datacenter scope and Allowed datacenter) and they must be logged in to the spec owner enterprise.
The cloud administrator can add one or more scopes to a spec, including the global scope.
Resource scope example
This example applies to template and spec scopes.