[12:34] <elopio> Hello
[12:34] <elopio> I'm trying to set up a quassel server on canonistack but it says allocating since 15 minutes ago.
[12:34] <elopio> shouldn't it be allocated by now?
[12:52] <lazyPower> elopio: hmm, i would think so
[12:52] <lazyPower> elopio: are you connected to the VPN, and have you verified the machine is not "stuck in allocating" in nova list?
[12:53] <elopio> lazyPower: now it says executing
[12:53] <elopio> now running install hook
[12:53] <elopio> wow, things are happening!
[12:53] <lazyPower> awww yisss
[12:53] <lazyPower> yeah canonistack can be a bit pokey, its a tad oversubscribed.
[12:54] <elopio> and started. lazyPower: you probably cheated in here. I don't buy it.
[12:54] <lazyPower> elopio: It's Levi-OOOOH-sa not LevioSAR  ;)
[12:58] <elopio_> look, I'm juju!
[12:58] <lazyPower> elopio: is this your first interaction with Juju?
[13:02] <elopio_> lazyPower: the first successful, yes.
[13:02] <lazyPower> thats awesome! Congrats!
[13:06] <elopio> now, how do I change the name of the machine? I'd like it to be named "quassel" instead of "1".
[13:06] <lazyPower> elopio: ah, juju treats machines as cattle not pets. The service you deployed should be named Quassel however in your juju status output.
[13:07] <elopio> ok, I can live with that.
[13:07] <lazyPower> to get a better view of how we model things, i highly recommend deploying the Juju GUI. It does a bang up job of displaying the model. juju deploy juju-gui --to 0 (which will colocate the gui on your bootstrap node, not consuming another machine)
[13:09] <elopio> thanks lazyPower. That's shiny.
[13:10] <elopio> now, I need a tarmac.
[13:11] <elopio> the only thing I didn't see on the available charms was dovecot or courier-imap.
[13:11] <elopio> I suppose I can install that manually.
[13:15] <lazyPower> We dont have any mail delivery agents charmed up, no. We have postfix available - but thats the end of the road afaik.
[13:17] <lazyPower> elopio: we have office hours today, might be a good opportunity for you to join and ask questions about juju / evaluating the contribution opportunity here
[13:18] <elopio> lazyPower: at what time is that?
[13:18] <elopio> I want to write a charm, and I'm thinking about getting started with nikola.
[13:18] <elopio> I'll definitely have many questions, but not likely today.
[13:19] <lazyPower> 2000 UTC
[13:20] <elopio> ok, I'll try ot make it.
[13:20] <lazyPower> if thats after hours, they are recorded on hangouts and we'll syndicate a link to the mailing list after the fact.
[13:21] <jrwren> lazyPower: MDA charm to what end?
[13:21] <lazyPower> jrwren: do we have any mail delivery agents?
[13:21] <jrwren> lazyPower: not that I know of :(
[13:21] <lazyPower> ^ thats the end. <3
[13:22] <jrwren> lazyPower: I can't imagine what an MDA charm would do. I'm trying to understand what one would mean.
[13:22] <lazyPower> jrwren: well, you could say for instance, deploy a dovecot service, and have actions that manage the user accounts. CRUD stuff
[13:23] <lazyPower> if you deploy something like roundcube, it could relate to it and provide a webhead to view email
[13:24] <lazyPower> deliver an action to manage DKIM, juju action do dovecot create_dkim domain=mx.jrwren.com - and the output gives you all the DNS entries to paste into your panel. or - optionally - add a DKIM relation between teh DNS charm and it to populate the DKIM signature (bonus points for integration)
[13:24] <jrwren> oh that is much more than MDA. I hear MDA, I think /bin/mail :)
[13:24] <lazyPower> perhaps add in a spamassasin subordinate + relation to handle filters
[13:24] <jrwren> would be very nice
[13:24] <lazyPower> and greylisting
[13:24] <lazyPower> i mean there's a *lot* of possibility there
[13:24] <elopio> and throw a mailpile in there just for fun.
[13:25] <lazyPower> elopio: aiui mailpile is intended to be run locally. running it remotely does very little to actually secure the data you're already paranoid about and therefore using mailpile to pgp encrypt
[13:25] <lazyPower> storing the keys on the server isn't a great idea. I was in a long talk w/ the maintainer as  I thought about charming it up
[13:25] <lazyPower> ultimately it was stated its not at all recommended to place it on a remote system.
[13:26] <elopio> I thought adding https to it was good enough.
[13:26] <elopio> but well, it would still be useful to deploy in a local lxc.
[13:26] <lazyPower> indeed. Thats how i ran it when i was beta testing it
[14:42] <aisrael> jose: are you still working on a review of the xcat charm (it shows locked by you)?
[14:43] <jose> aisrael: wat? no, let me check if I can unlock it
[14:46] <jose> aisrael: should be unlocked now - feel free to take it
[14:46] <aisrael> jose: will do, thanks!
[14:46] <jose> I'm studying for an exam later today and will check the queue after that
[14:46] <jose> np :)
[14:56] <jcastro> hazmat: can you PM me an updated email address for you?
[15:04] <lazyPower> alai`: HI Alai :)
[15:04] <alai`> hi lazyPower
[15:04] <alai`> ;)
[15:04] <lazyPower> alai`: i understand you're having a problem with the ETCD charm wrt testing calico
[15:04] <lazyPower> can you pastebin me the error code? i have received the bundle.
[15:04] <alai`> sure 1 sec
[15:05] <lazyPower> sorry, the juju log from the etcd service would be more helpful alai`
[15:05] <alai`> lazyPower, http://pastebin.com/SBE0NEMd
[15:05] <alai`> that's the error
[15:06] <lazyPower> well thats fun... i see you're pointed at the ~kubernetes namespace charm, which is the one containing the fix we resolved last week
[15:07] <lazyPower> http://bazaar.launchpad.net/~kubernetes/charms/trusty/etcd/trunk/view/head:/metadata.yaml - looking at the service definition, it has an etcd-proxy interface, but the relation is just 'proxy'
[15:07] <lazyPower> alai`: can you update the bundle from 'etcd-proxy' to just 'proxy'? that should resolve the error you're seeing
[15:07] <alai`> lazyPower, woot
[15:07] <alai`> +1 lazyPower
[15:07] <alai`> thanks
[15:10] <lazyPower> np lmk if you run into any further issues :)
[15:52] <beisner> wolsen, dosaboy - hacluster functional test fixup re: VIP @  https://code.launchpad.net/~1chb1n/charms/trusty/hacluster/amulet-extend/+merge/266355
[15:53] <beisner> and a > vivid bug discovered along the way: bug 1479661
[15:53] <mup> Bug #1479661: hacluster install hook fails on vivid (openhpid init script error) <amulet> <openstack> <uosci> <hacluster (Juju Charms Collection):New> <https://launchpad.net/bugs/1479661>
[15:55] <beisner> jamespage gnuoy fyi ^  prob not a 1507 blocker, but something to be aware of.
[19:06] <beisner> gnuoy, argh, my merged mojo-foo missed a sneaky 2nd spot where net_info is assigned.  i'll be shifting the env var detection up to a helper and calling that in get_mojo_config instead.  WIP...
[19:07] <beisner> gnuoy, ^ which is causing the 2nd neutron-gateway nic to be wired up to the wrong network.
[19:54] <mbruzek> Juju office hours in 6 minutes!
[19:54] <mbruzek> Get your questions ready
[19:55] <jcastro> alright everyone
[19:55] <jcastro> office hours will be here:
[19:55] <jcastro> https://plus.google.com/hangouts/_/hoaevent/AP36tYcQcnwaxPGDuxmx79tlvIS_t0-VO_fVra2LczPA5s6AKp8i7w
[19:55] <jcastro> if you want to jump in ^^^
[19:55] <jcastro> http://ubuntuonair.com if you just want to listen.
[20:03] <marcoceppi> Feel free to ask questions if you're watchin!
[20:04] <cory_fu> https://insights.ubuntu.com/2015/07/21/introducing-kubernetes-version-1-0/
[20:05] <cory_fu> https://www.youtube.com/watch?v=UUFGoWMPXWE
[20:05] <cory_fu> Those links courtesy of mbruzek
[20:15] <lazyPower> the google repository for upstream kubernetes for hacking on as a developer: https://github.com/googlecloudplatform/kubernetes
[20:16] <lazyPower> which is being demo'd now
[20:16] <lazyPower> if you just want to kick the tires of Kubernetes in a cloud - we have a bundle ready for you https://jujucharms.com/u/kubernetes/kubernetes-cluster/7
[20:21] <cory_fu> http://charmsreactive.readthedocs.org/en/latest/
[20:33] <mbruzek> Any questions for Juju office hours?
[23:25] <bhundven> is this a directory that the juju package should make? machine-0: 2015-07-30 23:20:52 DEBUG juju.wrench wrench.go:112 couldn't read wrench directory: stat /var/lib/juju/wrench: no such file or directory
[23:30] <bhundven> I've seen that message with 1.22 (ubuntu package) and 1.24 (ppa:juju/stable)