| Table of Contents |
|---|
A resource scope is a scope that is assigned to a resource, such as a VM template or a VApp spec, and it controls resource sharing. Resources can usually have multiple scopes that work in conjunction with other access controls. For example, for administrators these are user role privileges, enterprise allowed datacenters, and user scope.
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 hierarchy.
For example, for virtual machine templates, the template scopes define a list of tenants whose users can access a shared template.
Pricing scope for pricing models
Abiquo controls access to pricing models with a simple resource 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
...
list of enterprises whose users can access a resource, if they have the other required permissions. Resource scopes apply to VM templates and application blueprints (VApp specs).
To share a resource with enterprises, administrators select a set of scopes to assign to the resource. The users of the enterprises listed in the scopes can then access the resource.
Share VM templates, script templates, and VApp specs
The administrator can use scopes to share VM templates, script templates, and VApp specs.
...
| title | Changes to scopes in 4.0 |
|---|
...
blueprints (VApp specs) if they have the Allow user to switch enterprises privilege and administrator access to the resource in the enterprise that owns it.
The administrator can share a VM template, script template, or VApp spec with their own scope, other available scopes, or a child scope in their hierarchy.
...
The administrator can edit a template and add
To share a VM template or a script template:
Log in or switch to the enterprise that owns the template
Go to Catalogue and select a datacenter or public cloud region
Edit a template and go to Scopes
Select one or more available scopes
...
To allow all current and future
...
...
users to access the resource, select the
Global scopeor another unlimited scope
...
To share a spec:
Create a spec or edit a spec in the owner enterprise
Add one or more available scopes.
...
Resource scope example
This example applies to template and spec scopes.
...
Scope hierarchy example
An example scope hierarchy may include many levels. For example, a platform owner, resellers, customers, and departments.
In this case, the platform owner may manage global administrator users in their own scope. And then they may share templates and specs with other levels, for example, resellers and customers.
If the customers have a scope hierarchy for their departments, then customers may be able to share resources with the departments by scope.
...
Resource scope FAQ
Q: Which administrators can edit VM templates, script templates, and VApp specs?
A: Administrators in the owner enterprise (creator) with permissions to administer other enterprises
Q: How can admins share resources to users of other enterprises?
A: Assign scopes that contain the enterprises in their Enterprises list.
Abiquo reads the list of enterprises in the scopes and allows users from these enterprises to use the resources
Administrators can share templates with scopes in their own scope and scopes below their scope in the scope hierarchy tree