ailto:s...@yaple.net>>, "OpenStack Development Mailing List
(not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Cc: Greg DeKoenigsberg mailto:g...@ansible.com>>
Subject: Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules
We have
gt;
>
> [1] https://review.openstack.org/#/c/196943/
>
>
>
> ------------------
> *From:* Steven Dake (stdake)
> *Sent:* Wednesday, July 8, 2015 12:47 PM
> *To:* s...@yaple.net; OpenStack Development Mailing List (not for usage
> questions)
> *Cc:*
evelopment Mailing List
(not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Cc: Greg DeKoenigsberg mailto:g...@ansible.com>>
Subject: Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules
We have several Ansible modules that we've been carrying[0] which
Wednesday, July 8, 2015 at 5:15 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Cc: Greg DeKoenigsberg mailto:g...@ansible.com>>
Subject: Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules
A
List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Cc: Greg DeKoenigsberg mailto:g...@ansible.com>>
Subject: Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules
All,
I went ahead and wrote the temp module that will fill the gaps that
All,
I went ahead and wrote the temp module that will fill the gaps that the
GPLv3 modules will eventually solve. It appears that upstream Shade still
doesn't have merge the capability to create roles, even though mordred has
the reviews up. This means even if we solve the licensing issue, we will
On 7/7/15, 2:05 PM, "Robert Collins" wrote:
>On 4 July 2015 at 06:53, Steven Dake (stdake) wrote:
>> Kolla Devs as well as the Technical Committee,
>>
>> I wanted to get the TC¹s thoughts on this plan of action as we intend to
>> apply for big tent once our Ansible code has completed implement
Excerpts from Robert Collins's message of 2015-07-07 14:05:23 -0700:
> On 4 July 2015 at 06:53, Steven Dake (stdake) wrote:
> > Kolla Devs as well as the Technical Committee,
> >
> > I wanted to get the TC’s thoughts on this plan of action as we intend to
> > apply for big tent once our Ansible co
On 4 July 2015 at 06:53, Steven Dake (stdake) wrote:
> Kolla Devs as well as the Technical Committee,
>
> I wanted to get the TC’s thoughts on this plan of action as we intend to
> apply for big tent once our Ansible code has completed implementation. If
> the approach outlined in this email seem
Excerpts from Steven Dake (stdake)'s message of 2015-07-03 11:53:00 -0700:
> Kolla Devs as well as the Technical Committee,
>
> I wanted to get the TC’s thoughts on this plan of action as we intend to
> apply for big tent once our Ansible code has completed implementation. If
> the approach out
Steve,
We will need some of the modules from the "merge-it-all" branch of emoty's
fork[1]. If it is more convient, you can just grab them all. The ones we
require to proceed without triggering Option #4 would be the keystone
related modules. That list is as follows:
os_auth.py
os_keystone_domain.
age questions)"
mailto:openstack-dev@lists.openstack.org>>
Cc: Greg DeKoenigsberg mailto:g...@ansible.com>>
Subject: Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules
Please consider forwarding this to the legal list. The gpl is a bit c specific
and can be tric
might be ok, but
something to carefully consider.
Thanks,
Kevin
From: Steven Dake (stdake)
Sent: Friday, July 03, 2015 11:53:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Greg DeKoenigsberg
Subject: [openstack-dev] [kolla][tc] Plans for
Kolla Devs as well as the Technical Committee,
I wanted to get the TC’s thoughts on this plan of action as we intend to apply
for big tent once our Ansible code has completed implementation. If the
approach outlined in this email seems like a blocker and we should just start
with #4 instead, i
14 matches
Mail list logo
