Nova does not work with domain scoped token

[Tiago Martins]

Nova commands validate if a project id is present in context. Since Keystone V3, a domain scoped token can be generated, which do not add a project id to the context.

[Joe Gordon (jogo)]

This is part of a bigger bug which is AFAIK nova doesn't understand keystone V3 API.

[Joe Gordon (jogo)]

See https://blueprints.launchpad.net/nova/+spec/support-keystone-v3-api

[Brant Knudson (blk-u)]

What's the use case for having Nova accept a domain-scoped token? Keystone can also generate unscoped tokens, should Nova accept those too?

[Raildo Mascena de Sousa Filho (raildo)]

Brant Knudson:

https://blueprints.launchpad.net/keystone/+spec/domain-quota-management-and-enforcement

https://blueprints.launchpad.net/nova/+spec/domain-quota-driver-api

[Adam Young (ayoung)]

Original problem was with V3 tokens: this was in the RDO configuration, and not part of upstream Nova

[Adam Young (ayoung)]

Wrong bug

[Brad Pokorny (bpokorny)]

Does anyone still care about this? The blueprints referenced in comment 4 both look like there's no plan to make further progress. In addition, the last I heard, the nova team is not planning to support domain scoped tokens, in favor of using hierarchical projects to solve the same use case.

[Pushkar Umaranikar (pushkar-umaranikar)]

Solving inconsistency: Unassigned. Hence, changing status from "incomplete" to "new".

[Markus Zoeller (markus_z) (mzoeller)]

This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on. If you decide to work on this
consider using a blueprint [1] (with a spec [2]). I'll recommend to
read [3] if not yet done.

If there are any questions left, feel free to contact me (markus_z)
in the IRC channel #openstack-nova

References:
[1] https://blueprints.launchpad.net/nova/
[2] https://github.com/openstack/nova-specs
[3] https://wiki.openstack.org/wiki/Blueprints