Heinz,
If I remember correctly VMS, one version of Linux from long long ago
(scrolling credits, let the razing commence) and some others supported
process migration.
Is this "still a thing" now-a-days?
George,
I think it may behoove you to explain the problem domain is so folks can
point the right way.
I can say I there is Mesos : http://mesos.apache.org/ which (I think)
maybe combined with KVMs (one day LX-zone maybe?) to get what you want done.
I just know it exists.
Merry Yule!
-Will
On 12/28/15 3:17 PM, Heinz Nikolaus Gies wrote:
Hi Gorge some clarification on how FiFo / LeoFS works work. It does not offer
what I think you understand as HA. There is no hot migration / life migration.
It offers you the option to make a backup of your zone to LeoFS (including
incremental backups) and in the case of a catastrophic failure re-deploy on a
different hypervisor. Memory/CPU state is not migrated, nor is any disk state
since the last backup.
Regarding the question of the replica. What you need to define is the number of
replica, not the number of nodes, you always can add nodes what you can’t
change is the number of copies of each file that are kept - wich is referred to
as replica. A usually decent guess is having 3 replica, it is the ‘accepted
standard’ I think, and unless you know you need more or don’t care for your
data and want less there is not much reason to go with a different number.
Cheers,
Heinz
On Dec 8, 2015, at 16:17, George Mamalakis <[email protected]> wrote:
Hi Nahum,
And thanks for your clarifications.
On 08/12/2015 05:06 μμ, Nahum Shalman wrote:
On 12/08/2015 09:52 AM, George Mamalakis wrote:
I've read that SmartOS supports live migration and high availability through
Quemu using SmartDataCenter
Where? That is not accurate information and needs to be corrected. With SmartOS
and SmartDataCenter you should be implementing high availability at the
application layer, not the hypervisor layer. If live migration is a hard
requirement then SmartOS/SDC/FiFo are not the correct solution for you.
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.
Some more requirements I was given by my team involve configurable VM boot order
Also not a feature of SmartOS / SDC.
Which means that the boot order is random? Or do they start based on when they
were created (eg. older first)?
Thanks again for the help!
George.
--
George Mamalakis
IT and Security Officer,
Electrical and Computer Engineer (Aristotle Univ. of Thessaloniki),
PhD (Aristotle Univ. of Thessaloniki),
MSc (Imperial College of London)
School of Electrical and Computer Engineering
Aristotle University of Thessaloniki
phone number : +30 (2310) 994379
-------------------------------------------
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
