[01:05] <lazyPower-sprint> rcj: i dont think at present that is a known constraint
[01:27] <mbruzek> marcoceppi, tvansteenburgh  please take a look
[01:27] <mbruzek> https://code.launchpad.net/~mbruzek/charm-tools/categories-info/+merge/233849
[01:42] <jose> arosales: hey, I'm around now :)
[01:44] <lazyPower-sprint> jose: o/
[01:44] <jose> hey lazyPower-sprint!
[01:45] <jose> anything you need me to take a look at on the revq?
[01:45] <jose> I'm ready for n'acking
[01:47] <arosales> jose, hello
[01:48] <arosales> jose, I saw your comment re pagekite
[01:48] <jose> cool
[01:48] <mbruzek> jose, hello
[01:48] <jose> hey mbruzek!
[01:48] <arosales> I got some suggestions on the readme, and I am still trying to learn about pagekite myself
[01:48] <mbruzek> jose We are all sprinting and adding icons, readme, etc.
[01:49] <jose> arosales: it's a charm I still need to investigate on since it's tunnelling but only supports minecraft and html protocols
[01:49] <jose> mbruzek: if you could point me to a couple charms that need them, I can give a hand with it too
[01:49] <jose> checking on mbruzek's munin MP
[01:50] <mbruzek> jose can you log in to http://review.juju.solutions/
[01:50] <mbruzek> the log in feature is new
[01:51] <jose> awesome
[02:01] <lazyPower-sprint> hey asanjar, just to wrap wrap up zookeeper so its ready for the store i'm going to add a README update
[02:02] <lazyPower-sprint> you'll want to backport it to your devel branch before you move forward with the charm. But you need to illustrate that changing the zookeeper storage path is destructive, therefore immutable.
[02:02] <lazyPower-sprint> unless mbruzek says this is HORRIBLE
[02:02] <lazyPower-sprint> https://bugs.launchpad.net/charms/+bug/1353197
[02:02] <mup> Bug #1353197: hortonworks hdp2.1 zookeeper charm <Juju Charms Collection:Fix Committed> <https://launchpad.net/bugs/1353197>
[02:07] <mbruzek> Hey ecosystem, please check out my application for ubuntu membership
[02:07] <mbruzek> https://wiki.ubuntu.com/mbruzek
[02:08] <mbruzek> jcastro, ^
[02:53] <lazyPower-sprint> mwenning: perchance are you around?
[02:56] <mwenning> lazyPower-sprint, I am.
[02:56] <mwenning> sup
[02:56] <lazyPower-sprint> i'm remoted into the dell test lab
[02:57] <mwenning> ok.
[02:57] <lazyPower-sprint> and boysenberry.maas isn't found - looks liek either the bootstrapped env went away or my DNS is incorrectly setup
[02:57] <lazyPower-sprint> can you take a peek for me?
[02:59] <mwenning> lazyPower-sprint, stby
[02:59] <lazyPower-sprint> ack
[03:03] <mwenning> lazyPower-sprint, yeah, lookup boysenberry.maas: no such host
[03:04] <mwenning> lazyPower-sprint, are you working late or are you on a different part of the planet?
[03:12] <mwenning> lazyPower-sprint, I'm at home right now, I'll take a look at it first thing tomorrow morning (about 9:00 CST)
[03:16] <lazyPower-sprint> I'm west coast, working late at a sprint
[03:16] <lazyPower-sprint> thanks foir taking a look mwenning
[03:17] <mwenning> lazyPower-sprint, ok that should work out ok.
[03:21] <lazyPower-sprint> mwenning: if i'm not around, email me and i'll be around shortly. You've got priority for me given the nature of this merge and the time constraints i've got to work with.
[03:23] <mwenning> lazyPower-sprint, I'm going to try destroying and rebootstrapping juju.  timeout was 9999 (seconds?) so it probably timed out
[03:33] <mwenning> "never mind", looks like I'll have to reboot it from the lab.
[03:41] <lazyPower-sprint> ack. I saw the email followup mwenning - We'll re-convene on this in the morning
[03:41] <jose> woohoo, fun netsplit
[03:41] <lazyPower-sprint> mwenning: i dont want to keep you working late. I can bust this out early in the AM and get some some solid feedback.
[03:41] <mwenning> lazyPower-sprint, cool.  See you then.
[04:38] <ianunruh> is this still valid: https://juju.ubuntu.com/docs/howto-privatecloud.html
[04:38] <ianunruh> there doesn't seem to be any `juju metadata` or `juju generate-tools`
[04:45] <ianunruh> after configuring my OpenStack env, I keep getting
[04:45] <ianunruh> ERROR index file has no data for cloud {RegionOne http://172.20.4.10:5000/v2.0/} not found
[04:55] <ianunruh> interesting.. apparently the juju client for OS X doesn't have the metadata command
[13:09] <rogpeppe> has anyone here used the juju publish command?
[13:10] <rick_h_> rogpeppe: does it exist yet?
[13:10] <rick_h_> rogpeppe: it's something we've started a spec for
[13:10] <rogpeppe> rick_h_: it's existed for 18 months now
[13:11] <rogpeppe> rick_h_: the current version just pushes to launchpad and waits for the charm store to pick it up
[13:11] <rick_h_> rogpeppe: ah, cool then. Didn't realize it was already a command
[14:10] <jose> marcoceppi: ping
[15:24] <rbasak> Are bug reports accepted at for example https://github.com/juju/testing/issues, or should I file in Launchpad?
[15:32] <rbasak> niemeyer: one further question about licensing for https://github.com/go-yaml/yaml. I can't find an actual copyright statement.
[15:32] <rbasak> niemeyer: I presume this is Canonical? Please could you add a copyright claim to somewhere in that file, so it is clear who is licensing it?
[16:05] <niemeyer> rbasak: It's all Canonical
[16:05] <niemeyer> rbasak: I'll add a note to LICENSE
[16:06] <rbasak> Thanks!
[16:10] <niemeyer> rbasak: Done
[16:10] <rbasak> Thanks again!
[17:00] <allomov> Hey, all.
[17:01] <allomov> Does juju-local work with mac os ? What will it use instead of LXC ?
[17:10] <hazmat> allomov, it doesn't work on osx, you can download a vagrant image with juju local provider setup using lxc
[17:10] <hazmat> for osx local workflows.. else the client binary on osx can be used against public/private clouds, etc
[17:10] <hazmat> rogpeppe, i use hte publish command
[17:11] <hazmat> rogpeppe, i point it out to people when they ask why the charm store isn't publishing their charm
[17:11] <rogpeppe> hazmat: it seems to rely on someone running charmload periodically - is that right?
[17:11] <rogpeppe> hazmat: (it also seems to poll indefinitely without any delay, but perhaps i'm misreading the code)
[17:13] <hazmat> rogpeppe, charmload is running periodically and basically contionously.. publish is fairly quick in practice.
[17:14] <hazmat> rogpeppe, but yes i think your assumptions are correct,  alternatively you could try writing a charm and publishing it to see behavior ;-)
[17:14] <rogpeppe> hazmat: :-)
[17:15] <rogpeppe> hazmat: we're looking at adding a backwardly compatible API to the new charm store and wondering just how much compatibility is needed. for example, is it reasonable to ask charm publishers to use a newer version of juju?
[17:17] <hazmat> rogpeppe, imo that's reasonable.. as long as you keep the push  / store feedback
[17:17] <rick_h_> hazmat: the feedback would be over the changes api endpoint (the rss-like api added)
[17:17] <hazmat> rogpeppe, the goal is that it would eventually be actually a publish..
[17:17] <hazmat> rick_h_, that's not appropriate
[17:18] <hazmat> rick_h_, the point is to get feedback on a particular charm on why it wasn't published
[17:18] <rick_h_> hazmat: yes, that's the next step after getting the new api in place in the current store location with enuogh backwards compat to not break folks.
[17:18] <rogpeppe> hazmat: by "push / store feedback", you mean getting errors from the charm store when you try to publish a charm?
[17:18] <rogpeppe> hazmat: that's actually easier with the new model
[17:19] <rick_h_> hazmat: oh yes, sorry. Thought you meant feedback on 'it's loaded now'
[17:19] <hazmat> rogpeppe, yes.. ie. lint works, i've pushed the charm to lp, i've deployed it.. but its not showing up in the store.. why?
[17:19] <rogpeppe> hazmat: because you get the error directly from the charm store
[17:19] <hazmat> rogpeppe, with publish yes.. else the whole process is async
[17:19] <rogpeppe> hazmat: rather than relying on some async process to push it or set errors associated with it
[17:25] <jcastro> hi guys
[17:25] <jcastro> so the flagbearer charms will be: postgres, elasticsearch, rails, meteor, and chamilo
[17:31] <fuzzy> What do you mean by flagbearer?
[17:31] <fuzzy> Is there a specific reason mongo isn't in that list?
[17:32] <fuzzy> jcastro:
[17:32] <jcastro> we're picking charms that have tests, and use charm helpers.
[17:33] <jcastro> dunno the state of mongo off the top of my head, let me ask.
[17:33] <fuzzy> No worries, I was just curious.
[17:33] <jcastro> fuzzy, when we say "flagbearer" we mean "is this a good charm that people can look at and learn how to write a charm"
[17:34] <fuzzy> AH
[17:34] <jcastro> apparently the mongo charm is kind of huge, monolithic, doesn't use charm helpers to the extent that it should, etc.
[17:34] <jcastro> but, it for sure will remain "featured" on the gui
[17:34] <jcastro> it's a high quality charm, just not something you'd start off with.
[17:35] <fuzzy> The only reason I asked based on what you listed previously, you described about 70% of my stack
[17:35] <fuzzy> :)
[17:37] <jcastro> people are adding tests to those now, so you're in luck!
[18:09] <tvansteenburgh> fuzzy: i just pushed fixes for the meteor charm to https://code.launchpad.net/~tvansteenburgh/charms/precise/meteor/fix-npm-install
[18:10] <tvansteenburgh> fuzzy: (in case you are eager to try it)
[18:11] <tvansteenburgh> fuzzy: it's being reviewed now, hopefully will be pushed to the charm store soon
[18:11] <fuzzy> tvansteenburgh: If I get on that side of my work today, I'll totally try that.  Thank you :)
[18:11] <tvansteenburgh> fuzzy: sure thing!
[18:50] <whit> jcastro, gh:whitmo
[18:50] <cory_fu> jcastro: gh:johnsca
[18:55] <kentb> I'm trying to run a charm test using "charm test -e maas 10-deploy-test.py" but I get a complaint saying no tests were found....what am I missing?   juju is version 1.20.7 and I'm running Trusty 14.04.1 with charm-tools version 1.3.3
[18:56] <arosales> jcastro, fyi  jose just merged your meteor mp: https://code.launchpad.net/~jorge/charms/precise/meteor/readme-updates/+merge/233962
[18:56] <arosales> thanks jose
[18:56] <jose> not a prob arosales :)
[19:00] <jcastro> <3
[19:05] <allomov> hazmat: that's ok, thank you
[19:12] <mbruzek> kentb, are you in the charm directory?
[19:13] <mbruzek> kentb, I am running a similar command right now:  juju test -v --set-e 10-deploy
[19:23] <kentb> mbruzek: hey. thanks. I had to back up one directory and now it appears to be doing the bootstrap thing, so far.   I was inside the /tests directory of my charm prior to that
[19:25] <mbruzek> kentb, you are welcome
[19:58] <pafounette> hi
[19:59] <pafounette> can any one confirm that juju only check hardcoded error message without any l10n ?
[20:07] <pafounette> is there any reason explaining why juju check against EN strings but not the errno ?
[20:07] <pafounette> like ... here https://github.com/juju/juju/blob/master/environs/sshstorage/storage.go#L254
[20:09] <mbruzek> pafounette, there is a #juju-dev room that might have more of the juju developers in thre.
[20:09] <pafounette> thanks :)
[20:10] <mbruzek> pafounette, from the link you sent it does not look like Juju is looking up error message, but I am not a go programmer
[20:31] <marcoceppi> cory_fu: https://code.launchpad.net/~marcoceppi/charms/precise/chamilo/unit-tests/+merge/234000
[20:37] <cory_fu> marcoceppi: Looks great.  I will review and merge when I get a chance, or if you want to propose it upstream, that seems fine to me.
[20:38] <marcoceppi> cory_fu: I may, but laziness is setting in
[20:38] <cory_fu> marcoceppi: And I'm being pulled in a couple directions, so... :)
[20:38] <marcoceppi> I thought you had some other things you were fixing
[20:38] <marcoceppi> cory_fu: well, it's not urgent ;)
[20:39] <cory_fu> marcoceppi: I was just adding tests, which you covered.
[21:22] <tvansteenburgh> fuzzy: new meteor charm is in the store now
[21:23] <fuzzy> cool
[21:46] <cory_fu> marcoceppi: Oh yeah, we can't merge that upstream yet, because it relies on the charmhelpers changes.  Those still need tests as well; you didn't merge those, did you?
[21:47] <marcoceppi> cory_fu: not yet
[21:48] <cory_fu> Well, like I said, I need to add tests.  And I also want to add a helper for downloading a file & checksumming it
[22:27] <tiger7117> Hi
[22:28] <tiger7117> ERROR cannot assign unit "wordpress/0" to machine 2: series does not match
[22:28] <tiger7117> whats this meant ?
[22:28] <tiger7117> i gave this command # juju deploy wordpress --to=2
[22:28] <rick_h_> tiger7117: the charm you're deploying is one series (precise or trusty or something) and the machine is another. This is common if you try to colocate two different services on one machine
[22:29] <tiger7117> there is no other services on that machine No 2. so
[22:29] <rick_h_> tiger7117: right, but how did machine #2 come to be?
[22:30] <tiger7117> i was just deploying wordpress on # 2 and mysql # 3
[22:30] <tiger7117> i tried to deploy mysql and it worked with out any error message but for wordpress this Error message
[22:30] <rick_h_> tiger7117: does juju status show you what series is on machine #2? precise or trusty?
[22:31] <tiger7117> trusty
[22:31] <rick_h_> tiger7117: hmm, looks like no trusty wordpress charm
[22:32] <tiger7117> yes, looks like.. becoz now in juju status its showing Service: wordpress: charm: cs:precise/wordpress-26
[22:32] <tiger7117> and in Units: Wordpress/0, Agent-Status: pending
[22:32] <tiger7117> now ?
[22:34] <tiger7117> http://manage.jujucharms.com/~narindergupta/trusty/wordpress
[22:34] <rick_h_> so now you have to kill it off. juju resolved wordpress/0 and then juju destroy-service wordpress/0
[22:34] <rick_h_> tiger7117: yes, so that's someone's personal wordpress charm. I don't know anything about it.
[22:36] <tiger7117> # juju remove-service wordpress works .. destory-service unknow
[22:36] <tiger7117> well.. now what should i do to install/setup wordpress ?
[22:37] <rick_h_> tiger7117: so if you destory that machine and start over
[22:38] <rick_h_> there's a precise mysql charm that's been reviewed/etc
[22:38] <rick_h_> you can install it with juju deploy cs:precise/mysql
[22:39] <tiger7117> hmm.. so wordpress is in precise so now have to install mysql in precise ?
[22:39] <rick_h_> tiger7117: and then your juju deploy of the wordpress charm would work just fine
[22:39] <rick_h_> tiger7117: or use two machines, one precise and one trusty
[22:39] <tiger7117> how to make machine precise ?
[22:40] <rick_h_> you have to kill that machine and start over.
[22:40] <rick_h_> juju remove-machine I think
[22:41] <tiger7117> oh
[22:42] <tiger7117> i am using JuDo plugin for DigitalOcean
[22:42] <tiger7117> for adding machines of Digital Oceans
[22:59] <tvansteenburgh> trusty/swift-storage
[22:59] <jcastro> <-- reviewing trusty/mysql
[23:04] <tvansteenburgh> trusty/swift-proxy
[23:04] <jcastro> <-- review precise/tracks
[23:05] <aisrael> reviewing precise/thinkup
[23:05] <tvansteenburgh> trusty/rsyslog-forwarder-ha
[23:07] <tvansteenburgh> trusty/rsyslog
[23:08] <lazyPower-sprint> cs:trusty/quantum-gateway-5	
[23:09] <mbruzek> cs:trusty/pgbadger-0
[23:09] <tvansteenburgh> trusty/postgresql
[23:10] <marcoceppi> cs:trusty/landscape-client-4
[23:11] <tvansteenburgh> trusty/ntp
[23:11] <arosales> arosales cs:trusy/openstack-dashboard
[23:14] <tvansteenburgh> trusty/nova-compute
[23:14] <jcastro> precise/cassandra
[23:14] <jcastro> is done!
[23:15] <jcastro> precise/juju-gui
[23:18] <jcastro> precise/lodgeit
[23:23] <tvansteenburgh> trusty/nova-cloud-controller
[23:23] <jose> jcastro: mind a quick PM?
[23:23] <jcastro> sure!
[23:24] <lazyPower-sprint> arosales: http://paste.ubuntu.com/8304170/
[23:25] <tvansteenburgh> trusty/mongodb
[23:25] <kwmonroe> precise/pictor-3
[23:26] <lazyPower-sprint> mbruzek: https://code.launchpad.net/~lazypower/charms/trusty/quantum-gateway/fix_proof/+merge/234023
[23:27] <lazyPower-sprint> cs:trusty/ntp-5	
[23:30] <mwhudson> sooo
[23:31] <mwhudson> if i want a webpage with graphs of the load on all the machines i am deploying things with juju on
[23:31] <mwhudson> i need to read up about subordinate charms, right?
[23:32] <jcastro> both precise/juju-gui and trusty/juju-gui are done
[23:33] <jcastro> mwhudson, yep
[23:33] <jcastro> mwhudson, is it like a webui on each unit or an agent that reports to a centralized webui?
[23:34] <mwhudson> jcastro: more the latter
[23:34] <lazyPower-sprint> cs:trusty/keystone-7
[23:34] <jcastro> yeah so the agent would be a sub, the webui would be a normal charm
[23:34] <mwhudson> it's for a demo, i want to demonstrate load being spread across the cluster
[23:35] <mwhudson> jcastro: are there any of these charmed up already?  istr something about ganglia
[23:35] <jcastro> http://blog.dasroot.net/writing-the-papertrail-charm/
[23:35] <jcastro> check that out ^^^
[23:36] <jcastro> mwhudson, lazyPower-sprint just informed me that ganglia-node is a sub, probably what you want
[23:36] <jcastro> http://manage.jujucharms.com/charms/precise/ganglia-node
[23:37] <aisrael> cs:trusty/glance
[23:40] <mwhudson> jcastro: hmm thanks
[23:45] <lazyPower-sprint> did anyone land cs:trusty/jenkins yet?
[23:52] <jcastro> I'm taking precise/squid-forward-proxy
[23:53] <jcastro> I'm taking precise/vsftpd
[23:58] <jose> jcastro: do you have any more charms that fail proof?
[23:58] <jcastro> tons
[23:59] <jcastro> http://reports.vapour.ws/charm-tests-by-charm
[23:59] <jcastro> this is what we're going off right now
[23:59] <jose> cool, thanks
[23:59] <jcastro> the UI is not idea
[23:59] <jcastro> but if a charm proof is not 0, it failed
[23:59] <jcastro> adding tests also helps of course, heh