[00:00] 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] so there are some idempotency issues with the install hook as well. [00:01] lazyPower: so, even if not setting a domain name, it did run successfully before [00:01] just failed here, I'm checking [00:01] 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] 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] lazyPower: ^ [00:02] that's the error preventing it from finish [00:02] yeah. Give it s'more TLC and I'll recheck. I'm going to log out for the day. [00:02] its 8:00pm here local - long day [00:03] have a nice weekend! :) [00:03] and thanks again! [00:03] but if you need anything, email me, ping me, whatever :) [00:03] i'm happy to help [00:03] tc o/ have a good weekend === yo61_ is now known as robinbowes === blackboxsw is now known as 6JTAAB1LO === freeflying__ is now known as freeflying === allenap_ is now known as allenap === JoshStrobl is now known as 1JTAAP0WF === robinbowes is now known as yo61 === erkules_ is now known as erkules [03:04] anyone know how to build the juju binary from source? mine's getting hung up on the gwacl error [03:05] I asked in dev but it's quiet tonight [03:06] 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] ah, I see the problem [03:08] I need more cores [03:08] :{ [03:18] that's very, very different from all the lit I've seen saying to simply "go get launchpad.net/juju-core"... [03:18] but, I guess if it builds it builds [04:55] http://paste.ubuntu.com/7093712/ ==> status: pending ?! [05:01] ^ [05:10] "1.17.5.1", heh, the version looks like an ip.. [05:29] onrea: is your instance stuck in the pending state? [05:30] sarnold: wish me luck, i just applied for charmer status [05:30] * lazyPower crosses fingers [05:31] lazyPower: ooh! cool! [05:32] :) [05:51] lazyPower: When I run "watch juju status", nothings happens === robinbowes is now known as yo61 === Ursinha is now known as Ursinha-afk [18:06] geekmush1, ping [18:07] hey! still haven't circled back to juju yet … had a webserver get compromised, so have been doing that fire drill [18:07] (wasn't my fault! WP bad install, I think) [18:08] any updated for me to grab, tho? [18:08] geekmush1, no worries. [18:08] geekmush1, so i wanted to double check the version of juju you were using [18:09] geekmush1, afaics juju hadn't been initialized on that machine.. or your using something older than 1.17 [18:09] and 1.17 + is a pre-req for docean provider [18:09] I don't have the juju server up right now, but as I recall, it was the juju development apt repo [18:09] geekmush1, no worries.. i still see somethings i can fix up which i'll work on. [18:10] trying to play around with openstack dev in containers atm [18:10] cool … let me know! :) [18:16] wait, is there an actual docean provider now? [18:16] I thought it was manual provider [18:16] bodie_, its a plugin that automates digital ocean via manual provider [18:17] hm [18:17] but you still have to have already created the VM nodes right? [18:17] bodie_, ie.. bootstrap/add-machine/terminate-machine/destroy-environment via the plugin do the right thing wrt to do [18:17] bodie_, no.. it creates them for you using the do api [18:17] oh... I misread the docean walkthrough then, or i'm confused in some other way [18:17] bodie_, its not an actual provider.. its a client side provider [18:18] bodie_, ie.. you have to juju docean add-machine before doing juju deploy/add-unit [18:18] ohhhhh [18:18] I misunderstood that as actually adding the machine yourself on digitalocean [18:18] which really seemed to defeat the purpose, heh [18:18] hmm.. maybe i should clear up the docs there [18:18] oh, is that yours? [18:18] nice work if so [18:18] bodie_, yeah [18:19] the lxc plugin is the one i'm using on a daily basis.. manual provider + lxc-clone w/ snapshot. [18:19] why not make juju deploy do an add-machine first, if it's not there already? [18:19] yeah, that's pretty cool for sure [18:19] 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] bodie_, deploy relies on the provider on the state server to allocate the actual machine if one is not already available [18:20] bodie_, give it a whirl then.. feedback always welcome [18:20] I see [18:20] and since it's manual, it wouldn't know how [18:20] yup [18:20] in fact it throws an error on deploy now w/ manual === Ursinha-afk is now known as Ursinha === bodie_ is now known as bodie_|notaway === bodie_|notaway is now known as bodie_|notaway|t === bodie_|notaway|t is now known as bodie_ === bodie_ is now known as nackpaddywhack === nackpaddywhack is now known as bodie_ === allenap_ is now known as allenap === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away