[08:30] <kjackal> Hello Juju World!
[09:45] <andrey-mp> Hi! jamespage: are you here?
[13:27] <marcoceppi> if anyone is interested, charm and charm-tools are now snapped up in edge for testing.
[13:27] <marcoceppi> `snap install charm --edge`
[13:29] <rick_h_> marcoceppi: sweet
[13:29] <rick_h_> marcoceppi: was there any issues with the macaroon storage path and such?
[13:30] <marcoceppi> not when you PLUGinto home
[13:30] <marcoceppi> git was the biggest problem >_>
[13:30] <marcoceppi> rick_h_: https://github.com/juju-solutions/charm-pkg/blob/master/snapcraft.yaml
[13:31] <marcoceppi> rick_h_: however, putting the macaroon data in $SNAP_DATA_PATH is a good idea
[13:31] <rick_h_> very cool marcoceppi
[13:49] <cholcombe> stub, question for ya with the apt layer
[14:05] <stub> cholcombe: yo
[14:06] <cholcombe> stub,  i know it's super late there.  I'm running into some trouble getting the config.yaml correct with the apt layer.  I followed the readme closely but it won't build or deploy
[14:06] <cholcombe> stub, i'm falling back on adding the apt sources in my reactive.py which isn't really the best
[14:07] <stub> Got a pastebin?
[14:07] <cholcombe> sure one sec
[14:09] <cholcombe> stub, https://gist.github.com/cholcombe973/e1405d70ba4921178e0908d7c4a6ba1c
[14:10] <stub> cholcombe: at first glace that looks fine. What happens when you deploy it?
[14:10] <cholcombe> nothing it seems.  it doesn't setup either of the sources in the /etc/apt/sources.list file
[14:11] <cholcombe> when i include the same thing in the python reactive.py file it works ok
[14:11] <stub> cholcombe: Does your layer.yaml declare its using layer:apt, and its all been rebuild and upgraded?
[14:12] <cholcombe> stub, yeah i have this in there: includes: ['layer:basic', 'layer:apt', 'interface:ceph-client']
[14:13] <stub> The indentation seems wonky - it doesn't parse as yaml
[14:14] <cholcombe> oh yeah i fixed that
[14:14] <cholcombe> i recreated the file to show you what it looked like
[14:16] <stub> I'd need to see the logs to diagnose further
[14:16] <cholcombe> stub, ok no problem.  i can pack them up
[14:16] <cholcombe> stub, do you have a working example i can take a look at?
[14:17] <stub> The PostgreSQL charm uses the apt layer. Or are you after a mojo spec that configures it?
[14:18] <cholcombe> postgres charm sounds fine.  i'll check that out :)
[14:18] <cholcombe> either one.  i'm looking for how the config.yaml was setup
[14:18] <cholcombe> prob the mojo spec then
[14:18] <stub> telegraf-charm might be better
[14:18] <cholcombe> ok
[14:18] <stub> launchpad.net/telegraf-charm
[14:19] <cholcombe> awesome thank you
[14:21] <stub> cholcombe: In your logs, you should see 'Initializing Apt Layer', soon after which it will call charmhelpers.fetch.configure_sources() (not sure if that gets logged)
[14:22] <stub> One easy way to test the layer is being bootstrapped - set the 'package_status' config to 'bogus'. It should put your unit into a blocked state until you give it a valid value.
[14:23] <cholcombe> ok
[14:53] <stub> cholcombe: oh, that is your config.yaml you posted.
[14:54] <stub> cholcombe: You are setting install_sources and install_keys to strings, but in config.yaml options are mappings. You want to be setting options: install_sources: default: , not options: install_sources:
[14:56] <stub> https://git.launchpad.net/telegraf-charm/tree/config.yaml
[14:56] <stub> (I was thinking that was a deployment config for some reason)
[14:57] <andrey-mp> anybody knows where is jamespage? or where I can find him? maybe he is on vacation?
[15:09] <mbruzek> magicaltrout: Are you able to join the meeting?
[15:13] <cholcombe> stub, thanks!
[15:14] <stub> cholcombe: I'm surprised juju let you deploy it at all
[15:14] <cholcombe> stub, juju is lazy haha
[15:32] <cholcombe> stub, i updated the gist.  is this more like what the apt layer expects: https://gist.github.com/cholcombe973/e1405d70ba4921178e0908d7c4a6ba1c
[15:37] <stub> that doesn't look right
[15:38] <stub> https://gist.github.com/stub42/0438059a79dd1cf7d020fa8ad039b3dc
[15:42] <stub> gah... just revised it. I had bad yaml in one of the strings
[15:42]  * stub wishes again we had richer data types than strings
[15:42] <cholcombe> stub, i'll try that :).  Yeah this yaml is miserable
[15:43] <stub> I don't mind yaml. Its having to encode yaml into strings that get embedded in yaml :)
[15:43] <cholcombe> lol
[16:03] <cholcombe> stub, nope that doesn't work either.  nothing is added to the /etc/apt/sources.list file
[16:07] <stub> cholcombe: How about /etc/apt/sources.list.d ?
[16:07] <cholcombe> nope that's blank also
[16:08] <stub> Do you see the 'Initializing Apt Layer' message in the logs?
[16:09] <cholcombe> i do yeah
[16:09] <stub> Output from gpg after that?
[16:09] <cholcombe> nope.  lemme gist it
[16:10] <cholcombe> https://gist.github.com/cholcombe973/7438f1a25fe2da1a1c6c3a1014c67898
[16:10] <stub> There isn't much logging here, as it is just calling out to charmhelpers
[16:11] <cholcombe> right
[16:12] <stub> Have a look at your generated charm's config.yaml, and see if charm build included your updated defaults
[16:13] <cholcombe> stub, my bad i forgot to run charm build again.  let me try and deploy this again
[16:22] <cholcombe> stub, ah yes now we're getting somewhere.  invalid gpg armor header :)
[16:47] <petevg> cory_fu: For testing the new jdk setup we have in the bigtop base layer, which bundle is the most up to date for testing? Is it https://github.com/juju-solutions/bundle-bigtop-processing-mapreduce, or one of the others?
[16:52] <cory_fu> Is that still a thing?  We need to delete that repo
[16:53] <cory_fu> petevg: https://github.com/juju-solutions/bigtop/tree/master/bigtop-deploy/juju/hadoop-processing
[16:53] <petevg> cory_fu: aha. Thx.
[17:24] <bdx> cholcomb: sup
[17:32] <bdx> cholcombe: sup
[17:33] <bdx> cholcombe: what plans have you for vault_charm?
[17:35] <bdx> cholcombe: I think we need to combine forces on the vault thing
[17:36] <bdx> cholcombe: https://jujucharms.com/u/jamesbeedy/consul/1, https://jujucharms.com/u/jamesbeedy/consul-agent/6, https://jujucharms.com/u/jamesbeedy/vault/8
[17:36] <bdx> they all need readme, icon, and tests :-(
[17:37] <bdx> the^ consul, consul-agent, vault ha stack deploys successfully :-)
[17:38] <bdx> cholcombe: I've put alot of work into it recently .... lets chat when you get a minute
[17:49] <cholcombe> bdx, i'm trying to get the vault charm to hook up with consul so i can store cephx keys on it
[17:49] <cholcombe> bdx, do you have a bundle i can deploy of that whole setup?
[17:53] <bdx> cholcombe: omp
[18:02] <bdx> cholcombe: https://gist.github.com/jamesbeedy/102d1bbcfe5dbf6227f014348026d0a3
[18:14] <cholcombe> bdx, sweet thanks
[18:14] <bdx> cholcombe: one existing caveat to the vault charm is that non-leader units error when you request a token though
[18:14] <bdx> http://paste.ubuntu.com/23065296/
[18:15] <cholcombe> bdx, i see
[18:15] <bdx> cholcombe: because they all try to request the token
[18:15] <bdx> but only a singleton request need be made
[18:16] <cholcombe> yeah
[18:16] <cholcombe> that should be a leader only thing
[18:17] <bdx> yeah ... is there an 'is_leader()' call of some sort that you know of?
[18:18] <cholcombe> bdx, yeah.  are you using layers or old school?
[18:18] <bdx> layers
[18:19] <cholcombe> there's a leadership layer i remember seeing on interfaces.juju
[18:20] <bdx> yeah, vault is already using it
[18:21] <cholcombe> cory_fu, do you have any experience with the apt layer and custom sources?  I can't get it working :-/
[18:22] <cory_fu> cholcombe: A bit.  The most common thing I've seen go wrong is that, since config options can't be nested and thus it uses an embedded yaml string, the indentation on the value is really finicky
[18:22] <bdx> cholcombe: this might help there too -> https://github.com/jamesbeedy/layer-kibana/blob/master/config.yaml
[18:23] <cholcombe> bdx, yeah i'm having trouble with the gpg key.  it's complaining about an invalid header but i know it's valid
[18:23] <cholcombe> cory_fu, yeah the value is hard to get right
[18:23] <cory_fu> cholcombe: Can you point us to your config.yaml?
[18:23] <cholcombe> bdx, i'll try to copy your example
[18:23] <cholcombe> sure
[18:24] <cholcombe> cory_fu, bdx https://gist.github.com/cholcombe973/e1405d70ba4921178e0908d7c4a6ba1c
[18:24] <cory_fu> cholcombe: Your indentation is off on your GPG key
[18:24] <bdx> you need another space
[18:24] <cholcombe> ok
[18:25] <cholcombe> so 2 spaces in
[18:25] <cory_fu> Told you it's super finicky.  It's really annoying to deal with, and setting it on the CLI is even worse
[18:25] <bdx> I somewhat feel like those params should be options instead of configs
[18:25] <cholcombe> yeah.  we need a better way than this
[18:25] <cory_fu> This will get way better when config options support the schema syntax that action params do
[18:25] <bdx> aah
[18:26] <bdx> ha
[18:27] <cory_fu> Unfortunately, that's a breaking change and since it doesn't look like it's going to be in 2.0, I'm not holding my breath.
[18:27] <cory_fu> Unless the core devs can find a way to make it backwards compatible, which would be rather a bit more work
[18:28] <cholcombe> 11th deploy is a charm? lol
[18:28]  * cholcombe crosses fingers
[18:28] <cory_fu> :)
[18:30] <cory_fu> petevg: Any objection to me rebasing and squashing BIGTOP-2476-zookeeper?
[18:30] <cory_fu> No conflicts
[18:30] <petevg> @cory_fu: other than it never being a good idea to edit the history of a branch that multiple people have checked out :-)
[18:31] <petevg> The Bigtop people upstream don't seem to like to use github, including github's convenient "squash this when I merge" feature, though.
[18:31] <cory_fu> Yeah, except that the Bigtop reviewers have specifically asked for nicely squashed PRs
[18:31] <petevg> So, it's probably fine to just squash it now.
[18:32] <cholcombe> bdx, yeah so there should be an is_leader() function.  just requires a little searching
[18:32] <cory_fu> Right.  We could stop using the GitHub <-> Jira integration and submit patches that we manually update instead, but I personally don't find dealing with rebases all that painful
[18:32] <petevg> cory_fu: yeah. Go ahead. I have some outstanding changes against my local branch, but they're not difficult to recreate.
[18:32] <cory_fu> git stash is your friend.   ;)
[18:34] <petevg> cory_fu: In the past, I've had people do really horrible thing with merges when they tried to "fix" a squashed, which is why I try to avoid them. I won't do bad things with it, though, so we should be okay.
[18:35] <petevg> *things, *squashed branch
[18:35] <petevg> cory_fu: what we really need to do is get the dang PR merged so that we can stop merging other things to it.
[18:37] <bdx> cholcombe: yeah, just found it. thx
[18:37] <cholcombe> bdx, cory_fu thanks!  That got it to install finally
[18:38] <bdx> np! nice!
[18:39] <bdx> cholcombe: I'll keep you posted with my vault progress, going to get this mult-token-request thing squared away asap
[18:39] <cholcombe> bdx, awesome
[19:30] <cholcombe> what do people typically do for charms if the deb package being installed has an ncurses setup interface that gets invoked while installing?  coreycb you might know this
[19:32] <coreycb> cholcombe, I'm not sure, but I think that's frowned upon for deb packaging.  for openstack packages, one of the reasons we have separate core packages from Debian, is because Debian uses debconf prompts to configure things.
[19:32] <coreycb> frowned upon for Ubuntu that is
[19:32] <cholcombe> yeah the openattic package has debconf prompts.  i don't know how to disable them
[19:33] <cholcombe> or how i can give it a config file or something
[19:34] <coreycb> cholcombe, It looks like you can disable debconf - http://stackoverflow.com/questions/4401431/disable-prompts-while-installing-a-debian-package
[19:35] <cholcombe> coreycb, interesting.  thanks
[19:35] <coreycb> cholcombe, good luck
[19:35] <cholcombe> coreycb, ugh.  it's always something
[19:35] <coreycb> yep
[19:57] <mayurisapre> is there a way to access auth_url specified in environment.yaml file used for bootstrap, in charm hook?
[20:16] <mayurisapre> hi all.. is there a way to access auth url specified in environment.yaml file from charm hook?
[20:39] <marcoceppi> mayurisapre: no, the charms are disconnected from the environment they're deployed in
[20:45] <mayurisapre> marcoceppi : okay..is there a way to inject these values in deployed charm?
[20:45] <marcoceppi> mayurisapre: you can have them set via a configuration option on the charm
[20:45] <marcoceppi> mayurisapre: may I ask what you're charming up?
[20:46] <mayurisapre> i am deploying in openstack env
[20:46] <mayurisapre> and need these values for further operations in charm hooks
[20:47] <mayurisapre> what is the configuration option you just suggested?
[20:51] <mayurisapre> marcoceppi : ohh sorry .. are you talking about config.yaml file  provided in charm?
[20:52] <marcoceppi> mayurisapre: yes
[20:53] <mayurisapre> yes.. i thought of that option but if I could get auth_url that is more suitable in my case
[21:35] <bdx> cholcome: https://github.com/jamesbeedy/charm-vault/blob/master/reactive/vault.py#L56
[21:35] <bdx> cholcombe: ^ thats all it took
[21:35] <cholcombe> bdx, correct
[21:36] <bdx> pumped
[22:16] <marcoceppi> bdx: I don't have context, but could you use `@when('leadership.is_leader')`
[22:16] <marcoceppi> instead of an if block
[22:16] <marcoceppi> also, love seeing progress on the vault charm
[22:16] <marcoceppi> it's something I've heard a few people ask for already
[22:44] <bdx> marcoceppi: thanks for pointing that out, -1 me for not seeing that state decorating the function directly above ;/