EPEL-ANNOUNCE ansible 2.0 in epel

[Kevin Fenzi]

Greetings. 

I thought I would send out an email with the plans for epel and ansible
2.0. 

Since ansible 2.0 is (to a pretty high degree) compatible with the same
playbooks as 1.9.x, we are going to just update the existing ansible
package rather than create a parallel installable one. 

Note that while playbooks should be compatible and require no changes,
if you are using the ansible API, you will need to adjust your
scripts/plugins. See:
https://docs.ansible.com/ansible/developing_api.html
(The ansible api is not guaranteed stable between any versions)

To allow for additional testing and folks to check/port their
scripts/plugins we are going to leave the ansible 2.0.0.x packages in
epel-testing for a longer than normal time period. We will send another
notice before the 2.0.0.x version goes to stable. Currently version
2.0.0.2 is available in epel6 and epel7 testing repositories. 

Thanks, 

kevin

_______________________________________________
epel-announce mailing list
epel-announce(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/[e-mail]...

[Orion Poplawski]

On 01/18/2016 02:23 PM, Kevin Fenzi wrote:
>  Greetings.
>
>  I thought I would send out an email with the plans for epel and ansible
>  2.0.
>
>  Since ansible 2.0 is (to a pretty high degree) compatible with the same
>  playbooks as 1.9.x, we are going to just update the existing ansible
>  package rather than create a parallel installable one.
>
>  Note that while playbooks should be compatible and require no changes,
>  if you are using the ansible API, you will need to adjust your
>  scripts/plugins. See:
>  https://docs.ansible.com/ansible/developing_api.html
>  (The ansible api is not guaranteed stable between any versions)
>
>  To allow for additional testing and folks to check/port their
>  scripts/plugins we are going to leave the ansible 2.0.0.x packages in
>  epel-testing for a longer than normal time period. We will send another
>  notice before the 2.0.0.x version goes to stable. Currently version
>  2.0.0.2 is available in epel6 and epel7 testing repositories. 
Thanks for the heads up and working on this.

FYI - https://github.com/ansible/ansible/issues/13925 dupe of 
https://github.com/ansible/ansible/issues/13681 seems to be a big issue 
for me that I'd like to see fixed before it goes to stable.

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: [phone]
3380 Mitchell Lane                  orion(a)cora.nwra.com
Boulder, CO 80301              http://www.cora.nwra.com

[Randy Barlow]

>  Since ansible 2.0 is (to a pretty high degree) compatible with the
> same
>  playbooks as 1.9.x, we are going to just update the existing ansible
>  package rather than create a parallel installable one. 
Hello! I just wanted to point out that in practice the playbooks that I have written do
not work in Ansible 2.0. You may be right that it is "close" to compatible, but
I am concerned about this update and just wanted to share my voice.

[Orion Poplawski]

On 01/23/2016 09:32 AM, Randy Barlow wrote:
> > Since ansible 2.0 is (to a pretty high degree) compatible with
> the same
> > playbooks as 1.9.x, we are going to just update the existing ansible
> > package rather than create a parallel installable one.
>
>  Hello! I just wanted to point out that in practice the playbooks that I have written do
> not work in Ansible 2.0. You may be right that it is "close" to compatible, but
> I am concerned about this update and just wanted to share my voice. 
Are these known issues upstream?  If not, I would file a bug report.  I 
know there are some unavoidable incompatibilities but otherwise they are 
trying to make it compatible.


-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: [phone]
3380 Mitchell Lane                  orion(a)cora.nwra.com
Boulder, CO 80301              http://www.cora.nwra.com

[Stephen John Smoogen]

On 23 January 2016 at 09:32, Randy Barlow <rbarlow(a)fedoraproject.org&gt; wrote:
> > Since ansible 2.0 is (to a pretty high degree) compatible with
> the same
> > playbooks as 1.9.x, we are going to just update the existing ansible
> > package rather than create a parallel installable one.
>
>  Hello! I just wanted to point out that in practice the playbooks that I have written do
> not work in Ansible 2.0. You may be right that it is "close" to compatible, but
> I am concerned about this update and just wanted to share my voice. 
A couple of things:
1) Sometimes what worked in the earlier versions was a side effect of
working versus how it was supposed to work.
2) Sometimes they made changes in core methods (1.2 -> 1.3 I believe
had some changes that broke original ansible playbook examples)
3) Sometimes there are bugs.

Without a seeing the examples, seeing why it broke, it is hard to see
what of the above they are.


>  _______________________________________________
>  epel-devel mailing list
>  epel-devel(a)lists.fedoraproject.org
>  http://lists.fedoraproject.org/admin/lists/[e-mail]... 


-- 
Stephen J Smoogen.

[Kevin Fenzi]

On Sat, 23 Jan 2016 10:15:19 -0700
Orion Poplawski <orion(a)cora.nwra.com&gt; wrote:

>  On 01/23/2016 09:32 AM, Randy Barlow wrote:
>  >> Since ansible 2.0 is (to a pretty high degree) compatible with the
>  >> same playbooks as 1.9.x, we are going to just update the existing
>  >> ansible package rather than create a parallel installable one.  
>  >
>  > Hello! I just wanted to point out that in practice the playbooks
>  > that I have written do not work in Ansible 2.0. You may be right
>  > that it is "close" to compatible, but I am concerned about this
>  > update and just wanted to share my voice.  
>  
>  Are these known issues upstream?  If not, I would file a bug report.
>  I know there are some unavoidable incompatibilities but otherwise
>  they are trying to make it compatible. 
Yes, I would be very interested in seeing these playbooks as well if
you can place them somewhere. 

I worked pretty extensively with upstream to make sure all the fedora
infrastructure playbooks worked fine with 2.0. We fixed a number of
corner case bugs before the release. I'm sure there's still bugs, but
the ansible folks have been hunting them down. (the current version of
2.0 is 2.0.0.2 with some fixes already). 

kevin