One option would be to use a secret management service like Barbican to store those credentials/secrets and use it whenever you want to make a SOAP API call.
There's also Barbican resources available in the contrib section of the Heat repository which could also possibly be used and referenced to your custom resource's properties.  https://wiki.openstack.org/wiki/Barbican Regards, Sirushti Murugesan ________________________________________ From: Qiming Teng [teng...@linux.vnet.ibm.com] Sent: Friday, November 28, 2014 6:45 PM To: OpenStack Development Mailing List (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. It is not supposed to peek into their internals. Regards, - Qiming On Fri, Nov 28, 2014 at 06:19:56PM +0530, Pradip Mukhopadhyay wrote: > Hello, > > > Suppose we have a cinder backend in local.conf | cinder.conf as : > > > [myNFSBackend] > nfs_mount_options = nfsvers=3 > volume_backend_name = myNFSBackend > volume_driver = cinder.volume.drivers.netapp.common.NetAppDriver > netapp_server_hostname = IP > netapp_server_port = 80 > netapp_storage_protocol = nfs > netapp_storage_family = ontap_cluster > netapp_login = admin > netapp_password = password > netapp_vserver = vserver_name > nfs_shares_config = /opt/stack/nfs.shares > > > We would like to access some of such cinder backend configuration > information from Heat. More specifically from custom resource inside the > Heat (e.g. access the netapp_server_hostname, netapp_login, netapp_password > etc. when defining a custom resource class extending the base Resource > class). The purpose is to facilitate some (soap) service call to the > backend storage from custom resource definitions. > > > What is the best pattern/mechanism available? Any pointers to code/doc will > be highly appreciated. > > > Does any database table holds the local.conf (or service specific conf) > information? > > > > Thanks, > Pradip > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev