[03:38] <Sebas_> hey! somebody there?
[03:40] <Sebas_> jose or lazyPower take a look at this video at the time 1:15 http://hemingway.softwarelivre.org/fisl15/high/41f/sala41f-high-201405070913.ogv
[03:40] <Sebas_> I talk about juju and Drupal
[03:44] <jose> Sebas_: Cool! I'll take a look :)
[03:44] <Sebas_> jose \o/
[03:44] <Sebas_> actually was unexpected called to the stage hehe
[03:44] <jose> :P
[03:45] <Sebas_> so I didn't prepare anything, but was alright hehe
[03:45] <jose> is it in 1m15s or 1h15m?
[03:45] <Sebas_> 1h16m
[03:49] <Sebas_> jose: that was in the FISL 15
[03:49] <jose> is that this year?
[03:50] <Sebas_> yes! actually last wednesday
[03:50] <jose> awesome!
[03:50] <Sebas_> yeah! \o/
[03:51] <Sebas_> I talk with all kind of people about juju
[03:51] <Sebas_> for example redhat people from openshift
[03:51] <jose> tell them to switch to Ubuntu!
[03:52] <Sebas_> hehe they where really shock about what juju can do
[03:52] <Sebas_> haha yeah!
[03:52] <Sebas_> sadly ubuntu doesn't appear in the event
[03:53] <jose> maybe next year?
[03:53] <Sebas_> debian, redhat, opensuse, fedora and others
[03:53] <Sebas_> yes of course
[03:53] <Sebas_> I'm thinking in talk about juju next year
[03:54] <Sebas_> also talked with some guys from openstack community
[03:55] <Sebas_> they didn't know about openstack bundle, and the maas integration
[03:55] <Sebas_> they are using foreman
[03:55] <Sebas_> and puppet
[03:55] <jose> I assume they do now?
[03:55] <Sebas_> yes!!
[03:57] <Sebas_> but I didn't use already juju to deploy os, because I wanna to deploy it only with lxc containers
[03:57] <jose> oh well
[03:58] <Sebas_> i only have 1 dedicated server, and i really doesn't wanna to deploy openstack in VMs
[03:59] <jose> well, you can use the EC2 free tier
[03:59] <Sebas_> free you say?
[03:59] <sarnold> for tiny and slow machines :)
[03:59] <jose> http://aws.amazon.com/free
[04:00] <sarnold> but wonderful for testing things
[04:00] <Sebas_> ohh nice
[04:00] <Sebas_> yeah!
[04:00] <jose> I do all my charm development/testing on EC2's free tier :)
[04:00] <jose> hi sarnold :)
[04:00] <Sebas_> ahh ok
[04:00] <sarnold> hey jose :)
[04:01] <Sebas_> yeah but I was trying to avoid kvm's hehe
[04:01] <jose> it's not kvm
[04:01] <jose> or well, I'm not sure
[04:01] <sarnold> probably xen
[04:01] <sarnold> the best part is you mostly don't care :)
[04:01] <jose> yeah
[04:01] <Sebas_> yes probably xen
[04:01] <Sebas_> haha
[04:01] <Sebas_> ¬¬
[04:02] <jose> you just use it
[04:02] <jose> or well, at least I do
[04:02] <sarnold> *nod*
[04:03] <Sebas_> do you already tried openstack with juju ?
[04:04] <Sebas_> jose or sarnold hmm let me rephrase that, do you already deploy openstack with juju?
[04:04] <sarnold> Sebas_: not me, I don't have enough machines to make use of openstack, heh
[04:05] <Sebas_> sarnold: same problem here
[04:05] <Sebas_> i was trying some openstack all-in-one
[04:05] <Sebas_> but i don't know if it is something like that in ubuntu
[04:06] <Sebas_> like RDO from redhat has
[04:07] <sarnold> ahhh :)
[04:10] <jose> I don't use OpenStack :)
[04:11] <Sebas_> ohh, jose, you use other thing?
[04:12] <jose> yes, I use EC2
[04:12] <Sebas_> ahhh ok
[04:12] <sarnold> Sebas_: hrm, in the jujucharms.com there's a bundle for deploying openstack on a machine with nested KVM
[04:12] <sarnold> Sebas_: but I do'nt know the manage.jujucharms.com website well enough to find that bundle again
[04:12] <jose> let me try and do that for you
[04:12] <Sebas_> ohhh thanks!
[04:13] <sarnold> I've done nested KVM before when testing MAAS systems; it's a bit slow, but it got the job done..
[04:13] <sarnold> but nothing you'd want to use long-term
[04:14] <jose> sarnold: who created that bundle?
[04:14] <jose> is it http://manage.jujucharms.com/bundle/~james-page/openstack-on-openstack/openstack ?
[04:15] <sarnold> jose: that's the one! ah. it's for testing on clouds that already exist. :)
[04:16] <Sebas_> hmmm im getting a look
[04:16] <Sebas_> "The Ubuntu Server Team use this bundle for testing OpenStack-on-OpenStack."
[04:16] <Sebas_> hehe nice
[04:17] <Sebas_> the thing is to use openstack to manage the vm's with lxc
[04:17] <Sebas_> like the juju local does
[08:59] <zchander> Good morning (GMT+2 over here…). Is anyone around who provide some additional information about juju-gui together with a HAProxy based gateway?
[10:30] <rick_h_> zchander: never tried it but what's up?
[10:32] <zchander> I am (re)trying my MaaS cluster, but had to reinstall everything. I would like to access juju-gui from within our schoolnetwork, but our MaaS is in it’s own network.
[10:33] <zchander> I have a seperate server, with two network adapters, one connected to our schoolnetwork and one to our MaaS network. I would like to use the SSL enabled environment (Had the non-secure option working)
[10:37] <rick_h_> zchander: ok,so you could haproxy the 80 but not the 443?
[10:37] <zchander> rick_h_: Yes. using port 80 has worked (and before).
[10:40] <rick_h_> zchander: hmm, looks like we do send the port as 443 http://bazaar.launchpad.net/~juju-gui-charmers/charms/precise/juju-gui/trunk/view/head:/hooks/web-relation-joined#L29 if secure is on
[10:42] <zchander> My problem/issue is with HAproxy. I cannot seem to get a proper connection from my client (using SSL) to juju-gui (behind HAproxy)
[10:42] <rick_h_> zchander: looking at haproxy it seems it'll only pick up the port it's told if it has a service_name http://bazaar.launchpad.net/~charmers/charms/precise/haproxy/trunk/view/head:/hooks/hooks.py#L823
[10:42] <rick_h_> zchander: oh hmm, yea I'm not sure how the ssl pass through would work there.
[10:44] <rick_h_> at that point haproxy is playing a man in the middle attach almost to the client.
[10:45] <rick_h_> hmm, everything I'm seeing is having you setup haproxy to be the ssl endpoint
[10:51] <zchander> I am also trying it with Apache2 as the reverse proxy, but here I get some I/O error issues. Might be related….
[10:54] <rick_h_> zchander: yea, looking for docs/notes I did run across http://comments.gmane.org/gmane.comp.web.haproxy/15689 which seems to imply that it should be possible
[10:55] <rick_h_> zchander: the charm just might not support that complex a config ootb
[10:56] <zchander> The HAproxy server isn’t part of our juju environment. It is a seperate Ubuntu based server with 2 nics
[11:22] <rick_h_> zchander: oh ok, then yea. I think it should be possible just a matter of getting the right ssl handling config into the haproxy server I think.
[13:01] <rbasak> How do I generate a release tarball from the bzr branch (specifically 1.18)? I don't see any instructions anywhere, and the two are quite obviously different.
[13:05] <marcoceppi> rbasak: ask sinzui
[13:05] <sinzui> Be aware the answer might not make sense.
[13:06]  * sinzui still needs more coffee
[13:06] <rbasak> sinzui: I want to test the latest 1.18 branch against packaging in Utopic
[13:06] <rbasak> (since there's no release of the last few commits yet)
[13:06] <rbasak> So I tried to generate an orig tarball based on the bzr branch, which failed, and then I noticed that they aren't the same.
[13:07] <sinzui> rbasak, that is because devel/network broke juju devel and stable :)
[13:08] <rbasak> sinzui: yeah it's the fix for bug 1314686 I'm trying to verify
[13:08] <_mup_> Bug #1314686: Please add support for utopic <packaging> <juju-core:Fix Released by wallyworld> <juju-core 1.18:Fix Committed by wallyworld> <juju-core (Ubuntu):Triaged> <https://launchpad.net/bugs/1314686>
[13:08] <sinzui> rbasak, CI is catching up to devel at this hour. Next hour I will force a rebuild of stable if a new rev doesn't automatically trigger a build.
[13:08] <sinzui> rbasak, If you cannot wait a few hours, then you can build it yourself with lp:juju-releease-tools
[13:09] <rbasak> sinzui: OK, thanks. lp:juju-release-tools sounds like what I needed. I can wait though, but if I do, where do I get the orig tarball from after that? The orig tarball from the stable PPA?
[13:09] <sinzui> rbasak, http://bazaar.launchpad.net/~juju-qa/juju-release-tools/trunk/view/head:/README.md
[13:10] <sinzui> rbasak, make-release-tarball.bash -1 lp:juju-core/1.18
[13:10] <rbasak> sinzui: ah, great. Thanks!
[13:10] <sinzui> rbasak, make-package-with-tarball.bash stable ./juju-core_1.18.4.tar.gz \
[13:10] <sinzui>         'Full Name <user@example.com>'
[13:10] <sinzui> ^ that can be installed
[13:25] <rbasak> sinzui: thanks - I got a release tarball now I think. Do you accept MPs for juju-release-tools? I have a trivial fix, but it looks like it has only one revision fed from somewhere else.
[13:25] <sinzui> rbasak, We will accept fixes thanks
[13:26] <sinzui> rbasak, was the '-1' a problem. I often use the actual revno instead of an index
[13:27] <rbasak> sinzui: https://code.launchpad.net/~racb/juju-release-tools/hg/+merge/219188
[13:27] <rbasak> sinzui: ah, I missed the -1. I read the docs and looked up the revno.
[13:27] <sinzui> Thank you rbase. I will get that merged ina few minutes
[13:28] <rbasak> BTW, it gave me juju-core_1.18.4.tar.gz which doesn't quite seem right as there are more commits on top.
[13:28] <rbasak> "git describe" does something sensible here, by appending a suffix describing the extra commits (in git's case, the number of commits and the HEAD commit hash).
[13:28] <rbasak> Maybe that's appropriate here too?
[13:29] <rbasak> Or maybe just a "~bzr{revno}" if the tag doesn't exactly match.
[13:30] <rbasak> Actually "+bzr{revno}" would probably be more accurate.
[14:04] <Sebas_> lazyPower: thanks for the answer :)
[14:04] <lazyPower> Sebas_: o/  anytime
[14:04] <lazyPower> i'm puzzled why your bug isn't showing up in the rev queue
[14:04] <lazyPower> glad i saw the mail or your bug would have gone unnoticed.
[14:05] <Sebas_> lazyPower: take a look at the description i made in the bug report https://bugs.launchpad.net/charms/+bug/1315428
[14:05] <_mup_> Bug #1315428: Review needed: Drupal Charm <drupal> <Juju Charms Collection:New> <https://launchpad.net/bugs/1315428>
[14:05] <Sebas_> lazyPower: there are some of the questions
[14:05] <lazyPower> http://manage.jujucharms.com/tools/review-queue -- feel free to check ~ 15 minutes after you've opened a bug, it ingests every 15 minutes (so max wait is 30 mins) - and as you see its not in there.
[14:05] <Sebas_> lazyPower good to know that the mail helped hehe
[14:06] <lazyPower> indeed!
[14:06] <Sebas_> lazyPower nice, I sow it yesterday, but didn't see my issue hehe
[14:11] <mbruzek> Hey lazyPower there are more than one drupal charms out there.  I remember reviewing one recently.  What do we do with multiple requests for the same charm?
[14:11] <marcoceppi> Sebas_: lazyPower there's no linked bracnh
[14:11] <lazyPower> marcoceppi: ah, so the fact it's in github is the blocker for it getting into the queue. ok.
[14:12] <lazyPower> mbruzek: it'll require collaboration between the two charm authors i'd say. Drupal and ElasticSearch are both subject to this at the moment.
[14:12] <marcoceppi> mbruzek: none are in the store yet
[14:12] <lazyPower> mbruzek: that or may be the best charm win? (i really dotn know, this is a first to me)
[14:13] <lazyPower> Ideally we'd want both authors working together toward teh same goal, building a high quality charm that implements best practices from both branches. But that's my 2 cents.
[14:14] <mbruzek> Sebas_, for reference the other drupal charm is here: https://bugs.launchpad.net/charms/+bug/1290636
[14:14] <_mup_> Bug #1290636: New drupal charm submission. <Juju Charms Collection:Incomplete by dweaver> <https://launchpad.net/bugs/1290636>
[14:14] <Sebas_> mbruzek: ooh i see, opening here...
[14:14] <mbruzek> Sebas_, It uses apache2, and yours uses nginx, I would say that is pretty different.
[14:15] <Sebas_> mbruzek: it uses nginx with perusio configurations
[14:15] <mbruzek> Sebas_, but see if there is a way the authors could agree on something.
[14:15] <Sebas_> mbruzek: yes we can do a merge
[14:15] <mbruzek> Either that or race his charm to the store...
[14:16] <Sebas_> hehe
[14:16] <lazyPower> Sebas_: its ok to be opinionated in your charm, we encourage that. With that being said, extending one or the other - based on a user config (use_apache: type: boolean, default: false) would make it really nice...
[14:16] <lazyPower> to auto-tune the configuration to your given preference in httpd
[14:16] <Sebas_> mbruzek: there's others diferences too
[14:23] <Sebas_> there are other things like, importing an existing project, compass install, etc...
[14:23] <Sebas_> the thing is this charm is good practices oriented
[14:24] <Sebas_> a drupal boilerplate is used
[14:24] <lazyPower> dweaver: ping
[14:24] <lazyPower> Sebas_: you two should talk :)
[14:25] <Sebas_> lazyPower: yeah definitely
[14:28] <Tug> Hi everyone
[14:28] <mbruzek> Hi Tug
[14:28] <Tug> I'm having an error with debug-hooks
[14:28] <Tug> $ juju debug-hooks mongos/0
[14:28] <Tug> can't create socket: Permission denied
[14:28] <Tug> any idea ?
[14:29] <Sebas_> lazyPower: my questions about scaling are in the description of the issue, do you think thats enough?
[14:29] <lazyPower> Sebas_: occupied atm, can i get back to you?
[14:29] <Sebas_> lazyPower: to schedule our school charm :)
[14:29] <Sebas_> yes!! of course!
[14:29] <Sebas_> :D
[14:29] <Sebas_> lazyPower: thanksss
[14:29] <lazyPower> If you're not around when i circle back i'll reply to the thread.
[14:30] <lazyPower> thanks for your patience Sebas_
[14:30] <Sebas_> lazyPower :D
[14:30] <dweaver> lazyPower, pong
[14:31] <lazyPower> dweaver: Sebas_ is the other community member working on a drupal charm. You guys should coordinate, as there's awesome work in both charms.
[14:32] <Sebas_> dweaver: hey man!
[14:32] <dweaver> lazyPower, Yes, I saw there was another submission.  Hi Sebas_
[14:33] <Sebas_> dweaver: we should work together on this charm, what you think?
[14:33] <Sebas_> dweaver: if you can take a look at the charm to see what is doing
[14:34] <dweaver> Sebas_, I'd be happy to combine our resources.
[14:34] <Sebas_> but my goal is to deliver a best practices and enterprise charm ready
[14:34] <Sebas_> dweaver: \o/
[14:35] <Tug> it was working fine until now :'(. Please, do you guys have any tips to start debugging the issue ?
[14:35] <Sebas_> take a look at the charm later please :)
[14:36] <mbruzek> Tug I haven't seen that before.  Can you run:  juju ssh mongos/0 ?
[14:36] <Sebas_> dweaver: we need to put apache option as webserver in the other charm
[14:36] <Tug> mbruzek, yes I can
[14:36] <dweaver> Sebas_, That's a great goal and I'm happy to help.  Time is the problem for me, I don't have much spare, but I should be able to review the charm later this week and let you know what I think so far and some suggestions on how we can combine .
[14:36] <mbruzek> Tug, and you connect OK?  It looks like debug hooks failed on creating a connection.
[14:37] <Sebas_> dweaver: that would be great!! thanks :)
[14:37] <Tug> mbruzek, yes it connects fine. Then I can run $ sudo tmux attach-session -t mongos/0 and I also have can't create socket: Permission denied
[14:39] <lazyPower> Tug: looks like something detached you from teh session and there's  possibly a permissions problem. I ran into this before, but didn't think much of it - it wasn't production and i destroyed/redeployed
[14:39] <lazyPower> here's a bug that shows what i found: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597335
[14:41] <Tug> thx lazyPower, my error is even weirder as I'm running it with sudo
[14:41] <lazyPower> ah, thats no fun :(
[14:44] <Tug> not sure which process I could kill/restart...
[14:44] <Tug> I have 3 jujud
[14:45] <mbruzek> Tug, I believe lazyPower means to destroy-environment and restart this
[14:45] <mbruzek> juju destroy-environment
[14:46] <mbruzek> Tug, you should not need to kill individual processes
[14:46] <Tug> ok mbruzek, I'll try to destroy the service first I think
[14:47] <Tug> maybe even remove juju from the machine and add-machine later
[14:47] <mbruzek> Tug what environment are you using?
[14:47] <Tug> amazon
[14:48] <Tug> machines were created manually
[14:48] <mbruzek> Tug, I see
[15:50] <marcoceppi> hey stub got a second?
[16:01] <mbruzek> Is the 'HOME' environment variable not available in a hook environment?
[16:01] <mbruzek> in python I mean?
[16:01] <mbruzek> I am writing a charm in python, os.path.join(os.environ['HOME'], 'Liberty') that line fails.
[16:01] <mbruzek> But when I ssh to the charm 'HOME' is set for both ubuntu and root user.
[16:03] <marcoceppi> mbruzek: it's not set
[16:03] <marcoceppi> not in a hook at least
[16:04] <mbruzek> marcoceppi, ah I see.  Is there a good reason for not setting HOME ?
[16:04] <lazyPower> marcoceppi: since you're working with trusty testing, i've validated a MP works against a charm in series trusty - shoudl i go ahead and push it to trusty or wait for you to do it?
[16:04] <marcoceppi> mbruzek: probably, I mean what would HOME be?
[16:04] <mbruzek> I can just use a tmp directory or something.
[16:04] <lazyPower> meaning - it was targeted at precise, but works on trusty.
[16:04] <marcoceppi> lazyPower: link?
[16:04] <mbruzek> marcoceppi, I would expect HOME == /root
[16:04] <marcoceppi> mbruzek: I would expect HOME to be $CHARM_DIR
[16:05] <lazyPower> http://leankit.hostmar.co/lp:charms/elasticsearch/215696
[16:05] <mbruzek> You are after all the root user
[16:05] <marcoceppi> just because you're root doesn't mean you want things to end up in the HOME directory
[16:05] <marcoceppi> it makes people think about what they're doing, since services installed by charms should not run as root
[16:05] <mbruzek> That is fine, I was just trying to get a scratch area to do some work in, I thought HOME would be the place to do that
[16:06] <mbruzek> I can do it in temp.
[16:06] <mbruzek> or tmp
[16:06] <marcoceppi> mbruzek: tmp is a better place
[16:06] <marcoceppi> or $CHARM_DIR
[16:06] <marcoceppi> lazyPower: there's not elasticsearch charm in trusty
[16:06] <lazyPower> marcoceppi: i'm aware, thats why i asked.
[16:06] <lazyPower> this works on trusty
[16:06] <marcoceppi> lazyPower: there's not tests though
[16:07] <mbruzek> What would happen if a bash charm did "cd"  what directory would pwd return?
[16:07] <lazyPower> marcoceppi: there are when you pull elasticsearch and merge this in.
[16:07] <marcoceppi> lazyPower: ah, cool I'll keep that in mind
[16:07] <marcoceppi> mbruzek: probably either cwd or /
[16:08] <marcoceppi> lazyPower: if you want to give it the +1 and merge precise
[16:08] <marcoceppi> I'll do the promulgation to trusty
[16:08] <lazyPower> marcoceppi: already merged precise. pending your validation of trusty.
[16:08] <marcoceppi> lazyPower: ack, ty
[16:08] <Sebas_> i'm trying to deploy openstack all-in-one with juju in one dedicated server, so I'm going to try to deploy some charms that must be out of an lxc container
[16:08] <Sebas_> like the compute-node
[16:09] <marcoceppi> Sebas_: you really need two nodes to do that
[16:10] <marcoceppi> one for juju bootstrap (and all other services in LXC container)
[16:10] <marcoceppi> and a second one for nova-compute
[16:10] <Sebas_> marcoceppi: second dedicated server?
[16:12] <Sebas_> marcoceppi: i was thinking something like all the os charms in lxc, but! the compute-node (with lxc libvirt type) in the 0 machine
[16:12] <marcoceppi> right, everything can go in LXC excet nova-compute
[16:12] <Sebas_> marcoceppi: i'm triping ? hehe
[16:12] <Sebas_> right
[16:12] <marcoceppi> which I guess you /could/ put on node -
[16:12] <marcoceppi> 0*
[16:13] <marcoceppi> but it just seems like it'd do better on it's own machin
[16:13] <Sebas_> marcoceppi: \o/
[16:13] <marcoceppi> you also can't use ceph with this setup
[16:13] <Sebas_> of course, but i have only 1 machine hehe
[16:13] <Sebas_> marcoceppi: instead of swift ?
[16:14] <marcoceppi> well you couldn't have any ceph backed anything
[16:20] <Sebas_> marcoceppi: well, i'm going to try that approach adapting the openstack bundle
[16:20] <marcoceppi> Sebas_: good luck!
[16:20] <Sebas_> marcoceppi: thank you!!!
[17:08] <qhartman> If I destroy a service, should I expect juju to remove the associated packages from the machine it was deployed on?
[17:10] <qhartman> also, if I have all of my charm config in a file, and I run "juju set --config=config_file.conf the_charm" should I expect the_charm to get the updated config from there?
[17:16] <hatch> qhartman no it won't remove the associated packages, you'll have to account for that in the charm if you don't want to tear down the machine/container and create a new one (recommended)
[17:16] <hatch> qhartman when the config is updated the config update hook will be executed, from there, you do with the data what you wish
[18:51] <Sebas_> what's the best serie for deploying local juju ?
[18:51] <Sebas_> trusty ?
[18:51] <Sebas_> or precise ?
[18:53] <Sebas_> somebody? :P
[18:54] <Sebas_> i'm asking because i'm planning to deploy a nova-compute-node charm into the 0 machine
[18:58] <cory_fu> jose: Did you see my comment on the tracks charm?
[18:59] <jose> cory_fu: yep! I just came back from university
[18:59] <cory_fu> Oh, ok.  :)
[18:59] <cory_fu> It's so close!  :)
[18:59] <jose> are you sure I should do -lt?
[19:00] <cory_fu> Yeah.  Apparently, < does lexigraphical ordering instead of numerical ordering
[19:01] <jose> oh, ok
[19:01] <jose> I should change that everywhere, right?
[19:01] <cory_fu> Well, you could also use double parentheses instead of double brackets
[19:01] <cory_fu> http://www.tldp.org/LDP/abs/html/comparison-ops.html
[19:02] <cory_fu> I think everywhere you're comparing to a number (i.e., port)
[19:04] <jose> easier to do -lt :P
[19:04] <cory_fu> Yeah.  :)
[19:05] <jose> cory_fu: pushed!
[19:05] <cory_fu> Awesome!  Let me take a look
[19:06] <jose> cool
[19:09] <cory_fu> mbruzek: Here's an example of my super simple upstart script (writer) for Apache Allura: http://bazaar.launchpad.net/~johnsca/charms/precise/apache-allura/refactoring-with-tests/view/head:/scripts/write-service
[19:09] <mbruzek> Thanks cory_fu
[19:09] <lazyPower> jose: there's a problem with owncloud on default deploy. I've got a recent revision of the tests here - bazaar.launchpad.net/~lazypower/charms/precise/owncloud/refactor_amulet_tests/
[19:10] <lazyPower> that should be the last issue to resolve and its g2g for your dependent branch merge
[19:10] <lazyPower> s/owncloud on default deploy/ the port configuration code on default deploy/
[19:10] <cory_fu> I wrote that write_service script but it would be easier to have a files directory with the .conf files already created and just copy them into place with install or charmhelpers.core.host.write_file
[19:10] <jose> lazyPower: ack, taking a look
[19:10] <cory_fu> mbruzek: ^
[19:11] <mbruzek> cory_fu, yeah good idea.
[19:24] <Sebas_> yaiks!! juju-gui is not deploying, WARNING juju.worker.uniter.charm git_deployer.go:200 no current staging repo
[19:25] <Sebas_> with precise serie
[19:27] <jose> lazyPower: what's the problem with the owncloud charm?
[19:27] <jose> I cannot seem to find it
[19:27] <lazyPower> ports aren't exposed. Run the test with --set-e and --timeout 15m
[19:27] <lazyPower> then inspect the environment after the test runs.
[19:28] <jose> ok, trying now
[19:28] <lazyPower> jose: charm test -e amazon --set-e --timeout 20m 100-deploy.py -o test
[19:29] <lazyPower> that way you've got a) logs being piped after the run, b) an inspectable environment, and c) only running the test in question, nto waiting for the setup script to run.
[19:30] <whit> hazmat, bcsaller, setup completes, but hangs on the login
[19:31] <whit> this is aws single node
[19:31] <jose> (my amazon environment is named ec2)
[19:32] <bcsaller> whit: did you bootstrap with the proper constraints
[19:34] <Sebas_> wow! juju-gui is not deploying any more :(
[19:34] <Sebas_> http://pastebin.com/PT716tDT
[19:35] <marcoceppi> Sebas_: this is a juju-core issue not a juju-gui issue
[19:35] <marcoceppi> Sebas_: 1.18.2 ?
[19:35] <Sebas_> let me check
[19:35] <Sebas_> marcoceppi: 1.18.3.1
[19:40] <Sebas_> marcoceppi: do you think I must report a bug?
[19:50] <marcoceppi> this has been fixed in 1.19
[19:50] <marcoceppi> Sebas_: they removed the git requirement all together
[19:52] <Sebas_> oohh
[19:55] <Sebas_> marcoceppi: 1.19 is stable?
[19:55] <marcoceppi> Sebas_: no, 1.ODD are devel releases, 1.EVEN are stables
[19:55] <marcoceppi> Sebas_: but it's been a known shortcoming for a while in juju-core, using git as a state server for charms
[19:56] <Sebas_> ooohh marcoceppi i get it
[19:56] <Sebas_> marcoceppi: do you know a workarround for this?
[19:56] <jose> marcoceppi: did you get my comment about the wp mp?
[19:56] <marcoceppi> jose: no, link?
[19:56] <marcoceppi> Sebas_: for now just ssh in to the server and install git, then deploy again
[19:57] <Sebas_> hehe marcoceppi i was just going to do that
[19:57] <Sebas_> thanks :D
[19:57] <Sebas_> marcoceppi++
[19:57] <jose> marcoceppi: https://code.launchpad.net/~jose/charms/precise/wordpress/fix-1309980/+merge/216568
[19:58] <marcoceppi> jose: oh, yeah, as long as it's still in the review queue it'll get looked at
[19:58] <marcoceppi> (it's still in the review queue)
[19:59] <jose> I know, just wanted to let you know
[19:59] <Sebas_> humm thats strange "Could not resolve 'archive.ubuntu.com'"
[20:00] <jose> Sebas_: juju resolved unit/# --retry
[20:00] <Sebas_> jose: will try
[20:01] <Sebas_> jose: the thing is it isn't in a error state
[20:01] <jose> oh, where is that error?
[20:01] <Sebas_> *an error state
[20:02] <Sebas_> jose: i cant access internet from the machine
[20:03] <Sebas_> so the apt isn't finding the repository
[20:03] <marcoceppi> Sebas_: so there's your problem
[20:03] <Sebas_> marcoceppi: yep
[20:03] <marcoceppi> Sebas_: why git wasn't installed (it should be installed when a machine is provisioned)
[20:03] <marcoceppi> Sebas_: is this maas?
[20:03] <Sebas_> marcoceppi: it's juju-local
[20:03] <Sebas_> just that
[20:03] <marcoceppi> Sebas_: ah, can you run this?
[20:04] <Sebas_> in a trusty
[20:04] <marcoceppi> apt-config | grep -ri "proxy"
[20:04] <marcoceppi> inside the unit
[20:04] <Sebas_> marcoceppi: ok
[20:04] <marcoceppi> sudo apt-config dump | grep -ri "proxy"
[20:04] <marcoceppi> soryr, let me give you the real command
[20:04] <Sebas_> .profile:[ -f "$HOME/.juju-proxy" ] && . "$HOME/.juju-proxy"
[20:05] <marcoceppi> Sebas_: can you pastebin the output of sudo apt-config dump ?
[20:05] <Sebas_> marcoceppi: of course
[20:06] <Sebas_> marcoceppi: http://pastebin.com/j81bVttQ
[20:07] <marcoceppi> Sebas_: is that on your machine or the node?
[20:08] <Sebas_> unit
[20:08] <Sebas_> machine
[20:08] <Sebas_> marcoceppi: ubuntu@ubuntu-local-machine-2:~$ sudo apt-config dump
[20:08] <Sebas_> marcoceppi: why, it's wired? hehe
[20:09] <marcoceppi> well, I don't see any proxy lines in there
[20:09] <marcoceppi> so that's odd
[20:09] <Sebas_> its a fresh install of trusty and juju
[20:09] <marcoceppi> you should just be able to apt-get update/upgrade without issue
[20:09] <Sebas_> marcoceppi: yep, thats the first time that happen
[20:17] <Sebas_> marcoceppi: well, i think i'm gonna try to re install everything again
[20:48] <Sebas_> well, i tried with another version 1.18.1 and didn't work again, so the proxy isn't working
[20:48] <Sebas_> i don't know why :(
[21:50] <lazyPower> jose: i'm about to EOD
[21:50] <lazyPower> how's the owncloud discovery going?
[23:43] <jose> lazyPower: as I said, I didn't find out anything obvious, so if you could point me in the right direction I'd appreciate it :)