hi,
https://git.centos.org/log/rpms!ansible.git/c7-extras
is now in CentOS-Extras/ - this is going to impact every SIG that uses ansible in and from cbs.centos.org, or needs specific versions pin'd for their roles ( paas / cloud sig etc )
is there anything the SIG's need to validate before this content hits mirror.centos.org in a few days time ?
2017-09-08 0:38 GMT+02:00 Karanbir Singh mail-lists@karan.org:
Nothing on oVirt side.
On Thu, Sep 07, 2017 at 11:38:14PM +0100, Karanbir Singh wrote:
It makes me happy to see this becoming part of CentOS-Extras. I thought someone mentioned that Ansible is a standard component of RHEL 7.4, and I was waiting for the next CentOS update to get Ansible without needing to add dependencies on a repository from the opstools SIG.
Having Ansible available now already, makes it possible for me to just tag gdeploy (tool for deploying Gluster environments) into -release.
Thanks! Niels
On Fri, Sep 8, 2017 at 4:12 AM, Niels de Vos ndevos@redhat.com wrote:
I assume this is the same ansible that is in RHEL 7 Extras, and will follow the same update path and timing as RHEL's. If it's something different, then let us know.
I'm excited about this. This should be less work for our SIG, and should make it so the different SIG's all have slightly different ansibles.
Troy
On 08/09/17 14:36, Troy Dawson wrote:
the new ver is 2.3.1 - newer than what we ship in PaaS SIG, and running my prisioner for a 6 node cluster, failed with type errors. fwiw, master from openshift-ansible does work ok though.
On 08/09/17 17:31, Karanbir Singh wrote:
Yes, the fact that Ansible will be available directly can be a good and bad thing at the same time. SIG will have no other choice than ensuring that their installers always work with the ansible version that will be shipped automatically in Extras, and there will be no easy way to "tag" a specific version in a repo. (Well, a newer version can still be built through cbs and tagged for a specific SIG repo, but impossible to do for a lower version)
I think this is great news.
We'd like to have the opportunity to test it in the cloud SIG, is there a way to do that before it's in the wild ?
David Moreau Simard Senior Software Engineer | OpenStack RDO
dmsimard = [irc, github, twitter]
On Thu, Sep 7, 2017 at 6:38 PM, Karanbir Singh mail-lists@karan.org wrote:
Hi,
The ansible available in EPEL7 http://pkgs.fedoraproject.org/cgit/rpms/ansible.git/log/ will become deprecated and no new builds (like the latest ansible 2.4.0.0) will be made in EPEL7. It would be nice to have the latest ansible packaged for CentOS7 somewhere outside of EPEL - are there any plans how to handle this?
Cheers
Marcin
On Fri, Sep 8, 2017 at 7:18 PM, Brian Stinson brian@bstinson.com wrote:
The SIG's have been building the latest ansible in cbs. We (the Paas SIG) were originally doing it, but because our needs have leveled off, we have passed that torch on to the Virt SIG. https://cbs.centos.org/koji/buildinfo?buildID=19977
On Fri, Sep 22, 2017 at 6:09 AM, Marcin Dulak marcin.dulak@gmail.com wrote:
On Fri, Sep 22, 2017 at 3:23 PM, Troy Dawson tdawson@redhat.com wrote:
is it available somewhere as a yum repo to be rsynced locally as a local mirror?
Marcin
On Fri, Sep 22, 2017 at 6:44 AM, Marcin Dulak marcin.dulak@gmail.com wrote:
https://buildlogs.centos.org/centos/7/virt/x86_64/ovirt-4.1/
or, if you want the latest as fast as it's built
https://cbs.centos.org/repos/virt7-ovirt-common-candidate/x86_64/os/
Hi,
is there a reason the packages from https://cbs.centos.org/repos/virt7-ovirt-common-candidate/ are not signed?
Marcin
On Fri, Sep 22, 2017 at 6:40 PM, Troy Dawson tdawson@redhat.com wrote:
On 11/10/17 15:53, Marcin Dulak wrote:
Yes, as those repos aren't the ones to be used, but temporary repositories created by koji/mash before they can be sent to signing and then released through mirror.centos.org
Worth noting that pkg in candidate will *never* be sent outside btw, and -testing will go to https://buildlogs.centos.org while -release will land on mirror.centos.org (per documented process in the SIG guide)
Which repository on mirror.centos.org will correspond to https://cbs.centos.org/repos/virt7-ovirt-common-candidate/?
Marcin
On Wed, Oct 11, 2017 at 4:06 PM, Fabian Arrotin arrfab@centos.org wrote:
On 10/11/2017 09:13 AM, Marcin Dulak wrote:
None .. only items tagged to 'virt7-ovirt-common-release' get signed and released.
The candidate items live only in the repos on cbs. CI can pull from there.
Things tagged to 'virt7-ovirt-common-testing' would be placed (unsigned) in:
https://buildlogs.centos.org/centos/7/virt/x86_64/<ovirt-version>/common/
You can put the items on buildlogs (testing repo) in mailing lists and have users test from there (that is mirrored and has some bandwidth / load for use by others .. cbs does not have the bandwidth or load for full user testing, that is what the testing repo on buildlogs is for).
And released stuff would go (signed) into:
http://mirror.centos.org/centos/7/virt/x86_64/<ovirt-version>/common/
On 22 September 2017 at 14:09, Marcin Dulak marcin.dulak@gmail.com wrote:
As part of the work carried out internally at Red Hat to make this change the Ansible team has put together their own yum repos that can be used as a direct source from upstream too ...
https://releases.ansible.com/ansible/rpm/
They have a variety of builds there that can be used:
* release - the stable released version * preview - betas and release candidates leading up to a release * nightly - nightly builds of the devel and stable-* branches in git for early testing or fixes
The nightly repos sound especially useful for an "early warning" CI setup of testing ansible roles.
This is nice, and the packages as signed.
Marcin
On Mon, Oct 16, 2017 at 12:52 PM, James Hogarth james.hogarth@gmail.com wrote:
-
Brian Stinson -
David Moreau Simard -
Fabian Arrotin -
James Hogarth -
Johnny Hughes -
Karanbir Singh -
Marcin Dulak -
Niels de Vos -
Sandro Bonazzola -
Troy Dawson