[00:00] hazmat, is the websocket module used by python-jujuclient available anywhere in the ubuntu archive? [00:00] adam_g, no [00:00] didnt think so. darn. [00:01] adam_g, andreas has a package/ppa for python-jujuclient [00:02] adam_g, https://launchpad.net/~ahasenack/+archive/python-jujuclient [00:04] hazmat, ah, thanks [00:13] hey marcoceppi or anyone around, is there a link to the charm design template? [00:13] s/design/icon/ [00:14] jose: yeah I just uploaded it for the docs, http://marcanonical.com/icon.svg [00:14] that section of the charm author docs should be landing soonish [00:14] great, thanks! :) [01:21] marcoceppi: how should I do the copyright? to Canonical Ltd.? [01:21] jose: no! You're the copyright holder :D [01:22] ok! [01:22] We jsut ask that, in order to be in the store, the charms are licensed under a free license [01:27] great [01:27] * jose continues working === cmagina is now known as cmagina-away === defunctzombie_zz is now known as defunctzombie [05:23] hi there [05:25] i cant find installation for juju local [05:25] *guide === defunctzombie is now known as defunctzombie_zz [05:39] aaaand, he's gone === Guest68009|Away is now known as CyberJacob === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz === CyberJacob is now known as CyberJacob|Away === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz === balloons_ is now known as balloons === jpds is now known as Guest46086 [11:10] hello, guys [11:11] can somebody help me with this error? [11:11] error: cannot start bootstrap instance: no "precise" images in us-west-2 with arches [amd64 i386] [11:11] juju version:1.11.2-precise-amd64 [11:25] ok, I switched to backported 1.10 and it works === victorp_ is now known as victorp [12:11] pavel, where are you pulling 1.11.2 from to get that issue? [12:11] pavel, there are some problems with earlier golang versions - I think we should have that fixed today... [12:14] jamespage, from devel ppa [12:15] pavel, yeah - looks like the amd64 builds are still waiting to go through [12:16] ~1hr - if that does not happen I'll go see if we can get the priority bumped [12:16] don't worry, 1.10 is ok for me [12:18] when I run bootstrap from amd64 it looks for amd64 machine in ec2? [12:18] or it runs amd64 by default? [12:23] pavel: I think this is an issue with the cloud images format having been changed, which breaks deploying on ec2 with 1.11 [12:23] wallyworld: ^is that the symptom? [12:24] yes [12:25] jamespage, looks like it s working now....i ll play with it a bit, adding master and stuff, just to see what happen. [12:29] melmoth, great [12:29] I'll propose that for merge [12:45] adam_g, merged both of your updated charm-helpers branches - thanks! [12:49] wallyworld, when you have some simplestreams juju-tools avaliable happy to test that for you [12:50] jamespage: awesome thanks. i'm waiting on some sample data to test with myself. will let you know when we are at the stage where it can be consumed [12:51] * jamespage thinks that is a real enabler [12:51] * wallyworld does too [12:51] for most cases, it will be configless for the user === cmagina-away is now known as cmagina [12:52] hm... was the 'debug-hooks' command removed from 1.10? [12:53] as in, was it in juju-core and removed? no. [12:53] it hasn't been implemented in the rewrite. [12:54] see bug 1027876 [12:54] <_mup_> Bug #1027876: cmdline: Support debug-hooks

