- Getting Started
- Amazon Web Service
- Windows Azure
- HP Public Cloud
- Online Labs
- MAAS (bare metal)
- Manual Provisioning
- General config options
- Testing your setup
- Using Juju
- Deploying Services
- Using constraints
- Service Configuration
- Service Relationships
- Exposing Services
- Scaling Services
- Groups of Services
- Destroying Services
- Managing environments
- Charm High Availability
- Juju High Availability
- Using bundles
- Working with Units
- Working with Actions
- How to...
- Deploy a Node.js app
- Test and deploy on Rails
- Backup and Restore
- Manage Juju with the GUI
- Set up a Private Cloud
- Configure Proxy Access
- Deploy charms offline
- Vagrant Workflow
- Manage Authorised Keys
- Getting started
- Components of a charm
- /actions and actions.yaml
- Charm walkthrough
- How hooks are run
- Relations lifecycle
- Implementing relations
- Hook Errors
- Hook Debugging
- Hook Debugging with DHX
- Subordinate services
- Implicit Relations
- Charm Testing
- The Juju Charm Store
- Submit a charm
- Charm store policy
- Charm review process
- Best practices
- Charm Feature Rating
- Charm Icons
Metal As A Service is software which allows you to deal with physical hardware just as easily as virtual nodes. 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. Specifically, MAAS allows for services to be deployed to bare metal via Juju. For more information about MAAS, see maas.ubuntu.com
To enable Juju to work with MAAS, you should start by generating a generic configuration file using the command:
This will generate a file,
environments.yaml, which will live in your
~/.juju/ directory (and will create the directory if it doesn't already
Note: If you have an existing configuration, you can use
juju generate-config --show to output the new config file, then copy and
paste relevant areas in a text editor etc.
You'll need an API key from MAAS so that the Juju client can access it. Each user account in MAAS can have as many API keys as desired. One hard and fast rule is that you'll need to use a different API key for each Juju environment you set up within a single MAAS cluster.
To get the API key:
- Go to your MAAS preferences page, or go to your MAAS home page and choose Preferences from the drop-down menu that appears when clicking your username at the top-right of the page.
- Optionally add a new MAAS key. Do this if you're setting up another environment within the same MAAS cluster.
- Copy the key value - you will need it shortly!
Create or modify
~/.juju/environments.yaml with the following content: Create
or modify ~/.juju/environments.yaml with the following content:
maas: type: maas maas-server: 'http://<my-maas-server>:80/MAAS' maas-oauth: 'MAAS-API-KEY'
Substitute the API key from earlier into the
MAAS_API_KEY slot. You may need
to modify the
my-maas-server setting too; if you're running from the maas
package it should be something like "http://hostname.xxxx.yyy/MAAS".
It is also useful to add your SSH keys to the configuration, as then MAAS will be able to automatically add them to each unit. This may be done simply by adding the following option to the config:
...or point to any other appropriate key file.
An admin password will be generated when you try and bootstrap the Juju instance. you can specify this explicitly in the configuration if you like:
The default series for MAAS will automatically be set to 'precise'. You can override this setting by adding the optional configuration:
Juju automatically detects MAAS networks, and recognises physical and
virtual networks on each machine.
juju status will show the discovered networks. See
Juju Constraints and
Deploying Services to learn how to select machines
with networks and enable the networks for use.
There is one case where an additional configuration option should be made: when MAAS is managing the bridge and bringing networks up and down, set the "disable-network-management" option in environments.yaml to "true":
This tells Juju not to create a network bridge or to bring eth0 up and down during the cloud-init install phase. Juju will not make changes to the network configuration when its agents start.
Juju recognises MAAS-controlled hostnames. You can use the hostname when bootstrapping the state-server on a specific machine and add existing MAAS-controlled machines to the juju environment. For example:
juju bootstrap --to <hostname> juju add-machine <hostname>
For further steps with Juju on MAAS, you should check out the Juju instructions in the MAAS documentation
You should also refer to the section on general configuration options for additional and advanced customization of your environment.