[00:01] <kwmonroe> np magicaltrout, clearly my work here is done.
[00:07] <kwmonroe> magicaltrout: what's the issue url that you filed?  i'd like to know where to send my bill for all these zookeeper machines that never came up.
[00:22] <magicaltrout> hehe
[00:23] <magicaltrout> apparantly hatch has fixed it already
[14:18] <pekkari> Hi #juju, can anyone shed some light on the following paste? http://dpaste.com/0PAMSQY
[14:23] <magicaltrout> it says its broken
[14:24] <pekkari> well, I'm adding the code changes below to see if this is some thing I missed from how to setup a relation-changed hook in reactive charms magicaltrout
[14:27] <pekkari> I suspect the issue is around line 63, on the number of parameters set magicaltrout, does it says something to you?
[18:21] <sfeole>  does anyone know if there is any sort of revision tracking for juju charms, that corresponds to a specific commit in the charm source (on github  for example).  For example, charms have different versions charm/foo-1  -> charm/foo-2 -> charm/foo-3. Is there some sort of tracking that can tell me,  revision 2 contains all of specified fixes /commits in the source???
[18:24] <jhobbs> the openstack charms have a repo-info file with that info in them
[18:25] <jhobbs> which is super helpful; but I don't think there is a generic mechanism for that
[21:39] <heckles1000> Hey guys! I just started looking over the bigtop charms and I have a few questions/comments, that I am going to fire off.
[21:39] <magicaltrout> *boom*
[21:41] <magicaltrout> this is like the slowest cannon ever
[21:43] <heckles1000> apache software release vs charm release? is there any tracking going on between the charms and apache software, etc build system in place that builds releases charms when the apache software revs?
[21:45] <magicaltrout> kwmonroe who deals with the juju charms is also on the bigtop PMC heckles1000
[21:45] <magicaltrout> so there is reasonably close alignment
[21:45] <magicaltrout> I don't know how quick the release -> charm update cycle is, but i'm sure its not that shabby
[21:47] <heckles1000> oozie and other bigtop ecosystem software - do we have a contributing guidelines for charming bigtop things ... it seems some are getting sorely outdated .... some things are snapped some aren't, having a hard time finding consistency here I guess
[21:47] <magicaltrout> I think stuff outside of the bigtop ecosystem are largley up to community commits so YMMV
[21:48] <heckles1000> magicaltrout: for example https://github.com/juju-solutions/layer-apache-hadoop-namenode#overview shows hadoop 2.7.1
[21:48] <heckles1000> is that just a crusty readme, or do you think the softwware is just not up to date with recent hadoop releases
[21:49] <magicaltrout> ignore that
[21:49] <magicaltrout> https://github.com/juju-solutions/bigtop/tree/master/bigtop-packages/src/charm
[21:49] <magicaltrout> thats the namenode in the charmstore
[21:49] <heckles1000> lol ... om thanks
[21:49] <magicaltrout> if you find a charm in the charm store
[21:50] <magicaltrout> most are linked to project homepages or bug trackers
[21:50] <magicaltrout> assuming they've been maintained by the canonical folk
[21:50] <heckles1000> so like ..... is there a place where the single source of truth for all of the legit bigtop charms live, I feel like Im sorting through a ton of charms ...some seem irrelevant and its difficult for me to determine what is legit and what is stale
[21:51] <heckles1000> readmes like ^ in the charm repo dont help
[21:51] <heckles1000> :)
[21:51] <magicaltrout> i refer to the previous link ;)
[21:51] <magicaltrout> that appears to be the source of the bigtop charms
[21:51] <magicaltrout> although i've not committed any so i could be lying
[21:52] <heckles1000> yea
[21:52] <heckles1000> 8 months ago
[21:52] <magicaltrout> also
[21:52] <magicaltrout> https://github.com/juju-solutions/bigdata-community/wiki/Contributing
[21:52] <magicaltrout> oh
[21:52] <magicaltrout> link #1
[21:52] <heckles1000> ahhh thank you
[21:52] <magicaltrout> in that page
[21:52] <magicaltrout> https://github.com/apache/bigtop/tree/master/bigtop-deploy/juju
[21:53] <magicaltrout> seems likely
[21:53] <heckles1000> ok thanks for those
[21:53] <heckles1000> but everything looks stale
[21:53] <heckles1000> like where is hadoop 3.0?
[21:53] <magicaltrout> also https://github.com/juju-solutions/bigdata-community/wiki/Apache-Bigtop
[21:53] <heckles1000> jeeze ok
[21:53] <heckles1000> this is great info
[21:54] <heckles1000> how can I help get this all organized
[21:54] <kwmonroe> so... in the bigtop repo... there's bigtop-packages/charms and bigtop-deploy/juju
[21:54] <kwmonroe> those are the source of truths for the juju / bigtop charms and bundles
[21:54] <magicaltrout> kevs here, kev is the canonical source of the truth
[21:55] <magicaltrout> or something like that
[21:55] <kwmonroe> heh - thx for taking that fire magicaltrout :)
[21:55] <magicaltrout> also heckles1000 Bigtop 1.2.1 the latest release
[21:55] <kwmonroe> heckles1000: as for crustiness, bigtop does indeed lag behind upstream
[21:55] <magicaltrout> is Hadoop 2.7.3
[21:55] <magicaltrout> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+1.2.1+Release
[21:56] <kwmonroe> so like, hadoop-3 has just started being worked in bigtop
[21:57] <kwmonroe> heckles1000: how did you find your way to https://github.com/juju-solutions/layer-apache-hadoop-namenode#overview?  any -apache- charms are our previous gen (before bigtop) and should have been deprecated in favor of bigtop versions, eg, hadoop-namenode (good) vs apache-hadoop-namenode (bad)
[21:57] <heckles1000> sorry I didnt mean to call it crusty. I just realized there is a juju quickstart in the readme. I spent the last hour trying to use juju quickstart only realize it doesnt exist
[21:57] <heckles1000> oh but I was looking at the wrong readme
[21:58] <kwmonroe> ha!  doh.  so again, how did you come across that readme for layer-apache-hadoop?  i'll update links as needed (unless google took you there)
[21:58] <heckles1000> I see what your saying, that is probably why im confused looking at both new and old stuff
[21:58] <heckles1000> google
[21:59] <kwmonroe> def switch to bing
[21:59] <heckles1000> I didnt know the source for the new new. Thank you for the link
[21:59] <kwmonroe> using bing, you'll never come across the old stuff (or probably anything, really)
[22:00] <heckles1000> while I got you here do you mind if I ask a few more questions?
[22:01] <magicaltrout> don't ask if you can ask
[22:01] <magicaltrout> just fire them off ;)
[22:01] <magicaltrout> the worst you'll get is silence :)
[22:01] <kwmonroe> yeah heckles1000, fire away.  magicaltrout is as frisky as he's gonna get.
[22:01] <magicaltrout> kwmonroe's probably more impressed to find someone actually using his code ;)
[22:02] <heckles1000> Is there documentation for how to physically configure the nodes aka how do i provide disk for hdfs through the charm.  I see there is a thing called juju storage, how do i use it with hdfs
[22:02] <heckles1000> you guys are great lol
[22:02] <kwmonroe> heckles1000: that one is super simple!  you can't.  the bigtop charms don't have any juju storage wired in.
[22:03] <heckles1000> how do i tell hdfs which disk to use?
[22:03] <kwmonroe> heckles1000: at the moment, hdfs is configured on the root disk of all datanodes
[22:05] <heckles1000> how do i give it disks then? do you just deploy  nodes with super large extra large super resilient filesystem?
[22:05] <heckles1000> root filesystem:
[22:06] <kwmonroe> heckles1000: hdfs will handle the resilient part for you.  as for the super large part, when you deploy the datanode (hadoop-slave is what we deploy by default, it includes datanode and nodemgr), you can specify a root-disk constraint to whatever size you need.
[22:07] <kwmonroe> the datanodes are configured to use /var/lib/hadoop-hdfs/data on their root filesystem
[22:07] <heckles1000> I am using maas and my hdfs server has 12 disks each
[22:08] <heckles1000> can i configure maas to just  mount the array there
[22:08] <heckles1000> servers*
[22:09] <kwmonroe> hmm.. you lost me.  are you saying each of your servers has 12 disks?
[22:10] <heckles1000> yes. I have 10 data nodes each has 64gb satadom for the os and 12 6tb for hdfs storage
[22:13] <heckles1000> im trying to use maas to create a softraid across the disks, then juju storage to mount the array to the application/machine
[22:13] <heckles1000> it doesnt sound like this is a thing yet?
[22:14] <kwmonroe> heckles1000: i don't know if maas can configure/expose storage for you.  you could create an LVM array on each of your datanodes, add your 12 disks as PVs in a VG, create a monster LV, mount that as /mnt/mybigLV, then  "rmdir /var/lib/hadoop-hdfs/data/dir && ln -s /mnt/mybigLV /var/lib/hadoop-hdfs/data/dir"
[22:14] <heckles1000> would I be able to help contribute to making juju storage work with these charms, or is it something I would have to wait for the charms to grow storage capability ?
[22:14] <heckles1000> ahh I see
[22:14] <kwmonroe> heckles1000: it may be a thing -- i'm just not really familiar with maas
[22:15] <jhobbs> you can tell maas to make a software raid partition and tell it where to mount it
[22:15] <jhobbs> that should be fine
[22:15] <kwmonroe> ah cool jhobbs - thanks!
[22:16] <kwmonroe> so yeah heckles1000, however you make the LV, mount it on the datanode and symlink the mountpoint over to $dfs.datanode.data.dir
[22:17] <kwmonroe> fwiw heckles1000, this is just how you'd have to do it today.  proper storage support (juju storage) is a way better option, it's just not there today.
[22:17] <heckles1000> jhobbs, kwmonroe: so I can use maas + juju to do half of that process then by making the raid and mounting it using maas + juju storage
[22:18] <heckles1000> then just symlink the dirs ^^
[22:18] <jhobbs> i don't know anything about these charms, sorry :/ but maas will make the raid set, format it however you tell it to, and mount it wherever you want it to; that will all be done before juju and the charms take over
[22:18] <heckles1000> awesome
[22:18] <heckles1000> jhobbs: thanks
[22:18] <kwmonroe> heckles1000: the missing piece is that the charms wouldn't know what to do when you attached storage to them.  ideally, they'd have to do the datanode config to set the mount point, etc.
[22:19] <heckles1000> I see
[22:19] <heckles1000> is it just 1 single config that specifies the mountpoint?
[22:20] <kwmonroe> i think so heckles1000, see dfs.datanode.data.dir:  https://hadoop.apache.org/docs/r2.7.3/hadoop-project-dist/hadoop-hdfs/hdfs-default.xml
[22:20] <bdx> oh awesome!
[22:21] <kwmonroe> may also need to tweak some of the fs-limits
[22:21] <bdx> lets get this going
[22:21] <bdx> I need that too
[22:22] <bdx> kwmonroe: slacking
[22:22] <kwmonroe> heh
[22:22] <kwmonroe> i thought you needed network spaces bdx!
[22:22] <bdx> I need it alllll
[22:22] <kwmonroe> you can't possibly want 2 things in a week
[22:23] <magicaltrout> it means 2 people use kevs code
[22:23] <magicaltrout> he must be due a raise
[22:23] <kwmonroe> half of 'em are using the old stuff that cory_fu wrote though :/
[22:23] <kwmonroe> there goes my moneies
[22:24] <magicaltrout> just buy him a fedora or 7
[22:24] <kwmonroe> lol
[22:24] <cory_fu> ha
[22:35] <heckles1000> kwmonroe: how can I modify the charm to set $dfs.datanode.data.dir config value?
[22:36] <kwmonroe> heckles1000: another simple one!  you can't.  but if you open an issue for me here, https://github.com/juju-solutions/bigtop/issues, i'll see what i can do ;)
[22:38] <kwmonroe> heckles1000: the datanode config is hard coded by bigtop here:  https://github.com/apache/bigtop/blob/master/bigtop-packages/src/common/hadoop/conf.pseudo/hdfs-site.xml#L48
[22:39] <kwmonroe> so while you can't change it, you *can* do filesystem tricks to make it do what you want... hence the earlier workaround to symlink wherever your big 'ol mount point is over to that hard coded location ^^
[22:43] <kwmonroe> here's the workaround all in one go, assuming your big mount point is mounted at /mnt:  juju run --all "mv /var/lib/hadoop-hdfs /mnt && ln -s /mnt /var/lib/hadoop-hdfs"
[22:43] <heckles1000> kwmonroe: sweet that doesn't sound too bad.
[22:43] <kwmonroe> that'll be $300
[22:43] <heckles1000> kwmonroe: I do have something for you ...
[22:43] <kwmonroe> oh dear
[22:44] <heckles1000> kwmonroe: https://github.com/juju-solutions/bigtop/issues/53
[22:44] <kwmonroe> that'll be $500
[22:44] <heckles1000> haha
[22:45] <heckles1000> kwmonroe: thats great, thanks again for the workaround
[22:45] <kwmonroe> np heckles1000 - thx for opening the issue.  i'll get that scheduled in soon.
[22:46] <kwmonroe> bdx: PRs welcome for https://github.com/juju-solutions/bigtop/issues/53 ;)  i'll give you $40.
[22:46] <magicaltrout> i'm skint i'll do it for $30
[22:46] <kwmonroe> has to be a *mergeable* PR.  sorry magicaltrout.
[22:47] <magicaltrout> hey at least you don't need to get an ICLA off me :P
[22:53] <bdx> kwmonroe: aha, I gotchu https://github.com/juju-solutions/bigtop/issues/54
[22:53] <kwmonroe> um, bdx, that is the opposite of a PR
[22:54] <magicaltrout> lol
[23:50] <bdx> kwmonroe: is the data-node provided by hadoop-slave?
[23:51] <kwmonroe> yeah bdx, the slave includes layer-datanode and layer-nodemgr.  those respective sources live at https://github.com/juju-solutions/layer-hadoop-datanode and https://github.com/juju-solutions/layer-hadoop-nodemanager
[23:51] <bdx> cool, thanks
[23:52] <kwmonroe> bdx, it's not ideal, but charm build can't pull layers from repo subdirs, so we needed those layers in their own repos.
[23:52] <bdx> totally
[23:52] <bdx> is layer-hadoop-datanode used in any other bigtop charms?
[23:53] <kwmonroe> no
[23:54] <bdx> it seems sensible to add the storage bits to the layer-hadoop-datanode .... but I mean .... it seems more sensible to add them to the top layer