Re: [ovs-discuss] HA OVN "Central" as a kubernetes service

2020-06-26 Thread Brendan Doyle 

OK thanks so it does seem that the repo I pointed to:


I have found this:
https://github.com/ovn-org/ovn-kubernetes#readme


Is the master branch of
(https://github.com/ovn-org/ovn-kubernetes/commit/a07b1a01af7e37b15c2e5f179ffad2b9f25a083d) 
uses statefulset and headless service for starting ovn central raft 
cluster with 3 replicas. Cluster startup code and pod specs are


And does create an OVN central cluster as a k8 service.

I'll give it a try.

Thanks

On 25/06/2020 17:36, aginwala wrote:

Hi:

There are a couple of options as I have been exploring this too:

1. Upstream ovn-k8s patches 
(https://github.com/ovn-org/ovn-kubernetes/commit/a07b1a01af7e37b15c2e5f179ffad2b9f25a083d) 
uses statefulset and headless service for starting ovn central raft 
cluster with 3 replicas. Cluster startup code and pod specs are pretty 
neat that addresses most of the doubts.


OVN components have been containerized too to start them in pods. You 
can also refer to 
https://github.com/ovn-org/ovn/blob/d6b56b1629d5984ef91864510f918e232efb89de/Documentation/intro/install/general.rst 
 for the same and use them to make it work in pod specs too.



2. Write a new ovn operator similar to etcd operator 
https://github.com/coreos/etcd-operator which just takes the count of 
raft replicas and does the job in the background.


I also added ovn-k8s group so they can comment on any other ideas too. 
Hope it helps.




On Thu, Jun 25, 2020 at 7:15 AM Brendan Doyle 
mailto:brendan.do...@oracle.com>> wrote:


Hi,

So I'm trying to find information on setting up an OVN
"Central/Master"
high availability (HA)
Not as Active-Backup with Pacemaker, but as a cluster. But I want to
deploy and manage that
cluster as a Kubernetes service .

I can find lots of stuff on "ovn-kube" but this seems to be using
OVN as
a  kubernetes CNI instead of
Flannel etc.  But this is not what I want to do, I have a kubernetes
cluster using Flannel as the CNI,
now  I want to deploy a HA OVN "Central" as a kubernetes service.
Kind
of like how you can deploy
a MySQL cluster in kubernetes using a SatefulSet deployment.

I have found this:
https://github.com/ovn-org/ovn-kubernetes#readme

But it is not clear to me if this is how to setup OVN as a kubernetes
CNI or it's how to setup a HA
OVN central as kubernetes service.

Can anybody comment, has anyone done this?


I guess I could run an OVN central as standalone and use a kubernetes
deployment with 3
  replica sets and "export" as a NodePort service. And have a
floating/VIP on my kubernetes
nodes. And direct ovn-controllers to the VIP. So only the pod that
holds
the VIP would service
requests. This would work and give HA, but you don't get the
performance
of an OVN
clustered Database Model, where each OVN central could service
requests.




Thanks


Rdgs
Brendan

___
discuss mailing list
disc...@openvswitch.org 
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss



___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] OVS 2.12/2.13 compilation on Ubuntu Bionic

2020-06-26 Thread Maciej Jozefczyk 
Hello!

I would like to kindly ask You if there is a possibility to cherry-pick
patch [1] to stable branches OVS 2.12, OVS 2.13 and release new tags for it?

Without this patch we're now unable to compile OVS 2.12 in OpenStack
Neutron stable releases CI, because it recently started to fail on Ubuntu
Bionic with an error:

2020-06-24 14:50:13.975917 | primary |
/opt/stack/new/ovs/datapath/linux/geneve.c: In function
‘geneve_get_v6_dst’:
2020-06-24 14:50:13.975993 | primary |
/opt/stack/new/ovs/datapath/linux/geneve.c:966:15: error: ‘const
struct ipv6_stub’ has no member named ‘ipv6_dst_lookup’
2020-06-24 14:50:13.976026 | primary |   if
(ipv6_stub->ipv6_dst_lookup(geneve->net, gs6->sock->sk, &dst, fl6)) {
2020-06-24 14:50:13.976049 | primary |^
2020-06-24 14:50:14.010809 | primary | scripts/Makefile.build:285:
recipe for target '/opt/stack/new/ovs/datapath/linux/geneve.o' failed

The same happens for OVN 2.13. For now this blocks your CI pipelines.

Can I ask You to backport this patch?

Thanks,
Maciej

[1]
https://github.com/openvswitch/ovs/commit/5519e384f6a17f564fef4c5eb39e471e16c77235

-- 
Best regards,
Maciej Józefczyk
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] Question concerning GRE-encapsulated traffic *in* OpenStack provider VLAN network

2020-06-26 Thread Loschwitz,Martin Gerhard 
Folks,

I’m contacting you to find out if a behaviour I see is expected behaviour or 
actual misdemeanour in Open vSwitch and/or OVN. I have an OpenStack setup here 
that uses OVN. I have configured several VLAN-based provider networks. What I 
want to do is use a GRE-tunnel *inside* one of these VLAN networks. On the 
target compute node, I see that traffic enters the physical host but is not 
forwarded to the bridge to which the VM is connected. I can see that the flows 
for that are missing in the flow table.

I fully understand that OVN supports Geneve only, but in this case, I want my 
*tenants* to be able to use GRE encapsulation in a provider network. Is this 
supposed to work and this is either a bug or a misconfiguration? And if it is 
not expected to work, what are possible alternatives?

Thank you very much for your help in advance.

Best regards
Martin
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Linux Foundation slideshare - OVS 2017

2020-06-26 Thread Emily Ruf 
Hi Ben,

Before we head into the weekend, I wanted to give you a quick update. We’ve 
submitted a ticket to LinkedIn to find out why the account was locked and what 
action we need to take to reinstate the account.

I’ll update you once I have more details to share.

Emily Ruf, CMP
Event Manager
The Linux Foundation

M: 512-745-1456
E: e...@linuxfoundation.org



> On Jun 24, 2020, at 9:10 PM, Ben Pfaff  wrote:
> 
> Thanks a lot!  This surprised me...
> 
> On Wed, Jun 24, 2020 at 06:15:41PM -0400, Emily Ruf wrote:
>> Hi Ben,
>> 
>> Thanks for reaching out. I’ll look into this and report back asap.
>> 
>> Emily
>> 
>> Emily Ruf, CMP
>> Event Manager
>> The Linux Foundation
>> 
>> M: 512-745-1456
>> E: e...@linuxfoundation.org
>> 
>> 
>> 
>>> On Jun 24, 2020, at 5:29 PM, Ben Pfaff  wrote:
>>> 
>>> Hi Emily.  I think that you represent Linux Foundation regarding event
>>> planning; at least, I see that I've had email conversations with you
>>> before in this respect.
>>> 
>>> In 2017 the Open vSwitch project contracted with Linux Foundation to
>>> produce the Open vSwitch conference.  As part of that, LF posted all of
>>> the slides from the conference to SlideShare.  You can see links from
>>> https://www.openvswitch.org/support/ovscon2017/ to all of these.  As you
>>> can see, all of them link to an LF_OpenvSwitch account, which LF
>>> presumably created to host these slides.
>>> 
>>> All of these links now display the following message:
>>> 
>>>   Uploaded SlideShare Suspended
>>> 
>>>   This SlideShare was suspended because it violated SlideShare Terms
>>>   of Service and/or Community Guidelines. You can view more
>>>   SlideShares here.
>>> 
>>> Could LF please fix these Terms of Service or Community Guidelines
>>> violations, whatever they are?  The Open vSwitch project was never
>>> notified of these, so we do not know what they are.  Or, alternatively,
>>> would you please make the slides available to the OVS community in some
>>> other way?  We will host them ourselves, if you can get them for us.
>>> 
>>> Thanks,
>>> 
>>> Ben.
>> 

___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Linux Foundation slideshare - OVS 2017

2020-06-26 Thread Ben Pfaff 
OK!  That's a good start.  Thanks!

On Fri, Jun 26, 2020 at 03:57:20PM -0400, Emily Ruf wrote:
> Hi Ben,
> 
> Before we head into the weekend, I wanted to give you a quick update. We’ve 
> submitted a ticket to LinkedIn to find out why the account was locked and 
> what action we need to take to reinstate the account.
> 
> I’ll update you once I have more details to share.
> 
> Emily Ruf, CMP
> Event Manager
> The Linux Foundation
> 
> M: 512-745-1456
> E: e...@linuxfoundation.org
> 
> 
> 
> > On Jun 24, 2020, at 9:10 PM, Ben Pfaff  wrote:
> > 
> > Thanks a lot!  This surprised me...
> > 
> > On Wed, Jun 24, 2020 at 06:15:41PM -0400, Emily Ruf wrote:
> >> Hi Ben,
> >> 
> >> Thanks for reaching out. I’ll look into this and report back asap.
> >> 
> >> Emily
> >> 
> >> Emily Ruf, CMP
> >> Event Manager
> >> The Linux Foundation
> >> 
> >> M: 512-745-1456
> >> E: e...@linuxfoundation.org
> >> 
> >> 
> >> 
> >>> On Jun 24, 2020, at 5:29 PM, Ben Pfaff  wrote:
> >>> 
> >>> Hi Emily.  I think that you represent Linux Foundation regarding event
> >>> planning; at least, I see that I've had email conversations with you
> >>> before in this respect.
> >>> 
> >>> In 2017 the Open vSwitch project contracted with Linux Foundation to
> >>> produce the Open vSwitch conference.  As part of that, LF posted all of
> >>> the slides from the conference to SlideShare.  You can see links from
> >>> https://www.openvswitch.org/support/ovscon2017/ to all of these.  As you
> >>> can see, all of them link to an LF_OpenvSwitch account, which LF
> >>> presumably created to host these slides.
> >>> 
> >>> All of these links now display the following message:
> >>> 
> >>>   Uploaded SlideShare Suspended
> >>> 
> >>>   This SlideShare was suspended because it violated SlideShare Terms
> >>>   of Service and/or Community Guidelines. You can view more
> >>>   SlideShares here.
> >>> 
> >>> Could LF please fix these Terms of Service or Community Guidelines
> >>> violations, whatever they are?  The Open vSwitch project was never
> >>> notified of these, so we do not know what they are.  Or, alternatively,
> >>> would you please make the slides available to the OVS community in some
> >>> other way?  We will host them ourselves, if you can get them for us.
> >>> 
> >>> Thanks,
> >>> 
> >>> Ben.
> >> 
> 
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] OVSDB Error:Type mismatch for member 'uuid-name

