Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
1. in the next few days the packages should be promoted to the test repo [2] (currently it does not exist, we are waiting to be sync'ed in the background) 2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) *must be* 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.
The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
Il giorno mer 17 ott 2018 alle ore 11:39 Daniel Comnea < comnea.dani@gmail.com> ha scritto:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test
repo [2] (currently it does not exist, we are waiting to be sync'ed in the background) 2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) *must be* 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.
Hi, has the design for this centos-ansible package been discussed somewhere? Can we review its spec file before it lands on mirrors? Just willing to ensure it's not going to interfere with other sigs ansible builds and to check if this new package can be reused in Virt SIG or not.
The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/ _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
PSB
On Wed, Oct 17, 2018 at 11:02 AM Sandro Bonazzola sbonazzo@redhat.com wrote:
Il giorno mer 17 ott 2018 alle ore 11:39 Daniel Comnea < comnea.dani@gmail.com> ha scritto:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test
repo [2] (currently it does not exist, we are waiting to be sync'ed in the background) 2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) *must be* 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.
Hi, has the design for this centos-ansible package been discussed somewhere? Can we review its spec file before it lands on mirrors? Just willing to ensure it's not going to interfere with other sigs ansible builds and to check if this new package can be reused in Virt SIG or not. [DC]: Sandro i'll deffer that question to Brian as he is been working on this
The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift -origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/ _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA https://www.redhat.com/
sbonazzo@redhat.com https://red.ht/sig https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Oct 17 12:02, Sandro Bonazzola wrote:
Il giorno mer 17 ott 2018 alle ore 11:39 Daniel Comnea < comnea.dani@gmail.com> ha scritto:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test
repo [2] (currently it does not exist, we are waiting to be sync'ed in the background) 2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) *must be* 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.
Hi, has the design for this centos-ansible package been discussed somewhere? Can we review its spec file before it lands on mirrors? Just willing to ensure it's not going to interfere with other sigs ansible builds and to check if this new package can be reused in Virt SIG or not.
The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/ _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA https://www.redhat.com/
sbonazzo@redhat.com https://red.ht/sig https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Yes!
So far, since all the proper NVRs have been built in CBS we just cross-tagged those into the tags for shipping to the mirrors. We'll watch ansible upstream (https://releases.ansible.com/ansible/rpm/release/) and do a versioned centos-release-ansible package for each X.Y release. We'll also wrangle up the deps using a common directory
Example: Ansible 2.6
Buildlogs location: https://buildlogs.centos.org/centos/7/configmanagement/x86_64/ansible26/
Mirror location: http://mirror.centos.org/centos/7/configmanagement/x86_64/ansible26/
centos-release Test build: http://cbs.centos.org/koji/taskinfo?taskID=588210
Altarch pushes are coming as soon as we validate x86_64.
--Brian
On 10/17/18 3:38 AM, Daniel Comnea wrote:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test repo [2] (currently it does not exist, we are waiting to be sync'ed in the background)
- in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) /*must be*/ 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.
So does that mean we cannot test OKD v3.11 yet, unless we build our own version of ansible 2.6.x?
What will happen if we attempt to use ansible 2.7? I my testing, I get stuck at deploying the control plane pods - it seems the virtual networking was not set up by openshift-ansible.
The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
PSB
On Thu, Oct 18, 2018 at 6:17 PM Rich Megginson rmeggins@redhat.com wrote:
On 10/17/18 3:38 AM, Daniel Comnea wrote:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing
at [1].
As such we are calling for help from community to start testing and let
us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms
to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test
repo [2] (currently it does not exist, we are waiting to be sync'ed in the background)
- in one/two weeks time if we haven't heard any issues/ blockers we
are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) /*must be*/ 2.6.x
and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to
package and release a centos-ansible rpm which we'll promote in our PaaS repos.
So does that mean we cannot test OKD v3.11 yet, unless we build our own version of ansible 2.6.x? [DC]: so i've been waiting for Infra guys to build the rpm but they are traveling and as such i went ahead and tagged ansible 2.6. and it should appear [1] in next 15/20 min. That should unblock you all from testing it.
What will happen if we attempt to use ansible 2.7? I my testing, I get stuck at deploying the control plane pods - it seems the virtual networking was not set up by openshift-ansible. [DC]: there been few issues reported on this topic and since they were already know we made it clear which ansible version is supported (read - it works) and which not.
The rational is to bring more control around the ansible version used/
required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused
friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2]
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/
[3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Is Ansible not available in EPEL or not recommended? The last time I installed; I got 2.6 version.
I do turn off the EPEL repo after Ansible is installed when installing OpenShift.
On Oct 18, 2018 11:11 AM, "Daniel Comnea" comnea.dani@gmail.com wrote:
PSB
On Thu, Oct 18, 2018 at 6:17 PM Rich Megginson rmeggins@redhat.com wrote:
On 10/17/18 3:38 AM, Daniel Comnea wrote:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing
at [1].
As such we are calling for help from community to start testing and let
us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms
to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test
repo [2] (currently it does not exist, we are waiting to be sync'ed in the background)
- in one/two weeks time if we haven't heard any issues/ blockers we
are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) /*must be*/ 2.6.x
and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to
package and release a centos-ansible rpm which we'll promote in our PaaS repos.
So does that mean we cannot test OKD v3.11 yet, unless we build our own version of ansible 2.6.x? [DC]: so i've been waiting for Infra guys to build the rpm but they are traveling and as such i went ahead and tagged ansible 2.6. and it should appear [1] in next 15/20 min. That should unblock you all from testing it.
What will happen if we attempt to use ansible 2.7? I my testing, I get stuck at deploying the control plane pods - it seems the virtual networking was not set up by openshift-ansible. [DC]: there been few issues reported on this topic and since they were already know we made it clear which ansible version is supported (read - it works) and which not.
The rational is to bring more control around the ansible version used/
required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused
friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2]
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/
[3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 10/18/18 12:18 PM, Larry Brigman wrote:
Is Ansible not available in EPEL or not recommended? The last time I installed; I got 2.6 version.
Looks like EPEL7 has ansible 2.7:
# repoquery -i ansible
Name : ansible Version : 2.7.0 Release : 1.el7 Architecture: noarch Size : 62685201 Packager : Fedora Project Group : Development/Libraries URL : http://ansible.com Repository : epel_7
I do turn off the EPEL repo after Ansible is installed when installing OpenShift.
I used to enable epel7 for jq, but it looks like jq is being added to openshift
On Oct 18, 2018 11:11 AM, "Daniel Comnea" <comnea.dani@gmail.com mailto:comnea.dani@gmail.com> wrote:
PSB On Thu, Oct 18, 2018 at 6:17 PM Rich Megginson <rmeggins@redhat.com <mailto:rmeggins@redhat.com>> wrote: On 10/17/18 3:38 AM, Daniel Comnea wrote: > Hi, > > We would like to announce that OKD v3.11 rpms are available for testing at [1]. > > As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies. > > And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org <http://mirror.centos.org> repo: > > 1. in the next few days the packages should be promoted to the test repo [2] (currently it does not exist, we are waiting to be sync'ed in the background) > 2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed) > > > Please note the ansbile version use (and supported) /*must be*/ 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues. > > On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos. So does that mean we cannot test OKD v3.11 yet, unless we build our own version of ansible 2.6.x? [DC]: so i've been waiting for Infra guys to build the rpm but they are traveling and as such i went ahead and tagged ansible 2.6. and it should appear [1] in next 15/20 min. That should unblock you all from testing it. What will happen if we attempt to use ansible 2.7? I my testing, I get stuck at deploying the control plane pods - it seems the virtual networking was not set up by openshift-ansible. [DC]: there been few issues reported on this topic and since they were already know we made it clear which ansible version is supported (read - it works) and which not. > > The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused > friction recently (reflected on our CI as well as users reporting issues) > > > Thank you, > PaaS SiG team > > [1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ > [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ > [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/ > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel@centos.org <mailto:CentOS-devel@centos.org> > https://lists.centos.org/mailman/listinfo/centos-devel _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org <mailto:CentOS-devel@centos.org> https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi all,
First of all sorry for the late reply as well as for any confusion i may have caused with my previous email. I was very pleased to see the vibe and excitement around testing OKD v3.11, very much appreciated.
Here are the latest info:
- everyone who wants to help us with testing should use [1] repo which can be consumed: - in the inventory as [2] or - by deploying your own repo file [3] - nobody should use the repo i've mentioned in my previous email [4] (CentOS Infra team corrected me on the confusion i made, once again apologies for that)
Regarding the ansible version here are the info following my sync up with CentOS Infra team:
- very likely on Monday/ latest Tuesday a new rpm called centos-release-ansible26 will appear in CentOs Extras - the above rpm will become a dependency for the *centos-release-openshift-origin311* rpm which will be created and land in CentOS Extras repo at the same time OKD v3.11 will be promoted to mirror.centos.org - note this is the same flow as it was for all versions prior to v3.11 ( the rpm provides the CentOS repo location for OKD rpms).
*Note*:
1. if your flow up until now was to never use *centos-release-openshift-originXXX* rpm and you were creating your own repo files then you will need to make sure you pull as dependency the ansible 2.6.x (together with its own dependencies) rpm. It is up to you from where you are going to pull the ansible rpm: from Epel, from CentOS Extras etc. 2. with the above we are trying to have a single way of solving the ansible dependency problem
Hopefully this brings more clarity around this topic.
Thank you, PaaS SiG team
[1] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [2]
[OSEv3:vars] (...) openshift_additional_repos=[{'id': 'centos-okd-ci', 'name': 'centos-okd-ci', 'baseurl' :'http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311%7D/', 'gpgcheck' :'0', 'enabled' :'1'}]
[3] [centos-openshift-origin311-testing] name=CentOS OpenShift Origin Testing baseurl= http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311%7D/ enabled=0 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-PaaS
[4] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/
On Wed, Oct 17, 2018 at 10:38 AM Daniel Comnea comnea.dani@gmail.com wrote:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test
repo [2] (currently it does not exist, we are waiting to be sync'ed in the background) 2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) *must be* 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.
The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
Do you have a preferred public URL that I can use to help get the word out? If not, can you please consider turning this announcement into a blog post either on your website or on blogs.centos.org? Thanks.
On 10/17/18 10:38 AM, Daniel Comnea wrote:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test repo [2] (currently it does not exist, we are waiting to be sync'ed in the background)
- in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) /*must be*/ 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.
The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi Rich,
sorry for the late reply, i will consider doing that next time trying to write a blog post.
Dani
On Tue, Oct 23, 2018 at 10:38 AM Rich Bowen rbowen@redhat.com wrote:
Do you have a preferred public URL that I can use to help get the word out? If not, can you please consider turning this announcement into a blog post either on your website or on blogs.centos.org? Thanks.
On 10/17/18 10:38 AM, Daniel Comnea wrote:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies.
And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo:
- in the next few days the packages should be promoted to the test repo [2] (currently it does not exist, we are waiting to be sync'ed in the background)
- in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed)
Please note the ansbile version use (and supported) /*must be*/ 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues.
On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos.
The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues)
Thank you, PaaS SiG team
[1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2]
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/
[3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-- Rich Bowen: CentOS Community Manager rbowen@redhat.com @rbowen // @CentOSProject 1 859 351 9166 _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
Brian Stinson -
Daniel Comnea -
Larry Brigman -
Rich Bowen -
Rich Megginson -
Sandro Bonazzola