Ihar Hrachyshka wrote:
Hi,
we skip two next meeting slots and will meet again Jan 9th usual time.
Happy holidays y’all!
Ihar
OK just to clarify, I am talking about *UPGRADES* neutron meeting, not
general neutron team meeting. Sorry for any misunderstanding.
Ihar
Hi,
we skip two next meeting slots and will meet again Jan 9th usual time.
Happy holidays y’all!
Ihar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?su
Armando M. wrote:
Hi neutrinos,
I would like to propose Ryan and Nate as the go-to fellows for
service-related patches.
Both are core in their repos of focus, namely neutron-dynamic-routing and
neutron-fwaas, and have a good understanding of the service framework,
the agent framework a
Armando M. wrote:
Hi neutrinos,
Miguel Lavalle has been driving the project forward consistently and
reliably. I would like to propose him to be entrusted with +2/+A rights
in the areas he's been most prolific, which are L3 and DHCP.
At the same time, I'd like to propose Brian Haley as o
Waldemar wrote:
Hi Ihar et al,
Apologies for late reply. We were fighting couple of issues with the CI
in last couple of days. The networking problem mentioned by Ihar was one
of them.
We're running fine as of yesterday [1]. To stay on the safe side let's
wait a few days so CI proves stab
Izik Penso wrote:
Hi Neutron, Infra Cores,
Radware CI would like to acquire voting (+/-1 Verified) permission.
We voted before but we had to install a new CI and also changed our old
gerrit user with a new user because ssh key issues.
We are triggered by neutron-lbaas changes.
https://wi
+1.
Armando M. wrote:
Hi folks,
Abhishek Raut's recent involvement in OSC and python-neutronclient has
helped moving a few efforts along in the right direction. I would like to
suggest we double down on core firepower for the neutronclient repo
alongside Akihiro [1].
This not only wil
Ihar Hrachyshka wrote:
Jeremy Stanley wrote:
On 2016-10-04 18:22:10 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
When I execute 'bindep test’ locally, I get the following error on
centos7.2
which is expected:
Bad versions of installed packages:
sqlite version 3.7.17-8.el7 doe
Do you test with https://review.openstack.org/#/c/271830/ included? Would
be nice to use a setup with the patch included as our new base.
Brian Stajkowski wrote:
Yes, this actually has to do with the policy check on any list of objects,
including ports. The patch has to do with bypassing th
Hi all,
all candidates to chair the meeting are overbooked today and won’t be able
to lead it; we will cancel the meeting. We will meet the next week at usual
time.
Sorry for late notification,
Ihar
__
OpenStack Develo
Takashi Yamamoto wrote:
On Tue, Nov 29, 2016 at 11:53 AM, Takashi Yamamoto
wrote:
release team,
can we (networking-midonet) branch stable/newton from a past commit
with a RC tag, backport some changes [1], and then cut the first release
on the branch?
to answer myself, RC or beta-looking t
Armando M. wrote:
I did file bug [1]. FWIW, vpnaas on strongswan works fine in xenial [2],
and if the rally teams feel like not losing vpnaas coverage, they could
switch to strongswan.
[1] https://bugs.launchpad.net/python-neutronclient/+bug/1645819
[2] https://review.openstack.org/#/c/4
Armando M. wrote:
Hi folks,
A few hours ago a governance change [1] has been approved by TC members.
This means that from now on, the efforts for Load Balancing as a Service
efforts rest officially in the hands of the Octavia PTL and the Octavia
core team.
I will work with the help of
Anyone working on heat stable periodic doc job fix? Any patches to review?
I see it failing for quite some time for L and M.
> Begin forwarded message:
>
> From: "A mailing list for the OpenStack Stable Branch test reports."
>
> Subject: [Openstack-stable-maint] Stable check of openstack/heat
ant wrote:
>
> Thank you for sharing this.
>
> This gave me a much needed smile this morning. :-)
>
> Jay
>
>
> On 11/29/2016 06:48 AM, Ihar Hrachyshka wrote:
>> Hi,
>>
>> It was ‘cubswin:)’ before, but now that Cubs won [1] it’s ‘gocubsgo’ [2].
>>
Folks, note that this change basically changes ml2 driver API that was supposed
to be stable (now drivers receive context objects instead of sqlalchemy
sessions). I would like folks to chime in the review. I would also suggest to
announce the change during the next team meetings.
> On 22 Nov 20
Hi,
It was ‘cubswin:)’ before, but now that Cubs won [1] it’s ‘gocubsgo’ [2].
I hope it helps someone in the future.
[1]
http://www.chicagotribune.com/sports/baseball/cubs/ct-cubs-win-world-series-sullivan-spt-1103-20161102-story.html
[2]
https://git.launchpad.net/cirros/commit/?id=9a7c371ef32
> On 28 Nov 2016, at 12:18, Ihar Hrachyshka wrote:
>
> I suggest we disable votes for the setup until it’s fixed.
UPD: done, the CI is disabled for voting.
Ihar
__
OpenStack Development Mailing List (not
> On 26 Nov 2016, at 00:06, Ihar Hrachyshka wrote:
>
>>
>> On 14 Nov 2016, at 11:44, Znoinski, Waldemar
>> wrote:
>>
>> Hi Neutron, Infra Cores et al,
>> I would like to acquire voting (+/-1 Verified) permission for our Intel NFV
>> CI.
Hi all,
I am looking at
http://stackalytics.com/?project_type=openstack&module=neutron-group and I see
some reviews counted for projects that are for long out of neutron stadium
(f.e. dragonflow or kuryr or networking-hyperv). How can we get them excluded
from the official neutron stats?
I’ve
> On 14 Nov 2016, at 11:44, Znoinski, Waldemar
> wrote:
>
> Hi Neutron, Infra Cores et al,
> I would like to acquire voting (+/-1 Verified) permission for our Intel NFV
> CI.
>
> 1. It's running on Neutron changes since Q1'2015.
> 2. Wiki [1].
> 3. It's using openstack-infra/puppet-openstack
> On 25 Nov 2016, at 15:23, Takashi Yamamoto wrote:
>
> On Fri, Nov 25, 2016 at 8:02 PM, Ihar Hrachyshka wrote:
>>
>>> On 25 Nov 2016, at 11:02, Takashi Yamamoto wrote:
>>>
>>> On Fri, Nov 25, 2016 at 6:54 PM, Ihar Hrachyshka
>>> w
> On 25 Nov 2016, at 11:02, Takashi Yamamoto wrote:
>
> On Fri, Nov 25, 2016 at 6:54 PM, Ihar Hrachyshka wrote:
>>
>>> On 25 Nov 2016, at 09:25, Takashi Yamamoto wrote:
>>>
>>> On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka
>>> w
> On 25 Nov 2016, at 09:25, Takashi Yamamoto wrote:
>
> On Fri, Nov 25, 2016 at 5:18 PM, Ihar Hrachyshka wrote:
>>
>>> On 25 Nov 2016, at 05:26, Takashi Yamamoto wrote:
>>>
>>> hi,
>>>
>>> networking-midonet doesn't have st
een completed yet.
>
> the plan is to revert ocata-specific changes after branching newton.
I don’t think it’s a good idea since you will need to tag a release on branch
creation, that is supposed to be compatible with next releases in that same
branch.
>
> On Fri, Nov 25, 20
Hi,
could anyone from the midonet subproject take ownership of repo stable
branches? Newton branch is broken for weeks with no apparent actions from the
core team side.
> Begin forwarded message:
>
> From: "A mailing list for the OpenStack Stable Branch test reports."
>
> Subject: [Openstack
Hi,
Seems like newton branch of networking-odl is pulling neutron from master.
Whoever is responsible for the subproject, please fix.
> Begin forwarded message:
>
> From: "A mailing list for the OpenStack Stable Branch test reports."
>
> Subject: [Openstack-stable-maint] Stable check of opens
> On 24 Nov 2016, at 15:31, Jens Rosenboom wrote:
>
> 2016-11-24 15:08 GMT+01:00 Lenny Verkhovsky :
>> Hi,
>>
>> The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI
>
> What OS is the CI running on? Can you show the output of "dnsmasq
> --version" and "neutron-sanity-check" on
> On 24 Nov 2016, at 15:08, Lenny Verkhovsky wrote:
>
> Hi,
> The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI
>
>
> [1] https://review.openstack.org/#/c/393007/
We probably revert the patch: https://review.openstack.org/#/c/401985/
Ihar
> On 21 Nov 2016, at 12:38, Alan Pevec wrote:
>
>> 1. Final stable/liberty releases should happen next week, probably by
>> Thursday 11/17.
>
> I see only Cinder did it https://review.openstack.org/397282
> and Nova is under review https://review.openstack.org/397841
>
> Is that all or other p
> On 18 Nov 2016, at 13:58, Iago Santos Pardo wrote:
>
> Hello,
>
> We are using Neutron with the linuxbridge plugin and security groups enabled
> and we have some custom rules in iptables running on the compute nodes. When
> the agent rebuilds the firewall it changes the rules order, puttin
> On 16 Nov 2016, at 15:12, Matt Riedemann wrote:
>
> On 11/16/2016 7:53 AM, Ian Cordasco wrote:
>>
>>
>> -Original Message-
>> From: Ian Cordasco
>> Reply: Ian Cordasco
>> Date: November 16, 2016 at 07:06:27
>> To: OpenStack Development Mailing List (not for usage questions)
>>
>>
> On 17 Nov 2016, at 20:32, Armando M. wrote:
>
> Hi folks,
>
> Please do not recheck rally failures.
>
> There was a breaking change introduced by aodh [0] that prevented rally to
> work on trusty. We are switching to xenial as we speak anyway [1], so the
> glitch should be short lived.
To
> On 17 Nov 2016, at 19:42, Carl Baldwin wrote:
>
> Neutron (and Openstack),
>
> It is with regret that I report that my work situation has changed such that
> I'm not able to keep up with my duties as a Neutron core reviewer, L3
> lieutenant, and drivers team member. My participation has dro
> On 8 Nov 2016, at 04:07, Tony Breeds wrote:
>
> On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote:
>> Reviewing all the constraints work, I see that repositories have created
>> some workaround around requirements install for one of these two legimit
>> reasons - most often using
> On 8 Nov 2016, at 17:23, Ian Cordasco wrote:
>
>
>
> -Original Message-----
> From: Ihar Hrachyshka
> Reply: OpenStack Development Mailing List (not for usage questions)
>
> Date: November 8, 2016 at 02:39:24
> To: OpenStack Development Mailing
> On 7 Nov 2016, at 21:47, Ken'ichi Ohmichi wrote:
>
> Hi,
>
> Today a new hacking 0.12.0 is released.
> The release contains a new hacking rule:
>
> [H904] Delay string interpolations at logging calls.
>
> BTW, the hacking repo starts containing reno since this release but it
> is not used y
Hi all,
this is a recap for the neutron-server session that was on Fri.
===
tl;dr for Ocata, we proceed with adopting OVO (reviewers needed!),
push-notifications (now unblocked, Kevin already spins up patches), and
no-downtime-upgrades (contract alembic migrations will be forbidden for
Oc
Bob Ball wrote:
Hi Ihar,
I am puzzled. Is Neutron the only component that need to call to dom0?
No it's not. Nova has similar code to call plugins in dom0[1], and
Ceilometer will also need to make the calls for some metrics not exposed
through the formal API.
We don't want code dupli
Thierry Carrez wrote:
Bob Ball wrote:
Oslo.privsep seem try to launch a daemon process and set caps for this
daemon; but for XenAPI, there is no need to spawn the daemon.
I guess I'm lacking some context... If you don't need special rights,
why use a
rootwrap-like thing at all ? Why go thr
Hi YAMAMOTO (and other midokura folks),
I spotted unit tests in the branch are failing due to upper constraints not
applied. So I backported the fix as:
https://review.openstack.org/#/c/392698/ Sadly, it does not pass because
tempest for midonet v2 fails:
http://logs.openstack.org/98/3926
Vega Cai wrote:
Hi folks,
During the development of Tricircle, we find that one feature whose spec
has already been accepted is very useful, that is to enhance floating IP
router lookup to consider extra routes[1]. With this feature, floating IP
is allowed to be associated to internal ad
Tony Breeds wrote:
On Tue, Nov 01, 2016 at 12:45:43PM +0100, Ihar Hrachyshka wrote:
I suggested in the bug and the PoC review that neutron is not the right
project to solve the issue. Seems like oslo.rootwrap is a better place to
maintain privilege management code for OpenStack. Ideally, a
Nate Johnston wrote:
On Tue, Nov 01, 2016 at 01:17:25PM +0100, Ihar Hrachyshka wrote:
Armando M. wrote:
Slight variation, call it option 6:
1) Identify the most impacted (coupled) project affected by these
changes.
2) Fix it in order to provide folks with a recipe for how to address the
Armando M. wrote:
Slight variation, call it option 6:
1) Identify the most impacted (coupled) project affected by these changes.
2) Fix it in order to provide folks with a recipe for how to address the
breakages.
^ the step depends on how far we want to go with the adoption. If it’s just
Brandon Logan wrote:
Hello Neutrinos,
I've come across an issue that I'd like to get input/opinions on. I've
been reviewing some of the centralize config options reviews and have
come across a few that would cause issues with other projects that are
importing these options, especially stadium
Jianghua Wang wrote:
Hi Neutron guys,
I’m trying to explain a problem with the XenServer rootwrap and give a
proposal to resolve it. I need some input on how to proceed with this
proposal: e.g. if requires a spec? Any concerns need further discussion
or clarification?
Problem descripti
Michael Johnson wrote:
Hi Wanjing,
I responded to you in IRC but you may have logged off by the time I
was able to respond.
You are correct that this is an issue. We just this week noticed it.
It was an oversight that is causing the amphora agent to clone the
master branch amphora agent code
Joshua Harlow wrote:
Ihar Hrachyshka wrote:
In Neutron, we have a need to allocate random but unique addresses and
such. For that matter, we have a concept of exclusive resources:
https://github.com/openstack/neutron/tree/master/neutron/tests/common/exclusive_resources
that are relying on
In Neutron, we have a need to allocate random but unique addresses and
such. For that matter, we have a concept of exclusive resources:
https://github.com/openstack/neutron/tree/master/neutron/tests/common/exclusive_resources
that are relying on locks and shared file based resource allocation
Hi all,
due to the summit we cancel the next two upgrades subteam meetings.
We will get back Nov 7th, just in time to close any remaining gaps before
the world as we know it is destroyed by US elections the next day.
See you there,
Ihar
__
Henry Gessau wrote:
Anna Taraday wrote:
Henry, thanks for taking care of this!
In my opinion, it is just safe to use raw values in migration, because
migration is a strict point in time.
I remember how many patches I send in havana in Neutron for fixing
synchronization issues. Usage constan
Henry Gessau wrote:
Hi neutrinos,
In Neutron many attributes are stored in database fields. The size of these
fields therefore determines the maximum length of the attribute values.
I would like to get some consistency in place around how we define the
constants and where they are used. Here
Richard Woo wrote:
Ihar,
Thanks for your reply, seems like the fwaas is install when installed
neutron server:
root@controller-01:~# dpkg -l | grep neutron
ii neutron-common
2:8.2.0-0ubuntu1~cloud0 all Neutron is a virtual
network service f
Richard Woo wrote:
Hello, folks,
I have a small cluster running openstack liberty, today I am starting to
upgrading to Mitaka.
I am having a problem to launch l3 agent on network node.
I got the following error:
Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward
co
Miguel Lavalle wrote:
Dear Neutrinos,
I am organizing a social event for the team on Thursday 27th at 19:30.
After doing some Google research, I am proposing Raco de la Vila, which
is located in Poblenou: http://www.racodelavila.com/en/index.htm. The
menu is here: http://www.racodelavila
Alex Schultz wrote:
On Thu, Oct 13, 2016 at 3:27 AM, Thomas Bechtold
wrote:
On Tue, Oct 11, 2016 at 12:32:40PM -0600, Alex Schultz wrote:
On Tue, Oct 11, 2016 at 1:39 AM, Thomas Bechtold
wrote:
Hi,
On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote:
On Mon, Oct 10, 2016 at 5:0
Hi,
a friendly reminder that with the following releases shipped:
https://review.openstack.org/#/c/383781/ (mitaka)
https://review.openstack.org/#/c/383789/ (liberty)
we switch support phases for stable branches, as per [1]:
- stable/liberty is now phase III, meaning only CVE fixes are allowed
Vasyl Saienko wrote:
Hello Community,
Ironic and Neutron projects have become integrated even closer with
multitenancy implementation in Ironic.
There are 2 bugs that require separate ML2 driver specifically for Ironic
needs:
• Booting ironic instance, Neutron port remains in dow
Tony Breeds wrote:
Hi All,
Now that newton is out I'd like to moves stable/mitaka and stable/liberty
into the next support phase.
* Phase I: stable/newton ;P
* Phase II: stable/mitaka
* Phase III: All other stable branches[2]
For more details refer to [1].
So as of Friday 14th this wi
Jeremy Stanley wrote:
On 2016-10-04 18:22:10 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
When I execute 'bindep test’ locally, I get the following error on
centos7.2
which is expected:
Bad versions of installed packages:
sqlite version 3.7.17-8.el7 does not match >=3.8
I wou
Joshua Harlow wrote:
Flavio Percoco wrote:
On 03/10/16 23:25 +0100, Chris Dent wrote:
On Mon, 3 Oct 2016, Clay Gerrard wrote:
I just re-read your announcement - and I couldn't be happier you're
running
:D
a) Glad to hear it.
b) It's a shame these email threads didn't start last week. I
s
Ian Cordasco wrote:
-Original Message-
From: Tony Breeds
Reply: OpenStack Development Mailing List (not for usage questions)
, OpenStack Development Mailing List
(not for usage questions)
Date: October 5, 2016 at 08:14:40
To: OpenStack Development Mailing List (not for usage ques
Andreas Jaeger wrote:
TL;DR: Projects can use bindep.txt to document in a programmatic way
their binary dependencies
Python developers record their dependencies on other Python packages in
requirements.txt and test-requirements.txt. But some packages
havedependencies outside of python and we s
Tony Breeds wrote:
So it seems to me that we can revert:
https://review.openstack.org/#/q/status:merged+NOT+branch:master+project:openstack/requirements+topic:bug/1629830
?
https://review.openstack.org/#/q/status:open+NOT+branch:master+project:openstack/requirements+topic:bug/1629830
Ihar
_
UPD: some people suggested I should update the thread about the success of
the fixes. Long story short, affected projects (nova, trove) are fixed, so
we consider it done.
Ihar Hrachyshka wrote:
UPD: @dims pushed all four into gate. (Lord be merciful.)
Ihar
Ihar Hrachyshka wrote:
Long
Hi all,
I was serving as a bug deputy for the last two weeks. (Well, I planned to
serve for one week only, but then I forgot to set new deputies in the last
meeting I chaired, so the 2nd week was my punishment for short memory.)
There were several bugs that I did not know how to triage prop
UPD: @dims pushed all four into gate. (Lord be merciful.)
Ihar
Ihar Hrachyshka wrote:
Long story short, this topic should get us back to normal:
https://review.openstack.org/#/q/topic:bug/1629830
We could probably also ban the version in global-requirements.txt, but I
am bad at foresight
Ihar Hrachyshka wrote:
Long story short, this topic should get us back to normal:
https://review.openstack.org/#/q/topic:bug/1629830
We could probably also ban the version in global-requirements.txt, but I
am bad at foresight. I will let others to clean it up if needed.
Oh well, I am now
Long story short, this topic should get us back to normal:
https://review.openstack.org/#/q/topic:bug/1629830
We could probably also ban the version in global-requirements.txt, but I am
bad at foresight. I will let others to clean it up if needed.
Ihar
Graham wrote:
Also impacts designat
Emilien Macchi wrote:
A bit of investigation drove me to a new dependency required by
python-networking-cisco.
I proposed the new dependency in RDO:
https://review.rdoproject.org/r/#/c/2889/
"Since https://review.openstack.org/#/c/377937/ has been merged upstream,
we now require python-neutron
Matt Riedemann wrote:
There was a pycparser 2.14 package update on pypi today which is making
cinder-manager db sync fail. This is making all dsvm/grenade jobs fail in
master and stable/newton.
The upstream issue being tracked is:
https://github.com/eliben/pycparser/issues/147
OK, so th
Andrew Laski wrote:
A further hindrance to moving these checks to be OpenStack wide is that
each check violation is a failure. So in order to roll a new check out
across projects it requires a lot of churn in each project which
violates the checks. I would prefer to leave it up to each project
Matt Riedemann wrote:
On 10/1/2016 5:49 PM, Matt Riedemann wrote:
No you shouldn't need to mark strings for translation in test code. I
believe we have a hacking rule for marking LOG.info/warning/error
messages for translation but it should skip test directories.
Ah I guess the hacking rule
Akihiro Motoki wrote:
Hi,
I noticed strings in tests (unit tests or others) have translation marks
(_, _LE and so on).
Do we need translation marks for them?
I don't think so for most cases from various reasons below.
Only exception is to test translations.
From translators:
- Effort to t
Michał Dulko wrote:
On 09/30/2016 04:06 PM, Ihar Hrachyshka wrote:
Ihar Hrachyshka wrote:
Hi all,
today we landed https://review.openstack.org/#/c/269658/ (huge!) that
removed neutron/objects/network/ directory and replaced it with
neutron/objects/network.py file. Though it makes python
Ihar Hrachyshka wrote:
Hi all,
today we landed https://review.openstack.org/#/c/269658/ (huge!) that
removed neutron/objects/network/ directory and replaced it with
neutron/objects/network.py file. Though it makes python that sees old
.pyc files sad:
Failed to import test module
Hi all,
today we landed https://review.openstack.org/#/c/269658/ (huge!) that
removed neutron/objects/network/ directory and replaced it with
neutron/objects/network.py file. Though it makes python that sees old .pyc
files sad:
Failed to import test module: neutron.tests.unit.objects.test
Hi all,
there is a patch for neutron that switches neutron policy engine from
passing context.to_dict() into oslo.policy to using
context.to_policy_values() that was added recently to oslo.context.
The patch is: https://review.openstack.org/#/c/370499/
The new function from oslo.context re
Kevin Benton wrote:
There is no side effect other than log noise and a delayed reload? I
don't see why a revert would be appropriate.
I looked at the logs and the issue seems to be that the process isn't
tracked correctly the first time it starts.
grep for the following:
ea141299-ce07-4
I wish I did not need to write such emails late in the evening. Added
missing [neutron] tag.
Ihar Hrachyshka wrote:
Hi all,
so we started getting ‘Address already in use’ when trying to start
dnsmasq after the previous instance of the process is killed with kill
-9. Armando spotted it
Hi all,
so we started getting ‘Address already in use’ when trying to start dnsmasq
after the previous instance of the process is killed with kill -9. Armando
spotted it today in logs for: https://review.openstack.org/#/c/377626/ but
as per logstash it seems like an error we saw before (the
I just hit that TimeoutException error in neutron functional tests:
http://logs.openstack.org/68/373868/4/check/gate-neutron-dsvm-functional-ubuntu-trusty/4de275e/testr_results.html.gz
It’s a bit weird that we hit that 180 sec timeout because in good runs, the
test takes ~5 secs.
Do we have
Steve Martinelli wrote:
A bug was recently filed against keystone [1]. As of the Newton release
we depend on a class being public -- BaseAuthProtocol instead of
_BaseAuthProtocol [2]. Which was introduced in 4.1.0 [3].
The current requirement for keystonemiddleware is:
keystonemiddleware
Hi all,
Cathy noticed lately that networking-sfc 2.0.0 release did not trigger an
announcement email. This was because the tag pushed did not contain some
metadata required by the post-merge job:
http://logs.openstack.org/64/64eb217de2273cf3760b2f73967a77aed0346d96/release/networking-sfc-an
Thierry Carrez wrote:
Ihar Hrachyshka wrote:
[...]
I slightly disagree with enforcing another formal role to all teams. I
feel that we have enough of them (release liaison for one) to cover for
release cross-project work, and projects are free to set their teams
with more roles if needed
Thierry Carrez wrote:
Rob Cresswell wrote:
I've been toying with send this email for a while, but here goes: this
all feels like overcomplication and changing of a system that doesn't
really need to change.
Except the proposal here is actually to not change anything, but I see
what you mean.
Tony Breeds wrote:
On Thu, Sep 08, 2016 at 09:21:57AM -0500, Matthew Thode wrote:
Ya that makes sense, the patch can be altered to just block 4.13.1,2
(assuming 4.13.3 really does fix it)
I feel like we've gotten ourselves (well at least I'm confused) about what
we're trying to achieve here
Ihar Hrachyshka wrote:
Hi,
we have this latent bug where we pass objects for subnetpools into
extension functions. (That was a mistake made when switching to using
objects in base db plugin for the resource.) Now, we want to revert to
passing db models as we did before, so that our
I backported the fix to stable/newton:
https://review.openstack.org/#/c/367221/
Once it’s in, we’ll trigger another oslo.db release.
As for the blocking patch for requirements:
https://review.openstack.org/#/c/365565/, I disagree that we should block
oslo.db 4.13.0, because atm pymysql 0.7
Hi,
we have this latent bug where we pass objects for subnetpools into
extension functions. (That was a mistake made when switching to using
objects in base db plugin for the resource.) Now, we want to revert to
passing db models as we did before, so that our plugin api is consistent
and
Gyorgy Szombathelyi wrote:
-Original Message-
From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
Gyorgy Szombathelyi wrote:
Hi!
Maybe I'm overseeing something, but I'm wondering if table renames
breaks rolling upgrades.
Yes, they would. Do you suggest that we allo
Alexander wrote:
FYI,
A similar discussion was held for an api-ref change in Glance:
https://review.openstack.org/#/c/356693/
Thanks for the link, it led me to this discussion:
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101501.html
From the looks of it, seems like the re
Jeremy Stanley wrote:
On 2016-09-06 15:36:42 +0200 (+0200), Andreas Jaeger wrote:
On 2016-09-06 15:30, Ihar Hrachyshka wrote:
Andreas Jaeger wrote:
On 2016-09-06 15:02, Ihar Hrachyshka wrote:
[...]
Since neutron-lib is branched on stable/* boundary, I feel that it
would
be fine to
Gyorgy Szombathelyi wrote:
Hi!
Maybe I'm overseeing something, but I'm wondering if table renames breaks
rolling upgrades.
Yes, they would. Do you suggest that we allowed such a migration anywhere
in Newton?
E.g. if I'm upgrading neutron server instances one-by-one, and doing a db
ex
Ihar Hrachyshka wrote:
Julien Danjou wrote:
On Fri, Sep 02 2016, Mike Bayer wrote:
I've augmented it with mapper-level SQLAlchemy API use.
Awesome, thanks. :)
And "augmented" makes it sounds so futurist, whoohhh. :)
Ouch, sorry for that bug in my patch. :-|
Now that
Andreas Jaeger wrote:
On 2016-09-06 15:02, Ihar Hrachyshka wrote:
[...]
Since neutron-lib is branched on stable/* boundary, I feel that it would
be fine to keep one-to-one relationship between neutron and neutron-lib
api-ref branches.
We only publish the api-ref documents from master,
Is
Akihiro Motoki wrote:
What releases should we support in API references?
There are several options.
1. The latest stable release + master
2. All supported stable releases + master
3. more older releases too?
Option 2 sounds reasonable to me.
This question is raised in the neutron api-ref pat
Gary Kotton wrote:
Hi,
It is unclear what our policy is with objects. My understanding is that
an object should handle all of the database interaction. Is that not one
of the benefits of the objects? I
postedhttps://review.openstack.org/#/c/365459 and it has a number of
interesting comm
Andreas Jaeger wrote:
On 09/05/2016 07:45 AM, Tony Breeds wrote:
On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote:
Reviewing all the constraints work, I see that repositories have created
some workaround around requirements install for one of these two legimit
reasons - most oft
101 - 200 of 932 matches
Mail list logo
