1. BIGTOP Configuration and Wrapper Executable

2. Motivation Overall, even with bigtop, still lack the feel of one product family Upstream modules have inconsistent configuration mechanism Too many environment valuables to set for each modules Too many commands to remember to start various module daemons No easy way to query daemon status All or nothing for modules – cannot add/remove modules (??? – might be useful), maybe pulling down too much or too little.

3. Proposal Single BIGTOP_HOME environment to set All other environment variables could be derived and set and listed for the user by convention. Single executable “bigtop” for house keeping Start/stop modules List related settings, modules, ports, etc. Install/remove bigtop modules

4. Usage export BIGTOP_HOME=/usr/lib/bigtop /usr/bin/bigtop /usr/bin/bigtop -h/-help – Help message, and link to bigtop GettingStarted web page -list machines|daemons|ports|modules -start-stop -add-machine -add-machine -remove-machine | all -cluster sync-config| – rsync configuration files, jar files across cluster machines -clean – clean logs, caches across the cluster machines -install -install -uninstall -uninstall

5. What’s Not In Scope Wrapping upstream module commands such as hadoop, mahout, pig, etc. UI integration with Hue for the monitor and management of Hadoop Components.