+------------------------------------------------------------------------------ | On 2015-12-08 17:17:09, George Mamalakis wrote: | > The lower the level the better. For example, FiFo's "solution" with LeoFS > is very close to what we need (even though it's not at the hypervisor's > level), but the problem with it needs us to set the redundancy > configuration during the design phase which is somewhat difficult for us, > since our setup is expected to grow. As I stated in my original email, I > haven't found the SDC's section on how to accomplish high availability, so > that's what I'm trying to understand through this list.
qemu in illumos/SmartOS does not support live migration. Nor do we have live migration with zones (as does Solaris 11.) The abstraction for HA in SmartOS is assumed to be higher up -- at the app level. You should be architecting your aps in such a way they are resilient to the loss of a zone/VM _and_ a physical node. SDC itself has HA components, but still assumes you are implementing a load balancing tier (which you can run on your compute fleet) for pieces of it. https://docs.joyent.com/private-cloud/resilience > Which means that the boot order is random? Or do they start based on when > they were created (eg. older first)? They all effectively boot at once, see /lib/svc/method/svc-zones. If your apps require boot time orchestration, use something like ZK/Consul/etcd (or whatever you prefer) to manage that. Cheers. -- bdha ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
