tree: cd787f77103f5563225dcf159de0da1f865a5ec4 [path history] [tgz]
  1. .gitignore
  2. config_hosts
  3. gen_hosts.sh
  4. README.md
  5. vagrantconfig.yaml
  6. Vagrantfile
provisioner/vagrant/README.md
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

#BigTop VM provisioner

Overview

The Vagrantfile definition creates a bigtop virtual hadoop cluster for you, by pulling from existing publishing bigtop repositories. This cluster can be used:

  • to test bigtop smoke tests
  • to test bigtop puppet recipes

Eventually, we may also add ability to build AND provision bigtop in a vagrant recipe, which would essentially give full validation of the BigTop stack.

USAGE

  1. Install Vagrant(DO NOT install 1.8.5 because of a critical bug)

  2. Install vagrant-hostmanager plugin to manage /etc/hosts

vagrant plugin install vagrant-hostmanager
  1. (Optional) Install vagrant-cachier plugin to cache packages at local
vagrant plugin install vagrant-cachier
  1. To provision a one node Apache Hadoop cluster on top of vagrant boxes
vagrant up
  1. You can specify number of nodes you'd like to provision by modifying num_instances in vagrantconfig.yaml
num_instances: 5
  1. Test on local built packages is available by:

first, build up local yum repo

cd bigtop; ./gradlew alluxio-yum

and then enable local yum in vagrantconfig.yaml

enable_local_repo: true

finally, spin up the cluster

vagrant up

Override Vagrant configurations

You can override vagrant configurations from environment variables:

$ export REPO=http://repo.example.com/path/to
$ vagrant up

or

$ MEMORY_SIZE=8000 vagrant up

##Configure Apache Hadoop ecosystem components

  • Choose the ecosystem you want to be deployed by modifying components in vagrantconfig.yaml
components: "hadoop, hbase, yarn,..."

By default, Apache Hadoop and YARN will be installed. See bigtop-deploy/puppet/hieradata/site.yaml for more details.