<div dir="ltr">So I checked and not only is it regressed, it was intentionally removed on purpose because while it worked in some cases it did broke user expectations in other cases. The work to enable the Fan is the path forward on this. I apologize for running with out of date info on that. <br><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 23, 2016 at 9:49 AM Tom Barber <<a href="mailto:tom@analytical-labs.com">tom@analytical-labs.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Didn't know about AWS routing, interesting Rick! Although James is using AWS afaik so maybe its regressed there.</div><div dir="ltr"><div><br></div><div>Tom</div></div><div class="gmail_extra"><br clear="all"><div><div 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><div class="gmail_extra"><div class="gmail_quote">On 23 August 2016 at 14:45, Rick Harding <span dir="ltr"><<a href="mailto:rick.harding@canonical.com" target="_blank">rick.harding@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>That looks like something interesting. :)<br><br></div>Yes, the engineering team is working on adapting the Fan to public clouds as a first go at making sure containers can be routable ootb when using Juju. We'll just recently had a sprint scoping it out and see this as the solution to the problem your running into. <br><br></div>As you note, in cases where the containers can get dhcp addresses on the same network as the hosts, it's not an issue. OpenStack (depending on config) and MAAS work this way and aren't an issue. <br><br></div>At one point we had lxc container networking in AWS. I'm just bootstrapping to verify that this is still working properly in the latest 2.0 code and if not will file a bug that we've regressed in this. <br><br></div>tl;dr<br></div>containers should work with routing ootb on MAAS, OpenStack, and AWS. The team's working on leveraging the Fan for public clouds and other situations. <br><div><div><div><div><div><div><div><div><div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 23, 2016 at 9:26 AM Tom Barber <<a href="mailto:tom@analytical-labs.com" target="_blank">tom@analytical-labs.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Possibly something like... <a href="https://wiki.ubuntu.com/FanNetworking" target="_blank">https://wiki.ubuntu.com/FanNetworking</a> ? :)</div><div class="gmail_extra"></div><div class="gmail_extra"><br clear="all"><div><div 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: <a href="tel:%2B44%280%295603641316" value="+445603641316" target="_blank">+44(0)5603641316</a> </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><div class="gmail_extra"><div class="gmail_quote">On 23 August 2016 at 14:23, James Beedy <span dir="ltr"><<a href="mailto:jamesbeedy@gmail.com" target="_blank">jamesbeedy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><div><span style="background-color:rgba(255,255,255,0)">Mark,</span></div><div><span style="background-color:rgba(255,255,255,0)"><br></span></div><div><span style="background-color:rgba(255,255,255,0)">Thanks for the reply! Just to make sure I'm picking up what you are laying down, are you implying that Juju will soon support host <-> host container networking by supplying its own provider agnostic network fabric?</span></div><span><font color="#888888"><div><span style="background-color:rgba(255,255,255,0)"><br></span></div><div>~James</div></font></span></div><div><div><div><br>On Aug 23, 2016, at 4:29 AM, Mark Shuttleworth <<a href="mailto:mark@ubuntu.com" target="_blank">mark@ubuntu.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<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.<br>
<br>
Mark<br>
<br>
On 22/08/16 22:03, James Beedy wrote:<br>
</div>
<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></blockquote></div></div></div><br>--<br>
Juju mailing list<br>
<a href="mailto:Juju@lists.ubuntu.com" target="_blank">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/mailman/listinfo/juju</a><br>
<br></blockquote></div><br></div>
--<br>
Juju mailing list<br>
<a href="mailto:Juju@lists.ubuntu.com" target="_blank">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/mailman/listinfo/juju</a><br>
</blockquote></div></div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br></div></blockquote></div></div></div>