Openstack bundle creates two projects with names `admin` and `services`

[MggMuggins]

Deploy an openstack bundle and list projects:

$ os project list
+----------------------------------+----------+
| ID                               | Name     |
+----------------------------------+----------+
| 0086b84a8dcf44b5b425abbddbbbd8c3 | services |
| 0fddf0da32d549f89763f7deded274ad | services |
| 3ac0c8861bee423b9983a57f73bed0da | admin    |
| 5ed0b92db39b4d52a9286fab4d8626b6 | admin    |
| df5c8912a1594121a363f727024e9ed4 | demo     |
| e87e859a42394bafad754b82a37d30b4 | alt_demo |
+----------------------------------+----------+

My instances are deployed in 3ac0c8861bee423b9983a57f73bed0da and my amphora in 0086b84a8dcf44b5b425abbddbbbd8c3; the other projects are empty.

This is confusing/annoying if you're trying to determine which project a resource lives in.

[dosaboy]

Those projects are in different domains (if you use --long you can see the domain info). This is because openstack has a default domain and we create an "admin_domain". This has been standard for a very long time and I don' know if there is a way around it.

[MggMuggins]

At least there's a reasonable explanation for it; thanks. Wonder about either using the default domain or naming the admin and services projects something similar (adm and svc?) so as to be able to disambiguate using something other than UUID.

But it's a wishlist item for now :)