[12:55] I see... [12:55] is there any guide to upgrade charms that was written for 0.7 to 1.10 ? [12:56] for example I see that structure of config.yaml changed a bit [12:57] pavel: no doc on charm relevent changes from pyjuju to gojuju that I'm aware of [12:57] evilnickveitch: ^is there anything along those lines? [12:57] pavel: that said, the aim was for charms to basically be compatible [12:58] I still didn't figure out why, but my overrides in custom config for service deployment doesn't override default value [12:58] now I changed format of config.yaml and trying again [12:59] well, that sounds familar [13:00] mgz, pavel there isn't anything on rewriting charms for 1.x as yet. But I would be happy to hear of any issues with that so I could include something [13:00] fwereade: ^what's the answer to default values not getting overridden? [13:01] pavel, mgz, I'm not familiar with that... any more detail? are you using a yaml file with --config? [13:02] evilnickveitch: I think several of the issues should just be bugs for us, but we have made several deliberate changes that we really should get recorded somewhere, I'll do some poking [13:02] mgz thanks [13:02] fwereade, yes it's yaml file, but named with .yml [13:03] maybe it's my fault, I have to try several options more [13:03] pavel, that shouldn't be a problem; but there was a format change there, we released accepting a format that didn't match python [13:03] pavel, the python format is `servicename: {...}` [13:03] yes, I found new format in the docs [13:04] pavel, huh, the docs included the new format? bah [13:04] new format for default values [13:04] charm: mediawiki service: mediawiki settings: {} [13:05] pavel, I am not familiar with that format at all, would you link me where it came from please? [13:05] ah [13:05] sorry [13:05] my mistake [13:05] phew :) [13:05] I looked at ' juju get mediawiki' [13:06] pavel, just one note: inside the charm, the name "config.yaml" is special, and configs with different filenames will not be picked up; so far as we are aware we have not changed how that works [13:07] yes, this is clear [13:07] pavel, but when you're specifying service config settings, the format of the file you pass to --config has changed back to how it was in python, after a regrettable period of incompatibility [13:07] for 1.10 it's service: {} [13:07] ? [13:07] pavel, however the file name there should not make any difference [13:07] pavel, for 1.10 it's just a naked map without the service name [13:07] gotcha! [13:08] pavel, sorry about that one :( [13:08] no problem, thanks a lot for your help [13:10] in the official docs it's service: {} now, thought the recommended installation is 1.10 [13:12] we may need a note there, though we can probably get 1.11 out to everywhere when it's release [13:12] d [13:17] is there a date for 1.11 release? [13:17] this week! [13:17] awesome === ahs3` is now known as ahs3 [13:21] I'm also getting the same error as pavel with juju trunk: error: cannot start bootstrap instance: no "precise" images in us-east-1 with arches [amd64 i386] [13:22] teknico: ec2 is borked right now as the cloud images data changed [13:22] teknico, *that* I am afraid to say is because the image metadata format on cloud-images.ubuntu.com changed unexpectedly [13:23] you can either use 1.10, or --upload-tools if you build locally [13:24] fwereade, mgz, thanks, I have i386 locally, can I still use --upload-tools? [13:25] fwereade, juju deploy ... --upload-tools ? [13:25] sorry, juju bootstrap --upload-tools ? [13:28] teknico: good question, not sure. [13:28] teknico, pavel: sorry, it's the ubuntu image metadata we've lost [13:28] teknico, pavel: so far as I'm aware the tools are all still around [13:29] pavel: yeah, bootstrap, but it's uploading your own builds (so, you need all the deps and so on locally) [13:29] crap, I'll wait for fix :) [13:29] ah, yeah, pants, probably not the right work around [13:30] ok, I'll downgrade too :-) === tris- is now known as tris [13:35] pavel, we are just waiting for someone to get in so we can figure out exactly what happened [13:37] fwereade, hope it will be an easy fix [13:37] pavel, it really should be but we want clarity and certainty so we actually unbreak it, rather than just breaking it differently === balloons_ is now known as balloons === xerxas_ is now known as xerxas [14:04] pavel: how did you switch back to 1.10? I can't come up with the right command [14:05] what ubuntu distro do you use? [14:08] pavel: I'm on raring [14:09] ok, then [14:09] sudo apt-get autoremove juju juju-core [14:09] sudo add-apt-repository -r ppa:juju/devel [14:09] sudo apt-get update [14:09] sudo apt-get install juju-core [14:10] pavel: thanks, but the devel ppa has 1.11.2, hasn't it? https://launchpad.net/~juju/+archive/devel [14:11] there is '-r' there [14:11] it's for removing [14:11] aah, right === rbasak_ is now known as rbasak === _mup__ is now known as _mup_ [14:20] pavel: it worked, thanks [14:21] np [14:26] pavel, teknico, others: smoser has resolved the image metadata issue and I am able to bootstrap again === cmagina is now known as cmagina-away === shadeslayer_ is now known as shadeslayer [14:36] fwereade, yes, it's working! [14:37] pavel, great, sorry for the problem in the first place [14:37] fwereade, thanks for such quick fix === teknico is now known as teknico-phone === cmagina-away is now known as cmagina [14:41] m_3_: new charm in the queue, mailman! [14:42] jcastro: ack === cmagina is now known as cmagina-away [14:55] pavel, direct all praise toward smoser please :) [14:56] smoser, thank you so much :) === vednis is now known as Guest75277 === shadeslayer is now known as Guest33135 === chelz1 is now known as Guest96808 === Guest33135 is now known as shadeslayer [15:45] jam: any chance you will get to bug 1189507? [15:45] https://bugs.launchpad.net/juju-core/+bug/1189507 [15:45] <_mup_> Bug #1189507: juju-core duplicates quantum security groups

[15:48] jam: soonish anways [15:55] Well be starting charm meeting soon! [15:58] http://ubuntuonair.com/ [16:04] http://pad.ubuntu.com/7mf2jvKXNa [16:05] kirkland, pad with notes is @ http://pad.ubuntu.com/7mf2jvKXNa [16:06] can you grant me an access? [16:06] pavel, to the google hangout? [16:06] arosales: thanks! [16:06] to the pad? or I don't need it? [16:07] you shouldn't need access, are you getting an error [16:07] Yes, I'm getting an error [16:07] is this correct hangout url? https://plus.google.com/hangouts/_/calendar/ajVxODVtbWk2dWp2anRpaTVzMW4zbGk1aW9AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ.p11le79ijn643h9hl7bmc36hbg [16:07] it's empty at the moment [16:08] pavel, try: https://plus.google.com/hangouts/_/b32ae1008a86dcde437cb82a07c95aa5edb9c329?authuser=0&hl=en [16:08] for the hangout [16:08] pavel, http://pad.ubuntu.com/7mf2jvKXNa for the pad with notes [16:08] pavel welcome, we see you now :-) [16:08] pavel, thanks for joining === defunctzombie_zz is now known as defunctzombie [16:28] jamespage, sorry we were just ending [16:28] arosales, yeah - I missed the time [16:28] np [16:29] arosales, was busy raising bugs on juju-core :-) [16:30] jamespage, well thats time well spent then :-) [16:35] marcoceppi, are you reserving the tests top-level directory for charm tests? [16:40] arosale, I'm not able to access pad [16:41] arosales, "Either you have not been granted access to this resource or your entitlement has timed out. Please try again." === paraglade_ is now known as paraglade [16:45] pavel, hmm .. . === medberry is now known as med_ [16:45] arosales, maybe smth is wrong with my ubuntu one account ) [16:46] pavel, let me check another lp account and see if they can access the pad [16:47] arosales, looks like it's issue with my account [16:47] pavel, ok ping me if you continue to have issues [16:48] arosales, I'll create a brand new account and try again [16:49] pavel, ugh. ok [16:51] arosales, still getting this error [16:53] pavel, "Either you have not been granted access to this resource or your entitlement has timed out. Please try again." is that the error [16:53] yes === cmagina-away is now known as cmagina [17:10] mgz, jamespage: How are we looking for a saucy upload? [17:14] Daviey: we really need a release first, which... is proving annoying, with several breakages, not all juju-releated [17:15] (eg, today, 1.11 hasn't been working on ec2, because the cloud images data got changed) [17:16] mgz: Honestly, i'd be happy if we got something nonfunctional into saucy right now. [17:16] There is always one more bug, delaying it. [17:16] this is true. [17:18] mgz / jamespage: Is there any reason we can't just upload the daily from the PPA? [17:18] (I know it's not quite reproducible source that i'd like) [17:23] Daviey: I don't think the ppa has "dailies" === defunctzombie is now known as defunctzombie_zz [17:25] it does have a recent build, though [17:30] ahasenack: https://code.launchpad.net/~dave-cheney/+recipe/juju-core ? === CyberJacob|Away is now known as CyberJacob_ [17:38] Daviey: nice, that's news to me [17:39] Daviey: so just the tools story isn't handled by that, meaning, if you push this into saucy, people will have to remember to bootstrap with --upload-tools === thomi_ is now known as thomi [17:42] Ugh [17:45] and, hm, that also won't work. They need a full development environment [17:45] in which case they already have juju-core installed by source [17:55] jamespage, where can i find the nvp-transport-node subordinate? [18:25] adam_g: jamespage: looks like charm-helpers tests are broken on revno 46 for systems without python-dnspython installed [18:30] wedgwood, gah, ok. ill take a look now [18:30] adam_g: jamespage http://pastebin.ubuntu.com/5862461/ [18:30] cool, thanks [18:31] wedgwood, actually, im working on cleaning up other stuff in that area. ill fix that as part of that [18:31] perfect === defunctzombie_zz is now known as defunctzombie [18:36] adam_g, lp:~james-page/charms/precise/nvp-transport-node/trunk [18:36] adam_g, you need access to NVP bits and pieces to make it work [18:36] jamespage, thanks [18:37] jamespage, cool. was trying to get the full picture when looking at the nova-c-c merge. im wondering if it might be a good idea to encapsulate all of the additional nvp config in an nvp subordinate, to keep nova-c-c's config.yaml minimal [18:37] dunno if that + the transport subordinate would be awkward [18:38] adam_g, maybe [18:38] the transport sub gets used on nova-compute and quantum-gateway nodes [18:38] not nova-cc [18:38] me thinks [18:40] jamespage, thinking out loud... would it be possible to use a single subordinate that can be related to all 3 services? if its related to nova-c-c, it just exports its nvp-related config. if its related to q-gateway + nova-c, it goes thru the installation === defunctzombie is now known as defunctzombie_zz [19:09] adam_g, that might work; however I'm concerned re the bits and pieces that configure quantum networking in ncc [19:09] what we are really talling about is a redux on the way we integrated quantum into nova [19:11] jamespage, hmm, i think a lot of that is going to change heavily anyway as soon as it moves to templating [19:12] adam_g, agreed - that might be the right point in time to make this happen [19:12] the pattern is similar to the cinder backends stuff we discussed a while back [19:12] adam_g, I think the nvp-transport-node sub stands as it is [19:13] adam_g, the other bits are less than ideal but I don't want to waste to much time pushing them in to charms which are going to be re-written anyway. [19:14] jamespage, im just thinking about when/if we have an NVP subordinate for nova-c-c, we'll have an aditional NVP subordinate for q-gateway and nova-compute. other quantum plugins would require the same, probaby. might be better to have 1 subordinate with multiple interfaces [19:15] adam_g, I don't disagree [19:15] so actually maybe a nvp suboridinate that does different things to different charms determined by relationship is a good idea [19:15] adam_g, how about we park the charms for the next few weeks while we figure this stuff out [19:16] (the NVP updates that is) [19:17] sounds good [19:19] https://code.launchpad.net/~gandelman-a/charm-helpers/ha_os_cleanup/+merge/174028 [19:19] wedgwood, that should fix the tests [19:20] jamespage, ^ theres some cleanup we talked about yesterday, gonna propose the context + templating next then start on the nova-c-c charm so we can figure out how we want to do the subordinates [19:27] adam_g: I'll defer to jamespage for landing. I see some lint issues - I know he'll mention them. [19:27] wedgwood, oh thanks for reminding me. :) [19:28] ;) === defunctzombie_zz is now known as defunctzombie [19:34] done === vednis is now known as Guest31918 === DarrenS is now known as Guest18637 === med_ is now known as Guest36906 === wedgwood is now known as Guest90326 === cmagina is now known as cmagina-away === cmagina-away is now known as cmagina === Guest90326 is now known as wedgwood === cmagina is now known as cmagina-away === CyberJacob_ is now known as CyberJacob_|Away [23:19] Can someone pls help with this error [23:19] 2013-07-10 23:18:06,519 ERROR SSH forwarding error: bind: Cannot assign requested address [23:19] Is it trying to connect to a bind server ? === CyberJacob_|Away is now known as CyberJacob [23:30] BeatsMusic: no, 'bind' in this case means bind(2) system call, to request a specific address [23:30] Just got that [23:30] thx [23:30] looks like juju can't connect to zookeeper [23:30] 2013-07-10 23:29:10,123 DEBUG Spawning SSH process with remote_user="ubuntu" remote_host="m03.ops.nyc1.beats" remote_port="2181" local_port="45778". 2013-07-10 23:29:10,239 ERROR SSH forwarding error: bind: Cannot assign requested address === defunctzombie is now known as defunctzombie_zz === cmagina-away is now known as cmagina === cmagina is now known as cmagina-away === CyberJacob is now known as CyberJacob|Away [23:49] After juju bootstrap [23:49] all i get is this [23:49] server refused to accept the client [23:49] 2013-07-10 23:48:55,504:19440(0x7f489e5c3700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:46485] zk retcode=-4, errno=111(Connection refused): server refused to accept the client 2013-07-10 23:48:55,522:19440(0x7f489fdc6700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:50187] zk retcode=-4, errno=111(Connection refused): server refused to accept the client [23:50] The host is up, should i wait it out ?