On 11.9.2018 18:53, Alex Schultz wrote:
Thanks everyone for coming and chatting. From the meeting we've had a
few items where we can collaborate together.
Here are some specific bullet points:
- TripleO folks should feel free to propose some minor structural
changes if they make the
Thanks everyone for coming and chatting. From the meeting we've had a
few items where we can collaborate together.
Here are some specific bullet points:
- TripleO folks should feel free to propose some minor structural
changes if they make the integration easier. TripleO is currently
I just realized I booked the room and put it in the etherpad but
forgot to email out the time.
Time: Tuesday 09:00-10:45
Room: Big Thompson
https://etherpad.openstack.org/p/ansible-collaboration-denver-ptg
Thanks,
-Alex
On Tue, Sep 4, 2018 at 1:03 PM, Alex Schultz wrote:
> On Thu, Aug 9, 2018
On Thu, Aug 9, 2018 at 2:43 PM, Mohammed Naser wrote:
> Hi Alex,
>
> I am very much in favour of what you're bringing up. We do have
> multiple projects that leverage Ansible in different ways and we all
> end up doing the same thing at the end. The duplication of work is
> not really
Hi,
On Fri, Aug 10, 2018 at 5:00 AM, Wesley Hayutin wrote:
>
>
> On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
>
>> On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
>> wrote:
>> > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
>> >> Ahoy folks,
>> >>
>> >> I think it's
> On 8/10/18, 3:20 AM, "Paul Belanger" wrote:
>
>This is basically what I do with roles i write, allow the user to decide
> to step
>over specific tasks. For example, I have created nodepool_task_manager
> variable
>with the following:
>
>
>
A couple of changes [1][2] that I proposed to kolla ansible recently as a
PoC could be related here. Kolla ansible is full of almost identical roles
for each service, with a lot of duplicated 'code' (YAML). The idea was to
try to factor some of that out into shared roles. This results in less code
Hello,
On Fri, Aug 10, 2018 at 7:47 AM Paul Belanger wrote:
>
> On Thu, Aug 09, 2018 at 08:00:13PM -0600, Wesley Hayutin wrote:
> > On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
> >
> > > On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
> > > wrote:
> > > > Excerpts from Alex Schultz's
On Thu, Aug 09, 2018 at 08:00:13PM -0600, Wesley Hayutin wrote:
> On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
>
> > On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
> > wrote:
> > > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> > >> Ahoy folks,
> > >>
> > >> I think
On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
> On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
> wrote:
> > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> >> Ahoy folks,
> >>
> >> I think it's time we come up with some basic rules/patterns on where
> >> code lands when
On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann wrote:
> Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
>> Ahoy folks,
>>
>> I think it's time we come up with some basic rules/patterns on where
>> code lands when it comes to OpenStack related Ansible roles and as we
>>
Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> Ahoy folks,
>
> I think it's time we come up with some basic rules/patterns on where
> code lands when it comes to OpenStack related Ansible roles and as we
> convert/export things. There was a recent proposal to create an
>
Hi Alex,
I am very much in favour of what you're bringing up. We do have
multiple projects that leverage Ansible in different ways and we all
end up doing the same thing at the end. The duplication of work is
not really beneficial for us as it takes away from our use-cases.
I believe that
Ahoy folks,
I think it's time we come up with some basic rules/patterns on where
code lands when it comes to OpenStack related Ansible roles and as we
convert/export things. There was a recent proposal to create an
ansible-role-tempest[0] that would take what we use in
14 matches
Mail list logo
