Open Stack

Excellent idea! I'll add severity to the wiki.

Thanks!
-James

From: Tim Bell <Tim.Bell at cern.ch<mailto:Tim.Bell at cern.ch>>
Date: Thursday, November 8, 2012 8:41 AM
To: James R Penick <penick at yahoo-inc.com<mailto:penick at yahoo-inc.com>>, "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>>
Subject: RE: Operations use cases/pain points


Thanks for this initiative.

I can help with getting the feedback to the developers once we have the foundation user committee structure in place. This will give regular meetings with both the board and the TC for discussions on items such as you have raised.

We should also add a severity of the problem … i.e. is this an annoyance but can be worked around through to a show stopper for production use ? We could start with critical, high, medium, low as for the bug reports.

Tim

From: James R Penick [mailto:penick at yahoo-inc.com]
Sent: 08 November 2012 16:41
To: openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] Operations use cases/pain points

Hey Folks,
 I'm trying to gather operations use cases and pain points on the new Openstack Operations wiki (http://wiki.openstack.org/Operations).

The sort of things I'm looking for are the day to day tasks that Operators need to perform, which are difficult (or impossible) with the current Openstack toolset. Some examples:

 1.  It's not possible to list the roles for multi-tenant users. Eg, if a user is a member of multiple tenants, how do I (with a single command) list their role for all of those tenants?
 2.  The CLI depends on UUIDs. So adding a single user to a tenant looks like "keystone user-role-add --role_id = XXXX-XXXXXX-XXXXXXX-XXXAAA --tenant_id=XXXX-XXXXXX-XXXXXXX-XXXBBB --user_id=XXXX-XXXXXX-XXXXXXX-XXXCCC".
 3.  Live migration requires that each compute node NFS export the instances directory to all other compute nodes. That's not great from a security perspective.
And so on. My goal here is to capture pain points from Operators, and make sure that feedback is funneled back to the development community. I'm beginning to track these on the wiki here: http://wiki.openstack.org/OperationsUseCases The format isn't the best, but it's there. If you don't want to edit the wiki, feel free to reply to me and I'll add your use case. I'll try to clean up the format as we go and start opening bugs to track these enhancements/feature requests.

Thanks!
-James

Openstack Operations: Weaponizing Openstack.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20121108/db88c187/attachment.html>