=== CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie === CyberJacob|Away is now known as CyberJacob === thumper is now known as thumper-afk === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob [05:32] is there a known issue with juju 1.12 with destroying-service ? Since i switch to juju >=1, destroy-service fails silently most of the time [05:32] the service are shown as dying, but nothing else seems to happen [05:41] melmoth, i do have seen this [05:42] i do quite a lot those days [05:42] melmoth, me too === CyberJacob is now known as CyberJacob|Away === tasdomas_afk is now known as tasdomas === thumper-afk is now known as thumper === defunctzombie is now known as defunctzombie_zz [12:24] hi mectors [13:29] hi [13:30] 8-) [13:30] :p [13:34] hi [13:35] hi is any one her [14:01] jcastro, can Debian / Redhat images be deployed ? [14:02] not currently no [14:03] I think debian has cloud-init now, all that's needed is for someone to do the work [14:04] I tried using Debian with juju awhile back - problems with cloud-init confg & upstart [14:05] jcastro, re the rack charm, tell the author he has bug in his config. [14:06] that's preventing the store publishing, fwiw [14:06] jcastro, Can different ubuntu images be used in the same environment ? [14:09] geme: like different versions? [14:09] or different images as in cloud images? [14:09] hazmat: got any more detail? [14:10] hazmat: or is it that encoding issue sinzui and him ran into? [14:10] yes - different ubuntu cloud images ? [14:11] we do what is defined in "series" in environments.yaml, we don't have a way to specifify a custom image, for example [14:13] jcastro, nothing to do with encoding he has a bad config default value .. config: options.deploy_key.default: unexpected value [14:13] So, just the one image available for say precise ? [14:13] geme: yeah it will fetch the latest supported cloud-image and deploy that [14:14] http://cloud-images.ubuntu.com/releases/precise/release/ [14:30] jcastro, is there a timescale to support other oses ? [14:35] not really, any help would be accepted and appreciated, but we're not actively working on that at the moment [15:28] smoser, utlemming: talking with mgz on bug https://bugs.launchpad.net/juju-core/+bug/1188126 [15:28] <_mup_> Bug #1188126: Juju unable to interact consistently with an openstack deployment where tenant has multiple networks configured

[15:28] any way to tell cloud-init to bring up all detected networks? [15:32] arosales: generally with a cloud-drive you can send /etc/network/interfaces, but if they are using the EC2 meta-data source, then no [15:34] utlemming, (brainstrom) any way to patch cloud init to take ingest a value to detect and init all attached networks (ie not stop in the first) [15:39] smoser, ^ [15:48] arosales, i don't think it an issue of bringing up the network [15:49] afaik, the issue is that is being able to correctly identify which network juju should be using [15:49] given multiple [15:49] hazmat, just an idea mgz and I were batting around. mgz would have more insights then myself [15:50] jcastro, attempting 1st bootstrap using juju-core 1.13.1 and it errors - http://*.*.*.*:8080/v2.0/AUTH_ca452007af584a7f933e6a3e281f1c85/juju-dist/"/"streams/v1/index.sjson": cannot find URL "http://*.*.*.*:8080/v2.0/AUTH_ca452007af584a7f933e6a3e281f1c85/juju-dist/streams/v1/index.sjson" not found [15:50] * hazmat drops back to #juju-dev for it [15:50] hazmat: I don't see why, in the elmo-case, we shouldn't expect both to work [15:50] should index.sjson be index.json [15:50] (ie, they're trying to migrate an existing deployment to a new ip range, by adding an extra address to every instance) [15:51] geme: does it actually fail? AFAIK that's a common error during juju bootstrap -v but doesn't nessiarily mean it's failing. Is this a private openstack deployment? [15:52] yes - it's a private openstack [15:53] geme: Do you see any instances online started by juju in the dashboard? does juju status work? Was that the error that juju threw during bootstrap (actually, could you pastebin the the full output to the shell) [15:53] No instance deployed [15:53] geme, sounds similar to the https://lists.ubuntu.com/archives/juju/2013-August/002826.html thread [15:54] Have you created image metadata for your dpeloyment using the juju metadata command? [15:54] finally, what version of juju are you using? (juju version) [15:54] yes - image metadata created and posted to the public-bucket [15:55] juju-core 1.13.1 [15:55] error: cannot start bootstrap instance: no "precise" images in RegionOne with arches [amd64 i386] [15:56] pastbin url ? [15:57] pastebin url [15:57] geme, http://pastebin.ubuntu.com/ [15:57] geme: http://paste.ubuntu.com [15:57] ^^ [15:58] arosales, sorry. back now. [15:58] ah. for ec2, there is a well identified solution. [15:58] geme: juju will attempt to access several locations. starting with .sjson, then .json, then public simplestream data [15:58] that is simply just not implemented. [15:58] https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1153626 [15:58] <_mup_> Bug #1153626: Multiple Interfaces and IPs not detected in AWS VPC

