Just a heads up that ansible-core (the engine part of ansible) is now in CentOS stream 9:
https://gitlab.com/redhat/centos-stream/rpms/ansible-core
Note that this is the engine, you will likely want to install collections for modules and roles, etc.
kevin
On Wed, Sep 15, 2021 at 3:48 PM Kevin Fenzi kevin@scrye.com wrote:
Just a heads up that ansible-core (the engine part of ansible) is now in CentOS stream 9:
https://gitlab.com/redhat/centos-stream/rpms/ansible-core
Note that this is the engine, you will likely want to install collections for modules and roles, etc.
For those that might not have followed how Ansible has been refactored, take a look at https://www.ansible.com/blog/ansible-3.0.0-qa
ansible-core is the lowest level of the ansible stack and does not include many of the modules and plugins that those using ansible engine (ansible-2.9) might be used to. As Kevin said, you will almost certainly need additional modules/plugins not provided by ansible-core.
josh
On 16.09.21 14:22, Josh Boyer wrote:
On Wed, Sep 15, 2021 at 3:48 PM Kevin Fenzi kevin@scrye.com wrote:
Just a heads up that ansible-core (the engine part of ansible) is now in CentOS stream 9:
https://gitlab.com/redhat/centos-stream/rpms/ansible-core
Note that this is the engine, you will likely want to install collections for modules and roles, etc.
For those that might not have followed how Ansible has been refactored, take a look at https://www.ansible.com/blog/ansible-3.0.0-qa
ansible-core is the lowest level of the ansible stack and does not include many of the modules and plugins that those using ansible engine (ansible-2.9) might be used to. As Kevin said, you will almost certainly need additional modules/plugins not provided by ansible-core.
Out of curiosity
Does CS9 provide additional (sub)packages to extend the functionality?
Right now EPEL8 provide the the full stack based on ansible 2.9.
Will EPEL9 provide such packages to provide additional modules/plugins?
And more a ansible question: Does ansible3 provide a dependencies manager as consequence now?
--
Thanks Leon
On Thu, Sep 16, 2021 at 10:10 AM Leon Fauster leonfauster@googlemail.com wrote:
On 16.09.21 14:22, Josh Boyer wrote:
On Wed, Sep 15, 2021 at 3:48 PM Kevin Fenzi kevin@scrye.com wrote:
Just a heads up that ansible-core (the engine part of ansible) is now in CentOS stream 9:
https://gitlab.com/redhat/centos-stream/rpms/ansible-core
Note that this is the engine, you will likely want to install collections for modules and roles, etc.
For those that might not have followed how Ansible has been refactored, take a look at https://www.ansible.com/blog/ansible-3.0.0-qa
ansible-core is the lowest level of the ansible stack and does not include many of the modules and plugins that those using ansible engine (ansible-2.9) might be used to. As Kevin said, you will almost certainly need additional modules/plugins not provided by ansible-core.
Out of curiosity
Does CS9 provide additional (sub)packages to extend the functionality?
Not generally. ansible-core has been added to CS9 in support of System Roles only. This is analogous to how ansible is made available in RHEL 8. System Roles will include the modules/plugins it needs to manage the various areas of the OS, but they are not general purpose ansible packages.
Right now EPEL8 provide the the full stack based on ansible 2.9.
Will EPEL9 provide such packages to provide additional modules/plugins?
And more a ansible question: Does ansible3 provide a dependencies manager as consequence now?
I'll leave these for Kevin or someone else to answer in terms of EPEL 9 plans.
josh
I believe ansible-core includes a "dependency manager" depending on your definition. The ansible-galaxy command in ansible-core can install ansible collections so that's you can install modules that you may need.
It is similar in scope to pip, rubygem, cargo, or any other of the language package installers.
It does not resolve based on what modules/plugins are used in your playbooks but it will resolve dependencies between collection dependencies if needed (and those deps were properly listed).
I know that Nirik has plans to get newer ansible packages into epel which provide an all-in-one experience by installing about 75 collections which give you an experience similar what was included in ansible-2.9 but I'll let him speak to how he wants to do that.
-Toshio
On Thu, Sep 16, 2021, 7:20 AM Josh Boyer jwboyer@redhat.com wrote:
On Thu, Sep 16, 2021 at 10:10 AM Leon Fauster leonfauster@googlemail.com wrote:
On 16.09.21 14:22, Josh Boyer wrote:
On Wed, Sep 15, 2021 at 3:48 PM Kevin Fenzi kevin@scrye.com wrote:
Just a heads up that ansible-core (the engine part of ansible) is now
in
CentOS stream 9:
https://gitlab.com/redhat/centos-stream/rpms/ansible-core
Note that this is the engine, you will likely want to install collections for modules and roles, etc.
For those that might not have followed how Ansible has been refactored, take a look at https://www.ansible.com/blog/ansible-3.0.0-qa
ansible-core is the lowest level of the ansible stack and does not include many of the modules and plugins that those using ansible engine (ansible-2.9) might be used to. As Kevin said, you will almost certainly need additional modules/plugins not provided by ansible-core.
Out of curiosity
Does CS9 provide additional (sub)packages to extend the functionality?
Not generally. ansible-core has been added to CS9 in support of System Roles only. This is analogous to how ansible is made available in RHEL 8. System Roles will include the modules/plugins it needs to manage the various areas of the OS, but they are not general purpose ansible packages.
Right now EPEL8 provide the the full stack based on ansible 2.9.
Will EPEL9 provide such packages to provide additional modules/plugins?
And more a ansible question: Does ansible3 provide a dependencies manager as consequence now?
I'll leave these for Kevin or someone else to answer in terms of EPEL 9 plans.
josh _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Thu, Sep 16, 2021 at 08:02:08AM -0700, Toshio Kuratomi wrote:
I believe ansible-core includes a "dependency manager" depending on your definition. The ansible-galaxy command in ansible-core can install ansible collections so that's you can install modules that you may need.
It is similar in scope to pip, rubygem, cargo, or any other of the language package installers.
It does not resolve based on what modules/plugins are used in your playbooks but it will resolve dependencies between collection dependencies if needed (and those deps were properly listed).
I know that Nirik has plans to get newer ansible packages into epel which provide an all-in-one experience by installing about 75 collections which give you an experience similar what was included in ansible-2.9 but I'll let him speak to how he wants to do that.
Yeah.
For EPEL9, I hope to: * Make a 'ansible' package thats the collections in upstream 'ansible', minus any collections that are packaged seperately (either in rhel9 or epel9) and a 'ansible' metapackage. * Have that 'ansible' metapackage require all those collections and ansible-core, so when someone does 'dnf install ansible' they get hopefully pretty close to what upstream ansible is now.
I'm not sure if there will be problems with that yet tho. ;)
I'm hoping to basically do this for Fedora 36, so I should know more after that.
kevin --
-Toshio
On Thu, Sep 16, 2021, 7:20 AM Josh Boyer jwboyer@redhat.com wrote:
On Thu, Sep 16, 2021 at 10:10 AM Leon Fauster leonfauster@googlemail.com wrote:
On 16.09.21 14:22, Josh Boyer wrote:
On Wed, Sep 15, 2021 at 3:48 PM Kevin Fenzi kevin@scrye.com wrote:
Just a heads up that ansible-core (the engine part of ansible) is now
in
CentOS stream 9:
https://gitlab.com/redhat/centos-stream/rpms/ansible-core
Note that this is the engine, you will likely want to install collections for modules and roles, etc.
For those that might not have followed how Ansible has been refactored, take a look at https://www.ansible.com/blog/ansible-3.0.0-qa
ansible-core is the lowest level of the ansible stack and does not include many of the modules and plugins that those using ansible engine (ansible-2.9) might be used to. As Kevin said, you will almost certainly need additional modules/plugins not provided by ansible-core.
Out of curiosity
Does CS9 provide additional (sub)packages to extend the functionality?
Not generally. ansible-core has been added to CS9 in support of System Roles only. This is analogous to how ansible is made available in RHEL 8. System Roles will include the modules/plugins it needs to manage the various areas of the OS, but they are not general purpose ansible packages.
Right now EPEL8 provide the the full stack based on ansible 2.9.
Will EPEL9 provide such packages to provide additional modules/plugins?
And more a ansible question: Does ansible3 provide a dependencies manager as consequence now?
I'll leave these for Kevin or someone else to answer in terms of EPEL 9 plans.
josh _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 16.09.21 19:47, Kevin Fenzi wrote:
On Thu, Sep 16, 2021 at 08:02:08AM -0700, Toshio Kuratomi wrote:
I believe ansible-core includes a "dependency manager" depending on your definition. The ansible-galaxy command in ansible-core can install ansible collections so that's you can install modules that you may need.
It is similar in scope to pip, rubygem, cargo, or any other of the language package installers.
It does not resolve based on what modules/plugins are used in your playbooks but it will resolve dependencies between collection dependencies if needed (and those deps were properly listed).
I know that Nirik has plans to get newer ansible packages into epel which provide an all-in-one experience by installing about 75 collections which give you an experience similar what was included in ansible-2.9 but I'll let him speak to how he wants to do that.
Yeah.
For EPEL9, I hope to:
- Make a 'ansible' package thats the collections in upstream 'ansible', minus any collections that are packaged seperately (either in rhel9 or
epel9) and a 'ansible' metapackage.
- Have that 'ansible' metapackage require all those collections and ansible-core, so
when someone does 'dnf install ansible' they get hopefully pretty close to what upstream ansible is now.
I'm not sure if there will be problems with that yet tho. ;)
I'm hoping to basically do this for Fedora 36, so I should know more after that.
That would be amazing! Is it in rawhide already?
Thanks for your hard work.
-- Leon
On Thu, Sep 16, 2021 at 08:18:30PM +0200, Leon Fauster wrote:
On 16.09.21 19:47, Kevin Fenzi wrote:
On Thu, Sep 16, 2021 at 08:02:08AM -0700, Toshio Kuratomi wrote:
I believe ansible-core includes a "dependency manager" depending on your definition. The ansible-galaxy command in ansible-core can install ansible collections so that's you can install modules that you may need.
It is similar in scope to pip, rubygem, cargo, or any other of the language package installers.
It does not resolve based on what modules/plugins are used in your playbooks but it will resolve dependencies between collection dependencies if needed (and those deps were properly listed).
I know that Nirik has plans to get newer ansible packages into epel which provide an all-in-one experience by installing about 75 collections which give you an experience similar what was included in ansible-2.9 but I'll let him speak to how he wants to do that.
Yeah.
For EPEL9, I hope to:
- Make a 'ansible' package thats the collections in upstream 'ansible', minus any collections that are packaged seperately (either in rhel9 or
epel9) and a 'ansible' metapackage.
- Have that 'ansible' metapackage require all those collections and ansible-core, so
when someone does 'dnf install ansible' they get hopefully pretty close to what upstream ansible is now.
I'm not sure if there will be problems with that yet tho. ;)
I'm hoping to basically do this for Fedora 36, so I should know more after that.
That would be amazing! Is it in rawhide already?
Thanks for your hard work.
ansible-core is, but not the collections meta. Right now in rawhide 'ansible' is still 'ansible classic/2.9.x'
kevin
epel-devel@lists.fedoraproject.org