[10:37] <neiljerram> Morning all!  Does anyone happen to know the purpose of juju-br0 ?
[11:58] <marcoceppi> neiljerram: juju-br0 I think is used to bridge LXC/LXD containers and KVM machines deployed by juju to a network routable address
[11:59] <magicaltrout> I dont' think it includes LXD containers
[11:59] <magicaltrout> I have lxd local(although not the latest beta) and no juju-br0
[11:59] <magicaltrout> just a fat stack of veth adaptors
[12:00] <marcoceppi> magicaltrout: this would be more `juju deploy --to lxd:` than lxd running on your machine as a provider
[12:00] <magicaltrout> ah, yeah
[12:12] <neiljerram> marcoceppi, magicaltrout Thanks. I found some email trails that seemed to say that sometimes you get juju-br0 and sometimes lxcbr0 - but it wasn't clear to me why.
[12:14] <magicaltrout> I do have lxcbr0, I guess marcoceppi is correct, because lxd local stuff would all have networking at the same level, but if you dumped it into a running box, you'd have a hard time addressing it :)
[12:25] <andrey-mp> hi! can somebody point me to instruction how to publish charms? I've read this - https://jujucharms.com/docs/stable/authors-charm-store#submitting     I've made all needed branches - https://code.launchpad.net/~cloudscaling  and  https://code.launchpad.net/~apavlov-e   but my modules was not appeared in Juju. where is my mistake?
[12:26] <magicaltrout> its out of date andrey-mp :(
[12:26] <rick_h_> andrey-mp: working on getting an updated link
[12:27] <magicaltrout> https://jujucharms.com/docs/devel/authors-charm-store
[12:27] <rick_h_> andrey-mp: yes, sorry. The new docs should be going live this week
[12:28] <andrey-mp> thanks! will read and try )
[12:28] <rick_h_> andrey-mp: let us know if you hit any issues
[12:28] <andrey-mp> rick_h_: ok
[14:29] <aisrael> tvansteenburgh: Any known issues w/bundletester and juju 2 beta 9?
[14:31] <tvansteenburgh> i haven't tried it yet but if beta9 has the service->application rename then it's probably broken
[14:31] <tvansteenburgh> aisrael: ^
[14:31] <aisrael> tvansteenburgh: ack, confirming that's broken :/
[14:33] <rick_h_> aisrael: tvansteenburgh yes, the stack is broken on top of latest beta. We need to get things updated to work with the changes.
[14:33] <rick_h_> aisrael: tvansteenburgh another round will break in beta10 with the api updates coming as well
[14:34] <aisrael> rick_h_: Do we have a target date for beta 10?
[14:34] <rick_h_> aisrael: once a week is the beta request so I'd look at the end of this week
[14:34] <aisrael> rick_h_: awesome \m/
[15:52] <petevg> tvansteenburgh aisrael: can also confirm that amulet tests (and therefore bundletester) seem to be broken in beta9.
[15:52] <tvansteenburgh> petevg: everything is broken
[15:52] <petevg> At least it's not just me :-)
[15:53] <tvansteenburgh> sing it to the tune of the lego movie
[15:53] <petevg> Has anybody filed a ticket about a cheetah dependency breaking charm tools in Python3?
[15:53] <petevg> Now I've got it stuck in my head :-p
[16:14] <xilet> with the juju add-storage options, is there any way to use a lvm volume or does it have to be a physical device?
[16:44] <arosales> Hello, just as an fyi on the GUI, the charm store was updated today and looks to resolve:
[16:44] <arosales> https://github.com/juju/juju-gui/issues/1685
[16:44] <arosales> https://github.com/juju/juju-gui/issues/1765
[16:44] <arosales> but 2 new bugs came up as juju2 is still updating back-end services
[16:44] <arosales> https://github.com/juju/juju-gui/issues/1781
[16:44] <arosales> https://github.com/juju/juju-gui/issues/1780
[16:45] <arosales> marcoceppi: jcastro lazypower-travel ^^ note this week for conferences
[16:45] <arosales> and thanks to the UI team for working hard to try and keep up with a fast changing juju-core
[18:26] <bdx> charm store is bugging out
[18:27] <bdx> http://imghub.org/image/B6cP
[18:29] <rick_h_> bdx: is that public? Did your login expire? try /logout and login?
[18:30] <bdx> rick_h_: I did
[18:30] <bdx> multiple times
[18:30] <bdx> rick_h_: it shows here -> http://imghub.org/image/BI0X
[18:31] <bdx> `charm list` shows it -> http://paste.ubuntu.com/17607650/
[18:32] <rick_h_> bdx: ugh, file a bug please? and I'll get folks to look at it. https://github.com/CanonicalLtd/jujucharms.com/issues
[18:32] <rick_h_> there was a deploy today so maybe a regression. Can you check if it works for staging.jujucharms.com as well ple`ase?
[18:32] <bdx> yes, omp
[18:34] <bdx> rick_h_: even worse on staging
[18:34] <bdx> rick_h_: http://imghub.org/image/BQyu
[18:34] <bdx> that was after multiple logouts/logins
[18:35] <cholcombe> thedac, for your keystone-credentials interface are you meant to relate to keystone when using it?
[18:35] <rick_h_> bdx: oh right, to be expected I guess since you didn't upload your charm to the staging charmstore
[18:35] <cholcombe> thedac, i imagine the answer is yes
[18:45] <bdx> rick_h_: the charmstore client is developed at https://github.com/juju/charmstore-client ?
[18:46] <rick_h_> bdx: yes
[18:55] <bdx> rick_h_: ahhh, I previously missed the link you posted, you want the bug there instead of the charmstore-client repo?
[18:59] <rick_h_> bdx: right  i think the bug is in the website. you mention the cli tool working fine
[18:59] <bdx> entirely - gotcha
[19:23] <kwmonroe> hey, does hookenv.log work in an action?
[19:24] <kwmonroe> nm, yes it does
[19:35] <aisrael> kwmonroe: most, if not all, of the hookenv stuff works inside actions.
[19:36] <kwmonroe> cool aisrael -- turns out i was debug-logging with -i on the wrong unit and being like, um, where's me logs!?!
[19:36] <aisrael> :D
[21:46] <xilet> Is there a way to just attach a block device to a running charm (working with juju 2.0) as a raw device?
[22:25] <kjackal> hey kwmonroe, r u there?
[22:29] <marcoceppi> xilet: type: block for storage should be a "raw" disk
[22:30] <xilet> I am trying to get the syntax down, how would I add that to an exisiting charm?
[22:30] <marcoceppi> xilet: it should look something like this: https://jujucharms.com/docs/devel/developer-storage#adding-storage
[22:31] <marcoceppi> the second example block shows blockdevices
[22:39] <xilet> yeah, but do I just give it the location: of the block device I want to use? And do I need to redeploy the charm for it or can I use the set-config command for it? (Sorry new to juju)
[22:43] <kwmonroe> hey kjackal!  you're still on holiday.
[23:31] <bdx> charmers: I charmed up DHC's internal recommendation engine, and introduced one of our devs to charming/charmstore - he's super pumped
[23:31] <bdx> charmers: this is whelp -> https://github.com/DarkHorseComics/layer-whelp
[23:32] <bdx> I can't publish it to the store bc the wresource need be kept private
[23:32] <bdx> the charm layer is g2g for github - needs some tests though
[23:35] <marcoceppi> bdx: bad ass!
[23:35] <marcoceppi> bdx: a lightning talk on this at the charmer summit would be sweet
[23:36] <magicaltrout> didn't he already do one last time around? :P
[23:36] <bdx> magicaltrout: yeah - crashburnboom
[23:37] <marcoceppi> magicaltrout: great question
[23:37] <magicaltrout> "just wait... there is a chart coming" ;)
[23:37] <magicaltrout> touche
[23:37]  * magicaltrout can't be bothered googling the crazy e the french use
[23:39] <bdx> marcoceppi: totally
[23:41] <bdx> marcoceppi: what are you trying to do with that DjangoYamlTactic ?
[23:41] <marcoceppi> bdx: convert django.yaml to layer options for backwards compat
[23:41] <marcoceppi> haven't really gotten around to it
[23:42] <marcoceppi> (yet)
[23:44] <bdx> ok, I'm about to dump some cycles the next few days and refine some of mods I have for it ... how to you feel about approaching writing out settings files similar to pythonn-djago? - I already have this going on for memcache and postgres and was about to get busy on mongo and redis ...
[23:47] <bdx> https://github.com/jamesbeedy/layer-django/blob/modularize_and_refactor/reactive/django.py#L63-84 ?