[00:00] <lazyPower> jose: you know what I didnt do? I didn't set a domain name, then I re-ran the hook after it initially enabled the site
[00:00] <lazyPower> so there are some idempotency issues with the install hook as well.
[00:01] <jose> lazyPower: so, even if not setting a domain name, it did run successfully before
[00:01] <jose> just failed here, I'm checking
[00:01] <jose> 2014-03-15 00:00:00 INFO juju.worker.uniter context.go:255 HOOK /var/lib/juju/agents/unit-mailman-0/charm/hooks/install: line 150: warning: here-document at line 126 delimited by end-of-file (wanted `EOL')
[00:01] <jose> 2014-03-15 00:00:00 INFO juju.worker.uniter context.go:255 HOOK /var/lib/juju/agents/unit-mailman-0/charm/hooks/install: line 151: syntax error: unexpected end of file
[00:01] <jose> lazyPower: ^
[00:02] <jose> that's the error preventing it from finish
[00:02] <lazyPower> yeah. Give it s'more TLC and I'll recheck. I'm going to log out for the day.
[00:02] <lazyPower> its 8:00pm here local - long day
[00:03] <jose> have a nice weekend! :)
[00:03] <jose> and thanks again!
[00:03] <lazyPower> but if you need anything, email me, ping me, whatever :)
[00:03] <lazyPower> i'm happy to help
[00:03] <lazyPower> tc o/ have a good weekend
[03:04] <bodie_> anyone know how to build the juju binary from source?  mine's getting hung up on the gwacl error
[03:05] <bodie_> I asked in dev but it's quiet tonight
[03:06] <sarnold> bodie_: you could check out the build logs, they may have some guidance about what you've overlooked: https://launchpadlibrarian.net/168405383/buildlog_ubuntu-trusty-amd64.juju-core_1.17.4-0ubuntu2_UPLOADING.txt.gz
[03:08] <bodie_> ah, I see the problem
[03:08] <bodie_> I need more cores
[03:08] <bodie_> :{
[03:18] <bodie_> that's very, very different from all the lit I've seen saying to simply "go get launchpad.net/juju-core"...
[03:18] <bodie_> but, I guess if it builds it builds
[04:55] <onrea> http://paste.ubuntu.com/7093712/ ==> status: pending ?!
[05:01] <onrea> ^
[05:10] <sarnold> "1.17.5.1", heh, the version looks like an ip..
[05:29] <lazyPower> onrea: is your instance stuck in the pending state?
[05:30] <lazyPower> sarnold: wish me luck, i just applied for charmer status
[05:30]  * lazyPower crosses fingers
[05:31] <sarnold> lazyPower: ooh! cool!
[05:32] <lazyPower> :)
[05:51] <onrea> lazyPower: When I run "watch juju status", nothings happens
[18:06] <hazmat> geekmush1, ping
[18:07] <geekmush1> hey!  still haven't circled back to juju yet … had a webserver get compromised, so have been doing that fire drill
[18:07] <geekmush1> (wasn't my fault!  WP bad install, I think)
[18:08] <geekmush1> any updated for me to grab, tho?
[18:08] <hazmat> geekmush1, no worries.
[18:08] <hazmat> geekmush1, so i wanted to double check the version of juju you were using
[18:09] <hazmat> geekmush1, afaics juju hadn't been initialized on that machine.. or your using something older than 1.17
[18:09] <hazmat> and 1.17 +  is a pre-req for docean provider
[18:09] <geekmush1> I don't have the juju server up right now, but as I recall, it was the juju development apt repo
[18:09] <hazmat> geekmush1, no worries.. i still see somethings i can fix up which i'll work on.
[18:10] <hazmat> trying to play around with openstack dev in containers atm
[18:10] <geekmush1> cool … let me know!  :)
[18:16] <bodie_> wait, is there an actual docean provider now?
[18:16] <bodie_> I thought it was manual provider
[18:16] <hazmat> bodie_, its a plugin that automates digital ocean via manual provider
[18:17] <bodie_> hm
[18:17] <bodie_> but you still have to have already created the VM nodes right?
[18:17] <hazmat> bodie_, ie.. bootstrap/add-machine/terminate-machine/destroy-environment  via the plugin do the right thing wrt to do
[18:17] <hazmat> bodie_, no.. it creates them for you using the do api
[18:17] <bodie_> oh...  I misread the docean walkthrough then, or i'm confused in some other way
[18:17] <hazmat> bodie_, its not an actual provider.. its a client side provider
[18:18] <hazmat> bodie_, ie.. you have to juju docean add-machine before doing juju deploy/add-unit
[18:18] <bodie_> ohhhhh
[18:18] <bodie_> I misunderstood that as actually adding the machine yourself on digitalocean
[18:18] <bodie_> which really seemed to defeat the purpose, heh
[18:18] <hazmat> hmm.. maybe i should clear up the docs there
[18:18] <bodie_> oh, is that yours?
[18:18] <bodie_> nice work if so
[18:18] <hazmat> bodie_, yeah
[18:19] <hazmat> the lxc plugin is the one i'm using on a daily basis.. manual provider + lxc-clone w/ snapshot.
[18:19] <bodie_> why not make juju deploy do an add-machine first, if it's not there already?
[18:19] <bodie_> yeah, that's pretty cool for sure
[18:19] <bodie_> I use DigitalOcean a lot on my own, so I got really excited when I realized how simple juju would make that, until I thought I still had to make the VMs myself :S
[18:20] <hazmat> bodie_, deploy relies on the provider on the state server to allocate the actual machine if one is not already available
[18:20] <hazmat> bodie_, give it a whirl then.. feedback always welcome
[18:20] <bodie_> I see
[18:20] <bodie_> and since it's manual, it wouldn't know how
[18:20] <hazmat> yup
[18:20] <hazmat> in fact it throws an error on deploy now w/ manual