Re: [openstack-dev] [Zun] Add Deepak Mourya to the core team

2018-05-13 Thread Shuai Zhao
+1, welcome mourya007 ! On Mon, May 14, 2018 at 12:30 PM, Hongbin Lu wrote: > Hi all, > > This is an announcement of the following change on the Zun core reviewers > team: > > + Deepak Mourya (mourya007) > > Deepak has been actively involving in Zun for several months. He has > submitted several

[openstack-dev] [Zun] Add Deepak Mourya to the core team

2018-05-13 Thread Hongbin Lu
Hi all, This is an announcement of the following change on the Zun core reviewers team: + Deepak Mourya (mourya007) Deepak has been actively involving in Zun for several months. He has submitted several code patches to Zun, all of which are useful features or bug fixes. In particular, I would l

Re: [openstack-dev] [tripleo] tripleo upstream gate outtage, was: -> gate jobs impacted RAX yum mirror

2018-05-13 Thread Tristan Cacqueray
On May 14, 2018 2:44 am, Wesley Hayutin wrote: [snip] I do think it would be helpful to say have a one week change window where folks are given the opportunity to preflight check a new image and the potential impact on the job workflow the updated image may have. [snip] How about adding a perio

Re: [openstack-dev] [tripleo] tripleo upstream gate outtage, was: -> gate jobs impacted RAX yum mirror

2018-05-13 Thread Jeremy Stanley
On 2018-05-13 20:44:25 -0600 (-0600), Wesley Hayutin wrote: [...] > I do think it would be helpful to say have a one week change > window where folks are given the opportunity to preflight check a > new image and the potential impact on the job workflow the updated > image may have. If I could upda

Re: [openstack-dev] [neutron][ml2 plugin] unit test errors

2018-05-13 Thread Sangho Shin
Andreas and Neil, Thank you so much for your help. I was able to fix the issues thanks to your help. Sangho 나의 iPhone에서 보냄 2018. 5. 11. 오후 7:19, Neil Jerram 작성: >> On Fri, May 11, 2018 at 10:09 AM Andreas Scheuring >> wrote: >> So what you need to do first is to make a patch for networking

Re: [openstack-dev] [tripleo] tripleo upstream gate outtage, was: -> gate jobs impacted RAX yum mirror

2018-05-13 Thread Wesley Hayutin
On Sun, May 13, 2018 at 11:25 AM Jeremy Stanley wrote: > On 2018-05-13 08:25:25 -0600 (-0600), Wesley Hayutin wrote: > [...] > > We need to in coordination with the infra team be able to pin / lock > > content for production check and gate jobs while also have the ability to > > stage new content

Re: [openstack-dev] [tempest] Proposing Felipe Monteiro for Tempest core

2018-05-13 Thread Ghanshyam Mann
Thanks all for voting. We have all voting in favor of Felipe and enough to add him as Core. I will add him in Core list on gerrit. Welcome to the team Felipe!! -gmann On Sat, Apr 28, 2018 at 7:27 PM, Ghanshyam Mann wrote: > Hi Tempest Team, > > I would like to propose Felipe Monteiro (irc:

Re: [openstack-dev] Should we add a tempest-slow job?

2018-05-13 Thread Ghanshyam Mann
On Sun, May 13, 2018 at 1:20 PM, Ghanshyam Mann wrote: > On Fri, May 11, 2018 at 10:45 PM, Matt Riedemann wrote: >> The tempest-full job used to run API and scenario tests concurrently, and if >> you go back far enough I think it also ran slow tests. >> >> Sometime in the last year or so, the ful

Re: [openstack-dev] [tripleo] tripleo upstream gate outtage, was: -> gate jobs impacted RAX yum mirror

2018-05-13 Thread Matt Young
Re: resolving network latency issue on the promotion server in tripleo-infra tenant, that's great news! Re: retrospective on this class of issue, I'll reach out directly early this week to get something on the calendar for our two teams. We clearly need to brainstorm/hash out together how we can

Re: [openstack-dev] [horizon] Scheduling switch to django >= 2.0

2018-05-13 Thread Thomas Goirand
On 05/11/2018 05:14 PM, Akihiro Motoki wrote: > Hi zigo and horizon plugin maintainers, > > Horizon itself already supports Django 2.0 and horizon unit test covers > Django 2.0 with Python 3.5. > > A question to all is whether we change the upper bound of Django from > <2.0 to <2.1. > My proposal

[openstack-dev] [requirements][barbican][daisycloud][freezer][fuel][heat][pyghmi][rpm-packaging][solum][tatu][trove] pycrypto is dead and insecure, you should migrate

2018-05-13 Thread Matthew Thode
This is a reminder to the projects called out that they are using old, unmaintained and probably insecure libraries (it's been dead since 2014). Please migrate off to use the cryptography library. We'd like to drop pycrypto from requirements for rocky. See also, the bug, which has most of you cc

Re: [openstack-dev] [tripleo] tripleo upstream gate outtage, was: -> gate jobs impacted RAX yum mirror

2018-05-13 Thread Jeremy Stanley
On 2018-05-13 08:25:25 -0600 (-0600), Wesley Hayutin wrote: [...] > We need to in coordination with the infra team be able to pin / lock > content for production check and gate jobs while also have the ability to > stage new content e.g. centos 7.5 with experimental or periodic jobs. [...] It look

Re: [openstack-dev] [tripleo] tripleo upstream gate outtage, was: -> gate jobs impacted RAX yum mirror

2018-05-13 Thread Wesley Hayutin
On Sat, May 12, 2018 at 11:45 PM Emilien Macchi wrote: > On Sat, May 12, 2018 at 9:10 AM, Wesley Hayutin > wrote: >> >> 2. Shortly after #1 was resolved CentOS released 7.5 which comes directly >> into the upstream repos untested and ungated. Additionally the associated >> qcow2 image and conta

Re: [openstack-dev] [tripleo] tripleo upstream gate outtage, was: -> gate jobs impacted RAX yum mirror

2018-05-13 Thread Jeremy Stanley
On 2018-05-12 20:44:04 -0700 (-0700), Emilien Macchi wrote: [...] > Why do we have this situation everytime the OS is upgraded to a major > version? Can't we test the image before actually using it? We could have > experimental jobs testing latest image and pin gate images to a specific > one? > >