Hi! sorry to coming to this conversation rather late -- super busy @$WORK :-(
On Wed, Feb 25, 2015 at 9:57 AM, Christian Tzolov <[email protected]> wrote: > Hi Konstantin, > > Below are some of my findings. Note that so far i've played only with > CentOS6. > > - Missing python-setuptools and asciidoc packages. Don't remember which > project needed them. > - To build spark-rpm you need install scala and set the SCALA_HOME env. > - Due to https://issues.apache.org/jira/browse/CRUNCH-500 you can't use > Maven > 3.1. I've fixed this in the Crunch project but will not be available > until Crunch 0.12 release. For the time being can create a patch for > Crunch's do-component-build? In the Dockerfile I've downgraded maven to > 3.0.5 > - Hue (hue-ui) requires non root user to build the rpm. Right. And those are awesome findings. What we agreed at Bigtop a long time ago is that those types of requirements are best codified in a bigtop_toolchain puppet scripts. We really want our Docker files to be as simple as: - get puppet - puppet apply toolchain that's it. > I've tried > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+build+Bigtop using > the centos image. It seems like the /etc/profile.d/bigtop.sh is missing? The > 'toolchain' requires java to be installed first (and JAVA_HOME to be set). > This in turn requires 'sudo' package. For Spark you need to install Scala > and set SCALA_HOME. And for Hue you need to create sudo, passwordless > user... > Maybe with the ubunto image is better (haven't tried it) but for me the > above requires too many steps to prepare the environment. Why don't you ping me on IM and I can walk you through how we're thinking about this. Would be much quicker than on email. Also, it goes without saying, but your help with Docker/toolchain will be *greatly* appreciated. Lets make Bigtop better together! Thanks, Roman.
