Re: [openstack-dev] [neutron][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

2018-10-09 Thread Michel Peterson
On Sun, Sep 30, 2018 at 3:43 AM Miguel Lavalle wrote: > The next step is for each project to propose the jobs that they want to > run against Neutron patches. > This is fantastic. Do you plan to have all patches under a single topic for easier tracking? I'll be handling the proposal of these

Re: [openstack-dev] [doc][i18n][infra][tc] plan for PDF and translation builds for documentation

2018-09-13 Thread Michel Peterson
On Thu, Sep 13, 2018 at 1:09 AM, Doug Hellmann wrote: > The longer version is that we want to continue to use the existing > tox environment in each project as the basis for the job, since > that allows teams to control the version of python used, the > dependencies installed, and add custom

Re: [openstack-dev] [networking-odl][networking-bgpvpn][ceilometer] all requirement updates are currently blocked

2018-09-12 Thread Michel Peterson
On Tue, Sep 11, 2018 at 7:29 AM, Tony Breeds wrote: > > So I think we have the required reviews lined up to fix master, but they > need votes from zuul and core teams. > > Thanks a lot for the work, Tony. On the n-odl side, when the Depends-On gets merged I'll give it a +W.

Re: [openstack-dev] [networking-odl][networking-bgpvpn][ceilometer] all requirement updates are currently blocked

2018-09-06 Thread Michel Peterson
On Wed, Sep 5, 2018 at 6:03 PM, Matthew Thode wrote: > On 18-08-31 19:52:09, Matthew Thode wrote: > > The requirements project has a co-installability test for the various > > projects, networking-odl being included. > > > > Because of the way the dependancy on ceilometer is done it is blocking

Re: [openstack-dev] [neutron] tox-siblings alternative for local testing

2018-08-30 Thread Michel Peterson
On Wed, Aug 29, 2018 at 9:06 AM, Takashi Yamamoto wrote: > is there any preferred solution for this? > i guess the simplest solution is to make an intermediate release of neutron > and publish it on pypi. i wonder if it's acceptable or not. > There are pre releases available in PyPI [1]. You

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

2018-08-30 Thread Michel Peterson
On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston wrote: > Progress is also being tracked in a wiki page [4]. > > [4] https://wiki.openstack.org/wiki/Python3 > That wiki page should only track teams or subteams should also be included there? I'm asking because it seems that some subteams appear

Re: [openstack-dev] [goal][python3] week 3 update

2018-08-30 Thread Michel Peterson
On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann wrote: > | import zuul job settings from project-config | openstack/networking-odl > | https://review.openstack.org/597870 | master| > | switch documentation job to new PTI | openstack/networking-odl > |

Re: [openstack-dev] [goal][python3] week 3 update

2018-08-30 Thread Michel Peterson
On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann wrote: > > OK, there are somewhere just over 100 patches for all of the neutron > > repositories, so I'm going to wait for a quieter time of day to submit > > them to avoid blocking other, smaller, bits of work. > > > > Doug > > Those patches are up

Re: [openstack-dev] [goal][python3] week 3 update

2018-08-28 Thread Michel Peterson
On Mon, Aug 27, 2018 at 10:37 PM, Doug Hellmann wrote: > > If your team is ready to have your zuul settings migrated, please > let us know by following up to this email. We will start with the > volunteers, and then work our way through the other teams. > The networking-odl team is willing to

[openstack-dev] [infra] Greasemonkey script to see CI progress on OpenStack's Gerrit

2018-07-08 Thread Michel Peterson
Hello everyone, I've created a greasemonkey script that will show you the status of the current CI run on the OpenStack Gerrit in real time. I put it together really quickly so there is room for improvement. You can find it here: https://gist.github.com/mpeterson/bb351543c4abcca8e7bb1205fcea4c75

Re: [openstack-dev] [all][requirements] uncapping eventlet

2018-05-07 Thread Michel Peterson
On Fri, Apr 20, 2018 at 11:06 PM, Doug Hellmann wrote: > > We have made great progress on this but we do still have quite a > few of these patches that have not been approved. Many are failing > test jobs and will need a little attention ( the failing requirements > jobs

Re: [openstack-dev] [kolla][neutron][requirements][pbr]Use git+https line in requirements.txt break the pip install

2018-04-18 Thread Michel Peterson
On Wed, Apr 18, 2018 at 12:02 PM, Michel Peterson <mic...@redhat.com> wrote: > How can we fix this? There are several ways I can think of the top of my > head: > > >1. When encountered with edge cases like this one, first install that >dependency with a manual pi

Re: [openstack-dev] [kolla][neutron][requirements][pbr]Use git+https line in requirements.txt break the pip install

2018-04-18 Thread Michel Peterson
Hi, I'm one of the networking-odl core devs. On Wed, Apr 18, 2018 at 5:48 AM, Jeffrey Zhang wrote: > > Recently, one of networking-odl package breaks kolla's gate[0]. The direct > issue is ceilometer is added in networking-odl's requirements.txt file[1] > This is an

[openstack-dev] [neutron] Generalized issues in the unit testing of ML2 mechanism drivers

2017-12-13 Thread Michel Peterson
Through my work in networking-odl I've found what I believe is an issue present in a majority of ML2 drivers. An issue I think needs awareness so each project can decide a course of action. The issue stems from the adopted practice of importing `neutron.tests.unit.plugins.ml2.test_plugin` and

Re: [openstack-dev] [neutron][oslo.db] db retry madness

2017-09-10 Thread Michel Peterson
Thanks for this most interesting and informative exchange. On Fri, Sep 8, 2017 at 5:20 PM, Michael Bayer wrote: > On Fri, Sep 8, 2017 at 8:53 AM, Kevin Benton wrote: > > Since the goal of that patch is to deal with deadlocks, the retry can't > > happen down