[06:18] morning [06:18] how's brussles [06:19] ? [06:19] tis lovely [06:20] a lovely shade of pigeon [06:20] http://www.benjaminmoore.com/en-us/paint-color/pigeongray [06:44] jam: so I looked at the code for the NonValidatingHTTPClient in juju/utils and it just sets the InsecureSkipVerify flag to true. So apparently that IS the fix we went with before. [06:45] wwitzel3: so we need to discuss this, as saying "ok, just don't validate SSL connections ever" is going to be a good way forward === uru_ is now known as urulama [07:20] davecheney: morning, I was hoping you would be here [07:55] jamespage, https://plus.google.com/hangouts/_/canonical.com/juju-qa-meeting?authuser=1 [07:56] sinzui: hey, do you have a link to the new link to whatever you use to create custom streams? my streams are suddenly not working so I presume something changed === ericsnow is now known as ericsnow__ [09:36] who can review a simple fix for bug 1373385 http://reviews.vapour.ws/r/154/ ? [09:36] Bug #1373385: juju needs to support the MAAS API's not_tags constraint

=== ericsnow is now known as ericsnow__ [11:52] sinzui: sort of ping [11:52] hi perrito666 [11:53] hi, can you tell me if thisformat is correct? http://people.canonical.com/~hduran/juju-dist/ [11:56] perrito666, that looks good. I will try validating it [12:00] perrito666, that looks correct. wallyworld changes streams in trunk to use tools-stream to select the kind of tools. the default is "released" and that is what I see in the index.json [12:01] perrito666, I also confirm I can download the tar.gz and the sum matches [12:02] perrito666, There were issues last year where juju failed to download the tools (in cloud-init-output.log) and it was reported as a shasum mismatch instead of truncated file [12:04] sinzui_: well I ssh into the machine and then sha256sum it and the checksum is also correct [12:04] perrito666, maybe you want to try setting the tools-metadata-url to http://juju-dist.s3.amazonaws.com/testing/tools to verify something is pickup [12:04] I will thank you [12:22] sinzui_: so I upgraded my juju and created a new set of tools version: juju-1.21-alpha2-trusty-amd64 but now it seems to be ignoring me [12:22] RROR cannot bootstrap new instance: Juju cannot bootstrap because no tools are available for your environment. [12:22] You may want to use the 'tools-metadata-url' configuration setting to specify the tools location. [12:23] perrito666, juju get-env tools-metadata-url [12:23] * perrito666 destroys the whole things and starts over [12:23] by default is is not set [12:23] perrito666, but we can change it using set-env [12:27] sinzui_: just scrapped the whole thing and re bootstraping, so far seems to be working [12:52] perrito666, which cloud are you deploying too? I just bootstrapped in aws with you stream and the juju 1.20-alpha2 that was built by CI a few hours ago [12:52] aws [12:53] perrito666, http://pastebin.ubuntu.com/8514364/ [12:53] perrito666, I created a trusty instance in us-east-1 [13:01] sinzui_: can I gent your .jenv conf for that particular conf? [13:02] perrito666, http://pastebin.ubuntu.com/8514414/ [13:02] cmars: http://pastebin.ubuntu.com/8514413/ [13:03] sinzui_: Ill take a look === revagomes_ is now known as revagomes [13:08] sinzui_: it worked [13:11] perrito666, ? what is different in your yaml? [13:12] sinzui_: region is different and default series is not present, yet I have done no changes [13:13] sinzui_: Ill keep an eye for this happening again [13:14] perrito666, I set default-series because I don't trust juju to pick and LTS. Did your failures have a trusty machine? [13:14] they did === Ursinha-afk is now known as Ursinha [13:42] jaasteam: if someone could review : https://github.com/CanonicalLtd/blues_browser/pull/94 [13:43] wrong channel sorry === jcw4|travelling is now known as jcw4 [16:01] hazmat: is there any way to tell deployer about availability zones? I have a prod and dev host aggregate. I can juju boostrap --to zone=production, but then running deployer tries to throw everything on the nova AZ (dev). [16:07] I know everyone's super busy, but I'm trying to find info on juju w.r.t. docker [16:07] I noticed a very stale issue for docker integration and container networking from last year on launchpad [16:07] I'd really like to do some work in that direction if nobody else is, or if others are, maybe I could help out a bit, or something [16:36] hazmat: nevermind; working around it with juju add-machine zone=production for now. === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === jcw4 is now known as jcw4|away === jcw4|away is now known as jcw4 === Ursinha is now known as Ursinha-afk === jcw4 is now known as jcw4|away === Ursinha_ is now known as Ursinha === jcw4|away is now known as jcw4 === rogpeppe is now known as acmeboy