“Maas and Juju on LXD and ZFS – part 3/4”



In order to setup Juju we need to make some steps and requirements:

  • Creating a New Model in JUJU

check the list of our LXC container

$: lxc list
|      NAME      |  STATE  |        IPV4        | IPV6 |    TYPE    | SNAPSHOTS |
| xenial-juju    | RUNNING | (eth0) |      | PERSISTENT | 0         |
| xenial-maas    | RUNNING | (eth0) |      | PERSISTENT | 0         |

Once the container is running, on hosts file of VM Host we need to add the following lines to resolve hosts names

$: sudo nano /etc/hosts

then adding these lines

#Ubuntu 16.04Lts LXD-ZFS with MAAS & JUJU - Bridge     lxd

#Container for Ubuntu MAAS     xenial-maas
#Container for Ubuntu JUJU     xenial-juju
#Container fo vNodes     xenial-vnode00


see this link to understand the model in JUJU


first check our controller

$: juju list-controllers --refresh

Controller    Model  User   Access     Cloud/Region         Models  Machines    HA  Version
xenial-juju*  -      admin  superuser  localhost/localhost       2         1  none  2.0.1

now we can either to create a new model or use the default

$: juju add-model jujulab

that command to view the list

$: juju list-models

Controller: xenial-juju
Model       Cloud/Region   Status     Machines  Cores  Access  Last connection
controller  lxd/localhost  available         1      -  admin   just now
default     lxd/localhost  available         0      -  admin   1 minute ago
jujulab*    lxd/localhost  available         0      -  admin   never connected

we can see that also on its gui

Screen Shot 2017-02-07 at 15.23.12.png

to see the status

$: juju status

Model    Controller   Cloud/Region         Version
jujulab  xenial-juju  localhost/localhost  2.0.1
App  Version  Status  Scale  Charm  Store  Rev  OS  Notes
Unit  Workload  Agent  Machine  Public address  Ports  Message
Machine  State  DNS  Inst id  Series  AZ

the third part is done.

<- part 2/4 . part 4/4 ->

“cya to the next 1…. Njoy !”
bye dakj

Disclaimer: All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.

“We learn from our mistakes”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.