...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
Scope concepts
...
- A list of resources (enterprises and/or datacenters) for access control
...
- The list of resources (datacenters and enterprises) that the user can view and manage.
- The user must also have the other required permissions (privileges and allowed datacenters)
...
A user can deploy in allowed datacenters, even if they are not in their scope. An Administrator can manage users of the enterprises that are in their scope
...
A resource scope is a 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
...
Administrators can share VM templates and VApp specs with users in scopes beneath their own scope. But they cannot manage the enterprises that are not directly in their user scope
...
- The default scope for the cloud administrator that always includes all resources and cannot be modified
...
- The global scope
- Use all enterprises checkbox selected - ALL current and future enterprises
- Use all datacenters checkbox selected - ALL current and future datacenters
...
An unlimited scope cannot have a parent scope. It must be at the top of a scope hierarchy. An unlimited scope has new resources added automatically in its unlimited dimensions. Only a user with an unlimited scope can create an unlimited scope in the same dimensions as their scope.
...
- When a user creates a pricing model, the platform assigns the user's scope for tenants.
- Only users with the same tenant scope can manage the pricing models
- All users with pricing privileges can view the pricing model of their tenant
...
- You cannot change the pricing scope or display it in the UI
...
).
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.
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.
...
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 create their own have a scope hierarchy for their departments, then customers can may be able to share resources with the departments by scope.
...
Resource scope
...
FAQ
Q: Which administrators can edit templates or 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