Re: [ovs-discuss] Raft issues while removing a node

2018-12-13 Thread ramteja tadishetti
Hi,

Yeah, patch series url is no longer working, but this is the patchset
https://github.com/blp/ovs-reviews/commit/8ce2c1a5481dbfec1ba860f28b9d8e0ce881ee76

Thanks,
Ramteja

On Thu, Dec 13, 2018 at 5:17 PM aginwala  wrote:

> Hi Ben:
> I cannot see the patch series on the patchwork. Is it due to mail server
> sync issue or something else? Not sure if its appropriate to try out
> https://github.com/blp/ovs-reviews/commits/raft-fixes  since it has the
> patches in review in addition to some other patches?
>
> Regards,
>
> On Thu, Nov 15, 2018 at 9:18 AM Ben Pfaff  wrote:
>
>> On Thu, Nov 08, 2018 at 04:17:03PM -0800, ramteja tadishetti wrote:
>> > I am facing trouble in graceful removal of node in a 3 Node RAFT setup.
>>
>> Thanks for the report.  I followed up on it and found a number of bugs
>> in the implementation of the "kick" request.  There is a patch series
>> out that fixes all of the bugs that I identified:
>>
>> https://patchwork.ozlabs.org/project/openvswitch/list/?series=76115
>> ___
>> discuss mailing list
>> disc...@openvswitch.org
>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>
>

-- 

*Cheers,*
*Ramteja*

*"It's the possibility of having a dream come true that makes life
interesting"*
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


Re: [ovs-discuss] Raft issues while removing a node

2018-12-13 Thread aginwala
Hi Ben:
I cannot see the patch series on the patchwork. Is it due to mail server
sync issue or something else? Not sure if its appropriate to try out
https://github.com/blp/ovs-reviews/commits/raft-fixes  since it has the
patches in review in addition to some other patches?

Regards,

On Thu, Nov 15, 2018 at 9:18 AM Ben Pfaff  wrote:

> On Thu, Nov 08, 2018 at 04:17:03PM -0800, ramteja tadishetti wrote:
> > I am facing trouble in graceful removal of node in a 3 Node RAFT setup.
>
> Thanks for the report.  I followed up on it and found a number of bugs
> in the implementation of the "kick" request.  There is a patch series
> out that fixes all of the bugs that I identified:
>
> https://patchwork.ozlabs.org/project/openvswitch/list/?series=76115
> ___
> 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


Re: [ovs-discuss] Raft issues while removing a node

2018-11-15 Thread ramteja tadishetti
Awesome, thanks!

On Thu, Nov 15, 2018, 9:17 AM Ben Pfaff  wrote:

> On Thu, Nov 08, 2018 at 04:17:03PM -0800, ramteja tadishetti wrote:
> > I am facing trouble in graceful removal of node in a 3 Node RAFT setup.
>
> Thanks for the report.  I followed up on it and found a number of bugs
> in the implementation of the "kick" request.  There is a patch series
> out that fixes all of the bugs that I identified:
>
> https://patchwork.ozlabs.org/project/openvswitch/list/?series=76115
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


Re: [ovs-discuss] Raft issues while removing a node

2018-11-15 Thread Ben Pfaff
On Thu, Nov 08, 2018 at 04:17:03PM -0800, ramteja tadishetti wrote:
> I am facing trouble in graceful removal of node in a 3 Node RAFT setup.

Thanks for the report.  I followed up on it and found a number of bugs
in the implementation of the "kick" request.  There is a patch series
out that fixes all of the bugs that I identified:
https://patchwork.ozlabs.org/project/openvswitch/list/?series=76115
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


[ovs-discuss] Raft issues while removing a node

2018-11-08 Thread ramteja tadishetti
Hi,


I am facing trouble in graceful removal of node in a 3 Node RAFT setup.



Node1 :

$ovn-ctl --db-nb-addr=10.8.49.184 --db-nb-port=6641
--db-nb-create-insecure-remote=yes --db-nb-cluster-local-proto=tcp
--db-nb-cluster-local-port=6643 --db-nb-cluster-local-addr=10.8.49.184
start_nb_ovsdb



$ovn-ctl --db-sb-addr=10.8.49.184 --db-sb-port=6642
--db-sb-create-insecure-remote=yes --db-sb-cluster-local-proto=tcp
--db-sb-cluster-local-port=6644 --db-sb-cluster-local-addr=10.8.49.184
start_sb_ovsdb



$ovn-ctl start_northd --ovn-manage-ovsdb=no --ovn-northd-nb-db="tcp:
10.8.49.184:6641,tcp:10.8.49.181:6641,tcp:10.8.49.173:6641"
--ovn-northd-sb-db="tcp:10.8.49.184:6642,tcp:10.8.49.181:6642 tcp:
10.8.49.173:6642"



Node 2:

$ovn-ctl --db-nb-addr=10.8.49.181 --db-nb-port=6641
--db-nb-create-insecure-remote=yes --db-nb-cluster-local-proto=tcp
--db-nb-cluster-local-port=6643 --db-nb-cluster-local-addr=10.8.49.181
--db-nb-cluster-remote-addr=10.8.49.184 start_nb_ovsdb





$ovn-ctl --db-sb-addr=10.8.49.181 --db-sb-port=6642
--db-sb-create-insecure-remote=yes --db-sb-cluster-local-proto=tcp
--db-sb-cluster-local-port=6644 --db-sb-cluster-local-addr=10.8.49.181
--db-sb-cluster-remote-addr=10.8.49.184 start_sb_ovsdb



Node 3:

$ovn-ctl --db-nb-addr=10.8.49.173 --db-nb-port=6641
--db-nb-create-insecure-remote=yes --db-nb-cluster-local-proto=tcp
--db-nb-cluster-local-port=6643 --db-nb-cluster-local-addr=10.8.49.173
--db-nb-cluster-remote-addr=10.8.49.184 start_nb_ovsdb



$ovn-ctl --db-sb-addr=10.8.49.173 --db-sb-port=6642
--db-sb-create-insecure-remote=yes --db-sb-cluster-local-proto=tcp
--db-sb-cluster-local-port=6644 --db-sb-cluster-local-addr=10.8.49.173
--db-sb-cluster-remote-addr=10.8.49.184 start_sb_ovsdb





Now I forcefully stopped northd on Node 1 (Either by doing ovn-central stop
service or forcefully closing the vm in which node1 is running).

 Now Node 3 was elected as leader from remaining nodes(verified by running

$ovs-appctl -t /var/run/openvswitch/ovnnb_db.ctl cluster/status
OVN_Northbound )

$ovs-appctl -t /var/run/openvswitch/ovnsb_db.ctl cluster/status
OVN_Southbound )



Now i tried to remove node using unixctl on the non-leader node.

$ovs-appctl -t /var/run/openvswitch/ovnsb_db.ctl cluster/kick
OVN_Southbound 



Ideally it should remove node1 but this removed node 2 itself from the
cluster and making the cluster unavailable.



Could you please let us know, how to do a graceful node removal from
cluster if the node becomes unavailable?


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