shwstppr commented on a change in pull request #53: Constrained custom offerings update for 4.13 URL: https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304259986
########## File path: source/adminguide/service_offerings.rst ########## @@ -69,14 +74,20 @@ available offerings when they create a new VM. Based on the user’s selected offering, CloudStack emits usage records that can be integrated with billing systems. -Some characteristics of service offerings must be defined by the CloudStack -administrator, and others can be left undefined so that the end-user can -enter their own desired values. This is useful to reduce the number of -offerings the CloudStack administrator has to define. Instead of defining a -compute offering for every imaginable combination of values that a user +Compute offerings may be "fixed", "custom constrained" or "custom unconstrained". + +In fixed offering the Number of CPUs, Memory and CPU frequecy in each service +offerings are predefined by the CloudStack administrator, in custom unconstrained +offerings they are left undefined so that the end-user can enter their own desired +values when creating a guest instance. Since 4.13 custom constrained offerings have +been introduced to allow the end-user to enter the number of CPUs and memory +required within constraints set by the administrator. The constraints can be Review comment: Double space here, `administrator. The constraints`. Also in the line below. Although not showing in the docs html ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
