On 22 November 2016 at 06:09, Znoinski, Waldemar <
waldemar.znoin...@intel.com> wrote:
>
>
> >-Original Message-
> >From: Jeremy Stanley [mailto:fu...@yuggoth.org]
> >Sent: Monday, November 14, 2016 3:40 PM
> >To: openstack-in...@lists.openstack.org; openstack-dev@lists.openstack.
> or
Happy Thanksgiving!
Armando
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta
On 23 November 2016 at 01:47, zhi wrote:
> Hi, all
>
> Recently I did some research about trunk port in neutron by following
> document[1]. By creating a trunk port, I can use this port ( aka " parent
> port " ) to create a VM. So I can add or remove subports on this "parent
> port" which used by
Hi neutrinos,
In the last few hours a couple of changes landed [1,2] that caused a bit of
a jam in the neutron subproject gates, as they overlapped with another
change [3] having impact on the subprojects.
This is why it is important to communicate during team meetings and/or ML
that patches with
On 10 November 2016 at 17:36, Armando M. wrote:
> Hi Neutrinos,
>
> Some of you may be aware of our CI jobs have been transitioning to Xenial.
> There are a few jobs still left and taking into account mail [1] we need to
> accelerate the process a bit, especially for those jobs
] provides some tips on
>> how we see this workflow playing out.
>>
>> Thanks
>>
>> [1]
>> https://github.com/openstack/neutron-lib/blob/master/doc/sou
>> rce/contributing.rst
>> [2]
>> https://github.com/openstack/neutron-lib/blob/master/doc/
In particular the 'Phase 4: Consume' section [2] provides some tips on
>> how we see this workflow playing out.
>>
>> Thanks
>>
>> [1]
>> https://github.com/openstack/neutron-lib/blob/master/doc/
>> source/contributing.rst
>> [2]
>> h
On 24 November 2016 at 02:38, Thierry Carrez wrote:
> Gary Kotton wrote:
> > Please see - http://logs.openstack.org/82/401882/1/check/gate-vmware-
> nsx-python27-db-ubuntu-xenial/1ac0686/console.html#_2016-11-
> 24_06_58_38_520273
> > Here we are pulling trunk as there is no stable version to use
ch neutron change.
>
Right, and that's never gonna happen otherwise we might as well put all the
code back into one tree.
>
> On Nov 24, 2016 10:02, "Armando M." wrote:
>
>>
>>
>> On 24 November 2016 at 05:27, Neil Jerram wrote:
>>
>
would have been jobs from all sub projects voting
>> on each neutron change.
>>
>> On Nov 24, 2016 10:02, "Armando M." wrote:
>>
>>
>>
>> On 24 November 2016 at 05:27, Neil Jerram wrote:
>>
>> But I think a periodic check for a N
Tap-as-a-service is added to the stadium and tent.
>
How is this relevant to this discussion?
>
> A luta continua
>
>
>
> *From: *"Armando M."
> *Reply-To: *OpenStack List
> *Date: *Thursday, November 24, 2016 at 7:03 PM
> *To: *OpenStack List
> *Sub
Hi folks,
A recent devstack set of changes [0,1] accidentally broke the linuxbridge
job in that bridge_mappings are no longer applied correct. To add insult to
injury, this got applied to both stable and master (with the stable fix
landing first). See [2,3] for a difference.
This is not the first
On 29 November 2016 at 15:46, Armando M. wrote:
> Hi folks,
>
> A recent devstack set of changes [0,1] accidentally broke the linuxbridge
> job in that bridge_mappings are no longer applied correct. To add insult to
> injury, this got applied to both stable and master (with
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 the respective core teams to
On 27 November 2016 at 20:50, Takashi Yamamoto
wrote:
> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote:
> > Hi
> >
> > As of today, the project neutron-vpnaas is no longer part of the neutron
> > governance. This was a decision reached after the project saw a
On 30 November 2016 at 08:53, Michael Johnson wrote:
> Hi Flavio,
>
> These tags don't seem to be rendering/laying out well for octavia:
> https://github.com/openstack/octavia/blob/master/README.rst
>
> Any pointers to get this corrected or is this part of the backend
> rendering work you mention
https://github.com/openstack/neutron-lib/blob/
> master/doc/source/readme.rst
>
Thanks Steve, we'll follow suit!
Cheers,
Armando
>
> On Wed, Nov 30, 2016 at 2:44 PM, Armando M. wrote:
>
>>
>>
>> On 30 November 2016 at 08:53, Michael Johnson
>> wrote:
&
On 1 December 2016 at 07:45, Andreas Jaeger wrote:
> On 11/15/2016 12:30 AM, Clark Boylan wrote:
> > [...]
>
>> Just a friendly reminder that this is still happening. We will be
>> updating any jobs running on Trusty that should be running on Xenial on
>> December 6th. I have seen a few projects
ated access
to lbaas backports (i.e. tweaking gerrit ACLs).
Cheers,
Armando
>
> Michael
>
> On Thu, Dec 1, 2016 at 7:30 AM, Brian Haley wrote:
> > On 12/01/2016 08:54 AM, Ihar Hrachyshka wrote:
> >>
> >> Armando M. wrote:
> >>
> >>> Hi fo
Hi Neutrinos,
By now a few of us have noticed that the neutron core and driver teams have
lost a number of very talented and experienced engineers: well...this sucks
there's no more polite way to put it!!
These engineers are the collective memory of the project, know the kinks
and gotchas of the
On 29 November 2016 at 09:36, Zane Bitter wrote:
> On 29/11/16 10:28, Doug Hellmann wrote:
>
>> Excerpts from Chris Friesen's message of 2016-11-29 09:09:17 -0600:
>>
>>> On 11/29/2016 08:03 AM, Doug Hellmann wrote:
>>>
I'll rank my preferred solutions, because I don't actually like any of
>
On 29 November 2016 at 10:08, Doug Hellmann wrote:
> Excerpts from Zane Bitter's message of 2016-11-29 12:36:03 -0500:
> > On 29/11/16 10:28, Doug Hellmann wrote:
> > > Excerpts from Chris Friesen's message of 2016-11-29 09:09:17 -0600:
> > >> On 11/29/2016 08:03 AM, Doug Hellmann wrote:
> > >>>
On 30 November 2016 at 02:23, Kevin Benton wrote:
> >I'll let someone from the Neutron team fill in the details behind their
> >decision,
> because I don't want to misrepresent them.
>
> I can shed a bit of light on this since I'm a core and had been working
> for a driver vendor at the time of
On 5 December 2016 at 08:07, Jay Pipes wrote:
> On 12/05/2016 10:59 AM, Bence Romsics wrote:
>
>> Hi,
>>
>> I measured how the new trunk API scales with lots of subports. You can
>> find the results here:
>>
>> https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling
>>
>> Hope y
On 6 December 2016 at 08:49, Vasyl Saienko wrote:
> Hello Neutron Community,
>
>
> I've found that nice feature vlan-aware-vms was implemented in Newton [0].
> However the usage of this feature for regular users is impossible, unless
> I'm missing something.
>
> As I understood correctly it shoul
On 6 December 2016 at 14:36, Assaf Muller wrote:
> Hi all,
>
> General query - Is there anyone in the Dynamic Routing community that
> is planning on contributing a scenario test? As far as I could tell,
> none of the current API tests would fail if, for example, the BGP
> agent was not running.
On 6 December 2016 at 14:44, Tidwell, Ryan wrote:
> This is at the top of my list to look at. I've been thinking a lot about
> how to implement some tests. For instance, do we need to actually stand up
> a BGP peer of some sort to peer neutron with and assert the announcements
> somehow? Or shoul
trunk plugin only at
the time a parent port is bound and we hadn't come up with a clean and
elegant way to developer a validator that took into account of it. I'll
file a bug report to make sure this won't fall through the cracks. It'll be
tagged with 'trunk'.
[1] ht
Hi folks
Chasing down why [1] accidentally broke rally. Please do not recheck, and
the failure is persistent.
Thanks,
Armando
[1] https://review.openstack.org/#/c/408020
__
OpenStack Development Mailing List (not for usage q
On 8 December 2016 at 16:40, Armando M. wrote:
> Hi folks
>
> Chasing down why [1] accidentally broke rally. Please do not recheck, and
> the failure is persistent.
>
> Thanks,
> Armando
>
> [1] https://review.openstack.org/#/c/408020
>
https://review.openstac
On 5 December 2016 at 07:59, Bence Romsics wrote:
> Hi,
>
> I measured how the new trunk API scales with lots of subports. You can
> find the results here:
>
> https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling
>
> Hope you find it useful. There are several open ends, let m
On 8 December 2016 at 20:55, Armando M. wrote:
>
>
> On 5 December 2016 at 07:59, Bence Romsics
> wrote:
>
>> Hi,
>>
>> I measured how the new trunk API scales with lots of subports. You can
>> find the results here
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 will help speed up our transition to
Hi folks,
Due to conflicts, we are unable to host the drivers meeting today.
Apologies for the short notice.
Thanks,
Armando
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@
On 15 December 2016 at 09:50, Akihiro Motoki wrote:
> +1
>
Welcome to the team Abhishek!
>
> 2016-12-14 10:22 GMT+09:00 Armando M. :
>
>> Hi folks,
>>
>> Abhishek Raut's recent involvement in OSC and python-neutronclient has
>> helped moving a few e
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 our next Chief L3
Officer. B
On 16 December 2016 at 00:01, Clint Byrum wrote:
> So, I've been quietly ranting in hallways about this for a while. I may
> be way way off base here. I want to kick the discussion off, so I've
> submitted a proposal to the arch-wg about it. Please if you're interested
> in how Nova/Neutron/Cinde
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 and other bits and pieces. At
Hi Neutrinos,
Infra patch proposed in [1] got me thinking again about what we shall do
when it comes to multinode testing in the gate and how to focus our testing
and CI efforts upstream going forward. My line of thinking has always been
that multinode resources should be devoted to configurations
have a DVR+HA gate in the
> experimental queue.
>
Excellent! thanks for the update, John!
Cheers,
Armando
>
> John.
>
> [1]: https://review.openstack.org/#/c/383742/
> [2]: https://review.openstack.org/#/c/383827/
>
> On Fri, Dec 16, 2016 at 2:23 AM, Armando M. wrote
Hi folks,
Due to the holiday period we'll cancel the following meeting occurrences:
Dec 22
Dec 29
Jan 5
We'll meet again on Jan 12.
Happy holidays!
Armando
__
OpenStack Development Mailing List (not for usage questions)
Uns
Hi folks,
Due to the holiday period we'll cancel the following meeting occurrences:
Dec 26
Jan 3
We'll meet again on Jan 9.
Happy holidays!
Armando
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
Hi neutrinos,
A reminder that from this week on it is business as usual. Therefore the
calendar for team and drivers meetings is back up and running.
Cheers,
Armando
__
OpenStack Development Mailing List (not for usage questi
Hi neutrinos,
The PTL nomination week is fast approaching [0], and as you might have
guessed by the subject of this email, I am not planning to run for Pike. If
I look back at [1], I would like to think that I was able to exercise the
influence on the goals I set out with my first self-nomination
Hi,
Please have a look at [1]. The branch has been broken for some time now.
Thanks,
Armando
[1]
https://review.openstack.org/#/q/status:open+project:openstack/networking-sfc+branch:stable/newton
__
OpenStack Development Mai
Hi neutrinos,
The time for the PTG is approaching and if you are wondering about topics
and various agenda arrangements, you should consider the PTG more like a
mid-cycle on steroids: each project will be working on its own agenda,
usually via etherpads, and publish updates over the ML, up until a
On 12 January 2017 at 14:46, Joshua Harlow wrote:
> So I don't want to start to much of a flame-war and am really just trying
> to understand things that may be beyond me (so treat me nicely, ha).
>
> The basic question that I've been wondering revolves around the following
> kind of 'thought exp
On 12 January 2017 at 15:07, Armando M. wrote:
>
>
> On 12 January 2017 at 14:46, Joshua Harlow wrote:
>
>> So I don't want to start to much of a flame-war and am really just trying
>> to understand things that may be beyond me (so treat me nicely, ha).
>>
&
On 13 January 2017 at 10:47, Clint Byrum wrote:
> Excerpts from Joshua Harlow's message of 2017-01-12 22:38:46 -0800:
> > Kevin Benton wrote:
> > > If you don't want users to specify network details, then use the get me
> > > a network extension or just have them boot to a public (or other
> > >
On 13 January 2017 at 15:01, Clint Byrum wrote:
> Excerpts from Armando M.'s message of 2017-01-13 11:39:33 -0800:
> > On 13 January 2017 at 10:47, Clint Byrum wrote:
> >
> > > Excerpts from Joshua Harlow's message of 2017-01-12 22:38:46 -0800:
> > > &
On 19 January 2017 at 13:41, Bruno L wrote:
> Hi,
>
> November last year the Neutron team has announced that VPN as a Service
> will be no longer part of Neutron[1].
>
> We run a public cloud based in New Zealand called Catalyst Cloud[2]. Our
> customers find the VPN service extremely useful to i
Hi neutrinos,
We spotted [1] in the gate. Please wait for its resolution until pushing
patches into the merge queue.
Thanks,
Armando
[1] https://bugs.launchpad.net/neutron/+bug/1658806
__
OpenStack Development Mailing List (
On 23 January 2017 at 13:50, Jeremy Stanley wrote:
> On 2017-01-23 13:38:58 -0800 (-0800), Armando M. wrote:
> > We spotted [1] in the gate. Please wait for its resolution until pushing
> > patches into the merge queue.
>
> https://review.openstack.org/424323 seems to
Hi neutrinos,
No, it's not what you might be thinking...I am just delighted to see two
excellent candidates willing to take the reins of the project going forward
[1,2].
I couldn't hope for more enthusiasm; best of luck to both candidates and
anyone else who is going to step up! This is exciting!
On 24 January 2017 at 12:46, Jeremy Stanley wrote:
> On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote:
> > On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote:
> > > I'm on board with getting visibility into the drivers with
> improvements to
> > > driverlog, etc. What I'm uncertain
On 26 January 2017 at 12:53, Dariusz Ĺmigiel
wrote:
> Dear Neutrinos,
> Feature Freeze day arrived! Ocata-3 has been released, so it means
> that no new features will be allowed to current release... The only
> patches approved to be merged should be: release critical or gate
> blocker.
> All out
Hi folks,
Recently [1], a new meeting has been setup to give the neutron team a
dedicated time to discuss any upstream CI matter (gate issues, testing
strategies, etc), as well as an overflow space to be used after the main
team meeting section [3]. Kudos to Ihar for being our first chair.
Needle
lob/
> master/jenkins/jobs/python-jobs.yaml#L17
>
>
> PS: Congrats Ihar for your new role
>
>
>
> From: "Armando M."
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
&
On 1 February 2017 at 07:29, Ihar Hrachyshka wrote:
> Hi all,
>
> lately I see the requirements bot proposing new rebases for its
> patches (and bumping existing patch sets from the gate queue) every
> second hour, at least for Neutron [1], which makes it impossible to
> land the patches, and whi
Hi,
[TL;DR]: OpenStack services have steadily increased their memory
footprints. We need a concerted way to address the oom-kills experienced in
the openstack gate, as we may have reached a ceiling.
Now the longer version:
We have been experiencing some instabili
Hi,
There is something puzzling about release notes. I don't see 8.0.0 [1], and
it looks like features released in Mitaka are being advertised as Newton
features [2]. For instance, [3] 'Agent availability zones' shows as a
Newton feature when I am pretty positive that it went in Mitaka [4].
I sus
On 2 February 2017 at 08:40, Sean Dague wrote:
> On 02/02/2017 11:16 AM, Matthew Treinish wrote:
>
> >
> >
> > We definitely aren't saying running a single worker is how we recommend
> people
> > run OpenStack by doing this. But it just adds on to the differences
> between the
> > gate and what
On 2 February 2017 at 10:08, Sean Dague wrote:
> On 02/02/2017 12:49 PM, Armando M. wrote:
> >
> >
> > On 2 February 2017 at 08:40, Sean Dague > <mailto:s...@dague.net>> wrote:
> >
> > On 02/02/2017 11:16 AM, Matthew Treinish wrote:
> >
On 2 February 2017 at 12:19, Sean Dague wrote:
> On 02/02/2017 02:28 PM, Armando M. wrote:
> >
> >
> > On 2 February 2017 at 10:08, Sean Dague > <mailto:s...@dague.net>> wrote:
> >
> > On 02/02/2017 12:49 PM, Armando M. wrote:
> > >
On 2 February 2017 at 12:50, Sean Dague wrote:
> On 02/02/2017 03:32 PM, Armando M. wrote:
> >
> >
> > On 2 February 2017 at 12:19, Sean Dague > <mailto:s...@dague.net>> wrote:
> >
> > On 02/02/2017 02:28 PM, Armando M. wrote:
> > >
ctions, which is the entire purpose of the library, no?
> >
> > On Feb 2, 2017 13:53, "Sean Dague" wrote:
> >>
> >> On 02/02/2017 03:32 PM, Armando M. wrote:
> >> >
> >> >
> >> > On 2 February 2017 at 12:19, Sean Dague &g
On 2 February 2017 at 13:36, Ihar Hrachyshka wrote:
> On Thu, Feb 2, 2017 at 7:44 AM, Matthew Treinish
> wrote:
> > Yeah, I'm curious about this too, there seems to be a big jump in Newton
> for
> > most of the project. It might not a be a single common cause between
> them, but
> > I'd be curio
Hi,
With the release coming up, it's best to spend the time to polish what we
have.
Sorry for the short notice.
Thanks,
Armando
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ.
Hi neutrinos,
I have put a number of patches in the merge queue for a few sub-projects.
We currently have a number of these that are on an independent release
schedule. In particular:
- networking-bagpipe
- networking-bgpvpn
- networking-midonet
- networking-odl
- networking-sfc
P
On 2 February 2017 at 16:09, Armando M. wrote:
> Hi neutrinos,
>
> I have put a number of patches in the merge queue for a few sub-projects.
> We currently have a number of these that are on an independent release
> schedule. In particular:
>
>- networking-bagpipe
>
> The date of March 10th looks reasonable as a target, and we'll stick to
> that.
>
>
Excellent,
thanks for the update.
Cheers,
Armando
Best,
>
> -Thomas
>
>
>
> On 2 February 2017 at 16:09, Armando M. wrote:
>
>> Hi neutrinos,
>>
>> I h
On 9 February 2017 at 07:43, Morales, Victor
wrote:
> One of my favorites is the usage of #undo command during the meetings for
> fixing a quick copy & paste link. Should be necessary to include more
> information in this wiki entry[1]
>
Yes, I can't count the number of times during a meeting
On 9 February 2017 at 05:16, Doug Hellmann wrote:
> Excerpts from Doug Hellmann's message of 2017-02-08 23:54:06 -0500:
> > The patch to update the XStatic package versions [1] is blocked by a
> > patch to remove nova-docker from the requirements project sync list [2],
> > which is in turn runnin
601 - 673 of 673 matches
Mail list logo
