Thanks Sean, comments inline.
On 6 July 2015 at 16:58, Sean M. Collins wrote:
> I'd also like to chime in - we've had some discussions on -infra today
> about the partial upgrade issue, and collected the following notes on an
> etherpad.
>
> https://etherpad.openstack.org/p/neutron-partial-upgra
Hi Paul,
Let me look into it.
Thanks,
Armando
On 7 July 2015 at 08:51, Paul Michali wrote:
> I'm seeing that neutron-vpn repo py27 tests are now failing. Did a git
> bisect in Neutron and found that this commit is causing the failure (not
> sure what's broken).
>
> commit 18bc67d56faef30a0f734
Filed [1], I think this affected more than just vpn. Fix coming shortly.
Sorry, I thought I had taken the necessary measures :)
[1] https://bugs.launchpad.net/neutron/+bug/1472361
On 7 July 2015 at 09:11, Armando M. wrote:
> Hi Paul,
>
> Let me look into it.
>
> Thanks,
>
triage/experiment and get to a solution. I'll
watch [1] a little longer before I think it's safe to claim that we're out
of the woods.
Cheers,
Armando
[1] http://goo.gl/YM7gUC
[2] https://review.openstack.org/#/c/199668/
[3] https://review.openstack.org/#/c/199672/
On 22 June 2015 at
alvatore
>
>
>
> On 8 July 2015 at 20:21, Armando M. wrote:
>
>> Hi,
>>
>> Another brief update on the matter:
>>
>> Failure rate trends [1] are showing that unstable (w/ multiple API
>> workers + pymysql driver) and stable configurations (w/o
On 10 July 2015 at 16:01, Vadivel Poonathan
wrote:
> Hi,
>
> I have a Neutron plugin (actually a mechanism_driver under ML2) developed
> for Alcatel-Lucent Omniswitches and is currently being used. But it is not
> part of Neutron upstream, nor listed in the docs/wiki section. I tried to
> make it
On 7 July 2015 at 11:56, Doug Hellmann wrote:
> Excerpts from Ben Nemec's message of 2015-07-07 11:41:35 -0500:
> > On 07/04/2015 12:12 AM, Akihiro Motoki wrote:
> > > Hi Oslo and Neutron folks,
> > >
> > > Why is policy_dirs option deprecated in oslo.policy?
> > > In Neutron we have multiple rep
On 23 July 2015 at 05:25, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi all,
>
> I've stumbled on this one. It turns out we gate neutron against
> openstack installation that runs vpn-agent instead of l3-agent [1]. Is
> it really what we want to do? I would exp
Hi,
Since I was quoted, I would like to take the blame on behalf on the Neutron
core reviewer/drivers team for not providing the right guidance to resolve
the apparent conflict between the two proposals.
As some reviewers mentioned, we should really strive to catch two birds
with one stone, and e
On 29 July 2015 at 22:42, Anita Kuno wrote:
> On 07/29/2015 02:37 PM, Armando M. wrote:
> > Hi,
> >
> > Since I was quoted, I would like to take the blame on behalf on the
> Neutron
> > core reviewer/drivers team for not providing the right guidance to
> resolve
On 31 July 2015 at 20:33, Paul Carver wrote:
> On 7/31/2015 9:47 AM, Kyle Mestery wrote:
>
> However, it's reasonable to assume the later you propose your RFE bug, the
>> less of a chance it has of making it. We do enforce the Feature Freeze
>> [2],
>> which is the week of August 31 [3]. Thus, ef
Is this an example of +1+1=3?
On 12 August 2015 at 07:51, Doug Wiegley
wrote:
> A big +1 to both!!
>
> Doug
>
>
>
> On Aug 12, 2015, at 6:45 AM, Kyle Mestery wrote:
>
> It gives me great pleasure to propose Russell Bryant and Brandon Logan as
> core reviewers in the API/DB/RPC area of Neutron.
Hi,
If you wonder why hell broke loose, [1] will have the answer to your
questions.
Armando
[1] https://bugs.launchpad.net/neutron/+bug/1490380
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
a breaking update like this always
> comes around the end of a cycle or a feature freeze?
>
You missed 'weekends' :)
Not that it is any consolation, at least there are always a few brave
individuals that step in to the fire!
>
> Carl
>
> On Sun, Aug 30, 2015 at 9:54 PM
On 31 August 2015 at 09:53, Jeremy Stanley wrote:
> On 2015-08-31 10:33:07 -0600 (-0600), Carl Baldwin wrote:
> > I was under the impression that we had a plan to stop allowing these
> > external updates break our gate jobs.
> [...]
>
> We do, and it succeeded in protecting master branch integrat
On 31 August 2015 at 06:18, Ihar Hrachyshka wrote:
> Hi all,
>
> I see neutron folks pushing more neutron patches into the gate. They are
> all doomed to fail until [1] is resolved. So please stop approving patches,
> we only make harm by resetting the gate, with no chance to pass it.
>
> PS: it
On 31 August 2015 at 10:44, Edgar Magana wrote:
> Yeah!!
>
Well don't get so excited, the check queue is hovering over the 200 mark,
so.
>
> From: "Armando M."
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> Dat
On 31 August 2015 at 11:41, Armando M. wrote:
>
> On 31 August 2015 at 10:44, Edgar Magana wrote:
>
>> Yeah!!
>>
>
> Well don't get so excited, the check queue is hovering over the 200 mark,
> so.
>
>
well, that didn't last long:
We&#
Hi,
By now you may have seen that I have taken out your change from the gate
and given it a -2: don't despair! I am only doing it to give priority to
the stuff that needs to merge in order to get [1] into a much better shape.
If you have an important fix, please target it for RC1 or talk to me or
On 2 September 2015 at 09:40, Armando M. wrote:
> Hi,
>
> By now you may have seen that I have taken out your change from the gate
> and given it a -2: don't despair! I am only doing it to give priority to
> the stuff that needs to merge in order to get [1] into a much bett
be merged
during RC. Some other blueprints are best completed during feature freeze,
because of the rebase risk they cause...
Bottom line: never leave it to last minute!
> Thanks,
> Hirofumi
>
> On 2015/09/04, at 7:00, Armando M. wrote:
>
>
>
> On 2 September 2015 at 09:4
On 4 September 2015 at 15:33, Paul Carver wrote:
>
> Can someone from the Docs team take a look at why there isn't a docs URL
> for the networking-sfc repo?
>
Everything in OpenStack is code driven. And doc publishing happens through
code review as much as anything else. [1] Should provide point
On 10 September 2015 at 11:04, James Dempsey wrote:
> Greetings Devs,
>
> I'm very excited about the new RFE process and thought I'd test it by
> requesting a feature that is very often requested by my users[1].
>
> There are some great docs out there about how to submit an RFE, but I
> don't kno
On 12 September 2015 at 18:38, Gary Kotton wrote:
> Thanks! You did a great job. Looking back you made some very tough and
> healthy decisions. Neutron has a new lease on life!
> It is tradition that the exiting PTL buy drinks for the community :)
>
Ok, none of these kind words make you change y
On 15 September 2015 at 08:27, Mike Spreitzer wrote:
> Monty Taylor wrote on 09/15/2015 11:04:07 AM:
>
> > a) an update to python-novaclient to allow a named network to be passed
> > to satisfy the "you have more than one network" - the nics argument is
> > still useful for more complex things
>
On 15 September 2015 at 08:04, Monty Taylor wrote:
> Hey all!
>
> If any of you have ever gotten drunk with me, you'll know I hate floating
> IPs more than I hate being stabbed in the face with a very angry fish.
>
> However, that doesn't really matter. What should matter is "what is the
> most s
On 15 September 2015 at 11:28, Matt Riedemann
wrote:
>
>
> On 9/15/2015 10:27 AM, Mike Spreitzer wrote:
>
>> Monty Taylor wrote on 09/15/2015 11:04:07 AM:
>>
>> > a) an update to python-novaclient to allow a named network to be passed
>> > to satisfy the "you have more than one network" - the
On 15 September 2015 at 10:02, Doug Hellmann wrote:
> Excerpts from Armando M.'s message of 2015-09-15 09:30:35 -0700:
> > On 15 September 2015 at 08:04, Monty Taylor
> wrote:
> >
> > > Hey all!
> > >
> > > If any of you have ever gotten drun
On 15 September 2015 at 14:04, Mike Spreitzer wrote:
> "Armando M." wrote on 09/15/2015 03:50:24 PM:
>
> > On 15 September 2015 at 10:02, Doug Hellmann
> wrote:
> > Excerpts from Armando M.'s message of 2015-09-15 09:30:35 -0700:
> ...
> > As with
On 15 September 2015 at 15:11, Mathieu Gagné wrote:
> On 2015-09-15 2:00 PM, Fox, Kevin M wrote:
> > We run several clouds where there are multiple external networks. the
> "just run it in on THE public network" doesn't work. :/
> >
> > I also strongly recommend to users to put vms on a private n
On 15 September 2015 at 16:01, Monty Taylor wrote:
> On 09/15/2015 06:16 PM, Armando M. wrote:
>
>>
>>
>> On 15 September 2015 at 08:27, Mike Spreitzer > <mailto:mspre...@us.ibm.com>> wrote:
>>
>> Monty Taylor mailto:mord...@inaug
On 15 September 2015 at 16:08, Monty Taylor wrote:
> On 09/15/2015 06:30 PM, Armando M. wrote:
>
>>
>>
>> On 15 September 2015 at 08:04, Monty Taylor > <mailto:mord...@inaugust.com>> wrote:
>>
>> Hey all!
>>
>> If a
I would like to propose my candidacy for the Neutron PTL.
If you are reading this and you know me, then you probably know what I have
been up to up until now, what I have done for the project, and what I may
continue to do. If you do not know me, and you are still interested in
reading, then I wil
https://bugs.launchpad.net/grenade/+bug/1496650
HTH
Armando
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/
Hi fellow developers and reviewers,
Some of you may have noticed that I put together patch [1] up for review.
The intention of this initiative is to capture/share 'pills of wisdom' when
it comes to Neutron development and reviewing. In fact, there are a number
of common patterns (or anti-patterns
On 24 September 2015 at 09:12, Russell Bryant wrote:
> On 09/24/2015 10:18 AM, Salvatore Orlando wrote:
> > One particular issue is that the project implements the ovsdb
> protocol
> > from scratch. The ovs project provides a Python library for this.
> Both
> > Neutron and networking
On 25 September 2015 at 15:40, Chris Hoge wrote:
> In November, the OpenStack Foundation will start requiring vendors
> requesting
> new "OpenStack Compatible" storage driver licenses to start passing the
> Cinder
> third-party integration tests.
The new program was approved by the Board at
> th
On 25 September 2015 at 17:03, Ryan Moats wrote:
> First, congratulations to armax on being elected PTL for Mitaka. Looking
> forward to Neutron improving over the next six months.
>
> Second thanks to everybody that voted in the election. Hopefully we had
> something close to 100% turnout, becau
On 28 September 2015 at 18:01, Kruithof, Piet
wrote:
> There has been a significant response to the Nova Network/Neutron
> migration survey. However, the responses are leaning heavily on the side
> of deployments currently using Neutron. As a result, we would like to have
> more representation
Hi folks,
One of the areas I would like to look into during the Mitaka cycle is
'stability' [1]. The team has done a great job improving test coverage, and
at the same time increasing reliability of the product.
However, regressions are always around the corner, and there is a huge
backlog of out
On 30 September 2015 at 16:02, Cathy Zhang wrote:
> Hi Kyle,
>
>
>
> Is this only about the sub-projects that are ready for release? I do not
> see networking-sfc sub-project in the list. Does this mean we have done the
> pypi registrations for the networking-sfc project correctly or it is not
>
On 1 October 2015 at 06:45, Ihar Hrachyshka wrote:
> Hi all,
>
> I talked recently with several contributors about what each of us plans
> for the next cycle, and found it’s quite useful to share thoughts with
> others, because you have immediate yay/nay feedback, and maybe find
> companions for
On 1 October 2015 at 08:42, Sean M. Collins wrote:
> On Thu, Oct 01, 2015 at 11:05:29AM EDT, Kyle Mestery wrote:
> > On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins
> wrote:
> >
> > > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote:
> > > > - more changes with less infra tinkering!
lters and Google sheets Insights to see how well
(or bad) we've done this week.
Cheers,
Armando
[1] https://review.openstack.org/#/c/228733/
[2]
https://docs.google.com/spreadsheets/d/1UpxSOsFKQWN0IF-mN0grFJJap-j-8tnZHmG4f3JYmIQ/edit#gid=1296831500
On 28 September 2015 at 23:06, Armando
On 4 October 2015 at 09:19, Gary Kotton wrote:
> Hi,
> It appears that the addition has broken the vmware_nsx plugin (
> https://review.openstack.org/183369). We are still debugging. Would it be
> worthwhile considering adding this support as a feature branch and then
> when the entire feature is
On 4 October 2015 at 09:31, Gary Kotton wrote:
> Hi,
> When should we start to create a stable/liberty branch for the decomposed
> plugins? My understanding is that the plugin should be in line with
> Neutron. Changes in Neutron master (now Mitaka) may require plugin changes.
> Any ideas or thoug
waiting for a reply to message ID f4ed0bd26feb462c9b7b49a6d85caeae
>
> Now when I use the stable/liberty branch everything is OK
>
>
Ah, I suspect that's your culprit:
https://review.openstack.org/#/c/226362/
instead of AZ's initial support.
> Thanks
> Gary
>
> Fro
On 5 October 2015 at 03:14, Ihar Hrachyshka wrote:
> > On 02 Oct 2015, at 02:37, Armando M. wrote:
> >
> > Hi neutrinos,
> >
> > Whilst we go down the path of revising the way we manage/process bugs in
> Neutron, and transition to the proposed model [1], I was
Hi neutrinos,
One of the areas I would like to work on during the Mitaka cycle is
'consistency' [1].
We've grown quite a bit during the last cycle and we need to make sure we
are on the same page when it comes to code quality and reviews, and at the
same time speeding up review velocity without c
A kind reminder for tomorrow's meeting.
Please add agenda items to the meeting here [1].
See you all tomorrow!
Armando
[1] https://wiki.openstack.org/wiki/Network/Meetings
__
OpenStack Development Mailing List (not for usag
about the idea of creating a validation suite,
>> and it sounds like that's something we should again discuss in Tokyo for
>> the Mitaka cycle. I think a validation suite would be a great step forward
>> for Neutron third-party CI systems to use to validate they work with
On 6 October 2015 at 06:10, Ihar Hrachyshka wrote:
> > On 06 Oct 2015, at 10:36, Miguel Angel Ajo wrote:
> >
> > Hi, I was trying to help a bit, for now, but I don't have access in
> launchpad to update importance,
> > etc.
> >
> > I will add comments on the bugs themselves, and set a ? in the
>
Hi folks,
We are unable to merge stable changes to python-neutronclient (as shown in
[1,2]) because of the missing master fixes [3,4]. We should be able to
untangle Liberty with [5], but to unblock Kilo, I may need to squash [6]
with a cherry pick of [3] and wait [5] to merge.
Please bear with us
On 7 October 2015 at 07:50, Ihar Hrachyshka wrote:
> > On 06 Oct 2015, at 19:26, ZZelle wrote:
> >
> > Hi everyone,
> >
> >
> > As decided during last neutron meeting[1], we try to let Launchpad
> expire outdated bugs.
> >
> > The status of every bug without activity in last year has been set to
On 6 October 2015 at 20:06, Armando M. wrote:
> Hi folks,
>
> We are unable to merge stable changes to python-neutronclient (as shown in
> [1,2]) because of the missing master fixes [3,4]. We should be able to
> untangle Liberty with [5], but to unblock Kilo, I may need to squa
Hi folks,
As some of you may know, this summit we have 12 fishbowl sessions between
Wednesday and Thursday, and a full day on Friday for team get-together.
We broke down the 12 sessions in three separate tracks:
- https://etherpad.openstack.org/p/mitaka-neutron-core-track
- https://etherpa
A kind reminder for today's meeting.
Please add agenda items to the meeting here [1].
See you all in a few hours!
Armando
[1] https://wiki.openstack.org/wiki/Network/Meetings
__
OpenStack Development Mailing List (not for u
Hi folks,
A heads-up: we are currently experiencing a number of failures on the
stable/liberty for neutron [1].
Bear with us whilst we go through the painstaking process of fixing the
dependency issues that caused the recent grief.
Thanks,
Armando
[1]
https://review.openstack.org/#/q/status:ope
Hi folks,
We are in the last hours of Liberty, let's pause for a second and consider
merging patches only if absolutely necessary. The gate is getting clogged
and we need to give priority to potential RC3 fixes or gate stability fixes.
Thanks,
Armando
_
On 13 October 2015 at 16:55, Hirofumi Ichihara <
ichihara.hirof...@lab.ntt.co.jp> wrote:
>
>
> > On 2015/10/14, at 4:07, Armando M. wrote:
> >
> > Hi folks,
> >
> > We are in the last hours of Liberty, let's pause for a second and
> consider merg
Hi neutrinos,
>From last cycle, the team has introduced the concept of RFE bugs [0]. I
have suggested a number of refinements over the past few days [1,2,3] to
streamline/clarify the process a bit further, also in an attempt to deal
with the focus and breadth of the project [4,5].
Having said tha
Hi folks,
There are a number of outstanding stability issues that affect the
functional job [1]. No particular bug is a major offender, but taken all
together they hurt quite a bit.
If we don't get a good handle on this (even on a 'good' day there is a wide
gap between the job failure rate and th
On 14 October 2015 at 08:25, Doug Hellmann wrote:
> As with the other cross-project teams, the release management team
> relies on liaisons from each project to be available for coordination of
> work across all teams. It's the start of a new cycle, so it's time to
> find those liaison volunteers
On 14 October 2015 at 00:17, Flavio Percoco wrote:
> On 13/10/15 18:38 -0700, Armando M. wrote:
>
>> Hi neutrinos,
>>
>> From last cycle, the team has introduced the concept of RFE bugs [0]. I
>> have
>> suggested a number of refinements over the pa
A follow-up...
On 13 October 2015 at 18:38, Armando M. wrote:
> Hi neutrinos,
>
> From last cycle, the team has introduced the concept of RFE bugs [0]. I
> have suggested a number of refinements over the past few days [1,2,3] to
> streamline/clarify the process a bit further, als
On 16 October 2015 at 10:09, Sean M. Collins wrote:
> On Fri, Oct 16, 2015 at 11:36:13AM EDT, Salvatore Orlando wrote:
> > It might also make sense to ask contributors to resume the habit of
> tagging
> > bugs with 'backport-potential' even if not in the RC period.
>
> I like this idea because it
Folks,
The session [1] is planned for Thursday at 3.30pm. If you're interested,
please sign up. The time to submit ideas is running out.
Cheers,
Armando
[1] https://etherpad.openstack.org/p/mitaka-neutron-labs-lighting-talks
___
On 16 October 2015 at 15:14, Fox, Kevin M wrote:
> Then how about the alternate approach of:
>
> For bug fixes, copying an existing in tree unit test and tweaking it
> slightly to test for the bug is sufficient to get it accepted instead of
> forcing it to be rewritten in whatever the new hotness
A kind reminder for next week's meeting. Please add agenda items to the
meeting here [1].
We'll cancel the meeting of the week of the summit and the one after that.
Also, do not get caught in the switch from daylight savings when we get
back to them.
Cheers,
Armando
[1] https://wiki.openstack.o
Gal,
[2] is not meant to be edited by anyone just yet. This will lead to chaos
and an unproductive session. Once the link is out is obvious that anyone
can edit, but welcoming input is a recipe for disaster!
I appreciate the initiative, but please consider running thoughts by me for
advice.
Chee
rough bullet by bullet, we'll need an entire
summit :)
Cheers,
Armando
On 18 October 2015 at 09:14, Armando M. wrote:
> Gal,
>
> [2] is not meant to be edited by anyone just yet. This will lead to chaos
> and an unproductive session. Once the link is out is obvious that anyone
&g
Hi folks,
The schedule for the Neutron project is published in [1]. We are still
going through/ironing out some details, but for the most part (especially
the order of sessions) we should be all set.
See you in Tokyo!
Cheers,
Armando
[1] http://mitakadesignsummit.sched.org/overview/type/neutron
On 21 May 2015 at 08:58, Salvatore Orlando wrote:
> After putting the whole OpenStack networking contributors community
> through almost 8 cycles of pedant comments and annoying "what if"
> questions, it is probably time for me to relieve neutron contributors from
> this burden.
>
> It has been a
On 21 May 2015 at 09:58, Kyle Mestery wrote:
> On Thu, May 21, 2015 at 9:51 AM, Doug Wiegley <
> doug...@parksidesoftware.com> wrote:
>
>>
>> On May 21, 2015, at 9:14 AM, Armando M. wrote:
>>
>>
>>
>> On 21 May 2015 at 08:58, Salvatore Orlan
On 23 May 2015 at 04:43, Assaf Muller wrote:
> There's no real reason as far as I'm aware, just an implementation
> decision.
>
This is inaccurate. There is a reason(s), and this has been asked before:
http://lists.openstack.org/pipermail/openstack/2014-March/005950.html
http://lists.openstack.
On 25 May 2015 at 08:23, Mike Bayer wrote:
>
>
> On 5/25/15 10:24 AM, Henry Gessau wrote:
>
>> Yes, unfortunately the autogenerate currently generates commands to drop
>> all the FWaaS, LBaaS and VPNaaS tables since their models are not in the
>> neutron tree. You can and should delete all these
On 25 May 2015 at 09:46, Mike Bayer wrote:
>
>
> On 5/25/15 12:34 PM, Armando M. wrote:
>
>
>
>
>
> One thing I would like to point out is that in this cycle we'll be working
> extensively in this area to make the very task you are working on easier to
>
On 28 May 2015 at 03:09, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I've heard that other projects come up with actual action lists and
> work assignments. I've heard Nova, Ironic, Oslo do it, and I witnessed
> just that in those Oslo sessions I had a chance to
You have better chances of getting an answer if you asked the -dev list and
add [Neutron] to the subject (done here).
That said, can you tell us a bit more about your deployment? You can also
hop on #openstack-neutron on Freenode to look for neutron developers who
can help you more interactively.
On 4 June 2015 at 14:17, Cathy Zhang wrote:
> Thanks for joining the service chaining meeting today! Sorry for the
> time confusion. We will correct the weekly meeting time to 1700UTC (10am
> pacific time) Thursday #openstack-meeting-4 on the OpenStack meeting
> page.
>
>
>
Cathy, thanks for dr
https://review.openstack.org/#/c/177946/
>
> Thanks
> Vikram
>
>
> On Fri, Jun 5, 2015 at 6:36 AM, Armando M. wrote:
>
>>
>> On 4 June 2015 at 14:17, Cathy Zhang wrote:
>>
>>> Thanks for joining the service chaining meeting today! Sorry for
Interestingly, [1] was filed a few moments ago:
[1] https://bugs.launchpad.net/neutron/+bug/1463129
On 2 June 2015 at 22:48, Salvatore Orlando wrote:
> I'm not sure if you can test this behaviour on your own because it
> requires the VMware plugin and the eventlet handling of backend response.
+1
On 11 June 2015 at 09:27, Carl Baldwin wrote:
> +1!
>
> On Thu, Jun 11, 2015 at 8:34 AM, Henry Gessau wrote:
> > As one of the Lieutenants [1] for the API and DB areas under the PTL, I
> would
> > like to propose Ann Kamyshnikova as a member of the Neutron API and DB
> core
> > reviewer team
+1
On 11 June 2015 at 12:42, Carl Baldwin wrote:
> +1
>
> On Thu, Jun 11, 2015 at 12:15 PM, Kevin Benton wrote:
> > Hello all!
> >
> > As the Lieutenant of the built-in control plane[1], I would like YAMAMOTO
> > Takashi to be a member of the control plane core reviewer team.
> >
> > He has bee
This is exactly what I did in [1].
Cheers,
Armando
[1]
https://review.openstack.org/#/q/status:open+branch:master+topic:neutron-unstable,n,z
On 12 June 2015 at 09:00, Clint Byrum wrote:
> Excerpts from Chris Dent's message of 2015-06-12 03:47:02 -0700:
> > On Fri, 12 Jun 2015, Joe Gordon wrote
+1
On 12 June 2015 at 13:49, Edgar Magana wrote:
> Excellent news! +1
>
> Cheers,
>
> Edgar
>
>
> On Jun 12, 2015, at 12:50 PM, Kevin Benton wrote:
>
> Hello!
>
> As the Lieutenant of the built-in control plane[1], I would
> like Rossella Sblendido to be a member of the control plane core
On 16 June 2015 at 17:31, Sam Morrison wrote:
> We at NeCTAR are starting the transition to neutron from nova-net and
> neutron almost does what we want.
>
> We have 10 “public" networks and 10 “service" networks and depending on
> which compute node you land on you get attached to one of them.
>
On 15 June 2015 at 19:34, Sam Su wrote:
> Hi stackers,
>
>
>
> I am going to implement a Neutron plugin, however when I checked the
> current Neutron code(master) structure, I found there are two way to
> organize a Neutron plugin:
>
> 1. The first one is implement all L2 and L3 functions u
On 16 June 2015 at 22:36, Sam Morrison wrote:
>
> On 17 Jun 2015, at 10:56 am, Armando M. wrote:
>
>
>
> On 16 June 2015 at 17:31, Sam Morrison wrote:
>
>> We at NeCTAR are starting the transition to neutron from nova-net and
>> neutron almost does what
Hi,
The infrastructure jobs are completed. The project repository [1] has been
provisioned, and it is ready to go. Spec [2] is being moved to the new
repo, with patch [3]. Any documentation/specification effort that pertains,
and/or is solely focused on SFC, should target the new repo from now on.
On 18 June 2015 at 04:30, Jay Pipes wrote:
> On 06/17/2015 02:24 PM, Cathy Zhang wrote:
>
>> Hi Nicolas,
>>
>> Thanks for your suggestion. Yes, we can add Application ID to the
>> parameter of the flow classifier/filter. The next updated version will
>> reflect this. Actually in its existing desi
On 18 June 2015 at 09:54, Jay Pipes wrote:
> On 06/18/2015 12:46 PM, Armando M. wrote:
>
>> On 18 June 2015 at 04:30, Jay Pipes > <mailto:jaypi...@gmail.com>> wrote:
>>
>> On 06/17/2015 02:24 PM, Cathy Zhang wrote:
>>
>> Hi Nicolas,
&
Hi,
A brief update on the issue that sparked this thread:
A little over a week ago, bug [1] was filed. The gist of that was that the
switch to pymysql unveiled a number of latent race conditions that made
Neutron unstable.
To try and nip these in the bud, the Neutron team filed a number of patch
O(1)
(some of computational complexities achieved after Miguel optimizations)
On 6 July 2015 at 09:24, Carl Baldwin wrote:
> +1!
>
> On Mon, Jul 6, 2015 at 4:02 AM, Kevin Benton wrote:
> > Hello!
> >
> > As the Lieutenant of the built-in control plane[1], I am proposing to add
> > Miguel Angel
Hi,
Not sure if we reached any conclusion with this thread, and I would like to
resume it so that we don't derail the initial plan set forth by Russell and
agreed during the Liberty summit, among other things.
If I look at the thread I think this can be summarized as follow. Please
correct me if
On 12 February 2016 at 09:15, Matt Riedemann
wrote:
> Forgive me for thinking out loud, but I'm trying to sort out how nova
> would use a microversion in the nova API for the get-me-a-network feature
> recently added to neutron [1] and planned to be leveraged in nova (there
> isn't a spec yet for
On 12 February 2016 at 11:08, Matt Riedemann
wrote:
>
>
> On 2/12/2016 12:44 PM, Armando M. wrote:
>
>>
>>
>> On 12 February 2016 at 09:15, Matt Riedemann > <mailto:mrie...@linux.vnet.ibm.com>> wrote:
>>
>> Forgive me for thinking out
Hi folks,
It looks like something slipped in and how we got persistent failures on
functional/fullstack jobs [1]. Has anyone triaged? I couldn't find anything
in [2].
The effect for this: we can't merge anything until this gets resolved. Some
might argue this is not necessarily a bad thing...
Ch
On 17 February 2016 at 11:12, Armando M. wrote:
> Hi folks,
>
> It looks like something slipped in and how we got persistent failures on
> functional/fullstack jobs [1]. Has anyone triaged? I couldn't find anything
> in [2].
>
Looks like [1] fixed it. Thanks Assaf.
Be s
On 17 February 2016 at 11:22, Assaf Muller wrote:
> On Wed, Feb 17, 2016 at 2:16 PM, Armando M. wrote:
> >
> >
> > On 17 February 2016 at 11:12, Armando M. wrote:
> >>
> >> Hi folks,
> >>
> >> It looks like something slipped in and ho
301 - 400 of 673 matches
Mail list logo
