-
Notifications
You must be signed in to change notification settings - Fork 129
BDRE development VM setup
Sri Harsha Boda edited this page Sep 15, 2017
·
1 revision
Before setting up your development VM we strongly recommend that you clone, build and run BDRE UI. Though one can automate the whole thing using a single script but due to lack of maturity of the scripts, please issue and review each and every step. BDRE developer VM needs atleast 8GB of RAM installed in your host machine.
These scripts are intended to install and configure everything required for BDRE. Following is the list of software it would currently install in the base VM.
- Hadoop Yarn, HDFS, Hive, Oozie, Hue (It's the open source Hadoop downloaded from HortonWorks repo)
- Maven
- Git 1.9
- Oracle JDK7
- Tomcat 6
- Jenkins
- MySQL 5.6
- Install Required Softwarefor building the VM.
- Clone the Jack repo in your local machine
git clone https://[email protected]/bdre/jack.git
- cd to 'installer' and edit 'config.vm.box' tp point to your CentOS box image in your local hard drive.
config.vm.box = "/Users/arijit/Downloads/CentOS-6.4-x86_64-v20131103.box"
- Perform a
vagrant up
and wait for the base CentOS VM to start. - From your host machine ssh to [email protected]. Password is vagrant.
- Make sure your VM is connected to the internet. If working from Wipro office, please setup Linux commandline proxy. For Wipro proxy details see this. For information about how to setup commandline proxy in Linux read this.
- Test your internet connectivity using
yum install dos2unix
‼️ Before proceeding further - become root using
sudo su
- As root cd to 'installer' (in /home/vagrant) and edit installer.conf to update several parameters
#OS Level
export BDRE_LINUX_USER_NAME=bdreusr
export BDRE_LINUX_USER_PASSWORD=cde3vfr4
#Jenkins level(currently unused)
export BDRE_JENKINS_ADMIN_USER_NAME=admin
export BDRE_JENKINS_ADMIN_USER_PASS=somepassword
#Git. change below and use your own git credentials
export BDRE_GIT_USER_NAME=bdrejohn
export BDRE_GIT_USER_PASSWORD=mypassword
export BDRE_GIT_BRANCH=develop
- Then perform a chmod +x *.sh
- Run the part-xx.sh (starting from part-0.sh) files manually one by one in order(very important) like below
./part-0.sh
./part-1.sh
./part-2.sh
./part-3.sh
./part-4.sh
./part-5.sh
./part-6.sh
./part-7.sh
./part-8.sh
./part-9.sh
./part-10.sh
./part-11.sh
./part-12.sh
./part-12A.sh
./part-12B.sh
./part-13.sh
./part-13A.sh
./part-13B.sh
./part-14.sh
./part-15.sh
./part-16.sh
./part-17.sh
- In case the scripts does not work due to CRLF problems try
dos2unix *.sh
- To start the VM do a
vagrant up
- To stop the VM do a
vagrant halt
- To destroy the VM and start afresh do a
vagrant destroy
- To recopy the files and run the bootstrap script do a
vagrant provision
- BDRE UI: http://192.168.33.9:8080/md-ui/pages/content.page (use admin/zaq1xsw2)
- Jenkins: http://192.168.33.9:8100/
- Metadata JDBC URL: jdbc:mysql://localhost:3306/<BDRE_MYSQL_MD_DB> (accessible from localhost)
- Namenode URL: hdfs://localhost:8020
- RM URL: localhost:8050
- HUE URL: localhost:8000
- Oozie Job URL: localhost:11000
- Oozie REST API URL: TBD
@bdrekapil please a page on how create/deploy/run jobs with BDRE with screenshots.