[openstack-dev] [infra] Stop enabling EPEL mirror by default

2017-04-04 Thread Paul Belanger
Greetings,

Recently we've been running into some issues keeping our EPEL mirror properly
sync'd. We are working to fix this, however we'd also like to do the following:

  Stop enabling EPEL mirror by default
  https://review.openstack.org/#/c/453222/

For the most part, we enable EPEL for our image build process, this to install
haveged.  However, it is also likely the majority of centos-7 projects don't
actually need EPEL.  I know specifically both RDO and TripleO avoid using the
EPEL repository because of how unstable it is.

Since it is possible this could be a breaking change, jobs will still be able to
use EPEL, but it will be an opt-in process. Your jobs will need to be updated to
do:

  $ sudo yum-config-manager --enable epel

Feel free to join us in openstack-infra if you have any questions or concerns.

-PB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra] Stop enabling EPEL mirror by default

2017-04-04 Thread Emilien Macchi
On Tue, Apr 4, 2017 at 1:02 PM, Paul Belanger  wrote:
> Greetings,
>
> Recently we've been running into some issues keeping our EPEL mirror properly
> sync'd. We are working to fix this, however we'd also like to do the 
> following:
>
>   Stop enabling EPEL mirror by default
>   https://review.openstack.org/#/c/453222/
>
> For the most part, we enable EPEL for our image build process, this to install
> haveged.  However, it is also likely the majority of centos-7 projects don't
> actually need EPEL.  I know specifically both RDO and TripleO avoid using the
> EPEL repository because of how unstable it is.
>
> Since it is possible this could be a breaking change, jobs will still be able 
> to
> use EPEL, but it will be an opt-in process. Your jobs will need to be updated 
> to
> do:
>
>   $ sudo yum-config-manager --enable epel
>
> Feel free to join us in openstack-infra if you have any questions or concerns.

On behalf of Puppet OpenStack and TripleO groups (both high consumers
of centos-7 nodes): no blocker, go for it.

> -PB
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra] Stop enabling EPEL mirror by default

2017-04-04 Thread Fox, Kevin M
It'll affect kolla-kubernetes, but we have a patch ready to go. Go for it.

Thanks,
Kevin

From: Emilien Macchi [emil...@redhat.com]
Sent: Tuesday, April 04, 2017 10:28 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [infra] Stop enabling EPEL mirror by default

On Tue, Apr 4, 2017 at 1:02 PM, Paul Belanger  wrote:
> Greetings,
>
> Recently we've been running into some issues keeping our EPEL mirror properly
> sync'd. We are working to fix this, however we'd also like to do the 
> following:
>
>   Stop enabling EPEL mirror by default
>   https://review.openstack.org/#/c/453222/
>
> For the most part, we enable EPEL for our image build process, this to install
> haveged.  However, it is also likely the majority of centos-7 projects don't
> actually need EPEL.  I know specifically both RDO and TripleO avoid using the
> EPEL repository because of how unstable it is.
>
> Since it is possible this could be a breaking change, jobs will still be able 
> to
> use EPEL, but it will be an opt-in process. Your jobs will need to be updated 
> to
> do:
>
>   $ sudo yum-config-manager --enable epel
>
> Feel free to join us in openstack-infra if you have any questions or concerns.

On behalf of Puppet OpenStack and TripleO groups (both high consumers
of centos-7 nodes): no blocker, go for it.

> -PB
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra] Stop enabling EPEL mirror by default

2017-04-04 Thread Ian Wienand
On 04/05/2017 03:02 AM, Paul Belanger wrote:
> Recently we've been running into some issues keeping our EPEL mirror
> properly sync'd. We are working to fix this, however we'd also like
> to do the following:

>   Stop enabling EPEL mirror by default
>   https://review.openstack.org/#/c/453222/

> For the most part, we enable EPEL for our image build process, this
> to install haveged.  However, it is also likely the majority of
> centos-7 projects don't actually need EPEL.  I know specifically
> both RDO and TripleO avoid using the EPEL repository because of how
> unstable it is.

I agree this is the step to turn it off in our gate, but I've been
trying to excise this so we move to a white-list method during builds,
which is more complicated.  This needs to be done, however, so that
3rd party CI who don't use our mirror scripts don't get EPEL hanging
around from the build too.

