<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
OK thanks so it does seem that the repo I pointed to:<br>
<br>
<blockquote type="cite">I have found this:<br>
<a href="https://github.com/ovn-org/ovn-kubernetes#readme"
rel="noreferrer" target="_blank">https://github.com/ovn-org/ovn-kubernetes#readme</a><br>
</blockquote>
<br>
Is the master branch of <br>
<blockquote type="cite">(<a
href="https://github.com/ovn-org/ovn-kubernetes/commit/a07b1a01af7e37b15c2e5f179ffad2b9f25a083d">https://github.com/ovn-org/ovn-kubernetes/commit/a07b1a01af7e37b15c2e5f179ffad2b9f25a083d</a>)
uses statefulset and headless service for starting ovn central
raft cluster with 3 replicas. Cluster startup code and pod specs
are</blockquote>
<br>
And does create an OVN central cluster as a k8 service.<br>
<br>
I'll give it a try.<br>
<br>
Thanks<br>
<br>
<div class="moz-cite-prefix">On 25/06/2020 17:36, aginwala wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPcQySgWM9vfUYS_LCpWzq-b5GoTpy7Y9+QPhc9m-=Hv-Suq3g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi:<br>
<br>
There are a couple of options as I have been exploring this
too:</div>
<div><br>
1. Upstream ovn-k8s patches (<a
href="https://github.com/ovn-org/ovn-kubernetes/commit/a07b1a01af7e37b15c2e5f179ffad2b9f25a083d"
moz-do-not-send="true">https://github.com/ovn-org/ovn-kubernetes/commit/a07b1a01af7e37b15c2e5f179ffad2b9f25a083d</a>)
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. </div>
<div><br>
OVN components have been containerized too to start them in
pods. You can also refer to <a
href="https://github.com/ovn-org/ovn/blob/d6b56b1629d5984ef91864510f918e232efb89de/Documentation/intro/install/general.rst"
target="_blank" moz-do-not-send="true">https://github.com/ovn-org/ovn/blob/d6b56b1629d5984ef91864510f918e232efb89de/Documentation/intro/install/general.rst</a>
for the same and use them to make it work in pod specs too.<br>
<br>
<br>
2. Write a new ovn operator similar to etcd operator <a
href="https://github.com/coreos/etcd-operator"
target="_blank" moz-do-not-send="true">https://github.com/coreos/etcd-operator</a>
which just takes the count of raft replicas and does the job
in the background.<br>
<br>
I also added ovn-k8s group so they can comment on any other
ideas too. Hope it helps.<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 25, 2020 at 7:15
AM Brendan Doyle <<a href="mailto:brendan.doyle@oracle.com"
target="_blank" moz-do-not-send="true">brendan.doyle@oracle.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
So I'm trying to find information on setting up an OVN
"Central/Master" <br>
high availability (HA)<br>
Not as Active-Backup with Pacemaker, but as a cluster. But I
want to <br>
deploy and manage that<br>
cluster as a Kubernetes service .<br>
<br>
I can find lots of stuff on "ovn-kube" but this seems to be
using OVN as <br>
a kubernetes CNI instead of<br>
Flannel etc. But this is not what I want to do, I have a
kubernetes <br>
cluster using Flannel as the CNI,<br>
now I want to deploy a HA OVN "Central" as a kubernetes
service. Kind <br>
of like how you can deploy<br>
a MySQL cluster in kubernetes using a SatefulSet deployment.<br>
<br>
I have found this:<br>
<a href="https://github.com/ovn-org/ovn-kubernetes#readme"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/ovn-org/ovn-kubernetes#readme</a><br>
<br>
But it is not clear to me if this is how to setup OVN as a
kubernetes <br>
CNI or it's how to setup a HA<br>
OVN central as kubernetes service.<br>
<br>
Can anybody comment, has anyone done this?<br>
<br>
<br>
I guess I could run an OVN central as standalone and use a
kubernetes <br>
deployment with 3<br>
replica sets and "export" as a NodePort service. And have a
<br>
floating/VIP on my kubernetes<br>
nodes. And direct ovn-controllers to the VIP. So only the pod
that holds <br>
the VIP would service<br>
requests. This would work and give HA, but you don't get the
performance <br>
of an OVN<br>
clustered Database Model, where each OVN central could service
requests.<br>
<br>
<br>
<br>
<br>
Thanks<br>
<br>
<br>
Rdgs<br>
Brendan<br>
<br>
_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@openvswitch.org" target="_blank"
moz-do-not-send="true">discuss@openvswitch.org</a><br>
<a
href="https://mail.openvswitch.org/mailman/listinfo/ovs-discuss"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mail.openvswitch.org/mailman/listinfo/ovs-discuss</a><br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>