Re: Metron dev environments moving to require Ansible 2.4+

[Michael Miklavcic]

I ran it up a second time and it seems to be working now. I'm not sure what
happened there, but I'll keep an eye on it.

On Mon, Oct 1, 2018 at 2:48 PM Nick Allen  wrote:

> I have been able to spin-up a development environment today without a
> problem.
>
> On Mon, Oct 1, 2018 at 3:58 PM Michael Miklavcic <
> michael.miklav...@gmail.com> wrote:
>
> > Anyone run latest master today with full dev? I'm seeing
> > NoClassDefFoundError exceptions on starting enrichments. I upgraded to
> > latest Ansible and the provisioning part seemed to work just fine.
> > https://gist.github.com/mmiklavc/56205526b4736e859aa7ba52468ff4f3
> >
> >
> > On Mon, Oct 1, 2018 at 6:46 AM zeo...@gmail.com 
> wrote:
> >
> >> Hi All,
> >>
> >> This has been pushed to master.  Please updated your Ansible
> >> appropriately.  Thanks!
> >>
> >> Jon
> >>
> >> On Fri, Sep 28, 2018 at 12:18 PM Otto Fowler 
> >> wrote:
> >>
> >>> Yeah,  I thought we had more but maybe they where removed.
> >>> Many places in *.md files referencing Ansible and versions too
> >>>
> >>>
> >>> On September 28, 2018 at 11:45:14, zeo...@gmail.com (zeo...@gmail.com)
> >>> wrote:
> >>>
> >>> Do you mean this
> >>>  >?
> >>> It was the only reference I could find on the wiki.  All of the READMEs
> >>> should be updated as a part of the PR, but feel free to provide your
> input
> >>> if I missed anything.
> >>>
> >>> Jon
> >>>
> >>> On Fri, Sep 28, 2018 at 10:15 AM Otto Fowler 
> >>> wrote:
> >>>
>  We should make sure the non-source documentation is updated
> 
> 
>  On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com
> )
>  wrote:
> 
>  Hi All,
> 
>  As it currently sits, once METRON-1758
>   is merged into the code
>  base, Ansible 2.4 or later will be required to use any of the Metron
>  ansible playbooks.  This is in contrast to the prior version
> requirements
>  outlined in Metron documentation which specifically point to 2.0.0.2
> and
>  2.2.0.0 as supported/recommended Ansible versions.  If you install
> Ansible
>  2.5.0 exactly you should not experience any issues spinning up pre-
> and post-
>  merge versions of Metron.
> 
>  I am broadcasting this to both the user and dev communities in advance
>  of any changes to provide an opportunity to voice any concerns.
> Thanks,
> 
>  Jon
>  --
> 
>  Jon
> 
>  --
> >>>
> >>> Jon
> >>>
> >>> --
> >>
> >> Jon
> >>
> >
>

Re: Metron dev environments moving to require Ansible 2.4+

[Nick Allen]

I have been able to spin-up a development environment today without a
problem.

On Mon, Oct 1, 2018 at 3:58 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:

> Anyone run latest master today with full dev? I'm seeing
> NoClassDefFoundError exceptions on starting enrichments. I upgraded to
> latest Ansible and the provisioning part seemed to work just fine.
> https://gist.github.com/mmiklavc/56205526b4736e859aa7ba52468ff4f3
>
>
> On Mon, Oct 1, 2018 at 6:46 AM zeo...@gmail.com  wrote:
>
>> Hi All,
>>
>> This has been pushed to master.  Please updated your Ansible
>> appropriately.  Thanks!
>>
>> Jon
>>
>> On Fri, Sep 28, 2018 at 12:18 PM Otto Fowler 
>> wrote:
>>
>>> Yeah,  I thought we had more but maybe they where removed.
>>> Many places in *.md files referencing Ansible and versions too
>>>
>>>
>>> On September 28, 2018 at 11:45:14, zeo...@gmail.com (zeo...@gmail.com)
>>> wrote:
>>>
>>> Do you mean this
>>> ?
>>> It was the only reference I could find on the wiki.  All of the READMEs
>>> should be updated as a part of the PR, but feel free to provide your input
>>> if I missed anything.
>>>
>>> Jon
>>>
>>> On Fri, Sep 28, 2018 at 10:15 AM Otto Fowler 
>>> wrote:
>>>
 We should make sure the non-source documentation is updated


 On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com)
 wrote:

 Hi All,

 As it currently sits, once METRON-1758
  is merged into the code
 base, Ansible 2.4 or later will be required to use any of the Metron
 ansible playbooks.  This is in contrast to the prior version requirements
 outlined in Metron documentation which specifically point to 2.0.0.2 and
 2.2.0.0 as supported/recommended Ansible versions.  If you install Ansible
 2.5.0 exactly you should not experience any issues spinning up pre- and 
 post-
 merge versions of Metron.

 I am broadcasting this to both the user and dev communities in advance
 of any changes to provide an opportunity to voice any concerns.  Thanks,

 Jon
 --

 Jon

 --
