in NSO HA (tailf-hcc), failover-master template isn't applied
I'm testing the NSO HA - BGP Anycast (L3) method, everything works as explained in the tailf_hcc.pdf except failover-master.
The SLAVE moves to MASTER, not to FAILOVERMASTER, and the failover-master templates is not applied to slave's quagga device, even the master template is not applied!!!! only the state is changed.
(please find attached log for the details)
Actually, I looked over the tailf-hcc package code and there's no FAILOVER-MASTER state in the HaStateType definition.. there are only NONE, SLAVE, MASTER, SLAVE_RELAY... How can a node move to FAILOVER-MASTER state?
Please guide me to right direction!
the configurations are following..
root@ncs# show running-config ha ha token kilskils ha local-user root ha interval 3 ha failure-limit 3 ha bgp failure-limit 3 ha bgp anycast-prefix 18.104.22.168/32 ha bgp anycast-path-min 1 ha bgp clear-enabled true ha member nso-2nd address 192.168.124.210 default-ha-role slave failover-master true quagga-device nso-2nd ! ha member nso-kils address 192.168.124.209 default-ha-role master quagga-device nso-kils !
Step 1 : configure debug server in Pycharm
Go to Run => Edit Configurations, click on "+" => Python Remote Debug
In "Local Host name " enter ip or host name of your local machine. Enter a available port in "Port :"
Give a name, here it's "NSO debug...
Abstract: RFM services can be hard to implement. Especially the lifecycle management of the delete case of the service can be a challenge. Nano Services uses an executable plan and kickers to supports the full lifecycle of a RFM service.
Previous instalments of this blog post series have covered requirements (parts I and II) and baselining, profiling/optimising and monitoring (part III). In this final part we will discuss some architectures you may want to consider as your system grows in...
In part I and part II of this blog, we have been discussing scale and performance requirements. In this third instalment we are going to look at baselining, profiling, optimising and monitoring scale and performance.
Baselining Scale and Perfo...
In part I of our Unlocking Performance in your NSO System blog we started discussing scale and performance requirements, including
Size of device configuration
Number of service instances
Frequency of operation