Re: [openstack-dev] Removing internet access from unit test gates

Excerpts from Jens Harbott's message of 2017-11-24 13:22:23 +: > 2017-11-21 15:04 GMT+00:00 Jeremy Stanley : > > On 2017-11-21 09:28:20 +0100 (+0100), Thomas Goirand wrote: > > [...] > >> The only way that I see going forward, is having internet access > >> removed from unit

Re: [openstack-dev] Removing internet access from unit test gates

2017-11-21 15:04 GMT+00:00 Jeremy Stanley : > On 2017-11-21 09:28:20 +0100 (+0100), Thomas Goirand wrote: > [...] >> The only way that I see going forward, is having internet access >> removed from unit tests in the gate, or probably just the above >> variables set. > [...] ...

Re: [openstack-dev] Removing internet access from unit test gates

On 2017-11-21 13:11:36 -0800 (-0800), James E. Blair wrote: [...] > If something like this is desirable, I think tox.ini may be the best > place for it, as it will cause local test runs to behave the same way as > in Zuul. This is a great point, any workarounds which need root privileges (e.g.,

Re: [openstack-dev] Removing internet access from unit test gates

Jeremy Stanley writes: > On 2017-11-21 17:46:14 +0100 (+0100), Thomas Goirand wrote: > [...] >> Doing this kind of a patch at first on a few project's tox.ini, >> absolutely! I might even start with Horizon and PBR (yes, there's a >> problem there as well... which I haven't

Re: [openstack-dev] Removing internet access from unit test gates

On 2017-11-21 17:46:14 +0100 (+0100), Thomas Goirand wrote: [...] > Doing this kind of a patch at first on a few project's tox.ini, > absolutely! I might even start with Horizon and PBR (yes, there's a > problem there as well... which I haven't reported yet). Though > generalizing it to 300+

Re: [openstack-dev] Removing internet access from unit test gates

On 2017-11-21 13:34:57 -0500 (-0500), Paul Belanger wrote: [...] > I don't think we'd need to use security groups, we could just > setup a local firewall ruleset to do this on the node if we > wanted. [...] I considered suggesting that in my original reply, but then realized that we still have

Re: [openstack-dev] Removing internet access from unit test gates

questions) > > <openstack-dev@lists.openstack.org> > > Subject: Re: [openstack-dev] Removing internet access from unit test > > gates > > > > On 2017-11-21 09:28:20 +0100 (+0100), Thomas Goirand wrote: > > [...] > > > The only way that I see going forward,

Re: [openstack-dev] Removing internet access from unit test gates

On 11/21/2017 04:04 PM, Jeremy Stanley wrote: > Removing network access from the machines running these jobs won't > work, of course, because our job scheduling and execution service > needs to reach them over the Internet to start jobs, monitor > progress and collect results. Right. > As you

Re: [openstack-dev] Removing internet access from unit test gates

> -Original Message- > From: Jeremy Stanley [mailto:fu...@yuggoth.org] > Sent: Tuesday, November 21, 2017 3:05 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] Removing i

Re: [openstack-dev] Removing internet access from unit test gates

On 2017-11-21 09:28:20 +0100 (+0100), Thomas Goirand wrote: [...] > The only way that I see going forward, is having internet access > removed from unit tests in the gate, or probably just the above > variables set. [...] Historically, our projects hadn't done a great job of relegating their

[openstack-dev] Removing internet access from unit test gates

Hi everyone! I believe all distributions are running unit tests of packages, either at build time, or later on (for example in autopkgtest). In Debian, it's done mostly at build time. There it's forbidden to access internet, and on purpose, Debian buildd servers wont provide internet access when