[12:32] <hazmat> kurt_, you can file bugs against the gui charm directly against the upstream (launchpad.net/juju-gui)
[12:33] <hazmat> kurt_, whyat i don't understand is why its problematic to deploy the gui on an lts instead of quantal for your use case
[21:18] <kurt_> Does anyone know if keystone works off the shelf in Precise with juju-gui?
[21:19] <thumper> I don't know what is worse, saying "No" or saying nothing...
[21:19] <thumper> all I can say is I don't know
[21:19] <thumper> but someone may :)
[21:19] <kurt_> :)
[21:20] <kurt_> seeing an error about missing config option for vip
[21:20] <kurt_> 2013-08-18 14:16:11,995 unit:keystone/3: unit.hook.api INFO: FATAL ERROR: ERROR: Config option has no paramter: vip
[21:20] <kurt_> but in the nice pretty demo I look at that Mathew Scott put together, it appears to work off the shelf
[21:26] <weblife> I want to use juju within the free tier of AWS but when I run : juju bootstrap --constraints "instance-type=t1.micro"  I am getting the following error :  error: invalid value "instance-type=t1.micro" for flag --constraints: unknown constraint "instance-type"
[21:26] <weblife> Has something changed? Or what the heck am I doing wrong?
[21:44] <jrwren> weblife: have you not bootstrapped?
[21:48] <weblife> I am trying to bootstap to a t1.micro and not a m1.medium
[21:49] <weblife> according to the documentation this should be legal: juju bootstrap --constraints "instance-type=t1.micro"
[21:50] <thumper> weblife: the new juju, version 1.x doesn't support instance-type constraints yet
[21:55] <weblife> thumper: blah(lol), thank you.  I wanted to use it on the AWS free tier.  Just got a bill for $247 because I didn't realize they charge on anything higher than t1.micro. Luckily they waived it this time once I called them.
[22:04] <marcoceppi> weblife: you can specify mem=128 to get a micro
[22:05] <marcoceppi> weblife: it's also only 700 hours of micros a month. so if you run 14 micros for 50 hours each additional hour per machine is billed to you
[22:06] <marcoceppi> personally, I found hpcloud to be way cheaper. with local provider being the cheapest :)
[22:09] <weblife> marcoceppi: you life saver, its actually 750 now.  I am looking into trying to use it to deploy a single website on 1 server,  kinda defeats the purpose of using juju i know.
[22:24] <weblife> marcoceppi: it actually launched a m1.small instance when using that constraint.  Thank you. Guess I'll have to wait for the 2.0 bootstrap change or whatever option appears for this.  HPCLOUD only allows 1 instance free per month for the first three months(blah). I see what your saying though for larger go-live deployments though, thanks for that tip.
[22:26] <marcoceppi> weblife: there's a way to get a micro using constraints. I think the cpu-power needs to be tweaked too. Try setting cpu-power, cpu-cores to 0 and mem really low (it'll find the next highest match) like 128, 256
[22:54] <weblife> marcoceppi:  that worked.
[23:11] <jrwren> weblife: what settings got you to micro?
[23:15] <weblife> juju bootstrap --constraints "cpu-power=0 cpu-cores=0 mem=128" : Hard to say which actually pushed it to t1.micro as marcoceppi mentioned it will find the highest match but my bet is on cpu-cores=0. Try to find out for sure in a little bit for you.
[23:26] <weblife> kinda strange, I don't know how doing a 'make -j' would react on other services but with ec2 it makes the compiler error.
[23:27] <kurt_> Anyone know what the correct openstack nova-compute distro to use with juju-gui is?
[23:28] <kurt_> I've tried essex, folsom and grizzly and on folsom and grizzly getting some 403 errors
[23:28] <kurt_> http://pastebin.ubuntu.com/6001151/
[23:29] <weblife> kurt_ not sure but I know with node-app you sometimes need to refresh once or twice to get it going
[23:30] <kurt_> weblife: yes, I've tried a few times.  I don't know enough about repositories to know if I need to add something or not