[04:27] <stub> marcoceppi: juju-log issues are covered by https://bugs.launchpad.net/juju-core/+bug/1274460
[04:27] <mup> Bug #1274460: juju-log vs. command line length limits <juju-log> <juju-core:Triaged> <https://launchpad.net/bugs/1274460>
[04:27] <stub> (and there are similar bugs for the other tools, which share the problems, apart from relation-get which has been fixed already)
[10:24] <apuimedo> Good morning
[10:24] <apuimedo> Does somebody here use the juju digital ocean plugin?
[10:25] <apuimedo> https://github.com/kapilt/juju-digitalocean
[10:25] <apuimedo> I saw some comment from lazyPower on one of the issues
[10:25] <apuimedo> for some reason `juju ssh` does not work in my digital ocean environment
[10:26] <axino> apuimedo: what does it do ?
[10:36] <apuimedo> axino: from poking around
[10:37] <apuimedo> I saw that it sshs to the bootstrap machine
[10:37] <apuimedo> and from there does `nc`
[10:37] <apuimedo> the first part worked, I can ssh to the bootstrap env
[10:37] <apuimedo> but the nc part would just leave me waiting forever
[10:39] <axino> apuimedo: can you reach the second instance from the bootstrap node ?
[10:40] <apuimedo> axino: I can ssh to it
[10:40] <apuimedo> but I don't know its pass
[10:40] <apuimedo> axino: are you using it frequently?
[10:41] <axino> apuimedo: I'm not :)
[10:43] <apuimedo> axino: what do you use, an OSt env?
[10:44] <axino> apuimedo: yes, OS and a bit of AWS
[10:44] <axino> apuimedo: can you run "juju --debug ssh $whatever_you're_sshing_to ?
[10:45] <apuimedo> axino: how well does the AWS one work for deploying OSt?
[10:46] <axino> apuimedo: I'm sorry, I don't get your question
[10:48] <apuimedo> axino: I mean, does the AWS environment work well for deploying OpenStack charms?
[10:50] <axino> apuimedo: I never deployed OpenStack charms to AWS
[10:50] <apuimedo> ah, ok
[10:51] <apuimedo> jamespage: have you?
[10:58] <apuimedo> gnuoy: I guess you use the internal OSt to launch openstack charms, right?
[10:59] <gnuoy> apuimedo, ost?
[11:00] <apuimedo> OpenStack
[11:01] <gnuoy> apuimedo, we use ost on ost and then ost on baremetal
[11:01] <apuimedo> cool
[14:27] <sebas5384> jcastro: Ubucon LatAm almost starting!
[14:28] <jcastro> glad to see you made it!
[14:28] <jcastro> people were, uhhh, worried you didn't make the flight, heh
[14:28] <sebas5384> yeah!! i were looking after the ride but I didn
[14:29] <sebas5384> didn't find any sign with my name
[14:29] <sebas5384> don't know what happen :P
[14:29] <sebas5384> but hey! I'm here in one pice
[14:29] <sebas5384> jose: is making an awesome work :)
[14:50] <urulama> jamespage: hey. frankban just released new deployer and also new juju-gui, which now allows you to deploy v4 bundles (so the new format you've been working with Makyo). Bundle deploy almost works, fails due to hook/config problem, no longer machine placement.
[14:51] <urulama> jamespage: and v3 -> v4 translation has landed, but that requires new charmstore release, which should happen next week
[14:52] <frankban> urulama, jamespage: also quickstart fixes to deploy v4 bundles with placement will land next week, for now the deployer should work, v0.5.1 released on Pypi and the juju stable PPA
[16:28] <apuimedo> marcoceppi: ping
[16:45] <sebas5384> someone is having problems with python dependencies? http://pastebin.com/qX0c98F0
[16:46] <sebas5384> I have almost the same problem with every charm deploy
[16:46] <sebas5384> help?
[16:55] <sebas5384> http://pastebin.com/qX0c98F0 help ?
[16:55] <marcoceppi> sebas5384: looking
[16:55] <sebas5384> marcoceppi: thanks o/
[16:56] <marcoceppi> sebas5384: can you ssh into the machine and run this:
[16:56] <marcoceppi> sudo apt-get -y install python-apt python-launchpadlib python-tempita python-yaml
[16:56] <marcoceppi> sebas5384: apt-get is having a problem installing one of those packages
[16:57] <sebas5384> yes
[16:57] <sebas5384> let me see
[16:57] <sebas5384> hmmm yeah couldn't even download the mysql for the mysql charm
[16:59] <sebas5384> http://pastebin.com/DaztURCf
[17:00] <sebas5384> marcoceppi: ^
[17:00] <sebas5384> it seems there's definitvely an apt problem
[17:00] <marcoceppi> sebas5384: well, there ya go. Looks like you've got a proxy or networking issue
[17:00] <marcoceppi> is this on local provider or a cloud?
[17:00] <sebas5384>  403  Forbidden
[17:00] <sebas5384> local
[17:00] <marcoceppi> somethign is up with the networkign wherever you are
[17:01] <marcoceppi> the archive is reachable here
[17:01] <sebas5384> maybe is something related to firewalls
[17:01] <sebas5384> yep definitively is that
[17:01] <sebas5384> marcoceppi: I'm going to do a demo tomorrow in the ubuconLA
[17:01] <sebas5384> and I wanted to show the local provider
[17:02] <marcoceppi> sebas5384: is this at the conference's wifi? or the hotel?
[17:02] <marcoceppi> or somewhere else?
[17:02] <sebas5384> conference wifi
[17:02] <marcoceppi> eek
[17:02] <sebas5384> i think i must deploy locally in the hotel
[17:02] <marcoceppi> jose: if you're around (you're probably mad busy) can you help sort this?
[17:03] <sebas5384> marcoceppi: jose is at the stage in this very moment
[17:03] <sebas5384> hehe
[17:03] <sebas5384> i'll talk with him
[17:03] <marcoceppi> sebas5384: haha, well he should be able to help hopefully
[17:03] <sebas5384> definitively!
[17:03] <sebas5384> thanks for your help marcoceppi :)
[17:03] <sebas5384> marcoceppi++
[17:04] <sebas5384> we should have some karma bots here :P
[20:12] <beisner> ping wolsen
[20:12] <wolsen> pong beisner
[20:12] <beisner> wolsen, hey so in kilo and later, rmq doesn't allow guest amqp connections unless coming from localhost
[20:13] <beisner> wolsen, so i've got tests that do all sorts of cool validation ... for combos up to kilo.
[20:13] <wolsen> beisner, mmm was it just kilo? I thought that was a change in rmq version 3.something iirc
[20:13] <wolsen> beisner, ahh right
[20:13] <beisner> wolsen, then i have a work-around in the tests to just force-enable guest from anywhere at kilo and later.
[20:13] <beisner> wolsen, but...
[20:13] <beisner> wolsen, that clobbers ssl configs, since it's all in the same funky lil erlang stanza
[20:14] <beisner> wolsen, ref:  https://www.rabbitmq.com/access-control.html
[20:14] <beisner> wolsen, tldr:  the rmq charm needs to grow a config option to set loopback_users to [], while preserving all of the mangling happening for ssl configs in that file.
[20:15] <beisner> wolsen, in order for me to include ssl tests that is.
[20:15] <wolsen> beisner, what about granting access for a specific user? oh those are made over the relations right?
[20:15] <beisner> wolsen, it looks to me like that file is only currently touched by the charm when ssl is on.
[20:15] <wolsen> beisner, oh
[20:15] <beisner> wolsen, yep, rock:hardplace
[20:16] <wolsen> beisner, yep... and enabling the option risks security :/
[20:16] <beisner> wolsen, right, but the charm is untestable (across our whole support matrix) without either adding that option
[20:16] <beisner> or
[20:17] <beisner> doing more serious mangling of configs in the test, outside of charm config options
[20:17] <beisner> which i try not to have to do
[20:17] <wolsen> beisner, that's fair
[20:18] <beisner> wolsen, the new test is this:
[20:18] <wolsen> beisner, fwiw, I'm not opposed to adding the option, just need to have the appropriate amount of "do not use this in the real world"
[20:18] <beisner> deploy precise-icehouse through vivid-kilo
[20:18] <beisner> 3 rmq units
[20:18] <beisner> send amqp msg to each unit, 1 at a time, and check that the message can be read from all other units
[20:19] <beisner> check that all units are represented IN all units cluster_status
[20:19] <beisner> so it's more of a core cluster/messaging functional check that works on the whole horizon of combos (sans ssl).
[20:20] <beisner> i have a whole load of helpers coming out of this too, which will make it easy to add the other scenarios
[20:21] <beisner> wolsen, i wonder if we can borrow creds from something else that does have perms to talk over the wire?
[20:21] <beisner> and use that in pika instead of guest
[20:22] <wolsen> beisner, should would be nice to be able to set a mock relationship here - so you could create it that way!
[20:23] <wolsen> beisner, we probably could borrow them if you really wanted to - seems like quite a kluge though
[20:23] <wolsen> beisner, I think its probably better to enable the guest account for what is being tested
[20:24] <beisner> wolsen, i was just running with the guest@guest pika thing the other tests were using.   i'll look at adding a separate user explicitly who can talk.  but if that involves that funky stanza thing, we'll still be clobbering ssl charm activities.
[20:24] <beisner> wolsen, the charm isn't plumbed for that file currently, except for in the ssl enablement pieces, so it doesn't look like that will be non-trivial.
[20:25] <beisner> s/non-trivial/trivial/   bah the double negatives
[20:25] <beisner> ie. the ssl charm config options are a bit antisocial wrt the file we need to touch
[20:43] <sebas5384> marcoceppi: the mediawiki scalable bundle is giving errors in the haproxy and mediawiki install hooks http://pastebin.com/8gXkdhKz
[20:43] <sebas5384> deploying in GCE
[20:43] <sebas5384> I'm gonna test it in aws later
[20:45] <marcoceppi> sebas5384: It looks like that ppa doesn't exist anymore
[20:45] <sebas5384> hmmm
[20:46] <sebas5384> so the charm is not updated?
[20:46] <sebas5384> maybe because is precise/
[21:13] <beisner> wolsen, got it sorted.  the test is just adding a testuser with necessary privs, should work independently of that file and the ssl erlangy stuff.
[21:13] <wolsen> beisner, sweet - that's even better
[21:20] <hazmat> tvansteenburgh: was there any clarity on how frankban's branch fixed the memory issue?
[21:30]  * beisner => eow
[21:43] <mwenning> hi juju team, how do I set proxy's on bootstrap nodes?  I tried 'http_proxy:  blah' in environments.yaml and it said "unknown config"
[22:12] <marcoceppi> mwenning: what version of juju?
[22:12] <marcoceppi> hazmat: tvansteenburgh is out for the next week
[22:13] <mwenning> marcoceppi, 1.24.3-trusty-amd64
[22:13] <marcoceppi> mwenning: try http-proxy
[22:13] <marcoceppi> and https-proxy
[22:13] <marcoceppi> mwenning: you can also set it on an exiting environment with juju set-env
[22:18] <mwenning> marcoceppi, thx .   in 30 minutes I'll know if that fixed it ;-)
[22:21] <mwenning> marcoceppi, is there a way to tell juju to just abort everything and quit?
[22:23] <marcoceppi> mwenning: ctrl + c?
[22:23] <mwenning> marcoceppi, nope, juju says something like 'waiting for bootstrap to finish' and keep right on going until all the timeouts finish.
[22:24] <marcoceppi> mwenning: you could maybe do juju destroy-environment --force
[22:24] <mwenning> marcoceppi, nope, juju ignores that if it's in the middle of a bootstrap
[22:25] <marcoceppi> \o.
[22:34] <mwenning> \o/ , Bootstrapping Juju machine agent
[22:41] <marcoceppi> mwenning: huzzah!