0

I am trying to deploy openstack base bundle with juju/maas. as described in this blog http://blog.naydenov.net/2015/11/deploying-openstack-on-maas-1-9-with-juju-network-setup/

please check below from my test and advise what is wrong?

all the the lxd machines that juju create are down with this error:

cannot start instance for machine "2/lxd/2": acquiring LXD image: no matching image found

juju debug-log has these errors related to DNS which I think is the cause to my problem:

machine-1: 09:39:24 WARNING juju.provisioner no name servers supplied by provider, using host's name servers.
machine-1: 09:39:24 WARNING juju.provisioner no search domains supplied by provider, using host's search domains.
machine-1: 09:39:24 WARNING juju.provisioner incomplete DNS config found, discovering host's DNS config
machine-0: 09:39:43 WARNING juju.provisioner failed to start machine 0/lxd/2 (acquiring LXD image: no matching image found), retrying in 10s (7 more attempts)

below is my environment:

juju version: 2.5.4-bionic-amd64

MAAS version: 2.5.2

openstack nodes are VMs on ESXi6.5 and all vSwitch were configured to allow Allow promiscuous mode, forged transmits and MAC changes.

maas network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto ens34
iface ens34 inet static
        address 10.205.58.28
        netmask 255.255.255.224
        network 10.205.58.0
        broadcast 10.205.58.31
#        gateway 10.205.58.30
#        dns-nameservers 10.205.58.28
        dns-search maas

auto ens33
iface ens33 inet static
        address 172.1.1.28
        netmask 255.255.255.0
        network 172.1.1.0
        broadcast 172.1.1.255
        gateway 172.1.1.27
        dns-nameservers 8.8.8.8
        dns-search maas

# for Admin-api
auto ens37
iface ens37 inet static
        address 192.168.10.1
        netmask 255.255.255.0
        network 192.168.10.0
        broadcast 192.168.10.255
#        gateway 192.168.10.2
        dns-nameservers 192.168.10.1
        dns-search maas
#       post-up iptables -t nat -A POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28
#       post-down iptables -t nat -D POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28

# for Compute-external
auto ens38
iface ens38 inet static
        address 192.168.40.1
        netmask 255.255.255.0
        network 192.168.40.0
        broadcast 192.168.10.255
#        gateway 192.168.40.2
        dns-nameservers 192.168.40.1
        dns-search maas
#        post-up iptables -t nat -A POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28
#        post-down iptables -t nat -D POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28


# for Compute-data
auto ens39
iface ens39 inet static
        address 192.168.50.1
        netmask 255.255.255.0
        network 192.168.50.0
        broadcast 192.168.50.255
#        gateway 192.168.50.2
        dns-nameservers 192.168.50.1
        dns-search maas
#        post-up iptables -t nat -A POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28
#        post-down iptables -t nat -D POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28

# for Storage-cluster
auto ens40
iface ens40 inet static
        address 192.168.70.1
        netmask 255.255.255.0
        network 192.168.70.0
        broadcast 192.168.70.255
#        gateway 192.168.50.2
        dns-nameservers 192.168.70.1
        dns-search maas
#        post-up iptables -t nat -A POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28
#        post-down iptables -t nat -D POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28

# for Storage-data
auto ens41
iface ens41 inet static
        address 192.168.60.1
        netmask 255.255.255.0
        network 192.168.60.0
        broadcast 192.168.60.255
#        gateway 192.168.50.2
        dns-nameservers 192.168.60.1
        dns-search maas
#        post-up iptables -t nat -A POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28
#        post-down iptables -t nat -D POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28

# for Public-api
auto ens42
iface ens42 inet static
        address 192.168.30.1
        netmask 255.255.255.0
        network 192.168.30.0
        broadcast 192.168.30.255
#        gateway 192.168.50.2
        dns-nameservers 192.168.30.1
        dns-search maas
#        post-up iptables -t nat -A POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28
#        post-down iptables -t nat -D POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28

# for Internal-api
auto ens43
iface ens43 inet static
        address 192.168.20.1
        netmask 255.255.255.0
        network 192.168.20.0
        broadcast 192.168.20.255
#        gateway 192.168.50.2
        dns-nameservers 192.168.20.1
        dns-search maas
#        post-up iptables -t nat -A POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28
#        post-down iptables -t nat -D POSTROUTING -o ens33 -j SNAT --to-source 172.1.1.28


up route add -net 10.32.245.0 netmask 255.255.255.0 gw 10.205.58.1

and below is the description for each fabric from MAAS GUI: maas fabrics

it seems from maas GUI for each machine that the containers were assigned IP address from corresponding space: containers from maas gui

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.