<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Tom,</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I think what I'm looking for here is consistency. Even using the lxd provider, you can't 'juju deploy myapp0 --to lxd:0' and 'juju deploy myapp1 --to lxd:1'; myapp0 and myapp1 will never be able to talk because the live on their respective host only subnet on each host. I think this would be a great place to make use of L3 tunnels to get from host to host. Hopefully this is what mark was hinting at :)</div><div><br>On Aug 23, 2016, at 4:32 AM, Tom Barber <<a href="mailto:tom@analytical-labs.com">tom@analytical-labs.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">James is also missing LXD Local :) Saves my dev cycles all the time and of course networking isn't an issue. I also use LXD remotely but I just run a cmd that forwards the ports I want to the host via IPTables so they are exposed to the wide world. Of course its a manual step, but I find it very useful.<div><br></div><div>Tom</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">--------------<div><br></div><div><div style="font-size:small"><font color="#999999">Director Meteorite.bi - Saiku Analytics Founder</font></div><div style="font-size:small"><font color="#999999">Tel: +44(0)5603641316 </font></div><div style="font-size:small"><font color="#999999"><br></font></div><div style="font-size:small"><font color="#999999">(Thanks to the Saiku community we reached our <a href="http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/" target="_blank">Kickstart</a> goal, but you can always help by <a href="http://www.meteorite.bi/products/saiku/sponsorship" target="_blank">sponsoring the project</a>)</font></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On 23 August 2016 at 12:29, Mark Shuttleworth <span dir="ltr"><<a href="mailto:mark@ubuntu.com" target="_blank">mark@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div><br>
LXC/LXD should work everywhere, but *networking* to those
containers is tricky. There is a dedicated team working on that
problem, and we expect to ahve the ability to make and use LXC
containers universally, soon.<br>
<br>
The remaining constraint will be that some charms try to modify
their guest kernel, and that of course will be prevented in a
container.<span class="HOEnZb"><font color="#888888"><br>
<br>
Mark</font></span><div><div class="h5"><br>
<br>
On 22/08/16 22:03, James Beedy wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">Team,
<div><br>
</div>
<div>Question: What providers can Juju deploy LXD to?<br>
</div>
<div><br>
</div>
<div>Answer: All of them.</div>
<div><br>
</div>
<div>Question: What providers support Juju deployed LXD (juju
deploy <application> --to lxd:0)?</div>
<div><br>
</div>
<div>Answer: MAAS</div>
<div><br>
</div>
<div><br>
</div>
<div>Problem: Juju can deploy LXD to all of the providers, but
Juju can **REALLY** only provision LXD on MAAS. I get the
impression that Juju is broken when I deploy applications to
lxd on any provider other than MAAS.</div>
<div><br>
</div>
<div>Proposed Solution: Disable `juju deploy <application>
--to lxd:0` on providers which it is not supported.</div>
<div><br>
</div>
<div><br>
</div>
<div>Thoughts?</div>
</div>
<br>
<fieldset></fieldset>
<br>
</blockquote>
<p><br>
</p>
</div></div></div>
<br>--<br>
Juju mailing list<br>
<a href="mailto:Juju@lists.ubuntu.com">Juju@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju" rel="noreferrer" target="_blank">https://lists.ubuntu.com/<wbr>mailman/listinfo/juju</a><br>
<br></blockquote></div><br></div>
</div></blockquote></body></html>