Well, everything you want to do here is cleanly possible with MAAS, Juju
and LXD, but you will need to dig into the tools and understand how the
model in Juju describes machines and networking.

Last, there is a particular set of gotchas around networking (which as
you point out is the tricky part in general) with containers. This is a
development focus in Juju currently and we hope to have a crisp "just
works" story for MAAS and some public clouds by 2.3.0. Till then you
will need to be something of an expert, but if you figure that out, it's
amazing what is possible.


On 08/08/17 11:06, Muhammad Yousuf Khan wrote:
> Thank you very much for the understanding right Mark. yes you are
> connect i was doing that however on your advice i manage to install it
> on new VM now one step is clear. but the problem is i notice. LXD is
> creating its own subnet and hide the guest behind the NAT. now the
> problem is how can LAN computers see LXD containers behind NAT. can't
> we use it the way we use it in bridge style. where it get the IP from
> LAN DHCP? instead of hiding behind NAT?
> in the context of same case. the whole idea deploying services like
> mysql, kyenotes any others will be fail as all the services will be
> behind NAT how come openstack services will integrate each other.
> Any knowledge sharing and tip will be highly appreciated.
> Thank,
> On Tue, Aug 8, 2017 at 1:07 PM, Mark Shuttleworth <m...@ubuntu.com
> <mailto:m...@ubuntu.com>> wrote:
>     On 08/08/17 08:31, Ante Karamatić wrote:
>>     If you want to run LXD on the same host where bind is running,
>>     you just have to configure bind to *not* listen on LXD network:
>> https://www.cyberciti.biz/faq/unix-linux-bsd-bind-dns-listenon-configuration/
>> <https://www.cyberciti.biz/faq/unix-linux-bsd-bind-dns-listenon-configuration/>
>>     uto, 8. kol 2017. 09:04 Muhammad Yousuf Khan <sir...@gmail.com
>>     <mailto:sir...@gmail.com>> je napisao:
>>         Thanks for the update Ante. but since MAAS also used Bind for
>>         its own DNS resolution. how come one can use juju or lxd in
>>         absence of bind. 
>>         any tip will be highly appreciated.
>>         Thanks,
>>         MYK
>     MYK, if I understand your problem, you are running a MAAS
>     controller on the VM (which means bind is running) and you want to
>     bootstrap a LXD localhost Juju controller on that same machine.
>     The question is why you need to bootstrap a local Juju on a MAAS
>     controller?
>     As Ante says, you can configure the MAAS bind to avoid grabbing
>     the lxd network interfaces, which ill allow LXD's dnsmasq to work
>     alongside bind (because bind is focused on the main network
>     interfaces, and dnsmasq is grabbing the lxd network interfaces).
>     But that's fiddly, you would need to look carefully over the bind
>     config files and make sure you don't inadvertently break MAAS. If
>     you are not familiar with bind configuration, I don't recommend
>     this approach.
>     The easy answer is just to create a separate VM that points
>     resolv.conf at the MAAS DNS server, and bootstrap Juju locally in
>     that VM. You can even IIRC use MAAS to create that new VM, using
>     the 'pod' functionality in 2.2.
>     Mark

Juju mailing list
Modify settings or unsubscribe at: 

Reply via email to