From c3aa1b43ab7b2e0c1a8a09128e147dbedabdd033 Mon Sep 17 00:00:00 2001 From: Andrija Panic <45762285+andrijapanicsb@users.noreply.github.com> Date: Wed, 7 Aug 2019 17:44:04 +0200 Subject: [PATCH 1/3] service-offerings-linked-to-zones-doc-update Added explanation that service offerings can be linked to specific zones --- source/adminguide/service_offerings.rst | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/source/adminguide/service_offerings.rst b/source/adminguide/service_offerings.rst index 29975c70f3..a02ad34111 100644 --- a/source/adminguide/service_offerings.rst +++ b/source/adminguide/service_offerings.rst @@ -57,12 +57,27 @@ present users with choices when creating a new instance: creating a new instance. For example, CloudStack includes CentOS as a template. See Working with Templates. -In addition to these choices that are provided for users, there is +In addition to these choices that are provided for users, there is another type of service offering which is available only to the CloudStack -root administrator, and is used for configuring virtual infrastructure -resources. For more information, see Upgrading a Virtual Router with +root administrator, and is used for configuring virtual infrastructure +resources. For more information, see Upgrading a Virtual Router with System Service Offerings. +Compute offering, disk offering, network offering and VPC offering cab be +linked (made available to) specific domain(s) and zone(s) or to all domains/zones. +Existing offerings can be updated with updateServiceOffering, updateDiskOffering, +updateNetworkOffering and updateVpcOffering API calls, by passing "domainid" and +"zoneid" parameters. To make a domain-specific offering public with root admin access, +“domainid=public” can be passed in the API call. To make a zone-specific offering available +for all zones with root admin access, “zoneid=all” can be passed in the API call. +Domain-admins can update service or compute offerings. However, they cannot change zones +for the offerings specified for their domain or subdomains. They cannot change the name, display text, +sort-key for offerings specified for their domains/subdomains and for other +domains which are not child domain for them. They can change domains (within +their subdomains) for the offerings specified for their domains/subdomains, +even if the offering is also specified for other domains which are not child +domain for them as such domains will not be affected by the update operation + Compute and Disk Service Offerings ---------------------------------- From c9237620b3f819da259bd42b4d23a6e22cdbfe2a Mon Sep 17 00:00:00 2001 From: Andrija Panic <45762285+andrijapanicsb@users.noreply.github.com> Date: Wed, 7 Aug 2019 17:54:04 +0200 Subject: [PATCH 2/3] typo --- source/adminguide/service_offerings.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/adminguide/service_offerings.rst b/source/adminguide/service_offerings.rst index a02ad34111..cde7bc86da 100644 --- a/source/adminguide/service_offerings.rst +++ b/source/adminguide/service_offerings.rst @@ -63,7 +63,7 @@ root administrator, and is used for configuring virtual infrastructure resources. For more information, see Upgrading a Virtual Router with System Service Offerings. -Compute offering, disk offering, network offering and VPC offering cab be +Compute offering, disk offering, network offering and VPC offering can be linked (made available to) specific domain(s) and zone(s) or to all domains/zones. Existing offerings can be updated with updateServiceOffering, updateDiskOffering, updateNetworkOffering and updateVpcOffering API calls, by passing "domainid" and From 9f1b03315ba6ed12a519c6234c017eb4bed93b44 Mon Sep 17 00:00:00 2001 From: Paul Angus Date: Sun, 1 Sep 2019 18:09:45 +0100 Subject: [PATCH 3/3] Update service_offerings.rst reworking --- source/adminguide/service_offerings.rst | 32 +++++++++++++++---------- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git a/source/adminguide/service_offerings.rst b/source/adminguide/service_offerings.rst index cde7bc86da..93c84f5557 100644 --- a/source/adminguide/service_offerings.rst +++ b/source/adminguide/service_offerings.rst @@ -63,20 +63,26 @@ root administrator, and is used for configuring virtual infrastructure resources. For more information, see Upgrading a Virtual Router with System Service Offerings. -Compute offering, disk offering, network offering and VPC offering can be -linked (made available to) specific domain(s) and zone(s) or to all domains/zones. -Existing offerings can be updated with updateServiceOffering, updateDiskOffering, +Scope +~~~~~~ + +Since version 4.13; compute offerings, disk offerings, network offerings and VPC offerings can be +scoped to (made available in) combinations of specific domain(s) and zone(s) or to all domains and zones. + +Existing offerings can be updated via the UI or via the updateServiceOffering, updateDiskOffering, updateNetworkOffering and updateVpcOffering API calls, by passing "domainid" and -"zoneid" parameters. To make a domain-specific offering public with root admin access, -“domainid=public” can be passed in the API call. To make a zone-specific offering available -for all zones with root admin access, “zoneid=all” can be passed in the API call. -Domain-admins can update service or compute offerings. However, they cannot change zones -for the offerings specified for their domain or subdomains. They cannot change the name, display text, -sort-key for offerings specified for their domains/subdomains and for other -domains which are not child domain for them. They can change domains (within -their subdomains) for the offerings specified for their domains/subdomains, -even if the offering is also specified for other domains which are not child -domain for them as such domains will not be affected by the update operation +"zoneid" parameters. + +A root admin can change a domain-specific offering to a public one via the UI, or +by passing “domainid=public” in the updateServiceOffering API call. To make a +zone-specific offering available for all zones, a root admin should include +“zoneid=all” in the API call or carry out the operation via the UI. + +Domain-admins have a limited scope to update service or compute offerings. They cannot +change the zone(s) in which the offerings are available, and they cannot change +the name, display text or sort-key for offerings. They can change the domain(s) +which an offering is available in, if the offering's scope is limited to only +domains and/or subdomains for which the domain admin is the admin. Compute and Disk Service Offerings