On 26 September 2014 14:18, Adam Young <ayo...@redhat.com> wrote:
> There are a few Keystone features that are coming together for Kilo.
> For endpoint binding, an endpoint will have to know its own id.   So the
> endpoint_id will be recorded in the config file.  This means that the
> endpoint should be created in keystone before bringing up the server.  Since
> we already require workflow like this to create the service users, this
> should not be too big a burden.  Then that becomes a check here:

That will break TripleO. We currently deploy everything and *then*
configure keystone. That is, we don't follow that workflow for service
users today.


Robert Collins <rbtcoll...@hp.com>
Distinguished Technologist
HP Converged Cloud

OpenStack-dev mailing list

Reply via email to