<html><body bgcolor="#FFFFFF"><p>We should reserve time at the next summit to discuss putting together a detailed user guide, laying down a skeleton so contributors can start filling in different parts.<br>Otherwise as we observe, everything is falling into the quick start guide.<br>Ton Ngo,<br><br><img width="16" height="16" src="cid:1__=07BBF44ADF81AA678f9e8a93df938690918c07B@" border="0" alt="Inactive hide details for "Qiao,Liyong" ---10/08/2015 06:32:36 PM---+1, we can add more detail explanation information of --mem"><font color="#424282">"Qiao,Liyong" ---10/08/2015 06:32:36 PM---+1, we can add more detail explanation information of --memory in magnum CLI instead of quick start</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Qiao,Liyong" <liyong.qiao@intel.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">openstack-dev@lists.openstack.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">10/08/2015 06:32 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] [magnum] Document adding --memory option to create containers</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font size="4">+1, we can add more detail explanation information of --memory in magnum CLI instead of quick start.<br><br>Eli.<br></font><br><font size="4">On 2015¦~10¤ë09¤é 07:45, Vikas Choudhary wrote:</font><ul><ul><font size="4">In my opinion, there should be a more detailed document explaining importance of commands and options. </font><br><font size="4">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.</font><br><br><br><font size="4">-Vikas</font><br><br><font size="4">On Fri, Oct 9, 2015 at 1:47 AM, Egor Guz <</font><a href="mailto:EGuz@walmartlabs.com" target="_blank"><u><font size="4" color="#0000FF">EGuz@walmartlabs.com</font></u></a><font size="4">> wrote:</font><ul><font size="4">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>¡X<br>Egor<br><br>From: Adrian Otto <</font><a href="mailto:adrian.otto@rackspace.com"><u><font size="4" color="#0000FF">adrian.otto@rackspace.com</font></u></a><font size="4"><mailto:</font><a href="mailto:adrian.otto@rackspace.com"><u><font size="4" color="#0000FF">adrian.otto@rackspace.com</font></u></a><font size="4">>><br>Reply-To: "OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#0000FF">openstack-dev@lists.openstack.org</font></u></a><font size="4"><mailto:</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#0000FF">openstack-dev@lists.openstack.org</font></u></a><font size="4">>><br>Date: Thursday, October 8, 2015 at 13:04<br>To: "OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#0000FF">openstack-dev@lists.openstack.org</font></u></a><font size="4"><mailto:</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#0000FF">openstack-dev@lists.openstack.org</font></u></a><font size="4">>><br>Subject: Re: [openstack-dev] [magnum] Document adding --memory option to create containers<br><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>On Oct 8, 2015, at 12:54 PM, Steven Dake (stdake) <</font><a href="mailto:stdake@cisco.com"><u><font size="4" color="#0000FF">stdake@cisco.com</font></u></a><font size="4"><mailto:</font><a href="mailto:stdake@cisco.com"><u><font size="4" color="#0000FF">stdake@cisco.com</font></u></a><font size="4">>> 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>From: Hongbin Lu <</font><a href="mailto:hongbin.lu@huawei.com"><u><font size="4" color="#0000FF">hongbin.lu@huawei.com</font></u></a><font size="4"><mailto:</font><a href="mailto:hongbin.lu@huawei.com"><u><font size="4" color="#0000FF">hongbin.lu@huawei.com</font></u></a><font size="4">>><br>Reply-To: "OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#0000FF">openstack-dev@lists.openstack.org</font></u></a><font size="4"><mailto:</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#0000FF">openstack-dev@lists.openstack.org</font></u></a><font size="4">>><br>Date: Thursday, October 8, 2015 at 9:00 AM<br>To: "OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#0000FF">openstack-dev@lists.openstack.org</font></u></a><font size="4"><mailto:</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#0000FF">openstack-dev@lists.openstack.org</font></u></a><font size="4">>><br>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></font><u><font size="4" color="#0000FF"><br></font></u><a href="https://review.openstack.org/#/c/232175/" target="_blank"><u><font size="4" color="#0000FF">https://review.openstack.org/#/c/232175/</font></u></a><font size="4"><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>¡P It is a good practice to always specifying the memory size, because containers with unspecified memory size won¡¦t have QoS guarantee.<br>¡P 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>¡P 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] </font><a href="https://blueprints.launchpad.net/magnum/+spec/autoscale-bay" target="_blank"><u><font size="4" color="#0000FF">https://blueprints.launchpad.net/magnum/+spec/autoscale-bay</font></u></a><font size="4"><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><u><font size="4" color="#0000FF">OpenStack-dev-request@lists.openstack.org</font></u></a><font size="4"><mailto:</font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><u><font size="4" color="#0000FF">OpenStack-dev-request@lists.openstack.org</font></u></a><font size="4">>?subject:unsubscribe</font><u><font size="4" color="#0000FF"><br></font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><u><font size="4" color="#0000FF">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><br><font size="4"><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><u><font size="4" color="#0000FF">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</font></u></a><u><font size="4" color="#0000FF"><br></font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><u><font size="4" color="#0000FF">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a></ul><br><font size="4"><br></font><br><tt><font size="4">__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font></tt><a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"><tt><u><font size="4" color="#0000FF">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</font></u></tt></a><tt><font size="4"><br></font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><u><font size="4" color="#0000FF">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></tt></a><tt><font size="4"><br></font></tt></ul></ul><br><tt><font size="4">-- <br>BR, Eli(Li Yong)Qiao[attachment "liyong_qiao.vcf" deleted by Ton Ngo/Watson/IBM] </font></tt><tt>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br></tt><br><BR>
</body></html>