Skip to content

Commit bcebc2d

Browse files
andrijapanicsbPaul Angus
authored andcommitted
service-offerings-linked-to-zones-doc-update (apache#66)
explanation of new service offering scoping
1 parent ab04a2e commit bcebc2d

1 file changed

Lines changed: 24 additions & 3 deletions

File tree

source/adminguide/service_offerings.rst

Lines changed: 24 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -57,12 +57,33 @@ present users with choices when creating a new instance:
5757
creating a new instance. For example, CloudStack includes CentOS as a
5858
template. See Working with Templates.
5959

60-
In addition to these choices that are provided for users, there is
60+
In addition to these choices that are provided for users, there is
6161
another type of service offering which is available only to the CloudStack
62-
root administrator, and is used for configuring virtual infrastructure
63-
resources. For more information, see Upgrading a Virtual Router with
62+
root administrator, and is used for configuring virtual infrastructure
63+
resources. For more information, see Upgrading a Virtual Router with
6464
System Service Offerings.
6565

66+
Scope
67+
~~~~~~
68+
69+
Since version 4.13; compute offerings, disk offerings, network offerings and VPC offerings can be
70+
scoped to (made available in) combinations of specific domain(s) and zone(s) or to all domains and zones.
71+
72+
Existing offerings can be updated via the UI or via the updateServiceOffering, updateDiskOffering,
73+
updateNetworkOffering and updateVpcOffering API calls, by passing "domainid" and
74+
"zoneid" parameters.
75+
76+
A root admin can change a domain-specific offering to a public one via the UI, or
77+
by passing “domainid=public” in the updateServiceOffering API call. To make a
78+
zone-specific offering available for all zones, a root admin should include
79+
“zoneid=all” in the API call or carry out the operation via the UI.
80+
81+
Domain-admins have a limited scope to update service or compute offerings. They cannot
82+
change the zone(s) in which the offerings are available, and they cannot change
83+
the name, display text or sort-key for offerings. They can change the domain(s)
84+
which an offering is available in, if the offering's scope is limited to only
85+
domains and/or subdomains for which the domain admin is the admin.
86+
6687

6788
Compute and Disk Service Offerings
6889
----------------------------------

0 commit comments

Comments
 (0)