On 13.07.15 15:35, Stefan Andres wrote: > Hi, > https://techwiki.juniper.net/Documentation/Contrail/Contrail_Controller_Feature_Guide/Configuration/50_Juniper_OpenStack_High_Availability > says 'A highly available deployment of Contrail requires at least two > control nodes, three config nodes (including analytics and webui) and > three database nodes.' > > Though what we discover when running 3 contrail-control daemons (on > three server) is: > > - vrouter connects to only 2 (always different, so sometimes on A && B, > sometimes A && C and sometimes B && C) > > When doing so we also experience network unavailability on some compute > nodes: > > 513752 10.0.80.11:22 X.X.X.X:56149 6 (1) > (K(nh):27, Action:D(NoSrcRt), S(nh):27, Statistics:0/0 UdpSrcPort > 63529) > > or > > 252404 10.0.80.1:53 10.0.80.11:53119 17 (1) > (K(nh):28, Action:F, S(nh):4, Statistics:0/0 UdpSrcPort 64509) > > > When stopping the third contrail-control daemon everything seems to work > fine again. > > Is it architectually possible to run more than 2 contrail-control nodes? > > Regards, > Stefan >
Hello, can someone point us in the right direction? Regards, Stefan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
