Operations/UseCases

What kind of things do OpenStack Operators need to do on a daily basis? Is it easy or difficult? Tracking these use cases will identify gaps in OpenStack tooling, offer valuable insight to the developers, and help improve OpenStack.

---

UUIDs in the CLI: painful

Problem: The CLI dependence on UUIDs makes simple day-to-day tasks a pain. Example:

 * keystone user-create --name=foo --email="foo@foo.com"; keystone user-create --name=bar --email="bar@bar.com"
 * keystone role-list | grep admin
| admin | XXXX-XXXXXX-XXXXXXX-XXXAAA |
 * keystone tenant-list | grep baz
| baz | XXXX-XXXXXX-XXXXXXX-XXXBBB |
 * keystone user-list | grep foo
| foo | XXXX-XXXXXX-XXXXXXX-XXXCCC|
 * keystone user-role-add --role_id = XXXX-XXXXXX-XXXXXXX-XXXAAA --tenant_id=XXXX-XXXXXX-XXXXXXX-XXXBBB --user_id=XXXX-XXXXXX-XXXXXXX-XXXCCC

Repeat the second two steps for the other users. I've done this with some seriously ugly for loops.

How should this work?:

$ keystone user-create --name=foo --email="foo@foo.com"
$ keystone user-role-add --user=foo --tenant=baz --role=admin

Bug Tracking this:

---

It's not possible to list the roles for a multi-tenant user

Problem: It's not possible to list all the roles for a multi-tenant user. Instead you have to go into the DB (or write a standalone tool to do it for you) How should this work?:

 1. keystone user-show --user=foo 
User foo:
 | Tenant |   Role   | Date Added |
 |  Foo     | Admin  | Tue Oct 16 17:29:11 UTC 2012 |
 |  Bar     | User  | Tue Oct 11 13:18:02 UTC 2012 |

Bug tracking this: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1021708

---

Nova show fails for instances whose image has been marked as deleted.

Problem: If you build a VM, then later mark its image as deleted, you cannot use 'nova show' to get instance details for that host. Example: -bash-4.1$ nova list

+--------------------------------------+-----------+--------+-----------------------+
| ID                                   | Name      | Status | Networks              |
+--------------------------------------+-----------+--------+-----------------------+
| f8566160-3e44-4fc3-9d1e-2e7d366d0929 | Server 35 | ACTIVE  | default=10.210.226.34 |
+--------------------------------------+-----------+--------+-----------------------+
-bash-4.1$ nova show f8566160-3e44-4fc3-9d1e-2e7d366d0929
ERROR: No image with a name or ID of '89958966-34f1-4e8f-baf1-ec842656cca6' exists.
-bash-4.1$ 

Bug Tracking this:

---

Nova list doesn't show compute node

Problem: We often need to know at a glance where VMs are running. At the moment we need to list VMs, grab the UUID, then run 'nova show' on that uuid. Total pain. It'd save a lot of time if we could just see the compute node in 'nova list', possibly with other information as well (flavor, instance_name, etc). Example:

-bash-4.1$ nova list --all_tenants | grep 10.210.226.40
| 67008226-2a50-45d2-83ca-c22e200e6506 | Server 47                   | ACTIVE | default=10.210.226.40 |
-bash-4.1$ nova show 67008226-2a50-45d2-83ca-c22e200e6506 | grep ATTR:host
| OS-EXT-SRV-ATTR:host                | some.compute.node.foo.com                               |       

Bug tracking this: https://bugs.launchpad.net/nova/+bug/1076473

---