init-hdfs.sh is specific to Hadoop's filesystem, so it belongs under /usr/lib/hadoop. Is Provision.groovy specific to HDFS, or is it for any HCFS? And is it even intended to always be specific to filesystems, or will it also be used to do initialization of other services? I think all that determines where it should be, and unless it is specific to HDFS it doesn't belong in the same place as init-hdfs.sh is now.
On Wed, Apr 23, 2014 at 6:24 AM, Jay Vyas <jayunit...@gmail.com> wrote: > Hmmm ok... I'll ask a different way to clarify. > > should provision.groovy be in src/common/hadoop as well? Right now it's > in another directory all together. > > After all it is meant to be a drop in replacement for init-hdfs.sh. > > So in current bigtop... either provison.groovy OR init-hdfs.sh is in the > wrong place, don't you think? > > > On Apr 23, 2014, at 12:42 AM, Konstantin Boudnik <c...@apache.org> wrote: > > > > Jay, > > > > I think the script is packed up into the hadoop package and is relied > upon by > > Puppet. So, it shouldn't be too hard to replace it. What seems to be the > > trouble? > > > > Cos > > > >> On Wed, Apr 23, 2014 at 12:31AM, Jay Vyas wrote: > >> Hi sean and others: > >> > >> I want to replace the init-hdfs.sh > >> (.//bigtop-packages/src/common/hadoop/init-hdfs.sh) > >> > >> with provision.groovy > >> (.//bigtop-packages/src/common/bigtop-utils/provision.groovy) > >> > >> It seems pretty complex. > >> > >> Any pointers on the lifecycle of bigtop-utils files in terms of where > and > >> how they get installed in the rpms? > >> > >> Nothing detailed, just some guidelines on how the utilities are > leveraged > >> during provisioning of a cluster, and what needs to be done to > integrate a > >> new utility into > >> the cluster.... > >> > >> i can grep around for the specifics. >
