[13:57] <natefinch> jcastro, marcoceppi:  man, there is so much missing from the charm writing docs
[13:57] <jcastro> like what?
[13:57] <marcoceppi> natefinch: yes, most of the effort was put in the user docs, the author docs are still, lacking
[13:58] <natefinch> jcastro: like... what's the format of config.yaml?
[13:58] <jcastro> I wasn't being faceitous, just want specifics, etc.
[13:58] <jcastro> oh
[13:58] <natefinch> jcastro: I'll make a list :)
[13:59] <marcoceppi> natefinch: please do!
[14:01] <aisrael> Examples using the Python charmhelpers. I think most of the examples use Bash.
[14:03] <natefinch> marcoceppi: but to unblock me - what are the valid values for "type" in config.yaml?  Specifically I have an int and a list of strings (email addresses)
[14:03] <marcoceppi> natefinch: no lists
[14:03] <marcoceppi> you get boolean, int, and string
[14:03] <natefinch> marcoceppi: bah
[14:04] <marcoceppi> natefinch: you have the power to fix this :)
[14:04] <marcoceppi> specifically, I would LOVE an ENUM field type
[14:04] <marcoceppi> which would produce a drop down in the gui and allow validation outside of the hooks
[14:05] <natefinch> marcoceppi: hmm yeah, that's a little more tricky than just a list....
[14:06] <marcoceppi> well, its completely different than a list
[14:06] <james_w`> another I had trouble finding was a list of the environment variables that each hook gets
[14:06] <marcoceppi> typically people just do comma and space delimited lists as strings
[14:07] <james_w`> turns out I just missed it though: https://juju.ubuntu.com/docs/authors-hook-environment.html
[14:09] <natefinch> marcoceppi: is JUJU_HOOK_NAME always available when hook is running, or only during debug?  Docs seem to indicate only during debug: https://juju.ubuntu.com/docs/authors-hook-environment.html#environment-variables
[14:09] <marcoceppi> natefinch: oh, I wasn't aware it was only debug
[14:10] <natefinch> marcoceppi: I don't know, I was asking you :)  I would hope it was just always set.  I can check the code if you don't know
[14:23] <jose> arosales: hey, do you know if we have a list of currently orphaned charms?
[14:25] <dannf> marcoceppi: advice on whether or not this is a reasonable way to go? if so, i'll propose similar things for other charms. https://code.launchpad.net/~dannf/charms/precise/mediawiki/restrict-ppa-to-precise/+merge/233062
[14:27] <marcoceppi> dannf: that looks fine to me
[14:36] <arosales> jose: I think we should be able to find those by looking for charms that have a bug that states "maintainer needed"
[14:37] <arosales> jose, but I don't have a readily available list that I could reference atm.
[14:46] <natefinch> marcoceppi: btw, what I'm working on: https://github.com/natefinch/discourse
[14:47] <jose> arosales: no worries. I will try and make one when possible
[14:47] <marcoceppi> natefinch: ah, awesome, using the docker version of the discourse
[14:47] <marcoceppi> natefinch: sweet
[14:47] <natefinch> marcoceppi: yep
[14:47] <natefinch> marcoceppi: and written in Go ;)
[14:48] <marcoceppi> breakin all the walls!
[14:48] <natefinch> marcoceppi: gotta keep things interesting.. if I don't make at least a few people mad every day, I'm not doing my job ;)
[14:50] <arosales> jose: we have the data from charm world on proof failures, and I think we have a maintainer needed bug. So may just be a matter of quering
[14:50] <jose> cool!
[14:52] <arosales> jose: btw congrats on your successful application to the ~charmers team :-)
[14:53] <jose> arosales: thanks! I really look forward to keep working with all you guys :)
[16:10] <bloodearnest> Is there a specific reason why "unit-get public-address" returns the private address when there is no public address?
[16:18] <marcoceppi> bloodearnest: that's what juju assumes is the public address?
[16:18] <marcoceppi> which cloud?
[16:20] <bloodearnest> marcoceppi: openstack
[16:20] <bloodearnest> and local
[16:21] <bloodearnest> marcoceppi: it means I need to compare the address against known private ranges, and even that is a guess
[16:21] <marcoceppi> bloodearnest: well, local is technically correct
[16:21] <marcoceppi> that's the public address.
[16:22] <marcoceppi> Not sure about openstack, mihgt need to open a bug about that
[16:23] <bloodearnest> marcoceppi: sure, it makes sense with local
[16:50] <JoshStrobl> Hey lazyPower, got any more good mixes for me to listen to?
[18:00] <kwmonroe> hey folks, default-series is empty in my local env config, and i'm running trusty.  when i charm get mongodb, it pulls from lp:~charmers/charms/precise/mongodb/trunk.  why does it grab from precise?
[18:00] <kwmonroe> i can get trusty/mongodb if i add the namespace.. just wondering why it doesn't choose trusty by default (on a trusty host)
[18:22] <marcoceppi> kwmonroe: charm isnt' tied to juju env
[18:23] <marcoceppi> charm was created when there was only one default series, which was precise
[18:23] <marcoceppi> so in order to support older workflows of just "charm get" it'll remain precise for sometime
[18:25] <kwmonroe> ah, gotcha marcoceppi.  thanks!
[20:38] <mbruzek> Hey #juju folks, I have a machine in "pending" because there are no matching tools for precise.
[20:38] <mbruzek> agent-state-info: no matching tools available
[20:38] <mbruzek> I tried bootstrapping thusly:
[20:38] <mbruzek> $ juju bootstrap -v -e local --series precise,trusty --upload-tools
[20:39] <mbruzek> Any ideas on what is wrong with my precise agent or how to fix?
[20:40] <mbruzek> From all-machines.log ERROR juju.provisioner provisioner_task.go:418 cannot find tools for machine "1": no matching tools available
[20:41] <mbruzek> I found an old bug that is fix released https://bugs.launchpad.net/juju-core/+bug/1309805
[20:41] <mup> Bug #1309805: LXC / Local provider machines do not boot without default-series <config> <local-provider> <lxc> <juju-core:Fix Released by jose> <https://launchpad.net/bugs/1309805>
[20:45] <mbruzek> 1.20.6-trusty-amd64