search for: xxnpry

...t > > > > > hard-coded slave names instead? > > > > > > > > > > E.g. > > > > > 1. fail slave renames > > > > > 2. rename of failover to XX automatically renames standby to XXnsby > > > > > and primary to XXnpry > > > > That wouldn't help. The time when the failover master gets renamed, the VF > > > > may not be present. > > > In this scheme if VF is not there it will be renamed immediately after registration. > > Who will be responsible to rename the slave,...

...gt; would it work if we just > > > > hard-coded slave names instead? > > > > > > > > E.g. > > > > 1. fail slave renames > > > > 2. rename of failover to XX automatically renames standby to XXnsby > > > > and primary to XXnpry > > > That wouldn't help. The time when the failover master gets renamed, the VF > > > may not be present. > > In this scheme if VF is not there it will be renamed immediately after registration. > Who will be responsible to rename the slave, the kernel? That's t...

...hard-coded slave names instead? > > > > > > > > > > > > E.g. > > > > > > 1. fail slave renames > > > > > > 2. rename of failover to XX automatically renames standby to XXnsby > > > > > > and primary to XXnpry > > > > > That wouldn't help. The time when the failover master gets renamed, the VF > > > > > may not be present. > > > > In this scheme if VF is not there it will be renamed immediately after registration. > > > Who will be responsible to ren...

Sorry for replying to this ancient thread. There was some remaining issue that I don't think the initial net_failover patch got addressed cleanly, see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268 The renaming of 'eth0' to 'ens4' fails because the udev userspace was not specifically writtten for such kernel automatic enslavement. Specifically, if it is a bond

...| | > Given renaming slaves does not work anyway: would it work if we just hard-coded slave names instead? E.g. 1. fail slave renames 2. rename of failover to XX automatically renames standby to XXnsby and primary to XXnpry -- MST

...se, especially the initial rename. > Thoughts? > > > would it work if we just > > hard-coded slave names instead? > > > > E.g. > > 1. fail slave renames > > 2. rename of failover to XX automatically renames standby to XXnsby > > and primary to XXnpry > That wouldn't help. The time when the failover master gets renamed, the VF > may not be present. In this scheme if VF is not there it will be renamed immediately after registration. > I don't like the idea to delay exposing failover master > until VF is hot plugged in (proba...

...se, especially the initial > rename. Thoughts? > > > would it work if we just > > hard-coded slave names instead? > > > > E.g. > > 1. fail slave renames > > 2. rename of failover to XX automatically renames standby to XXnsby > > and primary to XXnpry > That wouldn't help. The time when the failover master gets renamed, the > VF may not be present. I don't like the idea to delay exposing failover > master until VF is hot plugged in (probably subject to various failures) > later. What netvsc does now is wait 2 seconds (...