[openstack-dev] [magnum] Document adding --memory option to create containers

Adrian Otto adrian.otto at rackspace.com
Thu Oct 8 17:23:30 UTC 2015

Thanks Hongbin, for raising this for discussion. There is a middle ground that we can reach. We can collect a set of “best practices”, and place them together in a document. Some of them will be operational best practices for cloud operators, and some of them will be for end users. We can make callouts to them in the quick start, so our newcomers know where to look for them, but this will help us to keep the quickstart concise. The practice of selecting a memory limit would be one of the best practices that we can call out to.


On Oct 8, 2015, at 9:00 AM, Hongbin Lu <hongbin.lu at huawei.com<mailto:hongbin.lu at huawei.com>> wrote:

Hi team,

I want to move the discussion in the review below to here, so that we can get more feedback


In summary, magnum currently added support for specifying the memory size of containers. The specification of the memory size is optional, and the COE won’t reserve any memory to the containers with unspecified memory size. The debate is whether we should document this optional parameter in the quickstart guide. Below is the positions of both sides:

•         It is a good practice to always specifying the memory size, because containers with unspecified memory size won’t have QoS guarantee.
•         The in-development autoscaling feature [1] will query the memory size of each container to estimate the residual capacity and triggers scaling accordingly. Containers with unspecified memory size will be treated as taking 0 memory, which negatively affects the scaling decision.
•         The quickstart guide should be kept as simple as possible, so it is not a good idea to have the optional parameter in the guide.


[1] https://blueprints.launchpad.net/magnum/+spec/autoscale-bay
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151008/888c18ea/attachment.html>

More information about the OpenStack-dev mailing list