[15:59] arosales, ^ [16:02] marcoceppi, bootstrap -vv console output in pastebin [16:03] geme: can you paste the link please? [16:03] http://paste.ubuntu.com/5989532/ === tasdomas is now known as tasdomas_afk [16:19] geme: what's the region set to in your index.json file? [16:20] RegionOne [16:20] geme: could you paste the results of that file in a pastebin [16:21] also, it's nearing bed time for me. So if you're unable to get futher assistance, feel free to post to ask ubuntu or juju@lists.ubuntu.com for "offline" help [16:21] index.json ? [16:21] geme: yes [16:21] geme: I'm also assuming the *.* in the addresses are just you anonymizing the data? [16:21] yes [16:23] http://paste.ubuntu.com/5989600/ [16:24] geme: you dont' actually have any cloud data in there [16:26] ran this command - juju-metadata generate-image -i 65a1e7ba-eb56-48e6-9b4e-8f7c0c05e779 -s precise -r RegionOne -u http://15.25.24.11:5000/v2.0/ [16:26] Am I missing something ? [16:26] geme: not sure he's an example working index.json file for hpcloud [16:27] smoser, the conversation continued in #juju-dev between mgz and hazmat [16:28] marcoceppi, so the index.json is incorrect ? [16:29] geme: it's missing data, one sec [16:47] geme: what does imagemetadata.json look like? [16:48] http://paste.ubuntu.com/5989688/ [16:49] marcoceppi, need to drop off. Pick up tomorrow ? [16:49] geme: yes, I need to do the same [16:50] ok - catch you tomorrow. Thanks === CyberJacob|Away is now known as CyberJacob === defunctzombie_zz is now known as defunctzombie [18:17] uhm, where do i make changes to https://juju.ubuntu.com/docs/charms-constraints.html ? [18:22] arosales: wotcha think: https://juju.ubuntu.com/events/ [19:11] hi- [19:37] jcastro, looks good, thanks for updating it [19:37] lot of topics I am really interested in there too [19:37] good content [20:43] hi [21:00] sidnei: lp:juju-core/docs [21:01] thanks marcoceppi === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away [23:31] jamespage, How's it going? Was wondering if you could help me with some strange issues? [23:32] Hey can someone help me troubleshoot a strange Juju issue? [23:36] irossi, its end of day for europe and america time zones so may be good to mail the list and get some help there. [23:36] https://lists.ubuntu.com/mailman/listinfo/juju [23:36] or leave a post on askubuntu [23:36] OK thanks very much [23:36] irossi, I can try to help, but may have to point you to the list or askubuntu [23:38] arosales, Thanks. I have Openstack on 28 nodes deployed by Juju. Every once in a awhile, the juju machine agent starts to hog a lot of memory and I can't access the nodes. [23:38] irossi, which juju version are you running? [23:38] arosales, I'm able to reboot the bootstrap node, but it still shows instance-state: unknown while the agent-state is running [23:39] irossi: check log sizes, I think I've heard that juju logs never get rotated and can fill the disk they are on.. [23:39] we should fix that... [23:39] irossi: check df output on the inolved machines.. [23:39] sarnold, ah good point [23:39] arosales, sarnold Checking on all of the above [23:39] thumper: we may have already, this might be old cargo-culting :) [23:39] * thumper nods [23:40] all I know is tracking down problems due to full filesystems is -always- harder than it sounds. [23:40] so check them first :) [23:40] sarnold, thumper so juju rotates logs on 1.13 > [23:40] Most of the nodes are so pegged I can't ssh into them [23:41] arosales, sarnold: Juju 0.7 [23:41] arosales: excellent! thanks. :) [23:42] sarnold, I was actually asking :-) [23:42] I should have appended a "?" to that [23:42] arosales, sarnold: Checking on the logs too [23:44] arosales: oh :) haha [23:44] sarnold, but thumper would know the latest on log rotate in 1.13 [23:44] arosales, sarnold : So it Juju 0.7 too old? Are there bugs in that version that are good reason to upgrade? What's the recommended version? [23:45] arosales, sarnold : 1.13 ? [23:45] irossi, I don't know for certain the issue you are hitting is addressed in 1.13, but I would recommend it [23:46] arosales: I don't actually know about the log rotation... [23:47] arosales, What's the easiest way to upgrade? [23:47] sudo add-apt-repository ppa:juju/devel && sudo apt-get update && sudo apt-get install juju-core gets you the latest [23:47] arosales, Why devel? That doesn't sound stable... [23:47] there is also sudo add-apt-repository ppa:juju/stable [23:47] which is at 1.12 [23:47] haha [23:47] just was saying that devel got you the latest version if you were looking for a comparison [23:49] irossi, right now there is not a clean upgrade path from .7 to 1.13, but juju core devs are working on improving that. [23:49] irossi, probably not the answer you wanted to hear :-/ [23:49] arosales, OK [23:51] irossi, juju core devs are working on bugs such as https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1200878 [23:51] <_mup_> Bug #1200878: Upgrade breaks existing pyjuju deployment

[23:51] and making a better transition story from .7 to 1.x [23:52] arosales, So the upgrade path you describe, would you mind describing it a bit more and perhaps any risk? [23:55] irossi, I would have to ping hazmat on the current upgrade story from .7 to 1.x [23:55] not sure if he around atm === melmoth_ is now known as melmoth [23:58] arosales, Ok thx [23:58] arosales, I'll check in tomorrow [23:59] irossi, apologies, wish I had a better answer [23:59] irossi, but I also don't want to give you false info either.