I'd appreciate reviews

Firstly, we need to ensure the image build EPEL dependencies we have
are flexible to changes in default status.

 * https://review.openstack.org/439294 : don't install ccache
 * https://review.openstack.org/439911 : allow "--enablerepo" options
 for haveged install
 * https://review.openstack.org/439917 : install haveged from EPEL

Then we need a way to install EPEL, but disabled, during image builds

 * https://review.openstack.org/439926 : Add flag to disable EPEL

Then stop installing EPEL as part of the puppet install, and switch to
installing it from dib in disabled state

 * https://review.openstack.org/453322 : Add epel element (with disabled flag)
 * https://review.openstack.org/439248 : Don't install EPEL during puppet

At this point, our base images should be coming up with only
whitelisted EPEL packages (haveged, unless I find anything else I've
missed) and the repo disabled.

-i

p.s. tangential; but related is

 *  https://review.openstack.org/453325 : use Centos openstack repos, not RDO

This could probably be also moved into DIB as an element, if
we feel strongly about it (or infra-package-needs ... but I wasn't
100% sure that's early enough yet)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra] Stop enabling EPEL mirror by default

2017-04-11 Thread Paul Belanger
On Tue, Apr 04, 2017 at 01:02:59PM -0400, Paul Belanger wrote:
> Greetings,
> 
> Recently we've been running into some issues keeping our EPEL mirror properly
> sync'd. We are working to fix this, however we'd also like to do the 
> following:
> 
>   Stop enabling EPEL mirror by default
>   https://review.openstack.org/#/c/453222/
> 
> For the most part, we enable EPEL for our image build process, this to install
> haveged.  However, it is also likely the majority of centos-7 projects don't
> actually need EPEL.  I know specifically both RDO and TripleO avoid using the
> EPEL repository because of how unstable it is.
> 
> Since it is possible this could be a breaking change, jobs will still be able 
> to
> use EPEL, but it will be an opt-in process. Your jobs will need to be updated 
> to
> do:
> 
>   $ sudo yum-config-manager --enable epel
> 
> Feel free to join us in openstack-infra if you have any questions or concerns.
> 
> -PB
> 
Just a heads up, I believe we'll be landing this change tomorrow. It's been a
week so far and no major outrage. :)

As always, you can find us in #openstack-infra if you have problems / questions.

-PB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra] Stop enabling EPEL mirror by default

2017-04-14 Thread Paul Belanger
On Tue, Apr 11, 2017 at 06:48:52PM -0400, Paul Belanger wrote:
> On Tue, Apr 04, 2017 at 01:02:59PM -0400, Paul Belanger wrote:
> > Greetings,
> > 
> > Recently we've been running into some issues keeping our EPEL mirror 
> > properly
> > sync'd. We are working to fix this, however we'd also like to do the 
> > following:
> > 
> >   Stop enabling EPEL mirror by default
> >   https://review.openstack.org/#/c/453222/
> > 
> > For the most part, we enable EPEL for our image build process, this to 
> > install
> > haveged.  However, it is also likely the majority of centos-7 projects don't
> > actually need EPEL.  I know specifically both RDO and TripleO avoid using 
> > the
> > EPEL repository because of how unstable it is.
> > 
> > Since it is possible this could be a breaking change, jobs will still be 
> > able to
> > use EPEL, but it will be an opt-in process. Your jobs will need to be 
> > updated to
> > do:
> > 
> >   $ sudo yum-config-manager --enable epel
> > 
> > Feel free to join us in openstack-infra if you have any questions or 
> > concerns.
> > 
> > -PB
> > 
> Just a heads up, I believe we'll be landing this change tomorrow. It's been a
> week so far and no major outrage. :)
> 
> As always, you can find us in #openstack-infra if you have problems / 
> questions.
> 
Another (final?) update. We are seeing issues with jobs that have bindep.txt
requirements for python34 from epel. In this case, you'll need to propose a
patch to project-config, specifically your JJB. And enable epel before running
our install-distro-packages macro.

Additionally, we have now removed python34 from bindep-fallback.txt. If you
still depend on it, you'll need to add it to your project bindep.txt file.

-PB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev