On 31/10/14 14:55, Pavlo Shchelokovskyy wrote:
> Once I had an idea of detecting if Neutron is available during heat-
> engine start and simply not to register Neutron resources then (so they
> do not even show up in heat resource-type-list), but it turns out some
> deployments like TripleO do start heat before Neutron...
They start heat before keystone too ;)
Calling self.client_plugin('<client name>') would be enough to determine
if a service is available, and will be cheap to do during validation
since it is just looking up an already loaded service catalog.
On 31/10/14 14:55, Pavlo Shchelokovskyy wrote: type-list) , but it turns out some
> Once I had an idea of detecting if Neutron is available during heat-
> engine start and simply not to register Neutron resources then (so they
> do not even show up in heat resource-
> deployments like TripleO do start heat before Neutron...
They start heat before keystone too ;)
Calling self.client_ plugin( '<client name>') would be enough to determine
if a service is available, and will be cheap to do during validation
since it is just looking up an already loaded service catalog.