<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+1, we can add more detail explanation information of --memory in
magnum CLI instead of quick start.<br>
<br>
Eli.<br>
<br>
<div class="moz-cite-prefix">On 2015年10月09日 07:45, Vikas Choudhary
wrote:<br>
</div>
<blockquote
cite="mid:CABJxuZrEbnRDXdSaUxkQbs62hpW8gbwDTYZyJhNu+ky0i5mfng@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">In my opinion, there should be a more detailed
document explaining importance of commands and options.
<div>Though --memory is an important attribute, but since
objective of quickstart is to get user a minimum working
system within minimum time, it seems better to skip this
option in quickstart.</div>
<div><br>
</div>
<div><br>
</div>
<div>-Vikas</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Oct 9, 2015 at 1:47 AM, Egor
Guz <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:EGuz@walmartlabs.com" target="_blank">EGuz@walmartlabs.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Adrian,<br>
<br>
I agree with Steve, otherwise it’s hard to find balance what
should go to quick start guide (e.g. many operators worry
about cpu or I/O instead of memory).<br>
Also I belve auto-scalling deserve it’s own detail document.<br>
<br>
—<br>
Egor<br>
<br>
From: Adrian Otto <<a moz-do-not-send="true"
href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a><mailto:<a
moz-do-not-send="true"
href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a>>><br>
Reply-To: "OpenStack Development Mailing List (not for usage
questions)" <<a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
Date: Thursday, October 8, 2015 at 13:04<br>
To: "OpenStack Development Mailing List (not for usage
questions)" <<a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
Subject: Re: [openstack-dev] [magnum] Document adding
--memory option to create containers<br>
<span class=""><br>
Steve,<br>
<br>
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.<br>
<br>
Adrian<br>
<br>
</span><span class="">On Oct 8, 2015, at 12:54 PM, Steven
Dake (stdake) <<a moz-do-not-send="true"
href="mailto:stdake@cisco.com">stdake@cisco.com</a><mailto:<a
moz-do-not-send="true" href="mailto:stdake@cisco.com">stdake@cisco.com</a>>>
wrote:<br>
<br>
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.<br>
<br>
Regards<br>
-steve<br>
<br>
<br>
</span>From: Hongbin Lu <<a moz-do-not-send="true"
href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a><mailto:<a
moz-do-not-send="true" href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>>><br>
Reply-To: "OpenStack Development Mailing List (not for usage
questions)" <<a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
<span class="">Date: Thursday, October 8, 2015 at 9:00 AM<br>
</span>To: "OpenStack Development Mailing List (not for
usage questions)" <<a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a
moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
<span class="">Subject: [openstack-dev] [magnum] Document
adding --memory option to create containers<br>
<br>
Hi team,<br>
<br>
I want to move the discussion in the review below to here,
so that we can get more feedback<br>
<br>
<a moz-do-not-send="true"
href="https://review.openstack.org/#/c/232175/"
rel="noreferrer" target="_blank">https://review.openstack.org/#/c/232175/</a><br>
<br>
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:<br>
<br>
Pros:<br>
· It is a good practice to always specifying the
memory size, because containers with unspecified memory
size won’t have QoS guarantee.<br>
· 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.<br>
Cons:<br>
· 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.<br>
<br>
Thoughts?<br>
<br>
[1] <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/magnum/+spec/autoscale-bay"
rel="noreferrer" target="_blank">https://blueprints.launchpad.net/magnum/+spec/autoscale-bay</a><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
</span>Unsubscribe: <a moz-do-not-send="true"
href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a><mailto:<a
moz-do-not-send="true"
href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
BR, Eli(Li Yong)Qiao</pre>
</body>
</html>