Based on the proposed change to keystone:
https://code.launchpad.net/~celebdor/charms/trusty/keystone/midonet_valid_service/+merge/258772
I think the midonet-api charm needs a bit of refactoring so that keystone becomes responsible for tenant/user server and endpoint registration. This will be alot less racey than trying todo it remotely from midonet-api.
Based on the proposed change to keystone:
https:/ /code.launchpad .net/~celebdor/ charms/ trusty/ keystone/ midonet_ valid_service/ +merge/ 258772
I think the midonet-api charm needs a bit of refactoring so that keystone becomes responsible for tenant/user server and endpoint registration. This will be alot less racey than trying todo it remotely from midonet-api.