Difference between revisions of "Operations/UseCases"
| Line 4: | Line 4: | ||
== UUIDs in the CLI: painful == | == UUIDs in the CLI: painful == | ||
'''Problem:''' The CLI dependence on UUIDs makes simple day-to-day tasks a pain. | '''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 | + | <pre><nowiki> |
| + | * 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 | | | admin | XXXX-XXXXXX-XXXXXXX-XXXAAA | | ||
| − | * keystone tenant-list | grep baz | + | * keystone tenant-list | grep baz |
| baz | XXXX-XXXXXX-XXXXXXX-XXXBBB | | | baz | XXXX-XXXXXX-XXXXXXX-XXXBBB | | ||
| − | * keystone user-list | grep foo | + | * keystone user-list | grep foo |
| foo | XXXX-XXXXXX-XXXXXXX-XXXCCC| | | 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 | + | * keystone user-role-add --role_id = XXXX-XXXXXX-XXXXXXX-XXXAAA --tenant_id=XXXX-XXXXXX-XXXXXXX-XXXBBB --user_id=XXXX-XXXXXX-XXXXXXX-XXXCCC |
| + | </nowiki></pre> | ||
Repeat the second two steps for the other users. I've done this with some seriously ugly for loops. | Repeat the second two steps for the other users. I've done this with some seriously ugly for loops. | ||
'''How should this work?:''' | '''How should this work?:''' | ||
| + | |||
| + | <pre><nowiki> | ||
$ keystone user-create --name=foo --email="foo@foo.com" | $ keystone user-create --name=foo --email="foo@foo.com" | ||
$ keystone user-role-add --user=foo --tenant=baz --role=admin | $ keystone user-role-add --user=foo --tenant=baz --role=admin | ||
| + | </nowiki></pre> | ||
| + | |||
'''Bug Tracking this:''' | '''Bug Tracking this:''' | ||
| Line 24: | Line 31: | ||
'''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) | '''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?:''' | '''How should this work?:''' | ||
| − | + | ||
| + | <pre><nowiki> | ||
| + | 1. keystone user-show --user=foo | ||
User foo: | User foo: | ||
| Tenant | Role | Date Added | | | Tenant | Role | Date Added | | ||
| Foo | Admin | Tue Oct 16 17:29:11 UTC 2012 | | | Foo | Admin | Tue Oct 16 17:29:11 UTC 2012 | | ||
| Bar | User | Tue Oct 11 13:18:02 UTC 2012 | | | Bar | User | Tue Oct 11 13:18:02 UTC 2012 | | ||
| + | </nowiki></pre> | ||
| + | |||
'''Bug tracking this:''' | '''Bug tracking this:''' | ||
| + | |||
| + | == 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 | ||
| + | |||
| + | <pre><nowiki> | ||
| + | +--------------------------------------+-----------+--------+-----------------------+ | ||
| + | | 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$ | ||
| + | </nowiki></pre> | ||
| + | |||
| + | '''Bug Tracking this:''' | ||
Revision as of 16:43, 8 November 2012
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:
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:
