MAAS Region Controller

Here’s a quick tutorial to get you comfortable with the MAAS Operator Charm.

1. First, create some environment variables to facilitate this tutorial:

    # LaunchPad ID
    export LP_ID="my-lp-id"
    export MAAS_REGION_CHARM=./maas-region-charm/maas-region_ubuntu-22.04-amd64.charm
    export MAAS_AGENT_CHARM=./maas-agent-charm/maas-agent_ubuntu-22.04-amd64.charm

2. Install the base packages:

    sudo snap install juju
    sudo snap install lxd
    sudo snap install charmcraft --classic

3. Initialize Juju:

    # The actual command doesn't matter, just run juju once
    juju whoami

4. Create a managed LXD network as a control plane:

    lxc network create jujulab
    lxc network edit jujulab <<EOF
    name: jujulab
    description: "Juju lab network"
    type: bridge
    config:
      dns.domain: juju-lab
      ipv4.address: 10.70.0.1/24
      ipv4.dhcp: "true"
      ipv4.dhcp.ranges: 10.70.0.65-10.70.0.126
      ipv4.nat: "true"
      ipv6.address: none
    EOF

5. Integrate this lab network with the host’s DNS service:

    resolvectl dns jujulab 10.70.0.1
    resolvectl domain jujulab '~juju-lab'

6. Make this integration persistent (optional, but highly recommended):

    cat <<EOF | sudo tee /etc/systemd/system/lxd-dns-net-juju.service
    [Unit]
    Description=LXD per-link DNS configuration for jujulab
    BindsTo=sys-subsystem-net-devices-jujulab.device
    After=sys-subsystem-net-devices-jujulab.device

    [Service]
    Type=oneshot
    ExecStart=/usr/bin/resolvectl dns jujulab 10.70.0.1
    ExecStart=/usr/bin/resolvectl domain jujulab '~juju-lab'
    ExecStopPost=/usr/bin/resolvectl revert jujulab
    RemainAfterExit=yes

    [Install]
    WantedBy=sys-subsystem-net-devices-jujulab.device
    EOF

    sudo systemctl daemon-reload
    sudo systemctl enable --now lxd-dns-net-juju

7. Create an unmanaged network for Devices-Under-Test (DUT):

    lxc network create jujudata
    lxc network edit jujudata <<EOF
    name: jujudata
    description: "Juju test network"
    type: bridge
    config:
      dns.domain: jujudata
      ipv4.address: 10.70.1.1/24
      ipv4.dhcp: "false"
      ipv4.nat: "false"
      ipv6.address: none
    EOF

8. Create a LXD project to isolate the lab:

   We don’t need a Separate set of images for the project, so we disable it to save some disk space and download time.

    lxc project create juju-lab -c features.images=false
    lxc project switch juju-lab

9. Create a profile for Juju controllers:

    lxc profile create juju-host
    lxc profile edit juju-host <<EOF
    name: juju-host
    description: Juju host
    config:
        limits.cpu: 2
        limits.memory: 4GB
        user.user-data: |
            #cloud-config
            ssh_authorized_keys:
            - $(cat ${HOME}/.ssh/id_rsa.pub | cut -d' ' -f1-2)
            - $(cat ${HOME}/.local/share/juju/ssh/juju_id_rsa.pub | cut -d' ' -f1-2)
    devices:
        eth0:
            type: nic
            name: eth0
            network: jujulab
        eth1:
            type: nic
            name: eth1
            network: jujudata
        root:
            path: /
            pool: default
            type: disk
    EOF

10. Create a profile for devices under test:

    lxc profile create juju-dut
    lxc profile edit juju-dut <<EOF
    name: juju-dut
    description: Juju lab DUT
    devices:
        eth0:
            type: nic
            name: eth0
            network: jujudata
        root:
            path: /
            pool: default
            type: disk
    EOF

11. Create a few VMs:

    for h in $(seq 1 3); do \
        lxc launch ubuntu:jammy "m$h" --vm -p juju-host;\
    done;\
    sleep 5;\
    for h in $(seq 1 3); do \
        lxc exec "m$h" -- cloud-init status --wait;\
        ssh-keyscan -H "m$h.juju-lab" >> ~/.ssh/known_hosts;\
    done

12. Bootstrap the Juju controller:

    cat >| maas-bootstrap.yaml <<EOF
    clouds:
        maas-bootstrap:
            type: manual
            endpoint: ubuntu@m1.juju-lab
            regions:
                default: {}
    EOF

    juju add-cloud maas-bootstrap ./maas-bootstrap.yaml
    juju bootstrap maas-bootstrap maas-controller
    juju add-machine -m controller ssh:ubuntu@m2.juju-lab
    juju add-machine -m controller ssh:ubuntu@m3.juju-lab
    juju enable-ha -n 3 --to 1,2
    juju controllers --refresh

13. Deploy a PostgreSQL DB using the charm:

    juju deploy -m controller postgresql --channel 14/stable --series jammy --to 0
    juju add-unit -m controller postgresql -n 2 --to 1,2

14. Deploy HAProxy using the charm:

    juju deploy -m controller haproxy --series jammy --to 0
    juju add-unit -m controller haproxy -n 2 --to 1,2

15. Deploy a MAAS region controller using the charm:

    juju deploy -m controller ${MAAS_REGION_CHARM} --to 0
    juju status --watch 10s  # wait for it to initialize

16. Instruct Juju to consume offers:

    juju integrate -m controller maas-region postgresql
    juju integrate -m controller maas-region haproxy
    juju status --watch 10s  # wait for it to settle

17. Create a MAAS admin user:

    juju run -m controller maas-region/leader create-admin username=maas password=maas email=maas@example.com ssh-import=lp:${LP_ID}

18. Deploy a rack controller (“MAAS agent” using the charm:

    juju deploy -m controller ${MAAS_AGENT_CHARM} --to 1
    juju integrate -m controller maas-agent maas-region
    juju add-unit -m controller maas-agent --to 2

19. Get the MAAS URL, so you can access the MAAS instance:

    juju run -m controller maas-region/leader get-api-endpoint

That’s all there is to it! Now you can explore your lab MAAS instance, created with the MAAS Operator Charm.