Konstantinos Tsakalozos
on 19 October 2017
This article originally appeared on Konstantinos Tsakalozos' blog
When was the last time you had one of those “I wish I knew about that <time period> ago” moments? One of mine was when I saw MAAS (Metal as a Service). Back at the University, as a member of the MADgIK lab, I had to administer a couple of racks. These were the days of Xen paravirtualization, Eucaliptus and the GRID. Interesting times, but I now realise that if I had MAAS and Juju back then, I would have finished with that adventure a couple of years sooner!
From a high level MAAS will render your physical cluster into an IaaS cloud that provisions physical instead of virtual machines. As you might expect a PXE server will serve the images you ask via a good looking web UI. MAAS will discover what is on your network and make it dead simple to set VLANs and network spaces. Juju can use your MaaS deployment as if it were a cloud. This enables you to deploy OpenStack, Kubernetes and BigData solutions directly onto your hardware. It is a really powerful combination that can save you time (in the range of years in my case).
Lets do it!
Do not waste any more time on this blog, go and try MAAS on QEMU instances on your own machine. This play list will get you started. At the end you will have a (virtual) cluster on QEMU. One of the machines will act as the MAAS controller, the rest will be the cluster nodes.
Next step is to use MAAS from Juju.
Conclusion
I am off to the shop to get more RAM. No wonder this is such a short blog.
Resources
- MAAS — https://maas.io/
- MADgIK — http://www.madgik.di.uoa.gr/
- Juju — https://jujucharms.com/store
- MAAS on QEMU — https://www.youtube.com/playlist?list=PLvn2jxYHUxFlxNmc1dAbw524aoPmHxNpC
- Juju on MAAS — https://jujucharms.com/docs/2.1/clouds-maas
