[13:58] <noodles775> Hangout here for anyone who wants to join the conv: https://plus.google.com/hangouts/_/hoaevent/AP36tYeQwxrxdZGveiZVKpetKkySfiZswgNHf5t0qJUtsowh4qjIIg?authuser=0&hl=en-GB
[13:58] <noodles775> people who have used ansible or ansible+juju would be great :)
[14:05] <noodles775> http://goo.gl/iewo1m
[14:05] <noodles775> http://goo.gl/iewo1m
[14:06] <nessita> noodles775, what's the link?
[14:06] <noodles775> http://goo.gl/iewo1m
[14:08] <vila> some channel op to add ' | Slides at http://goo.gl/iewo1m' in the topic ?
[14:09] <wesleymason> Channel isn't registered by the looks, so no ops
[14:10] <pindonga> where are the slides michael is talking about?
[14:10] <wesleymason> pindonga: http://goo.gl/iewo1m'
[14:10] <pindonga> ta
[14:12] <jcastro> bloodearnest, can you share your screen with the slides?
[14:12] <jcastro> so that we have them in the video?
[14:13] <bloodearnest> noodles775: ^^
[14:15] <therealmarv> much better also for later. Thanks for screensharing.
[14:19] <vila> bloodearnest: you're cutting off like hell (if I recognize the voice right :-/)
[14:19] <wesleymason> bloodearnest: if you've not turned your video off and turned down your streaming you might want to
[14:19] <nessita> vila, he is, and he is
[14:19] <vila> nessita: ;-p
[14:19] <jcastro> is the video on the slides right now?
[14:19] <vila> jcastro: yes
[14:19] <jcastro> I can't see because I'm driving the slides
[14:19] <nessita> much better!
[14:20] <wesleymason> bloodearnest: much better
[14:20] <vila> +1
[14:22] <wesleymason> noodles775: other advantage is Ansible the project are very strict about being able to ship everything out of the box, e.g. reduced dependencies, making it more reliable to depend on in charms (either from packages, or vendoring etc.)
[14:23] <vila> QUESTION: Does that mean there is no ansible playbook for django ? (Yet ? Hope ! Hope !)
[14:25] <avoine1> https://code.launchpad.net/~patrick-hetu/charms/precise/python-django/ansible
[14:25] <avoine1> vila:  ^
[14:25] <avoine1> like I said it's not finish yet
[14:26] <vila> avoine1: \o/
[14:27] <jcastro> can you guys see the slides?
[14:27] <vila> jcastro: yes
[14:27] <bloodearnest> jcastro: yep, but we have to select your feed
[14:32] <gnuoy> QUESTION: Does it still work well when charms need to make non-trivial decisions based on current context? For example, if a charm needs to set a setting down its relation with charm A based on information it got from charm B and whether the current day of the month is divisible by 3.
[14:32] <vila> bloodearnest, jcastro: not true for the stream, ha, noodles775 just replaced the slides
[14:32] <jcastro> yeah I just closed the slides for  the discussion part
[14:32] <vila> jcastro: ack
[14:32] <jcastro> I think "Top 5 reasons to use Ansible for Charms" would be a great blog post
[14:32] <jcastro> hint hint
[14:32] <nessita> what line in the Makefile?
[14:33] <nessita> bloodearnest, ^
[14:33] <avoine1> 22 to 30
[14:33] <nessita> thanks
[14:34] <noodles775> nessita: https://github.com/absoludity/charm-bootstrap-wsgi/blob/master/Makefile#L25
[14:34] <nessita> ack
[14:34] <mbruzek> Thanks for the link to the example code.
[14:34] <mbruzek> QUESTION: Are there some good places to get more information about Ansible?  Tutorials or good links on the web?
[14:35] <wesleymason> mbruzek: the documentation on the main Ansible site is very good: http://www.ansible.com/home
[14:35] <urulama> mbruzek: http://docs.ansible.com :D
[14:36] <lazyPower> +1 to ansible module documentation
[14:36] <lazyPower> Its really exhaustive on what you can do with the modules.
[14:36] <mbruzek> Thank you
[14:36] <therealmarv> What is your opinion why use ansible vs. puppet vs. chef ? (beside it is python based)
[14:36] <wesleymason> There's also a very good ebook on leanpub for those who like to read offlline, but it's still incomplete: https://leanpub.com/ansible-for-devops
[14:36] <therealmarv> QUESTION What is your opinion why use ansible vs. puppet vs. chef ? (beside it is python based)
[14:37] <lazyPower> therealmarv: in my humble opinion - and i realize i'm not giving the presentation - its the learning curve
[14:37] <lazyPower> you can learn ansible an an afternoon. It will take a few days before you can be really proficient with chef/puppet if you dont have much experience with the frameworks beforehand.
[14:38] <gnuoy> bloodearnest, thanks
[14:38] <wesleymason> If you need it, it is quite easy to make a full Ansible task in Python too, to be called like any other task from the playbook
[14:38] <wesleymason> not just a shell out
[14:39] <lazyPower> QUESTION are we contributing modules to push back to the ansible project? And if we have built any, what would they be?
[14:39] <wesleymason> s/task/module
[14:40] <therealmarv> thanks!
[14:41] <lazyPower> That would be briliant to get some juju related tasks vs using the shell helper to do relation-set
[14:41] <lazyPower> +1
[14:42] <wesleymason> also parsing the yaml/json from a config-get/relation-get etc.
[14:42] <wesleymason> into list/dict that can just be passed into jinja2 template
[14:42] <bloodearnest> wesleymason: that kind of already done
[14:42] <gnuoy> It sounds like the ansible equivalent of charm helpers hookenv
[14:43] <lazyPower> @QUESTION is the charm-bootstrap template on github the "best" place to get started writing ansible charms today?https://github.com/absoludity/charm-bootstrap-ansible
[14:43] <wesleymason> bloodearnest: yeah by the charmhelper, but I don't think it'll work from another relation? e.g. like with the generic actions we talked about
[14:43] <bloodearnest> wesleymason: it should, it writes ALL THE DATA
[14:44] <bloodearnest> for all relations
[14:44] <wesleymason> ah right
[14:44] <lazyPower> noodles775: you should talk to tvansteenburgh
[14:44] <lazyPower> he's working on a boilerplate generator for ansible based charms
[14:44] <lazyPower> which is in charm-tools
[14:46] <lazyPower> QUESTION: When you say sharing roles, do you mean i can include a simple yaml and get all of the "relation pass data otw" already given to me, and i just implement the application specifics on my side?
[14:46] <bloodearnest> wesleymason: which is usually what your want anyway
[14:46] <lazyPower> otw = on the wire
[14:46] <nessita> thanks!
[14:47] <lazyPower> awww i missed cutoff
[14:47] <gnuoy> thanks everyone, really interesting
[14:47] <lazyPower> stupid delay
[14:47] <wesleymason> bloodearnest: yep
[14:47] <bloodearnest> lazyPower: that's kind of what we've already got
[14:47] <lazyPower> bloodearnest: i was asking more for the specifics re: ansible playbooks and what that gives me :)
[14:47] <bloodearnest> by roles, we mean pieces of functionality (nagios, logrotate, etc)
[14:48] <lazyPower> ah ok
[14:48] <lazyPower> so you just drop in that bit of yaml and you'll gain rotating logs, and proper monitoring definitions
[14:48] <bloodearnest> lazyPower: things we kept up having to reimplement in every charm
[14:48] <lazyPower> yeah, i'm in that cycle myself right now with a few charms that I'm responsible for
[14:48] <noodles775> lazyPower: if you get a chance, pull https://github.com/absoludity/charm-bootstrap-wsgi as it tries to demo the reusability of both wsgi-app functionality and nagios checks (leaving a really small playbook).
[14:48] <lazyPower> i thought about abstracting to a common library, but an ansible role would keep that tidy
[14:49] <bloodearnest> lazyPower: you have to also invoke them from your playbook (with parameters), but yes
[14:49] <bloodearnest> lazyPower: and including some roles is easier than adding it to charm helpers
[14:49] <bloodearnest> imo
[14:50] <lazyPower> Great work on the session gents. cheers!
[15:04] <mbruzek> For reference here are the Juju LXC documentation https://juju.ubuntu.com/docs/config-LXC.html
[15:06] <nessita> jcastro, QUESTION, does this instructions apply to precise?
[15:07] <mbruzek> The instructions are the same for precise and trusty.
[15:07] <nuclearbob> jcastro, I get "chown: invalid user: ‘ubuntu:ubuntu’
[15:07] <nuclearbob> "
[15:08] <nuclearbob> but maybe we should discuss that later
[15:08] <roadmr> QUESTION: For precise, which kernel is required? is 3.8 enough, or is 3.11 needed?
[15:08] <mbruzek> nuclearbob, what command were you running when you got the error?
[15:08] <nuclearbob> mbruzek, juju quickstart
[15:09] <nuclearbob> mbruzek, here's what I'm doing: http://pastebin.ubuntu.com/7629014/
[15:09] <pitti_uos> I see the juju GUI (through youtube)
[15:09] <nuclearbob> fwiw, I've used juju on canonistack, I'm just getting stuck on local
[15:09] <roadmr> nuclearbob: pastebin that cloud-init-output.log maybe?
[15:09] <mbruzek> nuclearbob, what version of Ubuntu are you using?  uname -a
[15:10] <nuclearbob> roadmr, mbruzek, I'
[15:10] <nuclearbob> m running devel/utopic, but I haven't updated yet today.  I can't see that file in my local system
[15:11] <mbruzek> nuclearbob, you probably shouldn't have removed .juju directory
[15:11] <roadmr> nuclearbob: "on remote host", use lxc-ls to see if the container started at least; if so, try sshing into it or using lxc-console or lxc-attach
[15:11] <nuclearbob> mbruzek: I backed it up, I can put it back if that helps
[15:11] <nuclearbob> roadmr, I have a bunch of containers, but none of them have juju in the name
[15:11] <mbruzek> Either that or remove and reinstall the latest juju
[15:11] <roadmr> (oh never mind me, the env was destroyed so the lxc won't be there probably)
[15:11] <nessita> I just finished installing juju-quickstart, can you please confirm that is the first command I should run?
[15:11] <kentb> it is
[15:11] <mbruzek> $ juju --version
[15:11] <mbruzek> 1.19.3-trusty-amd64
[15:12] <nuclearbob> I'
[15:12] <nuclearbob> ve got 1.19.3-utopic-amd64
[15:12] <nuclearbob> I can remove and reinstall if needed
[15:12] <nuclearbob> oh, is max-local-machine-1 where I should look for the log?
[15:12] <nuclearbob> I was looking for something with juju in the name
[15:13] <mbruzek> I think removing .juju was a problem, either restore that  or remove/install
[15:13] <nuclearbob> okay, to remove/install, is apt-get remove juju-core ; apt-get install juju-core good enough?
[15:13] <nessita> jcastro, can you please pause a little bit and recap how you edned up with mysql in the lxc?
[15:14] <mbruzek> nessita, Can you elaborate your question
[15:15] <lazyPower> nessita: assuming you've run juju bootstrap -  juju deploy mysql
[15:15] <nessita> I'm still waiting on juje-quickstart
[15:15] <nessita> so not sure what to type next
[15:15] <nessita> and wanted to recap what command to run next
[15:16] <pitti_uos> nessita: the mediawiki charm pulled in a mysql node
[15:16] <mbruzek> nessita, There is a lot going on it may take up to 3 or 6 minutes
[15:16] <lazyPower> nessita: do you still see the quickstart GUI or is it currently outputting the bootstrap text?
[15:16] <nuclearbob> roadmr, should I get rid of max-local-machine-1 and max-local-machine-2 before I run juju quickstart?
[15:16] <nessita> currrently showing: machine 1 provisioning is pending
[15:16] <nessita> (no new output in the last minute)
[15:16] <pitti_uos> nessita: he went to the GUI (which should already be open in browser) and just activated the mediawiki hub
[15:16] <roadmr> nuclearbob: yes, it's likely to try to create the same names again which will lead to clashes
[15:16] <nuclearbob> that curses ui is awesome
[15:16] <nessita> pitti_uos, nothing in the browser
[15:16] <lazyPower> nessita: ok. so if Machine 1 is still provisioning, this will take a moment - its downloading a 200mb cloud image template for your LXC installation
[15:16] <nessita> ack
[15:16] <lazyPower> this is a one time thing if you've never bootstrapped on the local provider before.
[15:16] <nuclearbob> hmm, it's taking forever to lxc-destroy them, that's interesting
[15:17] <lazyPower> after your first time bootstrapping, it will take seconds to spin up a new container, as the image is cached.
[15:17] <JamesTait> lazyPower, is that still the case even without a btrfs partition?
[15:17] <roadmr> nuclearbob: indeed, destroy should be fast. Did you -f (force)? we don't care about them so that may work
[15:17] <nuclearbob> roadmr, I'll try -f
[15:17] <lazyPower> JamesTait: Correct. it will still clone the lxc-template
[15:18] <lazyPower> it takes ~ 20 seconds? give or take?
[15:18] <roadmr> JamesTait: yes, the image is cached; you're thinking about cloning an existing container I think :)
[15:18] <nessita> much clearer, thanks!
[15:18] <nessita> perfect, understood
[15:18] <JamesTait> \o/
[15:19] <roadmr> JamesTait: lxc-clone -s will clone using a snapshot, traditionally btrfs or lvm, but you can e.g. --backingstore overlayfs to just use a dir-backed overlay
[15:20] <nessita> lazyPower, machine 1 is still provisioning, any way of checking progress (or if it's stuck)?
[15:20] <nuclearbob> roadmr: I have this command running for minutes and not returning: sudo lxc-destroy -f -n max-local-machine-1
[15:20] <nuclearbob> I hope I haven't borked my lxc setup
[15:20] <lazyPower> nessita: run sudo lxc-ls --fancy - do you see the precise/trusty template lxc containers listed?
[15:21] <roadmr> nuclearbob: hmm I've never seen that :/ can you lxc-console to see what it's doing?
[15:21] <nessita> lazyPower, https://pastebin.canonical.com/111495/
[15:21] <roadmr> nessita: maybe have a look at /var/log/juju/machine-0.log?
[15:22] <nessita> nessita@dali:~$ cat /var/log/juju/machine-0.log
[15:22] <nessita> cat: /var/log/juju/machine-0.log: No such file or directory
[15:22] <JamesTait> roadmr, ah, it's possible I misunderstood - I've been avoiding recreating my local juju env because it always seemed to take a while, and I assumed it was re-downloading the cloud image (which isn't good on a metered connection :-P)
[15:22] <nessita> roadmr, ^
[15:22] <nessita> now I got this error: juju-quickstart: error: machine 1 is in an error state: error: template container "juju-trusty-template" did not stop
[15:23] <roadmr> JamesTait: ahh :) now we're talking about different things. It will cache the downloaded cloud image (so don't worry about your metered connection). You could also install apt-cacher-ng and configure lxc to use it (/etc/default/lxc), to also cache package downloads
[15:23] <lazyPower> nessita: so it failed during creating the template. boo
[15:23] <roadmr> JamesTait: in this context, the cloning/snapshot stuff won't help much but it's not needed really
[15:23] <nuclearbob> sudo lxc-destroy -f -n max-local-machine-1 doesn't seem to return anything either.  Maybe I should wait for the part of the talk about lxc doing bad things
[15:23] <lazyPower> roadmr: is this an instance where you need to destroy the template and restart? the downloaded image should be re-used and it will quickly recreate teh template again.
[15:23] <nessita> so this is usually my experience with the local provider, is hard to make it work as the instructions show, it fails in way that, without further knowledge, is hard to debug or recover from
[15:24] <nessita> didrocks, that may be relevant for you ^
[15:24] <roadmr> lazyPower: indeed, thus even less of a concern for JamesTait, as juju/lxc are pretty good at caching and reusing templates
[15:24]  * JamesTait is recreating his juju env tonight.
[15:24] <nessita> lazyPower, any way of recovering from that error?
[15:24] <roadmr> nuclearbob: hmm.. yes, unsure how/why things got b0rked :(
[15:25] <sparkiegeek> roadmr: JamesTait: LXC works really nicely with squid deb proxy. See http://tribaal.org/making-lxc-and-juju-fly-on-ubuntu.html
[15:25] <lazyPower> nessita: you'll need to sudo lxc-destroy --name juju-trusty-template after doing sudo lxc-stop --name juju-trusty-template
[15:25] <lazyPower> nessita: then you can re-run the quickstart command and it *should* just do magic
[15:25] <JamesTait> sparkiegeek, agreed - I'm already using that setup. :)
[15:25] <nessita> lazyPower, on it!
[15:26] <nessita> lazyPower, same error again https://pastebin.canonical.com/111496/
[15:26] <nessita> jcastro, no question, but errors! :-/
[15:27] <lazyPower> hmm
[15:28] <nessita> jcastro, that's my usual case (local provider breaks and no idea how to fix), and I must confess is pretty frustrating
[15:28] <nuclearbob> QUESTION: where do I find this marvelous juju-clean?
[15:28] <nuclearbob> I think I missed that part
[15:28] <mbruzek> http://paste.ubuntu.com/7629087/
[15:29] <jcastro> https://github.com/juju/plugins
[15:29] <nessita> rigth now I have no lxc for juju-trusty-template in order for stop or destroy
[15:30] <didrocks> nessita: you don't have anything in /var/lib/lxc, right?
[15:30] <nessita> didrocks, I have all my usual container, not juju related
[15:30] <nessita> (sca, u1)
[15:30] <didrocks> nessita: did you update from the ppa or you are using juju-quickstart from bare trusty?
[15:30] <nessita> didrocks, I added ppa juju/stable and then installed juju-quickstart
[15:31] <nessita> juju-quickstart: Installed: 1.3.3+bzr74+ppa19~ubuntu14.04.1
[15:31] <bloodearnest> I had that exact thing too
[15:31] <lazyPower> nessita: there's a merge for the juju cleaner that has the commands to run. its not emrged yet
[15:31] <lazyPower> https://bugs.launchpad.net/juju-core/+bug/1320121
[15:31] <udsbotu> Launchpad bug 1320121 in juju-core "template container did not stop" [Medium,Triaged]
[15:31] <nessita> didrocks, my LXCs https://pastebin.canonical.com/111498/
[15:31] <lazyPower> didrocks: https://bugs.launchpad.net/juju-core/+bug/1320121
[15:31] <didrocks> lazyPower: thanks! it was that one :)
[15:31] <nessita> oh
[15:32] <lazyPower> yeah, i may look lazy but i promise i'm over ehre flying through browser windows looking for the info
[15:32] <nessita> +1
[15:32] <nessita> so anyone has the command handy to downgrade/fix juju-quickstart?
[15:32] <fgallina> nessita: not sure if helps, but my experience is that stuff generally breaks if I happen to be running one of my non-juju lxc instances while doing juju stuff. I don't know if that changed but I take that preventive step of stopping them before doing juju magic.
[15:32] <nessita> aja!
[15:33] <nessita> lazyPower, does that make sense? ^ I do have another (custom) LXC running
[15:33] <nessita> this other LXC is not juju-related
[15:33] <lazyPower> nessita: i've had custom lxc containers running before without encountering this, but that's anecdotal. Its worth investigating.
[15:33] <pitti_uos> jcastro: fixing mysql> yes, please :) it's a rather common one
[15:34] <nessita> shutting down my non-juju-lxc-container
[15:34] <lazyPower> whoops i pasted teh bug not the merge request in github for the commands
[15:34] <sparkiegeek> not fixing it by adding relation support for postgresql <-> mediawiki and ditching mysql ;) (j/k)
[15:34] <nessita> same error on juju-quickstart, trying now nuking my ~/.juju folder
[15:34] <lazyPower> nessita: if that fails, let me know and we'll go through the wiping of the LXC bits for Juju and restarting
[15:35] <nessita> lazyPower, on it
[15:35] <lazyPower> yeah there's going to be more  1 sec
[15:35] <lazyPower> let me fetch the link
[15:35] <lazyPower> https://github.com/juju/plugins/pull/11/files
[15:35] <pindonga> QUESTION: where do you get the plugins? I'm on trusty but I don't have the pprint command
[15:35] <lazyPower> Looking throught his plugin code, the commands used to wipe it. I need to create some non-juju lxc containers to make sure this doesn't affect them and it will be merged, so all you need to do in teh future is "juju clean" and it'll magically wipe it out for you.
[15:36] <lazyPower> pindonga: https://github.com/juju/plugins
[15:36] <sparkiegeek> pindonga: https://github.com/juju/plugins
[15:36] <pindonga> thx, would be nice if it was packaged for ubuntu, but it'll work for now
[15:36] <jcastro> https://github.com/juju/plugins
[15:37] <sparkiegeek> oh the lag...
[15:37] <nuclearbob> roadmr, now I'm getting "juju-quickstart: error: uploading tools for series [utopic precise trusty]"
[15:37] <lazyPower> nuclearbob: progress!
[15:37] <nuclearbob> lazyPower: indeed!
[15:38] <lazyPower> do you have a default series placed in your ~/.juju/environments.yaml for the local environment?
[15:38] <lazyPower> thats consistent with what i've seen before when we introduced trusty to the juju environments list.
[15:38] <lazyPower> er, series, not environments
[15:38] <lazyPower> sorry too many thought trains colliding at once
[15:39] <lazyPower> nessita: poke check - how's things going over there?
[15:39] <nessita> lazyPower, so I cleaned up everything, but I guess thre is no point of running juju-quickstart if the version in trusty is borked?
[15:39] <pitti_uos> jcastro: yes, thanks
[15:39] <nuclearbob> lazyPower, it looks like juju quickstart didn't give me a default series, maybe it should.  I'll add one for now
[15:39] <nessita> I can just bootstrap local and run juju-gui, I guess?
[15:39] <pitti_uos> jcastro: it was quite illustrative how to fix a broken charm, so I'm glad you showed that and not just the "all works" marketing demo :)
[15:40] <lazyPower> nessita: you can achieve the same thing quickstart was doign for you by doing: juju bootstrap && juju deploy juju-gui
[15:40] <nessita> lazyPower, running
[15:40] <nessita> lazyPower, I guess I need to generate-env first?
[15:40] <lazyPower> it wont automagically open the browser for you, and log you in though
[15:40] <nessita> I wiped the ~/.juju fir
[15:40] <nessita> dir*
[15:40] <pindonga> so, not sure if this is the same as nessita's issue, but juju-quickstart never finishes running... the env is bootstrapped but the gui machine is pending and nothing else moves
[15:40] <lazyPower> nessita: bootstrapping will handle that for you
[15:40] <lazyPower> oh!
[15:40] <nessita> ah, does it now?
[15:40] <lazyPower> yes if you wiped ~/.juju you need to juju init again
[15:40] <nessita> right
[15:41] <nessita> lazyPower, also "juju switch local", right?
[15:41] <nuclearbob> okay, I added default-series: trusty to my local environment, but I still get the same error uploading tools
[15:41] <lazyPower> correct
[15:41] <lazyPower> nuclearbob: this is during bootstrap correct?
[15:41] <nessita> done, check with juju env, running bootstrap now
[15:41] <lazyPower> nuclearbob: if you run juju bootstrap --upload-tools does it succeed?
[15:41] <roadmr> nuclearbob: wow :/ do you see anything interesting in /var/log/juju?
[15:42] <nuclearbob> lazyPower, I was runnign juju quickstart, if I just run juju bootstrap, it doesn't generate an error uploading the tools, but I still get the chown invalid user error, I'll check the juju log
[15:42] <nuclearbob> I don't have an ubuntu user on my workstation, is that the problem?
[15:42] <lazyPower> nuclearbob: are you on trusty?
[15:42] <nuclearbob> lazyPower, utopic
[15:42] <nuclearbob> and there is no /var/log/juju
[15:43] <lazyPower> Oh! interesting...
[15:43] <lazyPower> nuclearbob: it would be in ~/.juju/local/logs
[15:43] <nuclearbob> lazyPower, no local directory in .juju
[15:44] <lazyPower> nuclearbob: ok, stands to reason since bootstrap is failing
[15:44] <lazyPower> nuclearbob: can you do a traditional juju bootstrap without using quickstart?
[15:44] <lazyPower> or does it still complain about the ubuntu:ubuntu user?
[15:44] <nessita> jcastro, is that colourizing thing yours? juju's? system's?
[15:44] <lazyPower> i'll admit, i dont have much experience with whats going on in utopic, so i'm learning right along with you nuclearbob
[15:45] <lazyPower> nessita: ccze is a package in the repositories.
[15:45] <lazyPower> nessita: available with sudo apt-get install ccze
[15:45] <jcastro> nessita, it's a package in universe, ccze
[15:45] <nessita> lazyPower, juju-gui unit still pending, from over a minute ago, i should keep waiting, right?
[15:45] <lazyPower> be forewarned, there is a caveate if you do long-running tail's, and your logs pipe doesn't receive any activity after a while, it will appear frozen.
[15:45] <nessita> re: ccze, thanks!
[15:45] <nuclearbob> lazyPower, I am still getting the chown invalid user error
[15:45] <lazyPower> nessita: do you see the container listed in sudo lxc-ls --fancy?
[15:46] <lazyPower> nuclearbob: ok, sounds like a definitive bug against juju in utopic. Can you file a bug against juju-local with all the relevant log output + troubleshooting steps we have taken?
[15:46] <nessita> lazyPower, unique LXC currently running is nessita-local-machine-1  RUNNING  10.0.3.51  -     YES
[15:46] <lazyPower> nessita: and juju-status says its p ending?
[15:46] <nuclearbob> lazyPower, can do
[15:46] <nessita> lazyPower, yes https://pastebin.canonical.com/111502/
[15:47] <lazyPower> nessita: ok give it a few more moments
[15:47] <nessita> lazyPower, ah! but visiting 10.0.3.51 in the browser (now) works
[15:47]  * lazyPower scratches head
[15:47] <lazyPower> well
[15:47] <lazyPower> i'm glad its there
[15:47] <nessita> I'm in! first time in juju-gui ever
[15:47] <lazyPower> the status output is troubling
[15:48] <lazyPower> but heyyyyy
[15:48] <lazyPower> we got you inb4 you gave up!
[15:48] <lazyPower> hi5
[15:48] <sparkiegeek> jcastro: what version of Juju are you using? juju debug-log works with local provider in 1.19.3
[15:49] <nessita> jcastro, can you paste the tail command here? I lost which file to tail on
[15:49] <nessita> (please)
[15:49] <jcastro> tail -F postgresql-0-debug.log | ccze
[15:49] <jcastro> or
[15:49] <jcastro> tail -F all-machines.log | ccze
[15:49] <nessita> thanks!
[15:50] <mbruzek> sparkiegeek, I have verified that debug-log works on 1.19.3
[15:50] <sparkiegeek> mbruzek: yeah, one of my favourite new features/bug fixes ;)
[15:50] <mbruzek> sparkiegeek, I was unaware that was fixed!  I am very happy to see that!
[15:50] <nessita> jcastro, already sorted out, no worries
[15:52] <pindonga> so, I've been having the same issue locally for ages... I can't get the local provider to deploy anything locally... the machines never finish bootstrapping..
[15:52] <jcastro> that sounds like the template bug I had
[15:52] <pindonga> ie, strace on the jujud process shows it's waiting on some other process (presumably lxc?)
[15:52] <pindonga> however there is no lxc process running
[15:53] <pindonga> and when I launch lxc containers manually they do work :(
[15:53] <nessita> thank you!
[15:53] <JamesTait> Thanks jcastro!
[15:53] <pitti_uos> thanks jcastro
[15:53] <nuclearbob> thanks jcastro, roadmr, mbruzek, and lazyPower!
[15:54] <lazyPower> thanks for attending nuclearbob :)
[15:54] <pindonga> jcastro, sorry if I missed you mentioning the solution to the template issue... care to repeat?
[15:54] <JamesTait> And also roadmr, mbruzek and lazyPower! :)
[15:54] <mbruzek> nuclearbob, No problem, hit us up in #juju if you need any more help
[15:54] <roadmr> thanks, good session :)
[15:54] <lazyPower> pindonga: there's a plugin merge with teh commands to execute, would you like the link?
[15:54] <JamesTait> And nessita for pointing this session out to me. ;)
[15:54] <pindonga> please
[15:54] <pindonga> lazyPower, please :)
[15:54] <lazyPower> https://github.com/juju/plugins/pull/11/files -- needs testing with additional lxc containers not under juju control to validate the merge is good. but should be g2g
[15:55] <mbruzek> pindonga and JamesTait Here is a session we had for Troubleshooting Jujuhttp://www.youtube.com/watch?v=UuqFaTASBTE
[15:55] <bloodearnest> \o/ juju-clean plugin has fixed my broken local env :) Thanks jcastro
[15:55] <jcastro> yeah!
[15:55] <pindonga> lazyPower, so I should add these changes and run juju cleanup?
[15:55] <sparkiegeek> should be called juju-nuke-from-orbit
[15:55] <lazyPower> pindonga: i would run them manually until they get merged into the clean plugin
[15:56] <nessita> pindonga, I ran each command individually and re-bootstrapped
[15:56] <nessita> and it worked
[15:56] <bloodearnest> ORLY? I may just have to stay around then...
[15:56] <bloodearnest> nessita: \o.
[15:57] <jcastro> marco is mid-upgrading the plugin
[15:57] <jcastro> so we should have a newer one here in a little bit that should sort everyone
[15:58] <JamesTait> Thanks for the link, mbruzek.  Can I juju deploy more-hours-in-the-day so I have time to watch it? :-P
[15:58] <nessita> jcastro, I lost track of that status of juju-quickstart, shall I expect the fix in trusty?
[15:58] <nessita> (I'm using the juju stable ppa)
[15:58] <jcastro> stay on the PPA for now
[15:58] <jcastro> rbasak is in progress fixing in trusty
[15:59] <nessita> jcastro, thanks :-)
[16:00]  * fgallina moves to use the stable ppa
[16:01] <pindonga> jcastro, should I switch to the stable ppa? I'm using trusty
[16:05] <jcastro> pindonga, I prefer to use the PPA
[16:05] <rbasak> I would like to get the versions in the archive updated and updated frequently enough that the PPA becomes redundant, but we're not there yet.
[16:06] <pindonga> jcastro, lazyPower so, I've cleared everything up and re-run quickstart.. stuff seems to be moving... I'll report back when it stops...
[16:06] <pindonga> thanks for the help
[16:07] <jcastro> we're in #juju for the follow up
[16:08] <pindonga> ack
[16:13] <patrick-uds> QUESTION: do you plan to make it possible to deploy a bundle with containing local charms in juju-gui?
[16:13] <jcastro> ooh good one!
[16:13] <jcastro> I'll have him answer here in a minute
[16:21] <apw> props for being able to talk when you can hear yourself ...
[16:23] <urulama> QUESTION: will it be possible to link charms from different environments (in a multi env system)?
[16:25] <patrick-uds> maybe a local charm store could help out
[16:26] <urulama> great, thanks
[16:27] <jcastro> http://jujugui.wordpress.com/
[16:28] <urulama> QUESTION: multi user support -> are we talking about connecting to LDAP server?
[16:30] <rbasak> So juju's state server will use LDAP to connect to an LDAP server deployed using a charm in it's own environment? That sounds like fun :-P
[16:30] <urulama> sorry for being nosy :D
[16:31] <rbasak> urulama: thank you for participating!
[16:31] <urulama> thanks
[16:33] <urulama> rbasak: was a pleasure to get to know what's coming :D
[18:02] <marcoceppi> o/
[18:06] <mbruzek> If you want to follow along at home:  https://juju.ubuntu.com/docs/getting-started.html
[18:08] <mbruzek> Charm Tools:  https://juju.ubuntu.com/docs/tools-charm-tools.html
[18:10] <mbruzek> https://juju.ubuntu.com/docs/contributing.html
[18:14] <mbruzek> For those who do not already know, the YAML format is simple human readable format
[18:14] <mbruzek> http://en.wikipedia.org/wiki/YAML
[18:15] <mbruzek> The YAML specification can be found here: http://www.yaml.org/
[18:16] <mbruzek> The README file can be in Markdown format:  http://en.wikipedia.org/wiki/Markdown
[18:20] <mbruzek> Any questions for Macro please leave them here, prefix with QUESTION
[18:30] <mbruzek> Juju Icon documentation:  https://juju.ubuntu.com/docs/authors-charm-icon.html
[18:38] <nessita> video stoppped, is it just me?
[18:38] <mbruzek> I am still going
[18:38] <marcoceppi> nessita: you may need to refresh
[18:38] <nessita> on it
[18:39] <nessita> marcoceppi, so you just removed the whole peer section?
[18:39] <mbruzek> Yes he did
[18:40] <jcastro> marcoceppi, your audio cut out
[18:40] <nessita> mbruzek, thanks, I'm "back"
[18:40] <mbruzek> nessita, it looks like marco is having problems.
[18:40] <nessita> mbruzek, did he fix the "I: relation bar has no hooks
[18:40] <nessita> "
[18:40] <nessita> ?
[18:41] <nessita> my latest charm proof shows:
[18:41] <nessita> nessita@dali:~/charms/trusty/foobar$ charm proof
[18:41] <nessita> W: Includes template icon.svg file.
[18:41] <nessita> I: relation bar has no hooks
[18:41] <mbruzek> I = Informational and we are OK with them.
[18:42] <nessita> ah!
[18:42] <mbruzek> You would want to clean up any charm proof Warnings or Errors.
[18:42] <nessita> right
[18:49] <mbruzek> We are going to continue this session into the next hour please stay with us if you are seeing these messages about time left in our session.
[18:56] <fgallina> curly, no spaces.
[18:59] <mbruzek> Charm Interfaces documentation:  https://juju.ubuntu.com/docs/authors-charm-interfaces.html
[18:59] <mbruzek> Also here is a handy list of EXISTING interfaces:  https://manage.jujucharms.com/interfaces
[19:00] <marcoceppi> fgallina: thanks!
[19:04] <mbruzek> The hook environment is documented here:  https://juju.ubuntu.com/docs/authors-hook-environment.html
[19:07] <nessita>  juju-log "FOOOOO"
[19:07] <nessita> juju-log: command not found
[19:08] <nessita> anything extra I need to install?
[19:08] <nessita> ah, ok
[19:09] <mbruzek> nessita, You must be in a hook environment before those commands are available
[19:09] <pindonga> QUESTION: in case it hasn't been addressed before... recommendations on how to keep multiple branches for a charm (I found the issue in the past where keeping them side-by-side inside of the charm repository would cause issues, like the wrong branch being picked up by juju)
[19:10] <pindonga> ie, in particular is there a nice way to use lightweight checkouts when writing charms?
[19:16] <mbruzek> Thanks for the great question
[19:17] <pindonga> thx for the answer
[19:17] <pindonga> it'd be ideal if we could find a way to make juju work with symlinks at least
[19:17] <pindonga> so that I don't have to move folders around
[19:17] <pindonga> but at least you got me an idea (changing the charm name and keep branches side by side)
[19:18] <pindonga> which is better than keeping many repos (imho)
[19:19] <catbus1> the juju bootstrap node is not on?
[19:46] <jcastro> mbruzek, 15 minute warning!
[19:50] <mbruzek> Thanks jose
[19:50] <jose> :)
[20:02] <lazyPower> marcoceppi: juju scp -r doesn't work because juju isn't passing -r to the command
[20:02] <lazyPower> unless i'm way off base, but i'm about 99% sure thats the case.
[20:03] <lazyPower> i get really cheap and just tarball teh charmdir and copy that to $HOME, then juju scp that over.
[20:03] <lazyPower> its not ideal but it gets the job done
[20:06] <bloodearnest> lazyPower: juju scp --help shows examples of -r working as expected (1.18.3 anyway)
[20:06] <lazyPower> bloodearnest: yeah i saw that
[20:06] <lazyPower> but in practice it doesn't appear to be the case
[20:06] <lazyPower> perhaps docs contain feature creep ;)
[20:07] <bloodearnest> I'm sure I saw a -- to pass things through to raw scp at some point