=== CyberJacob is now known as CyberJacob|Away
=== timrc-afk is now known as timrc
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== mwhudson is now known as zz_mwhudson
=== tim is now known as thumper
=== tim is now known as thumper
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== zz_mwhudson is now known as mwhudson
=== freeflying_away is now known as freeflying
=== CyberJacob|Away is now known as CyberJacob
=== mwhudson is now known as zz_mwhudson
=== dosaboy_ is now known as dosaboy
bloodearnestarosales: pong09:42
jona_hi, I'm running juju on a virtual machine that I connect to through a vpn09:45
jona_if I run an apache-server on this virtual machine I am able to connect to it through the vm's ip09:46
jona_but when I run a service through juju, I don't know how to connect to it from my computer (that is, not from the virtual machine)09:46
jona_is it possible to make some sort of redirection so that when I go to the vm's ip in the browser the vm redirects me to the correct service (for example juju-gui)09:47
=== CyberJacob is now known as CyberJacob|Away
jamespagehazmat, do I need to bump juju-deployer in trusty to matchup with 1.17.0?  seeing some odd issues09:56
stubShould charms be running apt-get upgrade, or is that left to other mechanisms like Landscape?10:37
=== timrc is now known as timrc-afk
lazypowerjona_, your question needs a bit of clarification. Are you looking for a way to route to a juju lxc container inside of the virtual machine? or are you looking to reach a LXC on the HOST from the vm?10:47
lazypowerOr am I inferring too much, and there are no containers, just a service on a manually provisioned VM?10:48
jona_hi lazypower10:54
jona_I want to reach the lxc container inside of the virtual machine10:55
jona_the VM is on an openstacks-server, and I connect to the VM with ssh and a vpn10:55
jona_I am using the VM as a development environment, and juju seemed easy to use :)10:56
jona_when I hosted a plain apache-service on the VM I was able to connect to it by just putting the VM's ip in the browser10:56
lazypowerWithing knowing much of your network topology, i'm going to make recommendations based on what i feel is the path of least resistance10:56
lazypowerJuju by default does not use a routeable IP schema, it creates a bridged network interface to handle the IP routing of the local machine to the LXC containers. It doesn't sound like you have a setup that will lend itself easily to altering this bridged device for public/lan ip assignment, so you will need ot create a tunnel through your tunnel to reach the containers.10:58
lazypowerThis is largely untested through a VPN tunnel, but in theory it should work without a problem. There's an app called sshuttle that will allow you to create a virtual VPN within your VPN (man this seems heavy handed)10:58
marcoceppijona_: did juju create the openstack vm? or did you provision it in horizon?10:58
jona_actually I'm not the openstacks admin, the admin created the VM for me, and it's running ubuntu, and on the VM I installed juju11:04
marcoceppijona_: gotchya11:05
jona_I see, a vpn in the vpn was actually what I had in mind, but I'm rather new to these kinds of things11:06
jona_I'm more of a developer than a networking guy11:06
lazypowerjona_, well after conferring with Marco we both agree you can do this with just SShuttle. Let me fish up some docs for this, as its been a while since I had to do this.11:07
jona_oh all right11:07
lazypowerutlemming did a great write up, its listed under (optional) SSHuttle11:07
jona_oh okay11:07
jona_I'll take a look11:08
marcoceppijona_: vpn is the way to go, its not as painful as you might think, just needs the right configuration options11:08
lazypowernow replace the user@localhost bits accordingly with proper end points, ports, and users and you should be able to reach those LXC containers.11:08
jona_oh all right11:08
jona_seems doable :D11:09
jona_I'll try it11:09
jona_juju seems reaaally neat so I'd like to get to know it better :D11:09
jona_I tried the demo on the page and read a bit about it11:10
jona_and at least deploying the charms(?) is super practical, hehe11:10
marcoceppijona_: once you get it installed, replace vagrant@localhost:2222 with the ssh address for your ubintu machine11:10
=== timrc-afk is now known as timrc
jona_I'm supposed to do this on the VM right?11:11
marcoceppijona_: if you can install virtualbox, you might want to use the vagrant image. it'll install an Ubuntu vm on your desktop with the local provider already configured11:11
marcoceppijona_: well. for testing, sure! but juju runs best against a cloud environment like open stack for production stuff11:12
jona_oh okay, so if I actually want to use vm I should just get my admin to install it directly on the openstacks-server?11:13
lazypowerjona_, in regards to the VM talk, marco was speaking about pulling down the vagrant image on your workstation for testing purposes11:14
lazypoweryou already have juju installed and functioning in that VM, so you're good to go once you get your VPN or SSHuttle configured.11:15
marcoceppijona_: he would give you an account on the openstack install. you put your account details in juju then juju will spin openstack vms when you deplpy charms11:15
lazypower^ that is the most desireable outcome from this talk, as you're getting the integration juju provides out of the box.11:15
jona_ah I see11:16
marcoceppijuju supports multiple types of clouds. aws, openstack, azure, lxc, bare metal, etc11:16
jona_yeah I noticed11:16
jona_hm, I'm not sure if I misunderstood something, when does sshuttle do the shuttling? when I ssh to the VM's ip?11:17
marcoceppijona_: from your desktop to the vm11:18
jona_I ran this command11:19
jona_sshuttle -e 'ssh -o UserKnownHostsFile=/dev/null ubuntu@'
lazypoweronce you run that sshuttle command, your desktop will forward the request over that SSH tunnel to the VM, and route to the addresses of the LXC containers provisioned by juju/lxc.11:19
jona_or wait, I'm not supposed to touch the ports ?11:20
jona_I figured I'd set them to the port I use when SSHing11:20
lazypowerthat's correct11:20
lazypowerthe :2222 is vagrant specific11:20
jona_hm okay, but when I ssh'd to the ip it connected me to the VM as usual11:22
lazypowerrun juju status, and find the IP of the deployed apache charm11:22
jona_I should put that in instead?11:23
lazypowerYep, try to ping it, or plug it into your browser11:23
jona_it doesn't seem to find a connection11:24
jona_no ping packages received11:24
jona_but just so I understand the steps11:25
jona_I ran11:25
jona_sshuttle -e 'ssh -o UserKnownHostsFile=/dev/null ubuntu@'
jona_then I ssh'd again to the VM, where I ran started sshuttle11:25
lazypower192.168.10.222 is the IP of the VM?11:25
jona_then I tried pinging the ip for juju-gui ( as provided by juju status11:25
lazypowerthinking, 1 moment11:28
marcoceppijona_: if you put in your browser after running sshuttle, do you get the GUI?11:29
jona_nope, it just gets stuck on trying to conenct11:30
marcoceppiand you're running sshuttle from your desktop?11:31
jona_no on my VM11:31
marcoceppijona_: ah, there we go11:31
marcoceppirun sshuttle from your desktop11:31
jona_I actually asked about that :D11:31
marcoceppijona_: sorry we didn't make that more clear11:31
jona_no biggie ^^ thanks for helping me at all, haha11:32
jona_btw I run arch locally, and it just claimed "Errno 2 no such file or directory", maybe it's empty in /dev/null?11:33
lazypowergood call marco11:33
jona_it wasn't11:33
jona_hm, it says no such file or directory when I run sshuttle -e 'ssh -o UserKnownHostsFile=/dev/null ubuntu@' locally11:33
marcoceppijona_: is sshuttle installed?11:34
jona_this is an error sshuttle generates, I think11:34
marcoceppijona_: feel free to remove the '-o User.../dev/null' stuff from the -e parameter11:35
marcoceppiand give that a whirl11:35
jona_weird, it still gives the same error11:35
marcoceppitry giving the entire path to ssh11:36
marcoceppiie, /usr/bin/ssh11:36
jona_still same error :S11:36
jona_really weird11:36
jona_I am able to run ssh-V and sshuttle -V so they're both runable11:38
marcoceppican you run sshuttle -v for more verbosity? and paste the entire output11:38
jona_oh I googled the error11:39
jona_apparently I needed net-tools11:39
jona_though now I get some other errors11:39
jona_iptables v1.4.21: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)11:39
marcoceppiI guess you need insmod? Sorry haven't run arch in quite a while ;)11:40
jona_I tried running it but it said "missing filename"11:40
jona_I actually don't know what insmod is11:40
lazypowerit loads modules into the kernel space11:40
jona_I'm just gonna try rebooting brb11:42
jona_it works now11:43
jona_at least sshuttle does11:44
jona_now I'll try connecting with firefox11:44
jona_it doesn't seem to work11:44
jona_oh wait11:44
jona_I forgot11:44
jona_nope still doesn't work11:46
jona_now I've started sshuttle locally, connected to the VM, and tried pinging both and
jona_might it have with the ports to do? and does the /24 after in the sshuttle command matter?11:47
lazypowerthe /24 defines the CIDR range you want to route through that tunnel11:47
lazypower10.0.3.0/24 will route everything from .0 to .255 on the 10.0.3 block, if that makes sense.11:48
lazypowerbut no, the ports shouldn't be a problem. So long as sshuttle is actively running when you try to ping those ip's, or pull them up in a browser.11:48
jona_hm okay11:49
jona_got these warnings11:50
jona_don't know what they mean11:50
lazypowerwell those are good signs, it means sshuttle is establishing a connection with the server. It may not be active, but its trying11:52
lazypowerkill it and restart it, do you still get the warnings?11:52
jona_the server or shuttle?11:53
jona_hm, it seems to give the warning after like 5 minutes or so12:01
jona_afk for a while12:01
marcoceppijona_: can you try running sshuttle with the -v flag, might illuminate what's going on12:07
jona_the last row appeared when I entered in my browser12:09
jona_I have to eat now, but I'll write again when I'm back12:10
marcoceppijona_: cool, it seems to be working :\12:11
hazmatjamespage, i've had a bunch of similiar issue reports in the last week relating to the same watcher error, rogpeppe1 added some additional logging, and i was going to have a look this week, would be good to confirm we're referencing the same issue. the ppa needs updating though12:37
rogpeppe1hazmat: i've fixed that in trunk12:37
hazmatrogpeppe1, logging or watcher error?12:37
rogpeppe1hazmat: both12:38
hazmatrogpeppe1, what was the issue for the watcher?12:38
rogpeppe1hazmat: FWIW the additional logging *was* very useful for diagnosing the problem12:38
hazmatrogpeppe1, awesome12:38
rogpeppe1hazmat: the client watcher wasn't pinging12:38
rogpeppe1hazmat: (i updated the bug report)12:38
hazmatrogpeppe1, cool.. i thought that might be the case and commented on the bug to that effect..12:39
rogpeppe1hazmat: https://codereview.appspot.com/53810045/12:39
rogpeppe1hazmat: yeah - i'd actually merged the fix before you commented there :-)12:40
hazmatstrange normally i get a bug email from lp12:40
rogpeppe1hazmat: it was a bit of a giveaway that the client connection was closed after exactly 3 minutes12:40
rogpeppe1hazmat: a quick grep of the source for "3 \* time.Minute" found the source of the problem immediately...12:41
hazmatrogpeppe1, given a synchronous client not sure how to make that nicer.. outside of background threads..... ideally the ping timeout could be client configured12:41
rogpeppe1hazmat: i don't think we care about the client pinging12:42
hazmatrogpeppe1, umm.. i think you do.. guard against bad clients.12:42
hazmatrogpeppe1, your saying just wait for socket close?12:42
rogpeppe1hazmat: we should probably set SO_KEEPALIVE if it's not set already12:42
rogpeppe1hazmat: yeah12:42
rogpeppe1hazmat: but anyway, you should definitely make your client library concurrent-safe, because at the moment it wouldn't be possible to send a ping request in general, even if you wanted to12:44
hazmathmmm.. so alternatively for a sync client, i can hold store pings, and send opportunistic pongs12:44
rogpeppe1hazmat: that's not a good idea12:45
hazmatrogpeppe1, without concurrency how else to do that?12:45
rogpeppe1hazmat: use concurrency12:45
rogpeppe1hazmat: or callbacks, or something12:46
hazmatrogpeppe1, concurrent safe / concurrency.. mean event loop/scheduler.. i'm happy to do that, but the majority of users want idiomatic not framework12:46
jamespagehazmat, that sounds like what i see12:46
rogpeppe1hazmat: the main point is: clients need to be able to make concurrent calls on the same connection, however you allow that12:46
hazmatseems like something for the plain ride, a subclass that plays nice with gevent/eventlet12:47
rogpeppe1hazmat: yeah, you could have subclasses for various kinds of concurrency framework (twisted, gevent, callback)12:47
rogpeppe1hazmat: you could layer them all on top of a callback-based base layer12:48
hazmatnot doing callback oriented api, twisted and gevent can both do non-callback base, and i want the normal python usage to be non call back based.12:49
rogpeppe1hazmat: fair enough12:49
=== gary_poster|away is now known as gary_poster
jona_I am back marcoceppi13:07
jona_this is how the log looks now:13:08
josephtis this the place to ask juju-deployer questions?14:14
jamespagejosepht, its as good as any - hazmat wrote it :-)14:26
NemesisMateHi, I'm having troubles with juju, I'm just trying to do my first: `# juju bootstrap` (on ubuntu) but I'm getting the error: "ERROR no reachable servers". If I see through the `# juju status -v` I can see it stucks on "INFO juju.state open.go:68 opening state; mongo addresses: [""]; entity """.14:28
=== freeflying is now known as freeflying_away
=== rogpeppe2 is now known as rogpeppe
josephtI'm using canonistack.  I've sourced my novarc.  I get this: http://paste.ubuntu.com/6797562/ when I run: juju-deployer -bdv -c juju-deployer/webui.yaml, where webui.yaml's content is: http://paste.ubuntu.com/6797578/14:45
hazmatjosepht, so your probably using juju switch.. there's like 4 different ways that juju-core can lookup its env to operate on..deployer supports 3.. there's a bug outstanding for juju-core that it should just pass the env unambigiously to the plugin via env variables.. in the meantime.. you can just set JUJU_ENV env var to the env your using.14:50
hazmatcore bug is https://bugs.launchpad.net/juju-core/+bug/1246156..  arguable deployer should just support the four different ways till its done.14:53
NemesisMatehazmat, I don't know if you see my message, did you?, I can't solve that :(14:53
hazmatNemesisMate, that sounds like bootstrap never succeeded.. which provider are you using.. juju-core trunk has already changed provisioning to be synchronous so that these sorts of things are more obvious/easier to diagnose.14:55
hazmater.. changed s/provisioning/bootstraping14:55
NemesisMatewhat do you mean with provider?15:00
josephthazmat: thanks, that was it.15:03
hazmatNemesisMate, like openstack, ec2, etc.. your environment is configured to use which provider?15:04
hazmatin environments.yaml .. its the 'type' key on the environment config15:04
NemesisMate`# juju version` gives me: 1.16.5-quantal-amd64. I just installed it with an apt-get install from "ppa:juju/stable", I made a `juju init`, after that I changed to "default: local" on "~/.juju/environments.yaml", I made an apt-get install mongodb-server and a juju bootstrap15:05
NemesisMateIt's a local one15:05
hazmatNemesisMate, ic.. do you have a firewall setup on your local machine?15:07
hazmatNemesisMate, normally a local env bootstrap requires sudo ..15:08
NemesisMateNo, even I get "[initandlisten] connection accepted from #1" on /var/log/mongodb if I change mongodb port to 37017, but juju bootstrap hangs on that line15:08
NemesisMateyes, I'm using sudo15:08
hazmatNemesisMate,  juju will setup and install its own mongodb on a different port15:08
hazmatNemesisMate, typically you can just disable shutdown the package one unless your using it for other things15:09
NemesisMateif I let it without initializing mongo-db, I get the error I comment at start15:09
hazmatNemesisMate, the issue is what's happening to the separate mongodb process that juju is trying to setup15:09
hazmatNemesisMate,  ie ls /etc/init/juju* should show juju-db in addition to the machine agent15:10
hazmatNemesisMate, so starting back at square one.. i'd sudo service mongodb-server stop15:10
hazmatoh.. the juju jobs are prefixed with user name in the local provider case15:11
NemesisMateOk, I stopped mongodb, and I "juju destroy-environment -y" and try the "sudo juju bootstrap --verbose" and it ended with: http://pastebin.com/rT1zDDnY15:13
NemesisMateI just have this file: "/etc/init/juju-db-<user_name>-local.conf" from juju there15:16
NemesisMateIf I try to execute the command on that file (on the "exec" parameter) I get "error command line: unknown option sslOnNormalPorts". Maybe I need another mongodb version?15:25
Ming_When deploy on Amazon AWS is it OK to use our own AMI or must use precise, saucy,etc?15:27
NemesisMateok, thanks, that was it. I did again an apt-get mongodb-server install and this time it updated again.... (Why it didn't installed this version before?). This time is working great15:27
hazmatNemesisMate, cool.. yeah.. mongodb needs ssl support15:35
hazmatMing_, juju is setup to use pristine cloud-images15:35
hazmatNemesisMate, what distro version are you on? .. if your on precise.. the typically way to get that is via the cloud-archive tools ppa15:35
hazmatNemesisMate, there's also a mongodb with ssl in the juju stable ppa, but if you installed mongodb prior to adding and updating from the ppa you would have gotten the distro version (sans ssl)15:37
marcoceppirogpeppe: still getting watcher was stopped using 1.17.115:48
rogpeppemarcoceppi: can you paste me the machine-0.log ?15:48
rogpeppemarcoceppi: i suspect you're not actually using 1.17.115:48
marcoceppirogpeppe: mbruzek ran in to it ^^15:49
marcoceppirogpeppe: http://pastebin.ubuntu.com/6797420/ (not machine-0.log)15:49
mbruzekrogpeppe, how to get machine-0.log15:49
marcoceppimbruzek: ~/.juju/local/log/machine-0.log15:49
rogpeppembruzek: how do you know you're running 1.17.1 ?15:49
mbruzekThat is on my local filesystem somwhere right?15:49
rogpeppembruzek: what does "sudo which juju" print?15:50
mbruzeksudo juju version15:51
marcoceppirogpeppe: he installed the trusty binary that james put out15:51
rogpeppemarcoceppi: from which revision?15:52
rogpeppembruzek: please paste machine-0.log - that will tell me which version is actually running, and whether the issue is the same one15:52
marcoceppirogpeppe: I have no idea which one james cut that release from15:53
rogpeppembruzek: right, that's not the version with the fix in15:53
marcoceppirogpeppe: ah, sorry, we'll go back and compile/test again15:54
rogpeppembruzek: erm15:54
mbruzekWhich line tells you that?15:54
rogpeppembruzek: maybe it is!15:54
rogpeppembruzek: i'm not sure.15:54
rogpeppembruzek: i see it has the log fixes, but i still see the connection termination15:55
rogpeppembruzek: it would be good to know which revno james cut that version from15:56
mbruzekI still have the .deb15:56
mbruzekHow can I get you that information?15:56
rogpeppembruzek: i'm not sure i can easily find that info from the deb15:56
rogpeppembruzek: that just has the binary in, right?15:56
rogpeppembruzek: actually, perhaps you could send me the .deb?15:57
mbruzekdoing that now15:58
rogpeppembruzek: thanks15:58
* mbruzek is slowly uploading the file...16:00
* mbruzek curses his slow upload speed!16:00
marcoceppirogpeppe: it's on the juju list16:01
marcoceppimaybe...it's not?16:02
rogpeppemarcoceppi: was it jamespage that put the binary out?16:06
marcoceppiidk now, mbruzek where did you get that trusty.deb file?16:06
mbruzekrogpeppe, the note is sent16:06
rogpeppembruzek: thanks16:06
mbruzeklet me check my notes16:06
rogpeppembruzek: i'm still suspecting it's built from a revision earlier than 221916:07
rogpeppembruzek: got your email and downloaded, thanks16:08
mbruzekI don't think it was james16:08
mbruzekI was pointed to the jenkins site,16:08
marcoceppioh, shoot, I was confused, it's from the ci16:11
sinzuihi mbarnett16:12
sinzuisorry mbarnett . hi mbruzek16:12
mbarnetthello anyways!16:12
mbruzekWe were trying to locate the origin of the new-trusty.deb that was built16:12
mbruzeksinzui, I am still seeing the wait problem with the 1.17.1 version of juju local that I have16:13
rogpeppembruzek: have you tried building from tip?16:16
rogpeppembruzek: perhaps i could send you a binary and you could replace /usr/bin/jujud with it and see if you still get the problem?16:16
mbruzekThat would be fine, otherwise Marco showed me how to complile the go code16:17
mbruzekBut others had problems getting the right jujud tool installed16:17
sinzuimbruzek, rogpeppe: CI build binaries using the release tarball and the source package branch. They are stored at
sinzuiThe ones there are from r2239 according to
rogpeppesinzui: great.16:18
rogpeppembruzek: could you try using one of those and see if you can reproduce the issue?16:18
mbruzekDownloading it now, but that link appears to already be visited.16:19
mbruzekI will diff them16:19
rogpeppembruzek: FWIW i was able to reproduce the issue from your instructions, but with the fix applied it all seemed to work16:19
mbruzekThe files are different16:20
mbruzekc45da6c0387f2452a9f28a65a6577a5dbb9f585c  new-trusty.deb16:20
mbruzekmbruzek@skull:~/Downloads$ sha1sum new-trusty2.deb16:20
mbruzeke4907880eefa931ed63bdb85bb3cf6eb49b315f2  new-trusty2.deb16:20
rogpeppembruzek: let me know how you get along with the new version. i will keep my fingers crossed :-)16:21
mbruzekdoing that now rogpeppe16:21
rogpeppesinzui: i wonder if it might be good to bake the current bzr revision (long version) into the binary when building it16:22
rogpeppesinzui: particularly for dev versions16:22
marcoceppisinzui: since the debs are used, would it be wise to update the versions16:22
marcoceppiright, what rogpeppe said16:22
rogpeppewell, this isn't even a dev version, it's an arbitrary snapshot of tip16:23
sinzuimarcoceppi, rogpeppe. We are testing what will be released. we create actual deb versions as a part of the test. The names you see are symlinks to proper names. I don't know how to include the revision in the version without corrupting the test16:24
* sinzui has pondered using the real package names instead of the simplified names16:24
rogpeppesinzui: i wouldn't include the revision in the version16:25
sinzuiThat breaks the test16:25
rogpeppesinzui: but i would try to embed it in the binary16:25
sinzuirogpeppe, we are really testing the packaging.16:25
marcoceppisinzui: so, in other words, don't install this debs?16:25
marcoceppirather, install at your own risk16:25
sinzuiI did say it was bleeding edge. I didn't put them in a ppa16:26
* marcoceppi didn't even know they existed until this morning16:26
sinzuimarcoceppi, I have had to tell a lot of people about them recently and I also need to talk about tools-url/tools-metadata-url. I think I need to post going out to all the juju emos who want to cut themselves16:28
marcoceppisinzui: CI can be very sharp ;)16:29
marcoceppirogpeppe: looks like the bug is fixed, sorry about that16:35
marcoceppithanks again!16:35
rogpeppembruzek: did your tests succeed with the new binary?16:36
mbruzekyes it did16:36
rogpeppemarcoceppi: cool16:36
mbruzekI am in a hangout with marco16:36
=== avoine1 is now known as avoine
mhall119marcoceppi: ping16:41
teknicomarcoceppi (or anyone else), how do I determine which openstack version the charms are installing?16:45
teknicospecifically, the openstack-dashboard one16:46
teknicothe installed Horizon code is using a Django 1.4-ism alongside Django 1.5, and code goes boom :-)16:47
marcoceppiteknico: juju get openstack-dashboard16:55
marcoceppiteknico: that'll show your the optoins, including the openstack-release (I think that's the config option name)16:55
marcoceppipong mhall11916:56
teknicomarcoceppi, openstack-origin is cloud:precise-grizzly, thanks16:58
marcoceppiteknico: there ya go :)16:58
teknicoand how does the charm know which django version to install? can't find it16:58
marcoceppiteknico: isn't that a dependency on the package? The pocket cloud has a django version that matches each release of openstack16:58
marcoceppiie, doesn't horizon in grizzly  require django X and havana django Y, in that case django will be in the cloud archive for each version of openstack release16:59
teknicomarcoceppi, so in this case will it be http://cloud-tools.archive.ubuntu.com/ubuntu/dists/precise-backports/ ?17:03
marcoceppiteknico: depends, precise-grizzly maps to another cloud archive, not nessiarily the cloud-tools archive17:04
teknicowhere is that mapping defined?17:04
marcoceppiteknico: jamespage would probably be better at illuminating it17:06
* marcoceppi goes and looks17:06
jamespageteknico, you are hitting a bug in the fact that juju adds the cloud-tools repository to all precise instances17:07
jamespagecloud-tools has a newer version of django that precise-grizzly - #boom17:07
jamespageteknico, bug 124066717:08
teknicojamespage, so it's known, ok, thanks17:10
teknicoand there's even a workaround on the bug :-)17:11
jamespagesinzui, mramm: any chance https://bugs.launchpad.net/juju-core/+bug/1240667 could be bumped in priority17:11
mhall119marcoceppi: since jcastro isn't around, can you do a juju update on the ubuntu engineering live call in 30 minutes?17:24
marcoceppimhall119: uh, sure17:27
nboumazaHi Antonio...Can I interrupt for a few minutes..?17:57
evjuju-deployer respects JUJU_REPOSITORY, right?17:59
marcoceppiev: it /should/17:59
* marcoceppi checks code18:00
marcoceppiI don't see any explicit mention of it, ev18:02
evmarcoceppi: as in it doesn't override it or affect juju underneath juju-deployer's ability to use it, right?18:03
marcoceppiev: I assume it doesn't affect juju underneath, but hazmat would know more about that18:03
hazmatev, it doesn't.. there's a bug and branch outstanding18:03
evbug number?18:04
hazmatev  https://bugs.launchpad.net/juju-deployer/+bug/122939018:04
hazmati've got some deployer items to merge later today, i'll add that to the list, just need to get out from under some sisyphean work18:06
=== CyberJacob|Away is now known as CyberJacob
=== zz_mwhudson is now known as mwhudson
=== fcorrea__ is now known as fcorrea
dpb1marcoceppi: I got an approve from sid-nei here: https://code.launchpad.net/~davidpbritton/charms/precise/haproxy/fix-service-entries/+merge/202387, then I think he added another review.  Is that normal?20:19
marcoceppidpb1: looks like it's always been assigned to charmers? I'll do a cursory review of it in a few mins and merge if there's no major issues20:20
dpb1marcoceppi: thx20:21
=== BradCrittenden is now known as bac
dpb1using juju test, is there a way to use an environment that has an existing bootstrap, and leave it up?21:40
=== gary_poster is now known as gary_poster|away
marcoceppidpb1: yes22:05
marcoceppidpb1: err, there was a way22:05
marcoceppidpb1: could you file a bug?22:08
dpb1marcoceppi: ok22:08
marcoceppidpb1: I'll have that rolled out very soon22:08
dpb1marcoceppi: where do I file it?22:16
dpb1marcoceppi: https://bugs.launchpad.net/charm-tools/+bug/127174522:22
jcastromarcoceppi, do you know if we can export a bundle from the CLI yet?22:41
marcoceppidpb1: thanks22:41
marcoceppijcastro: not off the top my head22:42
marcoceppijcastro: we could pluginize one22:43
marcoceppiwouldn't be too hard22:44
jcastroWARNING no tools available, attempting to retrieve from https://streams.canonical.com/juju23:01
jcastroERROR bootstrap failed: cannot find bootstrap tools: XML syntax error on line 9: element <hr> closed by </body>23:01
jcastroanyone see this today?23:01
marcoceppijcastro: yeah, this has been happening for a while23:02
marcoceppijcastro: what version?23:02
jcastro1.17, doing an --upload-tools worksaround23:03
jcastroI was just wondering if we were tracking it somewhere23:03
marcoceppijcastro: use 1.17.1, I think it automatically uses upload tools now23:03
marcoceppijcastro: it's def known23:03
marcoceppi(when stream isn't found)23:03
hazmatjcastro, i've seen that on ec2 for a while when i forget --upload-tools23:09
hazmatrunning with trunk23:09
=== timrc is now known as timrc-afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!