aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorjay@apache.org <jayunit100>2014-10-30 21:21:01 -0400
committerjay@apache.org <jayunit100>2014-10-30 21:21:01 -0400
commit3fdbe98be4c467b14a03c0fe05d98f7bd5bbeeb2 (patch)
tree2a82a589d5aa7c7c0846fba5fe8576721ac33650 /README.md
parent11c8bd5543cd8f21d33f92447c5b996a5886d798 (diff)
BIGTOP-1510. Minor README update about bigtop-deploy.
Diffstat (limited to 'README.md')
-rw-r--r--README.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/README.md b/README.md
index dce5a9b6..2e0918d3 100644
--- a/README.md
+++ b/README.md
@@ -21,6 +21,11 @@ limitations under the License.
The primary goal of Apache Bigtop is to build a community around the packaging and interoperability testing of Apache Hadoop-related projects. This includes testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects.
+Immediately Get Started with Deployment and Smoke Testing of BigTop
+===================================================================
+
+The simplest way to get a feel for how bigtop works, is to just cd into `bigtop-deploy/vm` and try out the recipes under vagrant-puppet, docker-puppet, and so on. Each one rapidly spins up, and runs the bigtop smoke tests on, a local bigtop based big data distribution. Once you get the gist, you can hack around with the recipes to learn how the puppet/rpm/smoke-tests all work together, going deeper into the components you are interested in as described below.
+
Quick overview of source code directories
=========================================