2020-06-26 Thread Vasu Dasari 
Hi,

I am seeing a strange error. Can someone see if this ia bug or I am using
this wrong?

The following transaction is successful

root@ovs1:~# ovsdb-client transact '
[
  "Open_vSwitch",
  {
"op": "insert",
"row": {
  "name": "br1-eth1"
},
"table": "Interface",
"uuid-name": "a33f0e9e60105b9d8f8c15797107f29c"
  }
]
'
[{"uuid":["uuid","69ee67e3-4a32-4c88-998f-fd354b7b0509"]}]

whereas the following transaction fails:
root@ovs1:~# ovsdb-client transact '
[
  "Open_vSwitch",
  {
"op": "insert",
"row": {
  "name": "br1-eth1"
},
"table": "Interface",
"uuid-name": "133f0e9e60105b9d8f8c15797107f29c"
  }
]
'
[{"details":"Parsing ovsdb operation 1 of 1 failed: Type mismatch for
member 'uuid-name'.","error":"syntax
error","syntax":"{\"op\":\"insert\",\"row\":{\"name\":\"br1-eth1\"},\"table\":\"Interface\",\"uuid-name\":\"133f0e9e60105b9d8f8c15797107f29c\"}"}]
root@ovs1:~#

The only difference in above commands is the uuid-name string.
a33f0e9e60105b9d8f8c15797107f29c.  << Successful one
133f0e9e60105b9d8f8c15797107f29c.  << Failed one

Also you can notice that the first letter in the above strings is the only
thing that is different. Actually, this command fails if the first letter
is any digit(0-9).

Can someone please share what's going on here, why this is failing?

Thanks
-Vasu




*Vasu Dasari*
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVSDB Error:Type mismatch for member 'uuid-name

2020-06-26 Thread Ben Pfaff 
On Fri, Jun 26, 2020 at 06:10:09PM -0400, Vasu Dasari wrote:
> Hi,
> 
> I am seeing a strange error. Can someone see if this ia bug or I am using
> this wrong?
> 
> The following transaction is successful
> 
> root@ovs1:~# ovsdb-client transact '
> [
>   "Open_vSwitch",
>   {
> "op": "insert",
> "row": {
>   "name": "br1-eth1"
> },
> "table": "Interface",
> "uuid-name": "a33f0e9e60105b9d8f8c15797107f29c"
>   }
> ]
> '
> [{"uuid":["uuid","69ee67e3-4a32-4c88-998f-fd354b7b0509"]}]
> 
> whereas the following transaction fails:
> root@ovs1:~# ovsdb-client transact '
> [
>   "Open_vSwitch",
>   {
> "op": "insert",
> "row": {
>   "name": "br1-eth1"
> },
> "table": "Interface",
> "uuid-name": "133f0e9e60105b9d8f8c15797107f29c"
>   }
> ]
> '
> [{"details":"Parsing ovsdb operation 1 of 1 failed: Type mismatch for
> member 'uuid-name'.","error":"syntax
> error","syntax":"{\"op\":\"insert\",\"row\":{\"name\":\"br1-eth1\"},\"table\":\"Interface\",\"uuid-name\":\"133f0e9e60105b9d8f8c15797107f29c\"}"}]
> root@ovs1:~#
> 
> The only difference in above commands is the uuid-name string.
> a33f0e9e60105b9d8f8c15797107f29c.  << Successful one
> 133f0e9e60105b9d8f8c15797107f29c.  << Failed one
> 
> Also you can notice that the first letter in the above strings is the only
> thing that is different. Actually, this command fails if the first letter
> is any digit(0-9).
> 
> Can someone please share what's going on here, why this is failing?

As documented in the RFC, uuid-name must be an , which must start
with _ or a letter.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVSDB Error:Type mismatch for member 'uuid-name

2020-06-26 Thread Vasu Dasari 
Thank you Ben. I should have gone through the definition.

Vasu

> On Jun 26, 2020, at 7:52 PM, Ben Pfaff  wrote:
> 
> On Fri, Jun 26, 2020 at 06:10:09PM -0400, Vasu Dasari wrote:
>> Hi,
>> 
>> I am seeing a strange error. Can someone see if this ia bug or I am using
>> this wrong?
>> 
>> The following transaction is successful
>> 
>> root@ovs1:~# ovsdb-client transact '
>> [
>>  "Open_vSwitch",
>>  {
>>"op": "insert",
>>"row": {
>>  "name": "br1-eth1"
>>},
>>"table": "Interface",
>>"uuid-name": "a33f0e9e60105b9d8f8c15797107f29c"
>>  }
>> ]
>> '
>> [{"uuid":["uuid","69ee67e3-4a32-4c88-998f-fd354b7b0509"]}]
>> 
>> whereas the following transaction fails:
>> root@ovs1:~# ovsdb-client transact '
>> [
>>  "Open_vSwitch",
>>  {
>>"op": "insert",
>>"row": {
>>  "name": "br1-eth1"
>>},
>>"table": "Interface",
>>"uuid-name": "133f0e9e60105b9d8f8c15797107f29c"
>>  }
>> ]
>> '
>> [{"details":"Parsing ovsdb operation 1 of 1 failed: Type mismatch for
>> member 'uuid-name'.","error":"syntax
>> error","syntax":"{\"op\":\"insert\",\"row\":{\"name\":\"br1-eth1\"},\"table\":\"Interface\",\"uuid-name\":\"133f0e9e60105b9d8f8c15797107f29c\"}"}]
>> root@ovs1:~#
>> 
>> The only difference in above commands is the uuid-name string.
>> a33f0e9e60105b9d8f8c15797107f29c.  << Successful one
>> 133f0e9e60105b9d8f8c15797107f29c.  << Failed one
>> 
>> Also you can notice that the first letter in the above strings is the only
>> thing that is different. Actually, this command fails if the first letter
>> is any digit(0-9).
>> 
>> Can someone please share what's going on here, why this is failing?
> 
> As documented in the RFC, uuid-name must be an , which must start
> with _ or a letter.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss