Thanks!! When its ready we can add it again.
Thank you!
From: Emilien Macchi
Reply-To: OpenStack List
Date: Tuesday, February 20, 2018 at 9:14 AM
To: OpenStack List
Subject: Re: [openstack-dev] [neutron][l2gw] stable/queens tripleo issues
Hey Gary :-)
Yeah our CI isn't ready yet for stable/qu
Hey Gary :-)
Yeah our CI isn't ready yet for stable/queens, sorry for that.
I propose to disable TripleO jobs in stable/queens for l2gw project:
https://review.openstack.org/546059
Hopefully that helps!
Cheers,
On Mon, Feb 19, 2018 at 11:07 PM, Gary Kotton wrote:
> Hi,
>
> At the moment the s
Hi,
At the moment the stable/queens branch is broken due to the tripleo CI test
failing [i]. Does anyone have any hints here on what we should look at? I am
not sure if this is with ansible/centos…
Thanks
Gary
[i]
http://logs.openstack.org/88/543188/2/check/tripleo-ci-centos-7-scenario004-multin
On Mon, Feb 19, 2018 at 8:53 AM, Sean McGinnis
wrote:
[...]
>
> The final Queens RC deadline is Thursday, 22 FEBRUARY.
>
Too late, you said March. Thanks a lot for the extra-month :-)
/jk
--
Emilien Macchi
__
OpenStack Deve
On Mon, Feb 19, 2018 at 7:03 AM, Jeremy Stanley wrote:
[...]
> This is hopefully only a temporary measure? I think I've heard it
> mentioned that planning is underway to switch that CI system to Zuul
> v3 (perhaps after 3.0.0 officially releases soon).
>
Adding Tristan and Fabien in copy, they k
Perhaps we need to consider a backport of the syntax to the 2.5 series?
It could help with the transition for those who need to upgrade. However,
on the other hand it might make deployers more complacent to do so.
On Tue, Feb 20, 2018 at 2:03 AM, Jeremy Stanley wrote:
> On 2018-02-18 19:25:07 -
On Mon, Feb 19, 2018 at 10:00:59AM -0500, Michael Bayer wrote:
> Hi list -
>
> Apparently Cinder was misled by my deprecations within the
> oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
> in https://review.openstack.org/#/c/522290/ the assumption was made
> that these shoul
On Mon, Feb 19, 2018 at 03:24:24PM +0100, Bogdan Dobrelya wrote:
> With a backport of the YAQL fixes for tht made for Pike, would it be the
> full fix to make a backport of yaql 1.1.3 for Pike repos as well? Or am I
> missing something?
At some level that should be fine. In the broader OpenSteck
On Mon, Feb 19, 2018 at 06:10:56PM +0100, Alfredo Moralejo Alonso wrote:
> Recently, we have added a job in post pipeline for openstack/requirements
> in https://review.rdoproject.org to
> automatically post updates in RDO dependencies repo when changes are
> detected in upper-constraints. This
>
On 17/02/18 16:40, Dan Prince wrote:
Thanks for the update Emilien. A couple of things to add:
1) This was really difficult to pin-point via the Heat stack error
message ('list index out of range'). I actually had to go and add
LOG.debug statements to Heat to get to the bottom of it. I aim to sy
Howdy Stackers,
I’ve set up the review priorities etherpad [1] for us to use during the Rocky
cycle. It’s the same format we had back in Pike with the exception of a couple
of new sections I’ve added: "Non-priority approved blueprints” and "Co-authors
wanted”. The idea of the etherpad is to org
Hello everyone,
A new release candidate for networking-midonet for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-midonet/
Unless release-critical issues are found that warrant a release
candidate respin, this ca
Hello everyone,
A new release candidate for networking-ovn for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-ovn/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hello everyone,
A new release candidate for neutron for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/neutron/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formal
Hello everyone,
A new release candidate for neutron-dynamic-routing for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/neutron-dynamic-routing/
Unless release-critical issues are found that warrant a release
candidate respi
There is one critical bug from this week:
https://bugs.launchpad.net/neutron/+bug/1749667 - neutron doesn't correctly
handle unknown protocols and should whitelist known and handled protocols
There is a fix in progress for this already, thanks Brian for picking this
up.
There are three bugs that s
Every open source community is made up of real people with real feelings. Many
open source contributors are working in their free time to provide essential
software that we use daily. Sometimes praise is lost in the feedback of bugs or
missing features. Focusing on too much negative feedback can le
Hi all,
There is one critical bug from this week:
https://bugs.launchpad.net/neutron/+bug/1749667 - neutron doesn't correctly handle unknown protocols and should whitelist known and handled protocols
There is a fix in progress for this already, thanks Brian for picking this up.
There are three
I saw election email with the pointer to votes.
See no reason for stopping it now. But extending vote for 1 more week makes
sense.
Thanks,
Arkady
From: Melvin Hillsman [mailto:mrhills...@gmail.com]
Sent: Monday, February 19, 2018 11:32 AM
To: user-committee ; OpenStack Mailing List
; OpenStack O
> Data migration from where to where? We access the current state by
retrieving the data from leader db, or am I missing something here?
In case there are changes in how data is stored in one version of a
charm vs the other.
Another problem is application versioning: we do have version-specif
Hi everyone,
We had to push the voting back a week if you have been keeping up with the
UC elections[0]. That being said, election officials have sent out the poll
and so voting is now open! Be sure to check out the candidates -
https://goo.gl/x183he - and get your vote in before the poll closes.
On Sun, Feb 18, 2018 at 1:35 AM, Tony Breeds
wrote:
> On Sat, Feb 17, 2018 at 04:40:12PM -0500, Dan Prince wrote:
> > Thanks for the update Emilien. A couple of things to add:
> >
> > 1) This was really difficult to pin-point via the Heat stack error
> > message ('list index out of range'). I act
Summarizing all the reviews:
Doug's proposed check in oslo_db.tests: https://review.openstack.org/#/c/545859/
Mark oslo_db internal fixtures private: https://review.openstack.org/545862
Cinder: https://review.openstack.org/545860
Neutron: https://review.openstack.org/545868
Ironic: https://revie
In case anyone is interested in the details, I went through the exercise of a
basic bringup of Istio on Magnum k8s (with stable/pike):
https://tiswanso.github.io/istio/istio_on_magnum.html
I hope to update with follow-on items that may also be explored, such as:
- Istio automatic side-car injec
On Mon, Feb 19, 2018 at 11:50:21AM -0500, David Moreau Simard wrote:
> On Mon, Feb 19, 2018 at 10:44 AM, Sean McGinnis wrote:
> > Hey everyone,
> >
> > Just a quick reminder that Thursday, 22 March, is the deadline for any final
> > Queens release candidates. After this point we will enter a quiet
Thanks for recording it!
David Moreau Simard
Senior Software Engineer | OpenStack RDO
dmsimard = [irc, github, twitter]
On Mon, Feb 19, 2018 at 9:41 AM, James Slagle wrote:
> As mentioned in the TripleO meeting last week, I volunteered to give a
> deep dive on the state of TripleO and Ansible
On Mon, Feb 19, 2018 at 10:44 AM, Sean McGinnis wrote:
> Hey everyone,
>
> Just a quick reminder that Thursday, 22 March, is the deadline for any final
> Queens release candidates. After this point we will enter a quiet period for a
> week in preparation of tagging the final Queens release during
Alex and I have been working on the agenda for next week, based on what
people proposed in topics.
The draft calendar is visible here:
https://calendar.google.com/calendar/embed?src=tgpb5tv12mlu7kge5oqertje78%40group.calendar.google.com&ctz=Europe%2FDublin
Also you can import the ICS from:
https:
Excerpts from Michael Bayer's message of 2018-02-19 10:55:52 -0500:
> wow that's heavy-handed. should that be in an oslo utility package of
> some kind ?
I thought about that, but figured we should wait and see whether we
actually want to take the approach before polishing it. If we do we can
add
On Mon, Feb 19, 2018 at 10:57 AM, Andrey Kurilin wrote:
> As for downstream you can do whatever you want, but it looks like this issue
> should be solved in upstream. I mean if "tests" directory is located at the
> top level of the repo, no one will use it.
again, the search at
http://codesearch.
Imo, it creates more problems than profits. If someone wants to change the
code and run tests -> use git repositories. Prepared python package is not
about this.
2018-02-19 17:57 GMT+02:00 Doug Hellmann :
> IIRC we started doing that so that consumers building their own packages
> can run the tes
As for downstream you can do whatever you want, but it looks like this
issue should be solved in upstream. I mean if "tests" directory is located
at the top level of the repo, no one will use it.
Also, setuptools supports `exclude` option which should solve the issue as
well.
2018-02-19 17:41 GM
IIRC we started doing that so that consumers building their own packages
can run the tests for the packages easily. I don't know how many people
are doing that, and apparently at least some downstream consumers aren't
packaging everything anyway so they couldn't run those tests.
Excerpts from Andr
wow that's heavy-handed. should that be in an oslo utility package of
some kind ?
On Mon, Feb 19, 2018 at 10:52 AM, Doug Hellmann wrote:
> Excerpts from Doug Hellmann's message of 2018-02-19 10:15:34 -0500:
>> Excerpts from Michael Bayer's message of 2018-02-19 10:00:59 -0500:
>> > Hi list -
>>
Excerpts from Doug Hellmann's message of 2018-02-19 10:15:34 -0500:
> Excerpts from Michael Bayer's message of 2018-02-19 10:00:59 -0500:
> > Hi list -
> >
> > Apparently Cinder was misled by my deprecations within the
> > oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
> > i
Hey everyone,
Just a quick reminder that Thursday, 22 March, is the deadline for any final
Queens release candidates. After this point we will enter a quiet period for a
week in preparation of tagging the final Queens release during the PTG week.
If you have any patches merged to stable/queens th
On Mon, Feb 19, 2018 at 10:39 AM, Andrey Kurilin wrote:
> Can someone explain me the reason for including "tests" module into
> packages?
the "tests" module should not be inside packages. Downstream we have
CI running Cinder's test suite against packaged dependencies, which
fails because we don
On Mon, Feb 19, 2018 at 10:15 AM, Doug Hellmann wrote:
> Excerpts from Michael Bayer's message of 2018-02-19 10:00:59 -0500:
>> Hi list -
>>
>> Apparently Cinder was misled by my deprecations within the
>> oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
>> in https://review.o
Can someone explain me the reason for including "tests" module into
packages?
2018-02-19 17:00 GMT+02:00 Michael Bayer :
> Hi list -
>
> Apparently Cinder was misled by my deprecations within the
> oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
> in https://review.openstac
On Mon, Feb 19, 2018 at 04:13:04PM +0100, Andreas Jaeger wrote:
> On 2018-02-19 16:00, Michael Bayer wrote:
> > Hi list -
> >
> > Apparently Cinder was misled by my deprecations within the
> > oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
> > in https://review.openstack.org
Excerpts from Michael Bayer's message of 2018-02-19 10:00:59 -0500:
> Hi list -
>
> Apparently Cinder was misled by my deprecations within the
> oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
> in https://review.openstack.org/#/c/522290/ the assumption was made
> that these
On 2018-02-19 16:00, Michael Bayer wrote:
> Hi list -
>
> Apparently Cinder was misled by my deprecations within the
> oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
> in https://review.openstack.org/#/c/522290/ the assumption was made
> that these should be imported from os
On Mon, Feb 19, 2018 at 9:05 AM, Dmitrii Shcherbakov
wrote:
> Hi Liam,
>
>> I was recently looking at how to support custom configuration that relies
>> on post deployment setup.
>
> I would describe the problem in general as follows:
>
> 1) charms can get context not only from Juju (config option
On 2018-02-18 19:25:07 -0800 (-0800), Emilien Macchi wrote:
[...]
> My recommendation for TripleO devs: use the old syntax if you want your
> code to be tested by RDO Third party CI
[...]
This is hopefully only a temporary measure? I think I've heard it
mentioned that planning is underway to switc
Hi list -
Apparently Cinder was misled by my deprecations within the
oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
in https://review.openstack.org/#/c/522290/ the assumption was made
that these should be imported from oslo_db.tests.sqlalchemy.This
is an immense mistake
Dear all,
updates:
- tempest-full-queens and tempest-full-py3-queens are now available for
testing of branchless repositories [0]. They are used for tempest and
devstack-gate. If you own a tempest plugin in a branchless repo, you may
consider adding similar jobs to your plugin if you use it for te
As mentioned in the TripleO meeting last week, I volunteered to give a
deep dive on the state of TripleO and Ansible integration with
config-download.
I'll do that this week on Thursday February 22nd at 1400UTC.
Anyone can join via bluejeans: https://bluejeans.com/7754237859/
Etherpad: https://bl
Nice, thanks for the reviews. I'll check with the release team if we don't
have a stable core approve them by midday.
On Sun, Feb 18, 2018 at 6:31 PM, Matt Riedemann wrote:
> On 2/1/2018 9:51 AM, Lance Bragstad wrote:
>
>> Just like with feature freeze, I put together a review dashboard that
>>
On 2/19/18 3:18 PM, Sofer Athlan-Guyot wrote:
Hi,
Emilien Macchi writes:
Upgrading YAQL from 1.1.0 to 1.1.3 breaks advanced queries with groupBy
aggregation.
The commit that broke it is
https://github.com/openstack/yaql/commit/3fb91784018de335440b01b3b069fe45dc53e025
It broke TripleO: https
Hi,
Emilien Macchi writes:
> Upgrading YAQL from 1.1.0 to 1.1.3 breaks advanced queries with groupBy
> aggregation.
>
> The commit that broke it is
> https://github.com/openstack/yaql/commit/3fb91784018de335440b01b3b069fe45dc53e025
>
> It broke TripleO: https://bugs.launchpad.net/tripleo/+bug/17
I promise this is the last time I'll bug you about this. (Except
on-site, of course!)
I still have lots and lots of space for team/project/whatever interviews
at the PTG. You can sign up at
https://docs.google.com/spreadsheets/d/1MK7rCgYXCQZP1AgQ0RUiuc-cEXIzW5RuRzz5BWhV4nQ/edit#gid=0
You c
On Fri, 16 Feb 2018 17:49:37 +0100
Thomas Goirand wrote:
> On 02/16/2018 03:42 PM, Petr Kovar wrote:
> > On Thu, 15 Feb 2018 09:31:19 +0100
> > Thomas Goirand wrote:
> >
> >> Hi,
> >>
> >> Since I'm getting some pressure from other DDs to actively remove Py2
> >> support from my packages, I'm v
Hello all,
A very late mail to highlight that there will once again be a 1 day
track/room dedicated to talking about Fast-forward upgrades at the
upcoming PTG in Dublin. The etherpad for which is listed below:
https://etherpad.openstack.org/p/ffu-ptg-rocky
Please feel free to add items to the pa
Hi,
On Sat, Feb 17, 2018 at 10:40 PM, Dan Prince wrote:
> Thanks for the update Emilien. A couple of things to add:
>
> 1) This was really difficult to pin-point via the Heat stack error
> message ('list index out of range'). I actually had to go and add
> LOG.debug statements to Heat to get to t
Hi Liam,
> I was recently looking at how to support custom configuration that
relies on post deployment setup.
I would describe the problem in general as follows:
1) charms can get context not only from Juju (config options, relation
data, leader data), environment (operating system release,
55 matches
Mail list logo