Hi Numan, Yes, it's working. I think the networking-ovn plugin in OpenStack has some bugs. let me use a single IP first or maybe I can use pacemaker to create the VIP.
[root@zu-ovn-controller0 ~]# ovn-nbctl --db=tcp:10.101.101.100:6641,tcp: 10.101.101.101:6641,tcp:10.101.101.102:6641 ls-add sw0 [root@zu-ovn-controller0 ~]# ovn-nbctl --db=tcp:10.101.101.100:6641,tcp: 10.101.101.101:6641,tcp:10.101.101.102:6641 show switch 5d3ea060-f92f-41ab-8143-6a6534bbba98 (sw0) [root@zu-ovn-controller0 ~]# [root@zu-ovn-controller1 ~]# ovn-nbctl --db=tcp:10.101.101.100:6641,tcp: 10.101.101.101:6641,tcp:10.101.101.102:6641 show switch 5d3ea060-f92f-41ab-8143-6a6534bbba98 (sw0) Thank you very much :) Best Regards, Zufar Dhiyaulhaq On Wed, Aug 28, 2019 at 7:17 PM Numan Siddique <[email protected]> wrote: > > > On Wed, Aug 28, 2019 at 4:45 PM Zufar Dhiyaulhaq <[email protected]> > wrote: > >> Hi Numan, >> >> I have tried the command but output nothing. >> >> [root@zu-ovn-controller0 ~]# ovn-nbctl --db=tcp:10.101.101.100:6641,tcp: >> 10.101.101.101:6641,tcp:10.101.101.102:6641 show >> > > These commands seem to work. Try creating a logical switch like - > ovn-nbctl --db=tcp:10.101.101.100:6641,tcp:10.101.101.101:6641,tcp: > 10.101.101.102:6641 ls-add sw0 > ovn-nbctl --db=tcp:10.101.101.100:6641,tcp:10.101.101.101:6641,tcp: > 10.101.101.102:6641 show > > > [root@zu-ovn-controller0 ~]# ovn-sbctl --db=tcp:10.101.101.100:6642,tcp: >> 10.101.101.101:6642,tcp:10.101.101.102:6642 show >> Chassis "1ee48dd1-d520-476d-82d3-3d4651132f47" >> hostname: "zu-ovn-compute0" >> Encap geneve >> ip: "10.101.101.103" >> options: {csum="true"} >> Chassis "cd1a2535-522a-4571-8eac-8394681846a3" >> hostname: "zu-ovn-compute2" >> Encap geneve >> ip: "10.101.101.105" >> options: {csum="true"} >> Chassis "a5b59592-f511-4a7a-b37d-93f933c35ea5" >> hostname: "zu-ovn-compute1" >> Encap geneve >> ip: "10.101.101.104" >> options: {csum="true"} >> [root@zu-ovn-controller0 ~]# tail -f >> /var/log/openvswitch/ovsdb-server-nb.log >> 2019-08-28T09:12:31.190Z|00031|reconnect|INFO|tcp:10.101.101.102:6643: >> connection attempt failed (No route to host) >> 2019-08-28T09:12:31.190Z|00032|reconnect|INFO|tcp:10.101.101.102:6643: >> waiting 2 seconds before reconnect >> 2019-08-28T09:12:33.191Z|00033|reconnect|INFO|tcp:10.101.101.102:6643: >> connecting... >> 2019-08-28T09:12:33.192Z|00034|reconnect|INFO|tcp:10.101.101.102:6643: >> connection attempt failed (No route to host) >> 2019-08-28T09:12:33.192Z|00035|reconnect|INFO|tcp:10.101.101.102:6643: >> waiting 4 seconds before reconnect >> 2019-08-28T09:12:37.192Z|00036|reconnect|INFO|tcp:10.101.101.102:6643: >> connecting... >> 2019-08-28T09:12:37.192Z|00037|reconnect|INFO|tcp:10.101.101.102:6643: >> connection attempt failed (No route to host) >> 2019-08-28T09:12:37.192Z|00038|reconnect|INFO|tcp:10.101.101.102:6643: >> continuing to reconnect in the background but suppressing further logging >> 2019-08-28T09:22:52.597Z|00039|reconnect|INFO|tcp:10.101.101.101:6643: >> connected >> >> 2019-08-28T09:23:01.279Z|00040|reconnect|INFO|tcp:10.101.101.102:6643: >> connected >> >> I have tried with ovn-ctl to create the clustered-databases, but the >> problem is same, stuck when creating neutron resources. I think it because >> the ovn-northd run in 3 nodes, but neutron only run on a single controller. >> > > I don't think that's the issue. > The issue seems to be that networking-ovn is not tested with connecting to > clustered db. > Try passing just one remote to neutron server and see if it works. > > > May be you can ask this question in the openstack ML to get more attention. > > Numan > > >> this is the step: http://paste.openstack.org/show/766470/ >> should I try the step first? but check with passing the remote URL to >> command? >> >> Best Regards, >> Zufar Dhiyaulhaq >> >> >> On Wed, Aug 28, 2019 at 6:06 PM Numan Siddique <[email protected]> >> wrote: >> >>> >>> >>> On Wed, Aug 28, 2019 at 4:04 PM Zufar Dhiyaulhaq < >>> [email protected]> wrote: >>> >>>> [ovn][clustered] Confusing to create ovsdb-server clustered databases >>>> >>>> Hi Everyone, I have successfully created OpenStack with OVN enabled. >>>> But the problem comes when I try to cluster the ovsdb-server. My scenario >>>> is trying to cluster the ovsdb-server databases but only using single >>>> ovn-northd. >>>> >>>> My cluster: >>>> - controller0 : 10.100.100.100 / 10.101.101.100 (ovn-northd, >>>> ovsdb-server, neutron server) >>>> - controller1 : 10.100.100.101 / 10.101.101.101 (ovsdb-server) >>>> - controller2 : 10.100.100.102 / 10.101.101.102 (ovsdb-server) >>>> - compute1 : 10.100.100.103 / 10.101.101.103 >>>> - compute2 : 10.100.100.104 / 10.101.101.104 >>>> - compute3 : 10.100.100.105 / 10.101.101.105 >>>> >>>> 10.100.100.0/24 : Management Network >>>> 10.101.101.0/24 : Data Network >>>> >>>> I have installed the OpenStack using the manual method. Below is the >>>> step to create ovsdb-server and neutron services. >>>> - step 1: bootstrapping ovsdb-server cluster : >>>> http://paste.openstack.org/show/766463/ >>>> - step 2: creating neutron service in controller : >>>> http://paste.openstack.org/show/766464/ >>>> - step 3: creating neutron service in compute : >>>> http://paste.openstack.org/show/766465/ >>>> >>>> But when I try to create neutron resource, Its always hang (only >>>> neutron resource). >>>> >>>> This is the full logs of all nodes, contain: >>>> http://paste.openstack.org/show/766461/ >>>> - all openvswitch logs >>>> - port (via netstat) >>>> - step bootstraping ovsdb-server >>>> >>>> Neutron logs in controller0: paste.openstack.org/show/766462/ >>>> >>>> Anyone know why stuck? Are my step is wrong? >>>> >>>> >>> Hi Zufar, >>> >>> Have you tried connecting to the clustered dbs using ovn-nbctl ? >>> Does it work fine when you pass the remotes i.e >>> $ovn-nbctl --db=tcp:10.101.101.100:6641,tcp:10.101.101.101:6641,tcp: >>> 10.101.101.102:6641 show >>> >>> If so, then it seems to me you have configured the clustered db properly. >>> >>> Also please take a look at - "man ovn-ctl" and grep for "Creating a >>> clustered db on 3 nodes". >>> >>> May be the python IDL code or the ovsdbapp which networking-ovn uses >>> doesn't support connecting >>> with multiple remotes ? >>> >>> I remember adding the support in the python IDL to accept multiple >>> remotes [1], but not sure >>> what's the status now. >>> >>> @Daniel - Do you have any comments/pointers ? >>> >>> [1] - >>> https://github.com/openvswitch/ovs/commit/31e434fc985c682708f5d92bde2ceae452bdaa4f >>> >>> https://github.com/openvswitch/ovs/commit/257edb1ae07c150023575dfb38ea8e539ad713de >>> >>> Thanks >>> Numan >>> >>> Thank you. >>>> >>>> Best Regards, >>>> Zufar Dhiyaulhaq >>>> _______________________________________________ >>>> discuss mailing list >>>> [email protected] >>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >>>> >>>
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
