Open Stack

In my opinion, there should be a more detailed document explaining
importance of commands and options.
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.


-Vikas

On Fri, Oct 9, 2015 at 1:47 AM, Egor Guz <EGuz at walmartlabs.com> wrote:

> Adrian,
>
> 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).
> Also I belve auto-scalling deserve it’s own detail document.
>
> —
> Egor
>
> From: Adrian Otto <adrian.otto at rackspace.com<mailto:
> adrian.otto at rackspace.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 13:04
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org
> >>
> Subject: Re: [openstack-dev] [magnum] Document adding --memory option to
> create containers
>
> Steve,
>
> 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.
>
> Adrian
>
> 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.
>
> Regards
> -steve
>
>
> 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
>
> https://review.openstack.org/#/c/232175/
>
> 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:
>
> Pros:
> ·         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.
> Cons:
> ·         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.
>
> Thoughts?
>
> [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
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151009/1f531840/attachment.html>