>>>
>>> Jon
>>>
>>> --
>>
>> Jon
>>
>

Re: Metron dev environments moving to require Ansible 2.4+

[Michael Miklavcic]

Anyone run latest master today with full dev? I'm seeing
NoClassDefFoundError exceptions on starting enrichments. I upgraded to
latest Ansible and the provisioning part seemed to work just fine.
https://gist.github.com/mmiklavc/56205526b4736e859aa7ba52468ff4f3


On Mon, Oct 1, 2018 at 6:46 AM zeo...@gmail.com  wrote:

> Hi All,
>
> This has been pushed to master.  Please updated your Ansible
> appropriately.  Thanks!
>
> Jon
>
> On Fri, Sep 28, 2018 at 12:18 PM Otto Fowler 
> wrote:
>
>> Yeah,  I thought we had more but maybe they where removed.
>> Many places in *.md files referencing Ansible and versions too
>>
>>
>> On September 28, 2018 at 11:45:14, zeo...@gmail.com (zeo...@gmail.com)
>> wrote:
>>
>> Do you mean this
>> ?
>> It was the only reference I could find on the wiki.  All of the READMEs
>> should be updated as a part of the PR, but feel free to provide your input
>> if I missed anything.
>>
>> Jon
>>
>> On Fri, Sep 28, 2018 at 10:15 AM Otto Fowler 
>> wrote:
>>
>>> We should make sure the non-source documentation is updated
>>>
>>>
>>> On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com)
>>> wrote:
>>>
>>> Hi All,
>>>
>>> As it currently sits, once METRON-1758
>>>  is merged into the code
>>> base, Ansible 2.4 or later will be required to use any of the Metron
>>> ansible playbooks.  This is in contrast to the prior version requirements
>>> outlined in Metron documentation which specifically point to 2.0.0.2 and
>>> 2.2.0.0 as supported/recommended Ansible versions.  If you install Ansible
>>> 2.5.0 exactly you should not experience any issues spinning up pre- and 
>>> post-
>>> merge versions of Metron.
>>>
>>> I am broadcasting this to both the user and dev communities in advance
>>> of any changes to provide an opportunity to voice any concerns.  Thanks,
>>>
>>> Jon
>>> --
>>>
>>> Jon
>>>
>>> --
>>
>> Jon
>>
>> --
>
> Jon
>

Re: Metron dev environments moving to require Ansible 2.4+

[zeo...@gmail.com]

Hi All,

This has been pushed to master.  Please updated your Ansible
appropriately.  Thanks!

Jon

On Fri, Sep 28, 2018 at 12:18 PM Otto Fowler 
wrote:

> Yeah,  I thought we had more but maybe they where removed.
> Many places in *.md files referencing Ansible and versions too
>
>
> On September 28, 2018 at 11:45:14, zeo...@gmail.com (zeo...@gmail.com)
> wrote:
>
> Do you mean this
> ?
> It was the only reference I could find on the wiki.  All of the READMEs
> should be updated as a part of the PR, but feel free to provide your input
> if I missed anything.
>
> Jon
>
> On Fri, Sep 28, 2018 at 10:15 AM Otto Fowler 
> wrote:
>
>> We should make sure the non-source documentation is updated
>>
>>
>> On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com)
>> wrote:
>>
>> Hi All,
>>
>> As it currently sits, once METRON-1758
>>  is merged into the code
>> base, Ansible 2.4 or later will be required to use any of the Metron
>> ansible playbooks.  This is in contrast to the prior version requirements
>> outlined in Metron documentation which specifically point to 2.0.0.2 and
>> 2.2.0.0 as supported/recommended Ansible versions.  If you install Ansible
>> 2.5.0 exactly you should not experience any issues spinning up pre- and post-
>> merge versions of Metron.
>>
>> I am broadcasting this to both the user and dev communities in advance of
>> any changes to provide an opportunity to voice any concerns.  Thanks,
>>
>> Jon
>> --
>>
>> Jon
>>
>> --
>
> Jon
>
> --

Jon

Re: Metron dev environments moving to require Ansible 2.4+

[Otto Fowler]

Yeah,  I thought we had more but maybe they where removed.
Many places in *.md files referencing Ansible and versions too


