Open Stack

On Wed, Apr 15, 2015 at 7:58 PM, Tom Fifield <tom at openstack.org> wrote:

> If they do they need more help than we can give...
>>
>
> So, ummm, there is actually a valid use case for ops on devstack: it's
> part of the learning process.
>

Yes, this is very true.  The context in my mind included the
not-present-above phrase "in production".

In my rounds, I've had feedback from more than a few whose first OpenStack
> experience was to run up a devstack, so they could run ps aufx, brctl,
> iptables, etc just to see what was going on under the covers before moving
> on to something more 'proper'.
>

I hear this too, and do not want to discourage those use cases.  However,
there is little real guidance on what parts of DevStack are representative
of a production deployment and what parts should not be replicated.
DevStack's use of sudo, for example, is one of those places that would be a
huge security issue in any real deployment.

While acknowledging that the primary purpose and audience of devstack is
> and should remain development and developers, if there is something we can
> do to improve the experience for those ops first-timers that doesn't have a
> huge impact on devs, it would be kinda nice.
>

So I would be interested in hearing ideas on this topic.  One of the
reasons DevStack is (still) written in shell script is that we always felt
it was easier to demonstrate how the pieces fit together that way.

dt

-- 

Dean Troyer
dtroyer at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150415/8ab55d60/attachment-0001.html>