"dev" wrote on 07/19/2016 10:44:27 PM:
> From: Chen Li
> To: d...@openvswitch.org
> Date: 07/19/2016 10:44 PM
> Subject: [ovs-dev] Issue when using ovn with Openstack
> Sent by: "dev"
>
> Hi list,
>
> I have an all-in-one devstack environment with ovn enabled.
> I create a neutron network.
> C
"discuss" wrote on 06/17/2016 05:24:19
PM:
> From: Cathy Zhang
> To: Na Zhu
> Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack
> Development Mailing List \(not for usage questions\)" d...@lists.openstack.org>, John McDowall
> , discuss
> Date: 06/17/2016 05:25 PM
> Subject: Re: [o
John McDowall wrote on 06/17/2016 04:07:38
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: discuss , Na Zhu ,
> "OpenStack Development Mailing List (not for usage questions)"
> , Srilatha Tangirala/San
> Francisco/IBM@IBMUS
> Date: 06/17/20
Murali R wrote on 06/17/2016 12:33:09 PM:
> From: Murali R
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff , discuss
> Date: 06/17/2016 12:33 PM
> Subject: Re: [ovs-discuss] [ovn] provider networks
>
> > Your question makes me think that you are using provider network
In-line below
"discuss" wrote on 06/15/2016 05:51:20
PM:
> From: John McDowall
> To: Na Zhu
> Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack
> Development Mailing List \(not for usage questions\)" d...@lists.openstack.org>, discuss
> Date: 06/15/2016 05:51 PM
> Subject: Re: [ovs-
Apologies for being delayed on replying and in-line back as well
Ryan
John McDowall wrote on 06/15/2016 05:58:35
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Na Zhu , Srilatha Tangirala/San Francisco/
> IBM@IBMUS, "OpenStack Development Mailing Li
"discuss" wrote on 06/14/2016 10:31:40
PM:
> From: John McDowall
> To: Na Zhu
> Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack
> Development Mailing List \(not for usage questions\)" d...@lists.openstack.org>, discuss
> Date: 06/14/2016 10:48 PM
> Subject: Re: [ovs-discuss] [opens
John McDowall wrote on 06/02/2016 11:03:28
AM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff , "disc...@openvswitch.org"
> , Justin Pettit ,
> "OpenStack Development Mailing List" d...@lists.openstack.org>, Russell Bryant
>
John McDowall wrote on 05/31/2016 07:57:02
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff , "disc...@openvswitch.org"
> , Justin Pettit ,
> "OpenStack Development Mailing List" d...@lists.openstack.org>, Russell Bryant
>
John McDowall wrote on 05/31/2016 03:21:30
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff , "disc...@openvswitch.org"
> , Justin Pettit ,
> "OpenStack Development Mailing List" d...@lists.openstack.org>, Russell Bryant
>
John McDowall wrote on 05/31/2016 03:19:54
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff , "disc...@openvswitch.org"
> , Justin Pettit ,
> "OpenStack Development Mailing List" d...@lists.openstack.org>, Russell Bryant
>
"Armando M." wrote on 05/31/2016 01:12:32 PM:
> From: "Armando M."
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 05/31/2016 01:13 PM
> Subject: [openstack-dev] [Neutron][Release] Changing release model
> for *-aas services
>
> Hi folks,
>
> Having looked at t
John McDowall wrote on 05/26/2016 11:08:43
AM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff , "disc...@openvswitch.org"
> , Justin Pettit ,
> "OpenStack Development Mailing List" d...@lists.openstack.org>, Russell Bryant
>
John McDowall wrote on 05/26/2016 10:59:48
AM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS, Ben Pfaff
> Cc: "disc...@openvswitch.org" , Justin
> Pettit , OpenStack Development Mailing List
> , Russell Bryant
> Date: 05/26/2016 11:00 AM
> Sub
Ben Pfaff wrote on 05/25/2016 07:44:43 PM:
> From: Ben Pfaff
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: John McDowall ,
> "disc...@openvswitch.org" , OpenStack
> Development Mailing List , Justin
> Pettit , Russell Bryant
> Date: 05/25/2016 07:44 PM
>
John McDowall wrote on 05/25/2016 07:27:46
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List" , Ben
> Pfaff , Justin Pettit , Russell Bryant
>
> Date: 05/25/2016 07:2
John McDowall wrote on 05/24/2016 06:33:05
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List"
> Date: 05/24/2016 06:33 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc
John McDowall wrote on 05/18/2016 03:55:14
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List"
> Date: 05/18/2016 03:55 PM
> Subject: Re: [OVN] [networking-ovn] [networking
t make sense?
Ryan
- Original message -From: John McDowall To: Ryan Moats/Omaha/IBM@IBMUSCc: "disc...@openvswitch.org" , "OpenStack Development Mailing List" Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVNDate: Wed, May 18, 2016 3:55 PM
Ryan,
OK all three
John McDowall wrote on 05/11/2016 12:37:40
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List"
> Date: 05/11/2016 12:37 PM
> Subject: Re: [OVN] [networking-ovn] [networking
John McDowall wrote on 05/11/2016 12:37:40
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List"
> Date: 05/11/2016 12:37 PM
> Subject: Re: [OVN] [networking-ovn] [networking
John McDowall wrote on 05/11/2016 12:06:55
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List"
> Date: 05/11/2016 12:07 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc
John McDowall wrote on 05/11/2016 11:30:07
AM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List"
> Date: 05/11/2016 11:30 AM
> Subject: Re: [OVN] [networking-ovn] [networking-sf
John McDowall wrote on 05/10/2016 11:11:57
AM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List"
> Date: 05/10/2016 11:12 AM
> Subject: Re: [OVN] [networking-ovn] [networking-sf
John McDowall wrote on 05/09/2016 10:46:41
AM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org" , "OpenStack
> Development Mailing List"
> Date: 05/09/2016 10:46 AM
> Subject: Re: [OVN] [networking-ovn] [networking
John McDowall wrote on 05/08/2016 07:34:52
PM:
> From: John McDowall
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: "disc...@openvswitch.org"
> Date: 05/08/2016 07:35 PM
> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN
>
> Correcting ovs address
>
&g
need help with the rebasing, I'm happy to work with you...
Ryan Moats (regXboi on IRC, jayhawk87 on github)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
"Armando M." wrote on 12/04/2015 03:43:29 PM:
> From: "Armando M."
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 12/04/2015 03:44 PM
> Subject: Re: [openstack-dev] [Neutron][DVR]
>
> > On 4 December 201
turn into?
I'm not yet for or against, I'm just trying to think what the commit
messages are going to end up looking like...
Ryan Moats (regXboi)
Oleg Bondarev wrote on 12/04/2015 02:44:58 AM:
> From: Oleg Bondarev
> To: "OpenStack Development Mailing List (not for usage qu
Apologies to those who get this twice - I'm fighting with mail
clients/servers this morning (and I'm pretty sure I'm losing)
As a US person, I'm going to vote -1 on moving to 1600 UTC on Tuesdays - I
already have too many other meetings stacked up in this slot...
Ryan M
I missed this the first time around, but I concur with the comments of the
other deputies -
the effort only took me about an hour or two a day and I think it's been
rather helpful :)
Ryan Moats (regXboi)
__
Open
ondering if it should only be in neutron or
if it should be elsewhere (like user docs that go along with code that
would implement [2] in oslo...
Thoughts and comments are welcome,
Ryan Moats (regXboi)
[1] https://etherpad.open
Ditto Ryan (regXboi) Moats
Carl Baldwin wrote on 11/02/2015 11:47:27 AM:
> From: Carl Baldwin
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 11/02/2015 11:48 AM
> Subject: Re: [openstack-dev] [Neutron] Weekly DVR Meeting starting next
week
>
> Thanks, Brian.
(With apologies to the Who)...
"Meet the new things, same as the old things"
DVR - let's make it real folks :)
Performance - I keep turning over rocks and finding things that just don't
make sense to me...
I suspect others will come a calling as
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, because that is an important
responsibility of the population.
I couldn't have said it better, Sean.
Ryan Moats
"Sean M. Collins" wrote on 09/14/2015 05:01:03 PM:
> From: "Sean M. Collins"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 09/14/2015 05:01 PM
> Subject: [ope
iberty, we have a large list of new items for the design summit
[1], which we will work to pare down into items that can be delivered in
Mitaka
Thanks,
Ryan Moats (IRC handle: regXboi)
[1] https://etherpad.openstack.org/p/neutron-mita
k Development Mailing List (not for usage questions)"
>
> Date: 08/19/2015 04:26 PM
> Subject: Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup
>
> On Wed, Aug 19, 2015 at 05:11:55PM EDT, Ryan Moats wrote:
> > One thing came up during lunch was including unit and fu
One thing came up during lunch was including unit and functional testing of
dual stack in the check and gate queues - I was regaled over lunch with one
operator's experiences in trying to run Neutron on a dual stack system.
Ryan Moats (regXboi)
Edgar Magana wrote on 08/19/2015 03:43:
osen, so I'm not sure yes if the selection of devstack-trusty for [1] is
the bug,
or the fact that devstack-trusty is missing pieces that bare-trusty has is
the bug.
Looking for help from knowledgeable people about how to go about getting
this addressed.
Thanks,
Ryan Moats
IRC: regXboi
[1
I will be there for my lightning talk, and I think armax and kevin_benton
will be there - it would be good to find some time for us to pow-wow, along
with some teleconference so that carl_baldwin and mestery can join in...
Ryan Moats (regXboi)
Mike Dorman wrote on 08/03/2015 10:07:23 PM
If that's the case, then I'd say let's just solve this right way and create
a new construct rather...
Ryan Moats
Kevin Benton wrote on 07/28/2015 06:44:53 PM:
> From: Kevin Benton
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Da
Kevin, doesn't this in itself create technical debt on the nova side in the
sense of what an instance attaches to?
I agree that it looks like less technical debt than conditionally
redefining a network, but without nova buy-in, it looks
like a non-starter...
Ryan
Kevin Benton wrote on 07/28/2015
+1
Kyle Mestery wrote on 07/27/2015 08:16:07 AM [with a
bit of cleanup]:
> > On Mon, Jul 27, 2015 at 6:57 AM, Thierry Carrez
wrote:
> > Ihar Hrachyshka wrote:
> > > I noticed that dvr job is now voting for all stable branches, and
> > > failing, because the branch misses some important fixes fr
The alternative is to do what has been done with the neutron meeting itself
- have it be held in two alternating time slots.
Ryan
Damon Wang wrote on 07/22/2015 12:08:03 PM:
> From: Damon Wang
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Cc: Eran Gampel , Antoni S
rs to adoption by operators and would like (as we move
forward) to invite operators in to provide their input...
Thanks,
Ryan Moats
[1] https://etherpad.openstack.org/p/neutron-instrumentation__
OpenStack Development Mailing List (no
Gabriel Bezerra wrote on 03/10/2015 12:34:30 PM:
>
> Em 10.03.2015 14:24, Carl Baldwin escreveu:
> > Neutron currently does not enforce the uniqueness, or non-overlap, of
> > subnet cidrs within the address scope for a single tenant. For
> > example, if a tenant chooses to use 10.0.0.0/24 on m
;192.168.0.1',
> 'pool_id': 'my_pool_id'}
>
> I am generally not a big fan of RESTful actions. But in this case the
> semantics of the API operation are that of a subnet creation from within
a
> pool, so that might be ok.
This would be my preferred approach of
other contributors working on it
> will resume it for the next release.
>
> Salvatore
>
> [1] https://review.openstack.org/#/c/132661/
>
> On 5 February 2015 at 22:52, Ryan Moats wrote:
> I've run into a set of use cases where it would really be useful to
> be a
ally close.
So, I'm wondering if there is a blueprint that I missed when I went
searching or if there are folks that would be interested in seeing along
the lines of [1] getting implemented...
Thanks in advance,
Ryan Moats
[1]
https://wiki.openstack.org/wiki/Neutron/sharing-model-for-exter
Sigh... hit send too soon and forgot to sign...
+1 to that idea...
Ryan
Jay Pipes wrote on 02/02/2015 04:35:36 PM:
>
> What about having a separate HTTP header that indicates the "OpenStack
> Error Code", along with a generated URI for finding more information
> about the error?
>
> Something
+1 to that idea...
Jay Pipes wrote on 02/02/2015 04:35:36 PM:
>
> What about having a separate HTTP header that indicates the "OpenStack
> Error Code", along with a generated URI for finding more information
> about the error?
>
> Something like:
>
> X-OpenStack-Error-Code: 1234
> X-OpenStack-Er
Ian Wells wrote on 11/19/2014 02:33:40 PM:
[snip]
> When you have a plugin that's decided to be synchronous, then there
> are cases where the DB lock is held for a technically indefinite
> period of time. This is basically broken.
A big +1 to this statement
Ryan Moats__
solation and
> > related questions
> >
> > On Nov 19, 2014, at 1:49 PM, Ryan Moats wrote:
> >
> > I was waiting for this because I think I may have a slightly
> > different (and outside of the box) view on how to approach a solution
to this.
> >
> > Concep
arios, then I think we will find that we've solved the
multi-master problem essentially "for free".
Ryan Moats
Mike Bayer wrote on 11/19/2014 12:05:35 PM:
> From: Mike Bayer
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 11/19/2
+1
Sumit Naiksatam wrote on 08/08/2014 02:44:55 PM:
> From: Sumit Naiksatam
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 08/08/2014 02:45 PM
> Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy -
Renaming
>
> Thanks Jay for your constructive fee
Edgar Magana wrote on 08/07/2014 04:37:39 PM:
> From: Edgar Magana
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 08/07/2014 04:40 PM
> Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy -
Renaming
>
> Ryan,
>
> COPS implies a common protocol to
GBP groups.
Ryan Moats
Edgar Magana wrote on 08/07/2014 04:02:43 PM:
> From: Edgar Magana
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 08/07/2014 04:03 PM
> Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy -
Renam
[snipping to save BW]
Aaron Rosen wrote on 08/06/2014 03:26:24 PM:
> Note: I'm not going to use the pure group policy API as I have been
> a fan of the
> 2-group approach from day 1, I'm going to use the commands as stated
> in the patch set, and I'm going to assume (dangerous I know) that I
>
; Hi Ryan,
>
> On Wed, Aug 6, 2014 at 11:55 AM, Ryan Moats wrote:
> Jay Pipes wrote on 08/06/2014 01:04:41 PM:
>
> [snip]
>
>
> > AFAICT, there is nothing that can be done with the GBP API that cannot
> > be done with the low-level regular Neutron API.
> I'l
Jay Pipes wrote on 08/06/2014 01:04:41 PM:
[snip]
> AFAICT, there is nothing that can be done with the GBP API that cannot
> be done with the low-level regular Neutron API.
I'll take you up on that, Jay :)
How exactly do I specify behavior between two collections of ports residing
in the sa
Yes
Henry Fourie wrote on 07/31/2014 12:32:23 PM:
> From: Henry Fourie
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Cc: Subrahmanyam Ongole
> Date: 07/31/2014 12:33 PM
> Subject: Re: [openstack-dev] [neutron][policy] Bridging the 2-group
> gap in group policy
>
> R
mary email
of an IRC meeting to the ML with a note of anything that was agreed in the
meeting and include a link to the meeting minutes and transcript.
Thanks,
Ryan Moats (regXboi)___
OpenStack-dev mailing list
OpenStack-dev@lists.openstac
he gap" and provide support to folks who want
to specify policy as something between two groups.
Ryan Moats (regXboi)
References:
[1]
http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-07-28-21.02.log.txt
[2]
https://docs.google.com/document/d/1ZbOFxAoi
pace.
Can somebody lend me a hand and either (a) tell me I'm reading the code
wrong or (b) explain why that choice was made?
Thanks in advance,
Ryan Moats
rmo...@us.ibm.com___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.op
65 matches
Mail list logo
