similar to: ATA failover between datacenters

Hello all, I am looking to run only 1 VM on this setup, don''t need to do live migration, although that would be nice, I just want to protect against hardware and datacenter/network failure. The VM is lightly loaded, not much disk I/O or CPU load. I have two machines, each one with 2 x SATA 250GB, and 1 SSD 128GB. (There is a simple RAID-1 SATA hardware controller on board). I am

I think RR DNS is the only viable solution under these circumstances. If you can cope with the fact that failovers won't be seamless, I don't think there's anything wrong with that though. On 07/21/2015 11:54 AM, Laz C. Peterson wrote: > The consensus seems to say no to RR DNS ? I am going to take that into serious consideration. > > With this proxy setup you describe, what

Hello, Assuming we have two (low traffic) servers (on different data centers) replicated using dsync, what is the best way to automatically direct users to the main server when it is up and to the redundant one when the main server is down? Using DNS? I've seen that DNS-based failover has generally issues (for example:

On Thu, Apr 19, 2018 at 06:42:02PM -0700, Sridhar Samudrala wrote: > +#if IS_ENABLED(CONFIG_NET_FAILOVER) > + > +int failover_create(struct net_device *standby_dev, > + struct failover **pfailover); Should we rename all these structs net_failover? It's possible to extend the concept to storage I think. > +void failover_destroy(struct failover *failover); > + > +int

Round-robin DNS last I checked can be fraught with issues. While doing something else I came up with this idea: Clients --> Load Balancer(HAProxy) --> Dovecot Proxy(DP) --> Dovecot Director(DD) --> MS1 / MS2. When DP checks say user100 it'll find a host=DD-POD1 that returns two IPs, those of the two DD that sit in front of POD1. This DD pair is the only pair in the ring and

Hi, I use dovecot for a long time now, but only as a single isolated server each time. I joined a company a few years back. We had trouble with compagnies hosting our mail, supposedly full redundant and so on. The company is small, but we have many dealers around the world, and it's growing. Mail became the fist choice for clients to contact the dealers. No mail, and we loose sales. For

On Mon, 7 May 2018 15:10:44 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > This provides a generic interface for paravirtual drivers to listen > for netdev register/unregister/link change events from pci ethernet > devices with the same MAC and takeover their datapath. The notifier and > event handling code is based on the existing netvsc implementation. >

On Tue, 26 Mar 2019 19:48:13 -0400 Si-Wei Liu <si-wei.liu at oracle.com> wrote: > When a netdev appears through hot plug then gets enslaved by a failover > master that is already up and running, the slave will be opened > right away after getting enslaved. Today there's a race that userspace > (udev) may fail to rename the slave if the kernel (net_failover) > opens the

On Tue, 26 Mar 2019 19:48:13 -0400 Si-Wei Liu <si-wei.liu at oracle.com> wrote: > When a netdev appears through hot plug then gets enslaved by a failover > master that is already up and running, the slave will be opened > right away after getting enslaved. Today there's a race that userspace > (udev) may fail to rename the slave if the kernel (net_failover) > opens the

On Mon, 7 May 2018 15:10:44 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > +static struct net_device *net_failover_get_bymac(u8 *mac, > + struct net_failover_ops **ops) > +{ > + struct net_device *failover_dev; > + struct net_failover *failover; > + > + spin_lock(&net_failover_lock); > + list_for_each_entry(failover,

On Mon, 7 May 2018 15:10:44 -0700 Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > +static struct net_device *net_failover_get_bymac(u8 *mac, > + struct net_failover_ops **ops) > +{ > + struct net_device *failover_dev; > + struct net_failover *failover; > + > + spin_lock(&net_failover_lock); > + list_for_each_entry(failover,

On Wed, May 02, 2018 at 10:51:12AM -0700, Samudrala, Sridhar wrote: > > > On 5/2/2018 9:15 AM, Jiri Pirko wrote: > > Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: > > > Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: > > [...] > > > > > > > > + > > > > + err =

Hi all, We're running gpfs 3.5.0.12 (5 total nsds & quorum servers, 2 nsds running samba), sernet-samba 4.1.4-7, and ctdb 1.0.114.7-1 and trying to get transparent failover to work from a windows 8 client. We have ctdb failover working, i.e. if I run mmshutdown on one of the nodes the IPs failover in a few seconds after the GPFS mount is unmounted. For our transparent failover test, I

Sat, May 26, 2018 at 09:22:18AM CEST, sridhar.samudrala at intel.com wrote: >On 5/25/2018 4:28 PM, Stephen Hemminger wrote: >> On Fri, 25 May 2018 16:11:47 -0700 >> "Samudrala, Sridhar" <sridhar.samudrala at intel.com> wrote: >> >> > On 5/25/2018 3:34 PM, Stephen Hemminger wrote: >> > > On Thu, 24 May 2018 09:55:14 -0700 >> > >

On Wed, Apr 03, 2019 at 12:52:47AM -0400, Si-Wei Liu wrote: > When a netdev appears through hot plug then gets enslaved by a failover > master that is already up and running, the slave will be opened > right away after getting enslaved. Today there's a race that userspace > (udev) may fail to rename the slave if the kernel (net_failover) > opens the slave earlier than when the

On Wed, Apr 03, 2019 at 12:52:47AM -0400, Si-Wei Liu wrote: > When a netdev appears through hot plug then gets enslaved by a failover > master that is already up and running, the slave will be opened > right away after getting enslaved. Today there's a race that userspace > (udev) may fail to rename the slave if the kernel (net_failover) > opens the slave earlier than when the

Il 16/07/20 12:40, Gerald Galster ha scritto: >> Some missing infos... >> >> - As load balancer I'm using a pair of keepalived with simple setup and >> not the DNS >> - Load balancer algorithm is "Weighted Least-Connection" >> - About 20 domains and 3000 email >> - I'm monitoring my backend servers with poolmon >> - The backend

On Fri, 25 May 2018 16:11:47 -0700 "Samudrala, Sridhar" <sridhar.samudrala at intel.com> wrote: > On 5/25/2018 3:34 PM, Stephen Hemminger wrote: > > On Thu, 24 May 2018 09:55:14 -0700 > > Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > > > >> --- a/drivers/net/hyperv/Kconfig > >> +++ b/drivers/net/hyperv/Kconfig >

On Fri, 25 May 2018 16:11:47 -0700 "Samudrala, Sridhar" <sridhar.samudrala at intel.com> wrote: > On 5/25/2018 3:34 PM, Stephen Hemminger wrote: > > On Thu, 24 May 2018 09:55:14 -0700 > > Sridhar Samudrala <sridhar.samudrala at intel.com> wrote: > > > >> --- a/drivers/net/hyperv/Kconfig > >> +++ b/drivers/net/hyperv/Kconfig >

> On 19 Mar 2019, at 23:19, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Tue, Mar 19, 2019 at 08:46:47AM -0700, Stephen Hemminger wrote: >> On Tue, 19 Mar 2019 14:38:06 +0200 >> Liran Alon <liran.alon at oracle.com> wrote: >> >>> b.3) cloud-init: If configured to perform network-configuration, it attempts to configure all available netdevs.