Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-20 Thread Gilles Dubreuil
Hi, Just wanted to add, for clarification, the need to restructure the openstacklib. The use of resource[:auth] parameter is causing the providers to behave differently depending on the context, as expressed earlier in this thread. I would to highlight the fact that this change is driven by

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-20 Thread Rich Megginson
On 05/20/2015 12:17 AM, Gilles Dubreuil wrote: Hi, Just wanted to add, for clarification, the need to restructure the openstacklib. The use of resource[:auth] parameter is causing the providers to behave differently depending on the context, as expressed earlier in this thread. I would to

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-06 Thread Gilles Dubreuil
It seems ~/.openrc is the only default, so just replacing the RC file default: Workflow to find credentials details: 1. From environment (ENV[token] or ENV[project] in short) 2. From a RC file located by convention in current user homedir: ~/.openrc 3. From an openstack configuration file such

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-06 Thread Colleen Murphy
On Wed, May 6, 2015 at 6:26 PM, Gilles Dubreuil gil...@redhat.com wrote: It seems ~/.openrc is the only default [...] The extras module places it at '/root/openrc' [1], so either the extras module should be changed or the providers should look in /root/openrc, either way it should be

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-06 Thread Gilles Dubreuil
On 07/05/15 11:33, Colleen Murphy wrote: On Wed, May 6, 2015 at 6:26 PM, Gilles Dubreuil gil...@redhat.com mailto:gil...@redhat.com wrote: It seems ~/.openrc is the only default [...] The extras module places it at '/root/openrc' [1], so either the extras module should be

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-05 Thread Gilles Dubreuil
Hi, To summarize from latest 2 discussions about this matter. Workflow to find credentials details: 1. From environment (ENV[token] or ENV[project] in short) 2. From a RC file located by convention in current user homedir: ~/openstackrc 3. From an openstack configuration file such as

[openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-05 Thread Colleen Murphy
I'm cross-posting to the dev list since this conversation should be happening there and is related to another thread there. I'm going to top-post a summary and then respond inline. The summary so far is that puppet-openstacklib provides a way to pass in credentials to an API-driven puppet type

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-05 Thread Rich Megginson
On 05/05/2015 12:20 PM, Colleen Murphy wrote: I'm cross-posting to the dev list since this conversation should be happening there and is related to another thread there. Ok. I'm not replying puppet-openstack. I'm going to top-post a summary and then respond inline. The summary so far is

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

2015-05-05 Thread Colleen Murphy
On Tue, May 5, 2015 at 11:36 AM, Rich Megginson rmegg...@redhat.com wrote: On 05/05/2015 12:20 PM, Colleen Murphy wrote: I'm cross-posting to the dev list since this conversation should be happening there and is related to another thread there. Ok. I'm not replying puppet-openstack.