On September 28, 2018 at 11:45:14, zeo...@gmail.com (zeo...@gmail.com)
wrote:

Do you mean this
?  It
was the only reference I could find on the wiki.  All of the READMEs should
be updated as a part of the PR, but feel free to provide your input if I
missed anything.

Jon

On Fri, Sep 28, 2018 at 10:15 AM Otto Fowler 
wrote:

> We should make sure the non-source documentation is updated
>
>
> On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com)
> wrote:
>
> Hi All,
>
> As it currently sits, once METRON-1758
>  is merged into the code
> base, Ansible 2.4 or later will be required to use any of the Metron
> ansible playbooks.  This is in contrast to the prior version requirements
> outlined in Metron documentation which specifically point to 2.0.0.2 and
> 2.2.0.0 as supported/recommended Ansible versions.  If you install Ansible
> 2.5.0 exactly you should not experience any issues spinning up pre- and post-
> merge versions of Metron.
>
> I am broadcasting this to both the user and dev communities in advance of
> any changes to provide an opportunity to voice any concerns.  Thanks,
>
> Jon
> --
>
> Jon
>
> --

Jon

Re: Metron dev environments moving to require Ansible 2.4+

[zeo...@gmail.com]

Do you mean this
?  It
was the only reference I could find on the wiki.  All of the READMEs should
be updated as a part of the PR, but feel free to provide your input if I
missed anything.

Jon

On Fri, Sep 28, 2018 at 10:15 AM Otto Fowler 
wrote:

> We should make sure the non-source documentation is updated
>
>
> On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com)
> wrote:
>
> Hi All,
>
> As it currently sits, once METRON-1758
>  is merged into the code
> base, Ansible 2.4 or later will be required to use any of the Metron
> ansible playbooks.  This is in contrast to the prior version requirements
> outlined in Metron documentation which specifically point to 2.0.0.2 and
> 2.2.0.0 as supported/recommended Ansible versions.  If you install Ansible
> 2.5.0 exactly you should not experience any issues spinning up pre- and post-
> merge versions of Metron.
>
> I am broadcasting this to both the user and dev communities in advance of
> any changes to provide an opportunity to voice any concerns.  Thanks,
>
> Jon
> --
>
> Jon
>
> --

Jon

Re: Metron dev environments moving to require Ansible 2.4+

[Otto Fowler]

We should make sure the non-source documentation is updated


On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com)
wrote:

Hi All,

As it currently sits, once METRON-1758
 is merged into the code base,
Ansible 2.4 or later will be required to use any of the Metron ansible
playbooks.  This is in contrast to the prior version requirements outlined
in Metron documentation which specifically point to 2.0.0.2 and 2.2.0.0 as
supported/recommended Ansible versions.  If you install Ansible 2.5.0
exactly you should not experience any issues spinning up pre- and post-
merge versions of Metron.

I am broadcasting this to both the user and dev communities in advance of
any changes to provide an opportunity to voice any concerns.  Thanks,

Jon
--

Jon

Re: Metron dev environments moving to require Ansible 2.4+

[Justin Leet]

I'm +1 on getting the PR merged in.

I'd just follow up on this thread post merge to let everyone know they have
to switch if they haven't.

On Fri, Sep 28, 2018 at 9:32 AM zeo...@gmail.com  wrote:

> Hi All,
>
> As it currently sits, once METRON-1758
>  is merged into the code
> base, Ansible 2.4 or later will be required to use any of the Metron
> ansible playbooks.  This is in contrast to the prior version requirements
> outlined in Metron documentation which specifically point to 2.0.0.2 and
> 2.2.0.0 as supported/recommended Ansible versions.  If you install Ansible
> 2.5.0 exactly you should not experience any issues spinning up pre- and post-
> merge versions of Metron.
>
> I am broadcasting this to both the user and dev communities in advance of
> any changes to provide an opportunity to voice any concerns.  Thanks,
>
> Jon
> --
>
> Jon
>

Metron dev environments moving to require Ansible 2.4+

[zeo...@gmail.com]

Hi All,

As it currently sits, once METRON-1758
 is merged into the code base,
Ansible 2.4 or later will be required to use any of the Metron ansible
playbooks.  This is in contrast to the prior version requirements outlined
in Metron documentation which specifically point to 2.0.0.2 and 2.2.0.0 as
supported/recommended Ansible versions.  If you install Ansible 2.5.0
exactly you should not experience any issues spinning up pre- and post-
merge versions of Metron.

I am broadcasting this to both the user and dev communities in advance of
any changes to provide an opportunity to voice any concerns.  Thanks,

Jon
-- 

Jon