MAAS: Difference between revisions
Line 27: | Line 27: | ||
* Role-based access control (RBAC) | * Role-based access control (RBAC) | ||
* Hardware testing and commissioning | * Hardware testing and commissioning | ||
== Github == | |||
maas/maas: Official MAAS repository mirror (may be out of date). Development happens in Launchpad (https://git.launchpad.net/maas/). | |||
https://github.com/maas/maas | |||
<blockquote> | |||
Metal as a Service -- MAAS -- lets you treat physical servers like virtual machines in the cloud. Rather than having to manage each server individually, MAAS turns your bare metal into an elastic cloud-like resource. | |||
What does that mean in practice? Tell MAAS about the machines you want it to manage and it will boot them, check the hardware's okay, and have them waiting for when you need them. You can then pull nodes up, tear them down and redeploy them at will; just as you can with virtual machines in the cloud. | |||
When you're ready to deploy a service, MAAS gives your tool of choice (e.g. Ansible, Chef, Puppet, SALT, Juju) the nodes it needs to power that service. It's as simple as that: no need to manually provision, check and, afterwards, clean-up. As your needs change, you can easily scale services up or down. Need more power for your Hadoop cluster for a few hours? Simply tear down one of your Nova compute nodes and redeploy it to Hadoop. When you're done, it's just as easy to give the node back to Nova. | |||
MAAS is ideal where you want the flexibility of the cloud, and the hassle-free power of Juju charms, but you need to deploy to bare metal. | |||
For more information see the MAAS guide - https://maas.io/ | |||
</blockquote> | |||
== Setup MAAS == | == Setup MAAS == |
Revision as of 04:00, 4 February 2024
MAAS
MAAS | Metal as a Service https://maas.io/
Very fast server provisioning for your data centre
Self-service, remote installation of Windows, CentOS, ESXi and Ubuntu on real servers turns your data centre into a bare metal cloud.
Welcome to metal-as-a-service.
Data centre automation Your next rack is a bare metal cloud. Metal-As-A-Service (MAAS) provisioning with Windows, ESXi, Linux.
- Bare metal cloud with on-demand servers
- Remote edge cluster operations
- Infrastructure monitoring and discovery
- Ansible, Chef, Puppet, SALT, Juju integration
- Super fast install from scratch
- VMWare ESXi, Windows, CentOS, RHEL, Ubuntu
- Custom images with pre-installed apps
- Disk and network configuration
- API-driven DHCP, DNS, PXE, IPAM
- REST API for provisioning
- LDAP user authentication
- Role-based access control (RBAC)
- Hardware testing and commissioning
Github
maas/maas: Official MAAS repository mirror (may be out of date). Development happens in Launchpad (https://git.launchpad.net/maas/). https://github.com/maas/maas
Metal as a Service -- MAAS -- lets you treat physical servers like virtual machines in the cloud. Rather than having to manage each server individually, MAAS turns your bare metal into an elastic cloud-like resource.
What does that mean in practice? Tell MAAS about the machines you want it to manage and it will boot them, check the hardware's okay, and have them waiting for when you need them. You can then pull nodes up, tear them down and redeploy them at will; just as you can with virtual machines in the cloud.
When you're ready to deploy a service, MAAS gives your tool of choice (e.g. Ansible, Chef, Puppet, SALT, Juju) the nodes it needs to power that service. It's as simple as that: no need to manually provision, check and, afterwards, clean-up. As your needs change, you can easily scale services up or down. Need more power for your Hadoop cluster for a few hours? Simply tear down one of your Nova compute nodes and redeploy it to Hadoop. When you're done, it's just as easy to give the node back to Nova.
MAAS is ideal where you want the flexibility of the cloud, and the hassle-free power of Juju charms, but you need to deploy to bare metal.
For more information see the MAAS guide - https://maas.io/
Setup MAAS
Setting and using up MAAS - JOID - OPNFV Wiki - https://wiki.opnfv.org/display/joid/Setting+and+using+up+MAAS
Nodes Networking: Deploying OpenStack on MAAS 1.9+ with Juju | Ubuntu blog - https://blog.ubuntu.com/2016/01/31/nodes-networking-deploying-openstack-on-maas-1-9-with-juju
pronouncebale machine names
I understand that sabdfl specifically requested 5-character machine names in MAAS (rather than MAC or IP based names like AWS).
I'd like to make an additional request from a usability perspective... Can we please make the MAAS machine names pronounceable? It's really, really difficult to talk about machines in a cluster when the name is "kslnw" or "xpxrqm".
Here's a suggestion:
$ sudo apt-get install wamerican $ shuf -n 1 /usr/share/dict/american-english | sed 's/[^a-zA-Z]//g'
That gives much more readable, though still random, machine names. That dictionary has 100K words in it. There's also wbritish, wcanadian. See the scowl source package or http://wordlist.sourceforge.net/ for more information.
Ref: Bug #1287224 “MAAS random generated hostnames are not pronouncea...” : Bugs : MAAS - https://bugs.launchpad.net/maas/+bug/1287224
Install
MAAS | How to install MAAS https://maas.io/docs/fresh-installation-of-maas
Install 3.4 Snap
As of 2024.02.03:
sudo snap install --channel=3.4 maas