[00:08] <stokachu> ah just needed a little more memory
[00:12] <marcoceppi> hazmat: cand you define a series per service or is it all or nothing with deployer?
[00:28] <hazmat> marcoceppi, you can do series per service, its not obvious.. the series at the service container level was inherited.
[00:29]  * hazmat looks up the mechanics
[00:29] <marcoceppi> hazmat: oh, awesome. Everytime I think I hit a snag in deployer, you come by to remind me how awesome it is
[00:29] <hazmat> oh.. its got warts.. but it does the trick more often that not
[00:30] <hazmat> marcoceppi, so it can't do vcs from multiple series.. but it can pull charmstore charms from multiple series
[00:31] <hazmat> marcoceppi, also you can override series on the cli
[00:31] <hazmat> but for mixed mode usage you need charm store charms
[00:31] <marcoceppi> hazmat: :\ so vcs (branch) is tied to parent series level? I'm trying to to mixed vcs
[00:33] <hazmat> marcoceppi, not yet.. it looks like its a pretty simple fix though.. if you want to file a bug.. i can work on it tomorrow during my flight.
[00:34] <marcoceppi> hazmat: sure, we may also be able to spend a few cycles working on the bug
[00:35] <hazmat> marcoceppi, no worries.. i've got some other pending items i should take care of on it tomorrow as well
[00:35] <marcoceppi> hazmat: https://bugs.launchpad.net/juju-deployer/+bug/1309274
[00:35] <_mup_> Bug #1309274: Can't override series for branch: defined services <juju-deployer:New> <https://launchpad.net/bugs/1309274>
[00:35] <hazmat> marcoceppi, thanks
[00:35] <marcoceppi> thank you!
[00:35] <hazmat> marcoceppi, but i'm not tackling tonight if your inclined that way ;-)
[00:36] <hazmat> np
[00:36] <marcoceppi> hah, that's fine, I'm too busy with the little doc fixes, still trying to wrap my head around python-markdown extensions
[08:11] <sridher> Will installed cache of local lxc  trusty, freshly download stable release of upgrade the old cache downloaded 3 days ago
[08:12] <sridher> ?
[08:13] <sridher> Download/replace or upgrade?
[12:59] <strikov> Hi guys. I'm using juju with openstack. I have use-floating-ip: 'true' which means that all instances get floating ip addresses during bootup. Is it possible to ask juju and charms to use these floating addresses to communicate between instances? Right now one of my instances tries to connect to bootstrap instance by its local ip and fails. But it'd connect fine if it uses floating ip of the bootstrap instance. Thanks.
[15:26] <Tug> Hi, I can't access the doc at https://juju.ubuntu.com/docs/getting-started.html
[15:29] <timrc> Tug, docs/ seems completely missing
[15:29] <timrc> :(
[15:30] <Tug> yep :(
[15:30] <timrc> jcastro, ^^^
[15:30] <jcastro> fixing it now
[15:30] <jcastro> there was a problem with the bzr branch
[15:30] <jcastro> give us like 5 minutes
[15:30] <Tug> no pb, thx :)
[15:33] <jcastro> Tug, all set
[15:37] <Tug> yes, working fine :)
[15:51] <jose> jcastro: everything's set for today's charm school, ubuntuonair.com will be updated 1h before the session
[15:52] <jcastro> <3
[15:53] <Tug> is juju supported on ubuntu 14.04 ?
[15:53] <Tug> I'm having errors :(
[15:56] <mbruzek> ping hazmat
[15:56] <marcoceppi> Tug: it is, what problems are you having?
[15:57] <mbruzek> cory_fu, and I are working on an amulet bug that the sentries are not created with the right series.  You and marcoceppi talked about a deployer bug that would not accept series.
[15:57] <cory_fu> https://bugs.launchpad.net/juju-deployer/+bug/1309274
[15:57] <_mup_> Bug #1309274: Can't override series for branch: defined services <juju-deployer:New> <https://launchpad.net/bugs/1309274>
[15:57] <marcoceppi> mbruzek: I think he may be traveling
[15:58] <mbruzek> Oh
[15:58] <mbruzek> marcoceppi, cory_fu and I came up with this JSON output after our code change.
[15:58] <mbruzek> http://pastebin.ubuntu.com/7276643/
[15:58] <mbruzek> marcoceppi, Does this look right?
[15:58] <mbruzek> It does not work, but we suspect that is due to the deployer bug.
[15:58] <marcoceppi> sure, but it's not going to work because of deployer
[15:59] <marcoceppi> mbruzek: you guys might be able to patch deployer while hazmat works on the bug
[15:59] <Tug> no it's alright, I needed to export GOPATH
[15:59] <mbruzek> marcoceppi, that is what we suspect.  Are we building the JSON correctly?
[16:00] <marcoceppi> mbruzek: ¯\_(ツ)_/¯ looks good to me
[16:22] <ghartmann> did anyone else came across an error "cannot start machine X: no matching tools available" ?
[16:34] <lazyPower> ghartmann: series? juju version?
[16:35] <ghartmann> ubuntu 3.10 -> juju 1.18.1-saucy-amd64
[16:36] <lazyPower> hmm. which environment are you working against?
[16:36] <ghartmann> local
[16:36] <lazyPower> give me a few to spin up a VM. I need to fetch an iso. I'll see if i can reproduce
[16:37] <ghartmann> I can check for logs if you want
[16:37] <lazyPower> if i cant, i'm going to blame the cached stuff. You've successfully bootstrapped before right? this is a new'ish problem?
[16:38] <ghartmann> yeap
[16:38] <ghartmann> how can I clean the cache ?
[16:38] <ghartmann> this env is my test env do I don't care reinstalling it
[16:40] <lazyPower> ghartmann: interesting... my dev environment is running 13.10 as well
[16:40] <ghartmann> I think it might be related with the upgrade
[16:41] <lazyPower> and apparently i just upgraded to 1.19
[16:41] <lazyPower>  ¯\_(ツ)_/¯
[16:42] <ghartmann> I had an env setup with 1.17 and upgraded 1.18
[16:42] <lazyPower> ghartmann: well, i can verify its working with 1.19
[16:42] <ghartmann> you are using the new ppa ?
[16:43] <lazyPower> i am, i have the dev ppa enabled
[16:45] <ghartmann> I will make the upgrade now
[16:57] <Tug> what are simplestreams ?
[17:01] <Tug> ok found the definition here :) https://juju.ubuntu.com/docs/howto-privatecloud.html
[17:05] <ghartmann> well it isn't solved
[17:05] <ghartmann> how do I clear juju cache ? I am planning to try a full reinstall
[17:09] <Tug> is it not the ~/.juju folder ?
[17:09] <ghartmann> ah, I had tried it
[17:09] <ghartmann> I am going for remove/purge
[17:10] <ghartmann> restart/reinstall
[17:10] <ghartmann> back in a few seconds
[17:16] <Tug> $ juju-quickstart
[17:16] <Tug> juju-quickstart: error: cannot use the amazon environment:
[17:16] <Tug> a value is required for the control bucket field
[17:18] <Tug> I have a value for "control-bucket" in /home/polo/.juju/environments/amazon.jenv if that's what it's talking about
[17:24] <Tug> I copied it when running juju-quickstart -i and it seems to work
[17:25] <Tug> I'm not sure why juju-quickstart saw it empty, maybe it used a different file
[17:27] <rick_h_> Tug: I think it's checking the environments.yaml field. I'm not sure if it looks into the jenv files as those can be recreated and such
[17:30] <Tug> oh no I see! in fact it has overwritten my environments.yaml
[17:31] <Tug> apparently it did copy my keys but not the region
[17:32] <rick_h_> Tug: what overwrote it?
[17:34] <Tug> juju-quickstart
[17:35] <rick_h_> Tug: please file that as a bug please. It should not do that
[17:35] <rick_h_> if it missed a field it needs to be updated to correct for that.
[17:35] <Tug> when running juju-quickstart -i it was able to somehow retrieve my current keys to connect to amazon but it ignored the other parameters
[17:35] <rick_h_> https://bugs.launchpad.net/juju-quickstart
[17:35] <rick_h_> oh, it ignores ones it doesn't know about, but if it lost or changed one it shold not have that's a bug
[17:36] <Tug> yeap probably
[17:37] <Tug> I can't access https://bugs.launchpad.net/juju-quickstart though
[17:37] <rick_h_> hmm, seems launchpad is having issues atm
[17:38] <Tug> yeah probably due to everyone's updating their ubuntu ?
[17:54] <rick_h_> Tug: launchpad is back up and responding for me if you've still got time to file that bug
[17:58] <Tug> ok doing it now
[18:01] <rick_h_> thanks Tug, really appreciate it
[18:13] <Tug> not sure I did things correctly
[18:13] <Tug> https://bugs.launchpad.net/juju-quickstart/+bug/1309678
[18:13] <_mup_> Bug #1309678: a value is required for the control bucket field <juju-quickstart:New> <https://launchpad.net/bugs/1309678>
[18:13] <Tug> first time reporting a bug in launchpad
[18:14] <rick_h_> Tug: sweet, congrats.
[18:14] <Tug> :) thx
[18:49] <lazyPower> Hey Jose, looks like jcastro isn't going to be back in time for this charm school
[18:49] <lazyPower> do you mind being my stand in announcer?
[18:49] <jose> sure, no worries, just let me set up my environment and I'll be there in 2mins
[18:55] <arosales> jose: to confirm are you setting up ubuntu on air for the upcoming juju plugins charm school?
[18:55] <jose> arosales: you mean, hosting, or setting it up?
[18:55] <jose> I can do both
[18:56] <arosales> for sure setting up, but hosting too if you are free
[18:56] <lazyPower> if anyone else wants to join the party.. speak up
[18:56] <jose> arosales: cool. I'll be hosting then
[18:56] <lazyPower> its goign to be a quick one. juju run is hyper handy but it'll be difficult to fill up the hour with just run
[18:56] <jose> arosales: just remind me the dates? I don't see it on my calendar
[18:57] <arosales> jose: roughly in 4 minutes
[18:57] <arosales> lazyPower: correct?
[18:57] <jose> arosales: isn't that one for juju ru?
[18:57] <lazyPower> yup
[18:58] <arosales> jose: Ya the OSX workflow got reschedule due to some juju box issues
[18:58] <jose> ok, all good then
[18:58] <arosales> so lazyPower was going to do a charm school on juju plugins and juju run
[18:58] <arosales> jose: in about 2 minutes :-)
[18:58] <jose> it's all good
[18:58] <arosales> jose: could you also share the hangout link if folks want to join directly
[18:59] <jose> https://plus.google.com/hangouts/_/ytl/vjVQa1PpcFP7bsYUNPvWzGCOUoWT528fqaHA2KZS4zU= that is
[19:00] <arosales> cory_fu: ^
[19:00] <arosales> jose: thanks
[19:07] <mbruzek> Question for lazyPower:  Where would I put scripts if I want to be able to run them with juju run?
[19:11] <mbruzek> juju run --unit mediawiki/0 'pwd'
[19:11] <mbruzek> lazyPower, ^^
[19:13] <jcastro> hi guys, sorry I am late!
[19:17] <arosales> jose: nice back ground btw
[19:17] <jose> arosales: thank you :)
[19:17] <arosales> jcastro: no worries jose has us rolling
[19:17] <jose> jcastro: any questions about juju run?
[19:18] <jcastro> not really, I <3 it
[19:20] <lazyPower> woo
[19:20] <arosales> jose: thanks for hosting us
[19:20] <lazyPower> lightning fast with the juju run
[19:20] <mbruzek> great job Jose!
[19:20] <jose> no worries :)
[19:20] <lazyPower> juju run jose-hoster
[19:20] <arosales> lazyPower: thanks for the educations
[19:20] <lazyPower> COMMAND BROKE 9000
[19:21] <lazyPower> so... arosales i was thinking
[19:21] <lazyPower> its about time for me to bequeath the title of charm bot 5000 to Jose... based on his RevQ work, and now he's starting to look at the audit efforts and writing tests
[19:21] <lazyPower> any objections?
[19:23] <arosales> lazyPower: just a name right?
[19:23] <lazyPower> oh dude, its more than just a name
[19:23] <lazyPower> its a birth right
[19:23] <arosales> lol
[19:23] <lazyPower> he's earned it
[19:23] <arosales> bequeth away then
[19:23] <mbruzek> I second that Jose is awesome
[19:24] <jose> :)
[19:24] <arosales> +1 thanks jose for you work on charms
[19:25] <jose> no worries, glad I could help :)
[19:25]  * jose registers CharmBot5000 on freenode
[19:25] <mbruzek> I want to know where jose  got that nice orange background
[19:25] <lazyPower> oh hey, i missed the timeout flag on juju run. so go ahead and run juju rum vim /etc/hosts -- it'll time out in 5 minutes by default.
[19:25] <lazyPower> s/rum/run
[19:25] <lazyPower> can you tell where my head is? its 5pm somewhere.
[19:25] <jose> mbruzek: orange wall was painted by myself, design was made by the Canonical Design Team (it's the same they have in London), and printed in vinyl
[19:26] <mbruzek> very nice
[19:26] <jose> there's a Juju pictogram somewhere around it
[19:26] <lazyPower> jose: how much would you charge me to come paint my office with that gnarly pictogram?
[19:27] <jose> lazyPower: plane ticket + hotel + food + $300
[19:27] <lazyPower> mbruzek: you got my tab right?
[19:27] <jose> and a trip to DisneyLand
[19:27] <mbruzek> I will cover lazyPower's expenses up to $20
[19:27] <lazyPower> woo
[19:47] <jose> lazyPower: that warning you got about adding IPs to known host list, it was because it was the first time connecting to the instance via ssh
[19:48] <lazyPower> Learning all kinds of good stuff today
[20:12] <jose> lazyPower: have a min?
[20:36] <lazyPower> jose: sfeole <-
[20:38] <jose> sfeole: https://code.launchpad.net/~jose/charms/precise/teamspeak3/1297650-fix - lp:~jose/charms/precise/teamspeak3/1297650-fix
[20:47] <sfeole> jose: another thing i just remembered is that when EC2 creates instances make sure that the security group assigned to that instance is not blocking port 9987
[20:48] <jose> sfeole: will deploy again and test in a minute
[21:03] <jose> sfeole: found the error, port was udp
[21:03] <sfeole> jose: great!  were you able to connect?
[21:03] <jose> sfeole: yep
[21:05] <sfeole> jose: awesome!  you changed that in the EC2 Network & Security panel ?
[21:05] <jose> sfeole: nope, the error was on the charm, and the EC2 security group had the port in both tcp and udp opened, so I could connect
[21:06] <jose> oh, no, it only had tcp opened
[21:06] <jose> I opened udp by doing open-port
[23:46] <lazyPower> jose: hi5 on finding the fix
[23:46] <jose> o/
[23:46]  * sarnold whistles
[23:46] <sarnold> what a charmbot
[23:46] <jose> haha, hey sarnold
[23:46] <sarnold> :)
[23:48]  * lazyPower snickers
[23:48] <axisys> trying to start a instance on ec2 and getting this error
[23:48] <axisys> $ juju deploy --constraints="instance-type=m1.large" hadoop hadoop-master
[23:48] <axisys> error: invalid value "instance-type=m1.large" for flag --constraints: unknown constraint "instance-type"
[23:49] <axisys> what gives
[23:49] <axisys> ?
[23:49] <jose> axisys: try ec2-instance-type
[23:49] <jose> otherwise, let me find the other way's details
[23:49] <axisys> error: invalid value "ec2-instance-type=m1.large" for flag --constraints: unknown constraint "ec2-instance-type"
[23:49] <axisys> following this
[23:49] <axisys> http://javacruft.wordpress.com/2012/08/16/charming-hadoop/
[23:49] <lazyPower> axisys: constraints have changed since 2012
[23:50] <lazyPower> axisys: juju.ubuntu.com/docs -- constraints now use cpu and memory mapping to determine the instance type
[23:50] <jose> ok, I'm finding the values
[23:50] <lazyPower> so, specify the mem limit, which i think is 4g on a large
[23:50] <axisys> lazyPower: I am running from ubuntu 14.04 64bit lts
[23:50] <axisys> lazyPower: ok
[23:50] <jose> also, I don't see an  m1.large, it's m3.large
[23:51] <jose> --constraints "mem=4G" should do
[23:51] <jose> (if that's the case)
[23:51] <axisys> worked!
[23:51] <lazyPower> boom!
[23:51] <jose> awesome :)
[23:51] <axisys> I tried with 1G
[23:51] <axisys> thanks
[23:52] <lazyPower> axisys: its all abstracted so they work from provider to provider without much muxing with flags.
[23:52] <lazyPower> so whatever you use to deploy to amazon will work with maas, openstack, etc.
[23:52] <lazyPower> sarnold: nice namedrop on the charmbot 5000 reference
[23:53] <sarnold> I think there's a typo on https://juju.ubuntu.com/docs/charms-constraints.html -- "cpu-power=0 cpu-power=0"
[23:53] <sarnold> lazyPower: hehe thanks :)
[23:53] <jose> sarnold: let me check and I'll commit a fix
[23:53] <jose> on the work
[23:53] <sarnold> woo
[23:54] <axisys> lazyPower: will it work with lxc ?
[23:54] <lazyPower> axisys: lxc doesn't really have "constraints" as it shares resources with the host
[23:56] <axisys> lazyPower: right.. make sense..
[23:57] <axisys> lazyPower: so what is the environemnt for lxc ? local?
[23:57] <axisys> I do not see it in ~/.juju/environment.yaml
[23:57] <lazyPower> yeah, LXC is the local environment
[23:57] <lazyPower> make sure you have the juju-local package installed if you want to use it.
[23:58] <axisys> its there
[23:58] <axisys> I am on 14.04 .. I guess it comes with it?
[23:59] <lazyPower> Possible.