[13:39] <marcoceppi> jamespage mgz what would it take to get charm-tools in backports?
[13:39] <jamespage> marcoceppi, just a bit of testing in older releases and a backport request
[13:39] <jamespage> its quite lightweight
[13:40] <jamespage> marcoceppi, 'requestbackport' is the tool
[13:40] <marcoceppi> jamespage: awesome, thanks
[13:41] <jamespage> marcoceppi, best thing todo would be to get it in a good state in saucy and then request backport to 12.04->13.04
[13:41] <jamespage> marcoceppi, https://wiki.ubuntu.com/UbuntuBackports
[13:41] <jamespage> documents the process
[13:50] <jcastro> scuttlemonkey: http://www.jorgecastro.org/2013/04/29/13-reasons-to-deploy-with-ubuntu-server/
[13:50] <jcastro> scuttlemonkey: does that earn me a RT since I mention ceph? :)
[13:55] <jcastro> hey gary_poster
[13:55] <jcastro> We'd like to put the gui instructions on the getting started page so people can deploy it right away
[13:56] <jcastro> any gotchas or should I just add what we put in the charm's README there?
[13:58] <gary_poster> jcastro, on call but the README should work *except* for jitsu deploy-to.  juju core version does not support deploying to machine 0 ATM, but I think they will open that up
[13:59] <scuttlemonkey> jcastro: haha, fosho :)
[14:02] <jcastro> gary_poster: I'm not even going to mention the jitsu part.
[14:05] <gary_poster> jcastro, cool!  go for it.  thanks
[14:25] <andreas__> jcastro: do you have a recording of last friday's charm school?
[14:28] <jcastro> it's not last friday
[14:28] <jcastro> it's this friday
[14:35] <andreas__> jcastro: ah, ok
[14:35] <jcastro> it will be recorded
[14:35] <jcastro> and I will announce that
[14:36] <andreas__> hm, juju-core question. Is juju set <service> key=value supposed to work on units that are in an error state?
[14:37] <andreas__> specifically, mine failed in the install hook, and juju set would fix it
[14:37] <andreas__> hm, maybe a set followed by retry
[14:37] <ahasenack> yep, works
[14:38] <sidnei> ahasenack: set + retry should work
[17:20] <rshade98> anyone know why this would start happening
[17:20] <rshade98> ERROR state: TLS handshake failed: x509: certificate signed by unknown authority
[17:59] <benji> I'm a bit surprised to get this error message:
[17:59] <benji> 2013-04-29 12:58:45,726 ERROR Bad 'instance-type' constraint 'hs1.8xlarge': unknown instance type
[18:00] <benji> is this a known issue?
[18:09] <marcoceppi> benji: what provider?
[18:09] <benji> marcoceppi: ec2
[18:21] <rshade98> ok two problems I ran into with an ec2 environment.
[18:22] <rshade98> I need a way to only bootstrap the certs, without getting the environment already setup error. And now that I have the certs my handshake fails. Any ideas?
[19:11] <jcastro> marcoceppi: arosales just got a text from Mims
[19:11] <jcastro> he's found a "good example stack on rack"
[19:12] <jcastro> (he's at railsconf)
[19:40] <arosales> jcastro, good to hear :-)
[19:40] <arosales> keep rock'in it m_3
[19:43] <jcastro> I envision him going like booth to booth or something. "excuse me sir, can you look at my charm?"
[21:54] <arosales> jcastro, its reverse people are stopping by where they they here they here the doctor is at asking to see his charm.
[22:53] <mwhudson> hi
[22:53] <mwhudson> i have wordpress deployed
[22:53] <mwhudson> but i'm accessing it via ssh port forwarding
[22:54] <mwhudson> and wordpress is generating links without the port so css etc doesn't work
[22:54] <mwhudson> is there something simple i can do about this, or is wp just dumb?
[23:11] <sarnold> mwhudson: on a first guess, it sounds to me like you may have chosen a poor replacement for an http proxy :)
[23:12] <mwhudson> heh well
[23:12] <mwhudson> generating urls with a hostname in when you don't have too is kinda daft too
[23:17] <sarnold> mwhudson: okay, that bit makes sense.
[23:45] <marcoceppi> mwhudson: yeah, wordpress is being pretty dumb
[23:46] <mwhudson> you'd think such a high profile piece of softwa...
[23:46] <mwhudson> oh never mind
[23:46] <marcoceppi> We actually had this problem early on when re-working the WordPress charm. Instead of using the URL of the  "primary" peer, all the URLs were re-written to be nginx-backend:8080
[23:46] <marcoceppi> which breaks quite a few things
[23:47] <mwhudson> ha
[23:47] <marcoceppi> As a stop-gap we wrote a plugin that basically utlized the pre-render hook to rewrite all URLs on the page
[23:47] <marcoceppi> That's not needed anymore, thankfully, I can't actually remember how we fixed it
[23:48] <marcoceppi> So, you could write a plugin that basically just rewrites all the URLs to be relative
[23:48] <mwhudson> given i only have wordpress installed because it's the "hello world" of juju
[23:48] <mwhudson> i'll pass i think
[23:48] <marcoceppi> mwhudson: sounds like a wise decision
[23:49] <marcoceppi> but! Sounds like your deployment worked out pretty well
[23:49] <mwhudson> yeah
[23:49] <mwhudson> it was a fight on several levels but it seems to be working now
[23:50] <mwhudson> (with pyju, goju isn't quite there on arm it seems)
[23:50] <mwhudson> the last bit of fun was that cloud-init really really wants the fqdn to have a dot in
[23:50] <mwhudson> so i had to make it so that $hostname.localdomain resolved in dnsmasq