Open Stack

In February, we're flying in a team of operators and a book sprint
facilitator to write an operators guide at Rackspace in Austin. Ahead of
the actual intense writing week, I would love to get a list of utilities
operators are using. We're collecting items now, and if you can write your
ideas in this etherpad [1] it would help us a lot. I can't promise they'll
all get into the guide, but tips and tricks are gathering here:

1. https://etherpad.openstack.org/EssexOperationsGuide (no, it won't be
Essex-based)

Thanks all -
Anne


On Thu, Jan 17, 2013 at 12:36 PM, Abel Lopez <alopgeek at gmail.com> wrote:

> One thing that has become painfully obvious in Openstack is the lack of
> operational tools.
> Too many times on this list, I've seen the answer be "Go in the database
> and manually fix it"
> This is fine for your small lab deployments, or when you're staffed with
> nothing but Sr. admins.
>
> We really need to start grouping and maintaining a set of 'safe for
> everyone' tools that can do some of these tasks.
>
> I have been thinking writing some utilities so that I wouldn't have to go
> into the database and toggle a '0' to a '1', or whatnot.
> I'm sure many of you on this list have your own tricks that you employ as
> well.
>
> We need to follow the approach of the openstack-chef cookbooks, where we
> all work towards making a better/reproducible environment using community
> books.
> We need to gather up all our 'aces up the sleeve' put them somewhere in
> the open, and make sure that even the most green Jr sysadmin can properly
> wield them.
>
> Doing so will truly 'operationalize' Openstack, and IMO would be a
> worthwhile thing.
> Thoughts?
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130117/420e86ed/attachment.html>