Cinder does not expose an API for this, and should not be doing so - such
an API is a security risk and of little benefit to most deployments in
doing so.
On 28 November 2014 at 18:57, Pradip Mukhopadhyay pradip.inte...@gmail.com
wrote:
Thanks Qiming Pavlo. We had looked into the v2 of Cinder
The first thing you may want to check is the Cinder API. If I'm
understanding this correctly, Heat only interact with other OpenStack
services via their APIs. It is not supposed to peek into their
internals.
Regards,
- Qiming
On Fri, Nov 28, 2014 at 06:19:56PM +0530, Pradip Mukhopadhyay
(not for usage questions)
Subject: Re: [openstack-dev] [heat] [cinder backend options] Propagate Cinder
backend config information to Heat
The first thing you may want to check is the Cinder API. If I'm
understanding this correctly, Heat only interact with other OpenStack
services via their APIs
That's true. Heat's job is mainly to call other OpenStack APIs in correct
order in order to achieve desired combination of infrastructure resources.
Physically though it may run on a completely different host where these
files are not present, even including a host that is outside of the
Thanks Qiming Pavlo. We had looked into the v2 of Cinder API listings:
http://developer.openstack.org/api-ref-blockstorage-v2.html. However most
likely (or may be we missed to note) none of the APIs peeped into/exposed
the Cinder's backend configuration (the info we were looking for). So we
were
