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

Adrian Otto adrian.otto at rackspace.com
Thu Oct 8 20:04:23 UTC 2015


I agree with the concept of a simple quickstart doc, but there also needs to be a comprehensive user guide, which does not yet exist. In the absence of the user guide, the quick start is the void where this stuff is starting to land. We simply need to put together a magnum reference document, and start moving content into that.


On Oct 8, 2015, at 12:54 PM, Steven Dake (stdake) <stdake at cisco.com<mailto:stdake at cisco.com>> wrote:

Quickstart guide should be dead dead dead dead simple.  The goal of the quickstart guide isn’t to tach people best practices around Magnum.  It is to get a developer operational to give them that sense of feeling that Magnum can be worked on.  The goal of any quickstart guide should be to encourage the thinking that a person involving themselves with the project the quickstart guide represents is a good use of the person’s limited time on the planet.


From: Hongbin Lu <hongbin.lu at huawei.com<mailto:hongbin.lu at huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thursday, October 8, 2015 at 9:00 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [magnum] Document adding --memory option to create containers

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/41dff454/attachment.html>

More information about the OpenStack-dev mailing list