Thanks, Ben! I'll keep a watch, but if I do miss anything please let me know
and I'll try to get to it quickly.
thanks,
-venu
From: Ben Pfaff
Sent: Friday, February 22, 2019 2:42 PM
To: Venugopal Iyer
Cc: Guru Shetty; Leonid Grossman; d...@openvswitch.o
This was definitely a bit quicker than I usually prefer for changes that
might have nonobvious side effects, but we are also very close to the
beginning of a release cycle, so I decided to be an optimist for once.
You can watch the OVS CI/CD here:
https://travis-ci.org/openvswitch/ovs
On
Thanks, Ben!
I was thinking there'll be additional test cycles to check for regression
before making it to the
code. From my side, I have tested it for the new feature, compatibility and run
the OVN community
tests (plus testing in our setup for OVN functionality).
How do I monitor for regressi
I applied this series to master. Thank you!
On Tue, Feb 12, 2019 at 03:52:48PM +, Venugopal Iyer wrote:
> HI, Ben:
>
>
> From: Ben Pfaff
> Sent: Monday, February 11, 2019 5:55 PM
> To: Venugopal Iyer
> Cc: Guru Shetty; Leonid Grossman; d...@openvswit
HI, Ben:
From: Ben Pfaff
Sent: Monday, February 11, 2019 5:55 PM
To: Venugopal Iyer
Cc: Guru Shetty; Leonid Grossman; d...@openvswitch.org
Subject: Re: [ovs-discuss] [ovs-dev] Geneve remote_ip as flow for OVN hosts
On Mon, Feb 11, 2019 at 08:09:59PM +
On Mon, Feb 11, 2019 at 08:09:59PM +, Venugopal Iyer wrote:
> Of course we want users to upgrade the entire system. We just need to
> make sure that it's possible to upgrade one piece at a time in an order
> that ensures that the system isn't broken by a partial upgrade. The
> specified order
From: Ben Pfaff
Sent: Thursday, February 7, 2019 6:53 PM
To: Venugopal Iyer
Cc: Guru Shetty; Leonid Grossman; d...@openvswitch.org
Subject: Re: [ovs-discuss] [ovs-dev] Geneve remote_ip as flow for OVN hosts
On Thu, Feb 07, 2019 at 08:10:48PM +, Venug
On Thu, Feb 07, 2019 at 08:10:48PM +, Venugopal Iyer wrote:
> > Also, as I mentioned the changes will mean that the ovn-controller will
> > need the ovn-central
> > to be updated to the changed version as well (i.e. if someone just installs
> > ovs and ovn-host
> > s/he can't expect it to be
Sorry, Ben, for the delay, just wanted to test out the compatibility, please
see response
inline prefixed with
Let me know if you have further questions.
thanks,
-venu
From: Ben Pfaff
Sent: Wednesday, February 6, 2019 10:15 AM
To: Venugopal Iyer
Cc:
It looks like we fell off ovs-dev somehow. I've added it back.
On Wed, Feb 06, 2019 at 05:50:39PM +, Venugopal Iyer wrote:
> Thanks, Ben!
>
> I missed and {} for an if; have fixed it; thanks for catching it!
>
> As for the TODOS:
> - ovn/controller/chassis.c was something I just wanted to
Hi Ben,
You are right, we briefly discussed this at ovscon; in-person meeting sounds as
a good way to progress.
Venu/Girish/myself are available next Wed - will this work for you?
We can come over to VMware campus, or host the meeting here at Nvidia (Santa
Clara HQ, San Tomas and Walsh)
to discu
Hi, Ben:
Agreed; mid/late next week should work for a meeting, will check with you about
availability/logistics.
thanks!
-venu
On Wednesday, December 12, 2018, 12:50:41 PM PST, Ben Pfaff
wrote:
If I'm not mistaken, we briefly discussed this at ovscon. It seems to
me that this is
If I'm not mistaken, we briefly discussed this at ovscon. It seems to
me that this is a fairly complicated issue and proposal, and it might
benefit from in-person discussion. I seem to recall that you are local
to the Bay Area, and, if so, do you think we could take some time,
perhaps next week,
Sorry for the resend, I am not sure how the pictures will render in the text
doc, so am attaching the PDF too.
thanks,
-venu
On Thursday, November 29, 2018, 9:26:54 AM PST, venugopal iyer
wrote:
Thanks, Ben.
Sorry for the delay. Please find attached a draft design proposal and let
Thanks, Ben.
Sorry for the delay. Please find attached a draft design proposal and let me
know your comments etc. I did some quick
prototyping to check for feasibility too; I can share that, if it helps.
Note, the document is a draft and, I admit, there might be things that I
haven't tho
Honestly the best thing to do is probably to propose a design or, if
it's simple enough, to send a patch. That will probably be more
effective at sparking a discussion.
On Wed, Oct 31, 2018 at 03:33:48PM +, venugopal iyer wrote:
> Hi:
> Just wanted to check if folks had any thoughts on the u
Hi:
Just wanted to check if folks had any thoughts on the use case Girish outlined
below. We do have
a real use case for this and are interested in looking at options for
supporting more than one VTEP IP.It is currently a limitation for us, wanted to
know if there are similar use cases folks ar
Would it be possible for the association to be made
when the logical port is instantiated on a node? and relayed on to the SB by
the controller, e.g. assuming a mechanism to specify/determine a physical port
mapping for a
logical port for a VM. The mappings can be specified
as
configuration on
How would OVN know which IP to use for a given logical port on a
chassis?
I think that the "multiple tunnel encapsulations" is meant to cover,
say, Geneve vs. STT vs. VXLAN, not the case you have in mind.
On Wed, Sep 05, 2018 at 09:50:32AM -0700, Girish Moodalbail wrote:
> Hello all,
>
> I would
19 matches
Mail list logo
