Ubuntu MAAS (Metal as a Service) VS Virtualization
Posted on 2014-07-27
I have a client that has been sold by someone on the idea of using Ubuntu MAAS (Metal as a Service) as opposed to virtualization. I'm not a MAAS expert but have lots of experience with virtualization.
Upon reviewing MAAS it seems like its use is specifically
1) If you want your OSes to be directly connected with the local hardware, unlike virtualization.
2) You can add additional servers on the fly and somehow your OSes can use those servers.
The MAAS website doesn't very clearly state the specific bullet point advantages so I was wondering if someone with experience with MAAS could elaborate on the following:
1) Can MAAS by used to live migrate OSes while they are running to other servers like virtualization?
2) By having multiple physical servers in the cluster, can any individual OS leverage the CPU/RAM/Networking performance from multiple physical servers at the same time?
3) Does MAAS provide any type of high availability? i.e. If a server goes down, can it automatically restart on another one?
4) Does MAAS support Windows OSes?
5) Are the MAAS Oses hardware independant? meaning if you have a backup of one, you can restore it to another server without having to do some "dissimilar hardware" restore?
6) How is data stored, is it to some virtual hard drive or directly to the local ext3 or ext4 filesystem or whatever MAAS uses?
I guess what I'm trying to find out with the above is: a) When would you use MAAS b) IT Administratively what advantage is it? c) What sort of high availability/redundancy resiliency does it have?
Thanks very much.