[01:02] <jac_cplane>  I'm running into bug 1628337 - cloud init install NTP before configuring archives.   I see from github that it was fixed 20 days ago.  can someone tell me how I can get this fix?   i'm running MAAS 2.1.5 - I deleted my current xenial image and downloaded it again via maas.
[01:02] <mup> Bug #1628337: cloud-init tries to install NTP before even configuring the archives <verification-done> <cloud-init:Fix Released by smoser> <cloud-init (Ubuntu):Fix Released> <cloud-init (Ubuntu Xenial):Fix Released> <https://launchpad.net/bugs/1628337>
[01:18] <jac_cplane> please disregard - figured it out
[05:51] <bdx> does anyone have an example bundle that uses a default space binding?
[05:51] <bdx> like
[05:51] <bdx> juju deploy --bind "default-space db=db-space db-admin=admin-space" mysq
[05:52] <bdx> but in a bundle
[05:52] <bdx> http://paste.ubuntu.com/25929870/
[05:52] <bdx> I want to deploy charms to lxd and bind to spaces in a bundle
[05:53] <bdx> but then other charms that don't have network bindings fail to deploy when not given a default space
[05:53] <bdx> just unsure how to do that in the bundle
=== mpjetta_ is now known as mpjetta
=== frankban|afk is now known as frankban
[15:57] <Dmitrii-Sh> bdx: have to be explicit in every app for now
[15:57] <Dmitrii-Sh> https://bugs.launchpad.net/juju/+bug/1719804
[15:57] <mup> Bug #1719804: Allow specifying a default space binding on a per-bundle basis <juju:Triaged> <https://launchpad.net/bugs/1719804>
[16:38] <Dmitrii-Sh> bdx: you could use yaml aliases to define a single space and reuse it across different charms
[16:39] <Dmitrii-Sh> aliases:
[16:39] <Dmitrii-Sh>   default-space: &default-space my-space
[16:39] <Dmitrii-Sh> ...
[16:39] <Dmitrii-Sh> bindings:
[16:39] <Dmitrii-Sh>   "": *default-space
=== primeribz is now known as rahworkx
=== frankban is now known as frankban|afk