[07:48] <davidcalle> Morning o/
[08:00] <dpm> good morning all
[08:30] <svij> morning
[08:30] <Kilos> hi svij davidcalle dpm
[08:47] <davidcalle> Hey Kilos o/
[09:02] <svij> dpm: hey! Did you have time to look into the blog on ubucon.org? Also, I guess there wasn't a meeting yesterday?
[09:40] <dpm> hi svij, I started, but I didn't get too far trying to get the juju local deployment to work. It seems quite a bit has changed with the 2.0 release
[09:40] <svij> ah okay
[09:43] <dpm> it seems the time did not work for the others yesterday, as I hadn't received any confirmation to the new time - I joined the hangout nevertheless in case someone would show up, but after a few minutes I closed the hangout
[09:43] <svij> ah ok, as I heard the others didn't have time either
[09:44] <dpm> that's fine, we can talk on the next meeting. Other than that, I didn't have other updates
[09:44] <svij> me neither.
[09:44] <dpm> I think as the next announcement, we should work out and open registration
[09:45] <svij> and we need a few sponsors
[09:49] <dpm> jcastro, marcoceppi, that reminds me - I understand the local (lxc) provider is no longer available in juju 2.0. Is there a way at all to currently get local deployments to work with LXD, even if it's a bit of a hack? I read https://jujucharms.com/docs/devel/temp-release-notes#lxd-provider but I couldn not figure it out
[09:50] <dpm> On juju 2.0 I could not even figure out how to generate the initial config
[09:54]  * svij is going to visit Canonical HQ later today to play with all the devices \o/
[09:59] <dpm> svij, nice!
[09:59] <dpm> balloons, or I guess I can ping you now for questions on juju ^ ;)
[10:02] <svij> and Im going out for a beer with thibaut
[10:03] <svij> but I guess he will drink my beer :D
[12:13] <marcoceppi> dpm: it's a lot easier in 2.0
[12:13] <marcoceppi> dpm: just install lxd, run lxd init (answer questions), then do `juju bootstrap my-new-local-stuff lxd`
[12:14] <dpm> marcoceppi, \o/
[12:14] <dpm> marcoceppi, I figured out that bit, and I've got juju locally running, however
[12:14] <dpm> I'm having trouble with the local charm for ubucon
[12:15] <dpm> marcoceppi, $ juju deploy local:trusty/ubucon
[12:15] <dpm> ERROR unknown schema for charm URL "local:trusty/ubucon"
[12:15] <marcoceppi> dpm: yeah, all that goes away too
[12:15] <marcoceppi> dpm: just do `juju deploy /abs/path/or/relative/path/to/ubucon`
[12:15] <dpm> tried that too, that's where I got stuck. Let me re-run it and paste the output
[12:16] <dpm> marcoceppi, $ juju deploy ~/charms/trusty/ubucon
[12:16] <dpm> ERROR series not specified and charm does not define any
[12:16] <dpm> I think I'd need to change some .yaml files in the charm or layer, but I wasn't sure which
[12:16] <marcoceppi> dpm: ah, that's because I'm a horrible charm maintainer
[12:16] <marcoceppi> dpm: you can just do this for now
[12:16] <dpm> :)
[12:17] <marcoceppi> `juju deploy ~/charms/trusty/ubucon --series trusty`
[12:17] <dpm> on it
[12:17] <dpm> ok, juju did it without complaints so far
[12:18] <dpm> "Waiting for agent initialization to finish"
[12:18]  * dpm crosses fingers
[12:19] <marcoceppi> dpm: you'll also need to deploy postgresql, but I feel you may know that already
[12:19] <dpm> yeah, did that and added the relation
[12:21] <dpm> marcoceppi, I can update the charm/layer myself if you know off the top of your head which fields we should add and which yaml files to modify
[12:22] <marcoceppi> dpm: you'll want to pull down the layer, edit metadata.yaml, add a series key, which is a list of one string "trusty", then charm build on that layer and you'll have an updated charm with series defined by the charm
[12:23] <dpm> marcoceppi, great, will do that.
[12:23] <dpm> marcoceppi, argh! -> ubucon/0     error           idle        2.0-beta7 2                      10.194.112.38  hook failed: "install"
[12:25] <marcoceppi> dpm: pastebin me the logs from /var/log/juju/unit-ubucon-0* on that machine?
[12:27] <dpm> marcoceppi, http://pastebin.ubuntu.com/16944735/
[12:27] <marcoceppi> dpm: huh, that's odd
[12:28] <dpm> bzr: ERROR: Not a branch: "/srv/ubucon/ubucon-site/".
[12:29] <dpm> where's the install hook on http://bazaar.launchpad.net/~ubucon-site-developers/ubucon-site/ubucon-layer/files ?
[12:30] <dpm> brb
[12:30] <marcoceppi> dpm: reactive/ubucon.py
[12:38] <dpm> marcoceppi, hm, it seems the install hook is not explicitly defined here, so I'm guessing it's using a standard 'install' that simply checks out the repo. No idea what to do next
[12:38] <marcoceppi> dpm: not quite
[12:38] <marcoceppi> dpm: this may be a failure in the django layer
[12:53] <dpm> marcoceppi, interesting, trying to run the command manually from inside that unit gives me the same error, seems to be bzr related? http://pastebin.ubuntu.com/16945198/
[12:54] <dpm> ah, actually, that should be run as sudo, I guess
[12:54] <marcoceppi> dpm: what does `bzr info` show in the /srv/ubucon/ubucon-site direcetory
[12:55] <dpm> marcoceppi, http://pastebin.ubuntu.com/16945242/
[12:55] <marcoceppi> dpm: it's trying to merge before it did a bzr branch/pull
[12:55] <marcoceppi> which is weird
[13:10] <jcastro> dpm: yeah, lxd provider is fully supported, you want this page: https://jujucharms.com/docs/master/clouds-LXD
[13:11] <dpm> thanks jcastro
[13:12] <jcastro> our docs still haven't shifted over to the stable branch
[13:12] <jcastro> so like you probably ended up on old docs. :/
[13:12] <dpm> jcastro, yeah, but I figured it out from another doc in devel that looks similar to the one you showed me
[13:13] <dpm> I can't believe I'm stuck with a bzr error now, though :/
[13:16] <dpm> I wonder if this warning in `charm build` has anything to do with it, although it seems harmless
[13:16] <dpm> build: Please add a `repo` key to your layer.yaml, e.g. repo: bzr+ssh://bazaar.launchpad.net/~ubucon-site-developers/ubucon-site/ubucon-layer/
[13:24] <dpm> marcoceppi, the django layer the ubucon charm uses is https://github.com/marcoceppi/layer-django, right?
[13:24] <marcoceppi> dpm: yes
[13:26] <dpm> marcoceppi, ok, cool. So I guess there I can 1) look at the install hook if it needs debugging and 2) add the update hook we need for the site
[13:26] <dpm> or action, not sure of the right nomenclature
[13:26] <marcoceppi> dpm: there are not more hooks in charms, all the code lives in reactive/<name>.py ;)
[13:26] <marcoceppi> but otherwise, yes
[13:28] <dholbach> picking up my niece from kindergarten, bbiab
[13:28] <dpm> ok cool
[14:22] <dpm> marcoceppi, ok, one last question before I give up -> http://pastebin.ubuntu.com/16947271 - any ideas why no relations are being found?
[14:38] <marcoceppi> dpm: you're deploying the wrong thing
[14:38] <dpm> ouch
[14:38]  * dpm re-reads pastebin
[14:38] <marcoceppi> dpm: build: Destination charm directory: /home/dpm/charms/builds/ubucon
[14:38] <marcoceppi> dpm: you should be deploying that path
[14:42] <dpm> marcoceppi, argh, you're right, thanks! But should it not be ~/charms/trusty/ubucon instead? I can't recall having deployed from the 'builds' directory?
[14:42] <dpm> I mean when I did it earlier on
[14:43] <dpm> ah, they seem to have the same content
[14:43] <marcoceppi> dpm: you added series flag to the charm, so it's a different output
[14:44] <dpm> marcoceppi, so the right path to point to is always the build dir? Or does it make a difference? I just want to make sure we document the right thing in the site's deployment README
[14:51] <marcoceppi> dpm: the build output directory
[14:51] <dpm> ok, cool
[14:51] <marcoceppi> charm build takes the layer and builds a charm, the charm is what you ultimately want to deploy
[14:51] <dpm> running the install hook now
[14:51] <dpm> crossing fingers that bzr is happy
[14:52] <dpm> argh
[14:52] <dpm> hook failed: "install"
[14:52] <marcoceppi> dpm: i'll take a look in a min
[14:52] <dpm> awesome, thanks
[14:53] <czajkowski> c/
[14:57] <dpm> hey czajkowski
[15:28]  * svij waves from canonical hq.
[15:50] <davidcalle> svij: nice :)
[15:51] <dpm> svij, Telegram pics or it didn't happen! :-)
[15:52] <popey> pics from the roof :)
[15:52] <popey> (don't drop your phone)
[15:54] <svij> dpm: check the insiders group :P
[15:54] <svij> I mean outsiders group!
[15:54] <svij> popey: hmm.. I could drop this Pro 5.
[15:54] <popey> Don't! They're rare!  😃
[15:56] <svij> currently no one is looking for me. I think I could go out with the pro 5, the bq m10 and a nexdock! 🤔
[15:57] <davidcalle> svij: we won't tell on you :)
[15:58] <svij> this channel is luckily not publically logged... oh wait.
[16:03] <popey> you have the nexdock?
[16:03] <popey> didnt realise we got hold of one o fthem
[16:08] <svij> yep here is one beta thing as thibaut told me
[16:08] <svij> not tested yet
[16:30] <dholbach> see you next week
[16:30] <dholbach> have a good one
[16:31] <Kilos> cheers dholbach
[16:31] <Kilos> you have a good one too
[16:31] <Kilos> :D
[16:42] <svij> Im either too dumb for the nexdock or it doesnt work right now...
[16:51] <dpm> who let svij in at the office?
[16:51] <dpm> I'm starting to get worried :-)
[16:53] <svij> dpm: heh ;)
[16:55]  * svij likes the hardware of the pro 5
[16:55] <dpm> if there are news leaked about a super secret device over the weekend, we know who to ask where they came from...
[16:55] <svij> if only the OS would be way better...
[16:55] <dpm> such a troll...
[16:55] <svij> haha
[16:56] <popey> hehe
[16:58] <svij> dpm: I ll tell jane that you're naughty!111!
[17:02] <svij> too bad she is busy
[17:04] <dpm> :)
[17:20] <dpm> marcoceppi, have you had the chance to look at the ubucon charm install failure? I'm about to log off, but if you have a few pointers I can perhaps look at it some time during the weekend
[17:47] <dpm> marcoceppi, actually, the issue seems to be here http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/fetch/bzrurl.py#L48
[17:47] <dpm> branch() checks if the location exists, but it does not check if it's a bzr branch. Probably something else mkdir's the directory before, and branch() was not expecting this case
[17:48] <dpm> actually, that something is L62