Checking out
...
The following uses Ambari git for the development process. Please keep in mind git is read only and patches will have to be uploaded and committed via svn.
git clone git://git.apache.org/ambari.git
git checkout -b AMBARI-666 origin/AMBARI-666
Building Ambari
After checking out Ambari, you can build ambari with the steps below:
$ mvn clean install
Note: The above is for just building the jars. See below for starting/deploying the server and the agent.
Building Artifacts and Running the Server/Agent
NOTE: Though the documentation below mentions agent its not there yet and is coming up.
To build tarball artifacts run:
$mvn clean package assembly:assembly
This will build the server/agent tarballs.
NOTE: Run everything as root below. This will change as we go forward but for now run everything as root.
For running the server:
$ cp ambari-server/target/ambari-server-*-dist.tar.gz INSTALL_DIR /* where install dir is some directory where you want to run the server */
$ cd INSTALL_DIR
$ tar -zxvf ambari-server-*-dist.tar.gz
$ vim /etc/ambari/ambari.properties
Add the following entry:
security.server.keys_dir=INSTALL_DIR/ambari-server-1.0.3-SNAPSHOT/keystore
NOTE: INSTALL_DIR will have to be replaced with the actual path in the config file.
$ cd ambari-server-*
$ export AMBARI_PASSPHRASE="tmp"
$ java -cp lib/*: org.apache.ambari.server.controller.AmbariServer
The server will come up and run as a foreground process. Scripting will come later as we move along to run the server with proper confs/envs.
To check if the server is up and healthy, you can go to:
http://HOSTNAME:8080/api/check
The status will show as running.
or you can do: curl localhost:8080/api/check
NOTE: The health check is static as of now and will change later.
Running the agent.
The agent requires python 2.6 to run on a host. RHEL5/Centos5 have python 2.4 installed by default. To install 2.6 (NOTE: you can install both 2.4/2.6 on the host), install the epel repo and then run
$ yum install python26.
Python needs setuptools to be able to setup the project for development. Download http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg#md5=bfa92100bd772d5a213eedd356d64086 and then run:
$ sh setuptools-0.6c11-py2.6.egg
To setup the ambari agent:
$ mkdir -p /var/ambari /var/run/ambari /var/log/ambari /tmp/ambari-agent/
- The following dev process is easier than using setup.py and is a quicker turnaround. As soon as we have a good deployment story (rpm) we will add those in.
$ cd ambari-agent/src/main/python/ambari_agent
- Note that ambari agent requires facter to get the node information. Download facter tarball from http://downloads.puppetlabs.com/facter/facter-1.6.0.tar.gz
and uninstall in a directory.
Edit facter_home in AmbariConfig.py to the directory where facter is installed. The agent executes the script facter_home/bin/facter to get all the node information and also uses df to get the mount point information.
To run the agent:
$ export AMBARI_PASSPHRASE="tmp"
$ python2.6 main.py
The Server currently doesnt implement the apis needed for the agent, so the agent will just try connecting to the server and do nothing. Take a look at
/var/log/ambari.log to see the logs.
Building and running Ambari Web
Ambari Web uses Brunch (http://brunch.io/) as the application assembler for development purposes.
Brunch is used to build and deploy automatically in the background as the developer modifies source files (JS, LESS/CSS, Handlebars template files).
It can also start up a Node.js-based web server with a single command so that you can easily run the application from the application root directory without any special configuration.
To build, deploy, and run Ambari Web with Brunch:
1. Install NPM per http://nodejs.tchol.org/
2. Install Brunch
$ sudo npm install -g brunch
3. Download dependent packages into ambari-web/node_modules directory
$ cd ambari-web
$ npm install
4. Run Ambari Web (with automatic, continuous build/deploy):
$ brunch watch --server
This starts up the server at http://localhost:3333
To run unit tests, run:
$ brunch test
Currently, Ambari Web is still being developed in isolation with no integration with Ambari Server using mock data.
Ambari Server runs on Jetty, so when integration happens we need to deploy on the Jetty server.
The built application is self-contained under ambari-web/public. The content of this folder simply needs to be copied to the appropriate folder on Jetty.
Setting up Ambari in Eclipse
Ambari source
Follow the instructions under Checkout source code section of "How to contribute" guide.
We'll refer to the top-level "ambari" directory as AMBARI_DIR
in this document.
Tools needed to build Ambari
The following tools are needed to build Ambari from source.
Alternatively, you can easily launch a VM that is preconfigured with all the tools that you need. See the Pre-Configured Development Environment section in the Quick Start Guide.
- xCode (if using Mac - free download from the apple store)
- JDK 8 (Ambari 2.6 and below can be compiled with JDK 7, from Ambari 2.7, it can be compiled with at least JDK 8)
- Apache Maven 3.3.9 or later
Tip: In order to persist your changes to the JAVA_HOME environment variable and add Maven to your path, create the following files:File: ~/.profileCode Block source ~/.bashrc
File: ~/.bashrcCode Block export PATH=/usr/local/apache-maven-3.3.9/bin:$PATH export JAVA_HOME=$(/usr/libexec/java_home) export _JAVA_OPTIONS="-Xmx2048m -XX:MaxPermSize=512m -Djava.awt.headless=true"
- Python 2.6 (Ambari 2.7 or later require Python 2.7 as minimum supported version)
Python setuptools:
for Python 2.6: Download setuptools and run:Code Block sh setuptools-0.6c11-py2.6.egg
for Python 2.7: Download setuptools and run:
Code Block sh setuptools-0.6c11-py2.7.egg
- rpmbuild (rpm-build package)
g++ (gcc-c++ package)
Running Unit Tests
mvn clean test
Run unit tests in a single module:
Code Block mvn -pl ambari-server test
Run only Java tests:
Code Block mvn -pl ambari-server -DskipPythonTests
Run only specific Java tests:
Code Block mvn -pl ambari-server -DskipPythonTests -Dtest=AgentHostInfoTest test
Run only Python tests:
Code Block mvn -pl ambari-server -DskipSurefireTests test
Run only specific Python tests:
Code Block mvn -pl ambari-server -DskipSurefireTests -Dpython.test.mask=TestUtils.py test
Run only Checkstyle and RAT checks:
Code Block mvn -pl ambari-server -DskipTests test
NOTE: Please make sure you have npm in the path before running the unit tests.
Generating Findbugs Report
mvn clean install
This will generate xml and html report unders target/findbugs. You can also add flags to skip unit tests to generate report faster.
Building Ambari
Note: if you can an error that too many files are open while building, then run: ulimit -n 10000 (for example)
To build Ambari RPMs, run the following.
Note: Replace ${AMBARI_VERSION} with a 4-digit version you want the artifacts to be (e.g., -DnewVersion=1.6.1.1)
Note: If running into errors while compiling the ambari-metrics package due to missing the artifacts of jms, jmxri, jmxtools:
[ERROR] Failed to execute goal on project ambari-metrics-kafka-sink: Could not resolve dependencies for project org.apache.ambari:ambari-metrics-kafka-sink:jar: 2.0 . 0 - 0 : The following artifacts could not be resolved: javax.jms:jms:jar: 1.1 , com.sun.jdmk:jmxtools:jar: 1.2 . 1 , com.sun.jmx:jmxri:jar: 1.2 . 1 : Could not transfer artifact javax.jms:jms:jar: 1.1 from/to java.net (https: //maven-repository.dev.java.net/nonav/repository): No connector available to access repository java.net (https://maven-repository.dev.java.net/nonav/repository) of type legacy using the available factories WagonRepositoryConnectorFactory |
The work around is to manually install the three missing artifacts:
mvn install:install-file -Dfile=jms- 1.1 .pom -DgroupId=javax.jms -DartifactId=jms -Dversion= 1.1 -Dpackaging=jar mvn install:install-file -Dfile=jmxtools- 1.2 . 1 .pom -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion= 1.2 . 1 -Dpackaging=jar mvn install:install-file -Dfile=jmxri- 1.2 . 1 .pom -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion= 1.2 . 1 -Dpackaging=jar |
If when compiling it seems stuck, and you've already increased Java and Maven heapsize, it could be that Ambari Views has a lot of artifacts, and the rat-check is choking up. In this case, try running
git clean -df (this will remove untracked files and directories) mvn clean package -DskipTests -Drat.ignoreErrors=true or mvn clean package -DskipTests -Drat.skip |
Setting the Version Using Maven
Ambari 2.8+ uses a newer method to update the version when building Ambari.
Code Block | ||||
---|---|---|---|---|
| ||||
# Update the revision property to the release version
mvn versions:set-property -Dproperty=revision -DnewVersion=2.8.0.0.0
mvn -B clean install package rpm:rpm -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl |
Code Block | ||||
---|---|---|---|---|
| ||||
# Update the revision property to the release version
mvn versions:set-property -Dproperty=revision -DnewVersion=2.8.0.0.0
mvn -B clean install package rpm:rpm -DskipTests -Psuse11 -Dpython.ver="python >= 2.6" -Preplaceurl |
Code Block | ||||
---|---|---|---|---|
| ||||
# Update the revision property to the release version
mvn versions:set-property -Dproperty=revision -DnewVersion=2.8.0.0.0
mvn -B clean install package jdeb:jdeb -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl |
Ambari 2.7 and Earlier Releases (Deprecated)
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
mvn versions:set -DnewVersion=${AMBARI_VERSION}
#Note: The ambari-metrics project is not wired up to the main ambari project. However there is a dependency on ambari-metrics-common to build the ambari-server RPM.
#Hence you also need to set ambari-metrics project version as well.
pushd ambari-metrics
mvn versions:set -DnewVersion=${AMBARI_VERSION}
popd
mvn -B clean install package rpm:rpm -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl
|
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
mvn versions:set -DnewVersion=${AMBARI_VERSION}
#Note: The ambari-metrics project is not wired up to the main ambari project. However there is a dependency on ambari-metrics-common to build the ambari-server RPM.
#Hence you also need to set ambari-metrics project version as well.
pushd ambari-metrics
mvn versions:set -DnewVersion=${AMBARI_VERSION}
popd
mvn -B clean install package rpm:rpm -DskipTests -Psuse11 -Dpython.ver="python >= 2.6" -Preplaceurl |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
mvn versions:set -DnewVersion=${AMBARI_VERSION}
#Note: The ambari-metrics project is not wired up to the main ambari project. However there is a dependency on ambari-metrics-common to build the ambari-server RPM.
#Hence you also need to set ambari-metrics project version as well.
pushd ambari-metrics
mvn versions:set -DnewVersion=${AMBARI_VERSION}
popd
mvn -B clean install package jdeb:jdeb -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl |
Ambari Server will create following packages
- RPM will be created under
AMBARI_DIR
/ambari-server/target/rpm/ambari-server/RPMS/noarch. - DEB will be created under
AMBARI_DIR
/ambari-server/target/
Ambari Agent will create following packages
- RPM will be created under
AMBARI_DIR
/ambari-agent/target/rpm/ambari-agent/RPMS/x86_64. - DEB will be created under
AMBARI_DIR
/ambari-agent/target
Optional parameters:
- -X -e: add these options for more verbose output by Maven. Useful when debugging Maven issues.
- -DdefaultStackVersion=STACK-VERSION
- Sets the default stack and version to be used for installation (e.g., -DdefaultStackVersion=HDP-1.3.0)
- -DenableExperimental=true
- Enables experimental features to be available via Ambari Web (default is false)
- All views can be packaged in RPM by adding -Dviews parameter
- mvn -B clean install package rpm:rpm -Dviews -DskipTests
- Specific views can be built by adding
--projects
parameter to the -Dviews- mvn -B clean install package rpm:rpm --projects ambari-web,ambari-project,ambari-views,ambari-admin,contrib/views/files,contrib/views/pig,ambari-server,ambari-agent,ambari-client,ambari-shell -Dviews -DskipTests
- mvn -B clean install package rpm:rpm --projects ambari-web,ambari-project,ambari-views,ambari-admin,contrib/views/files,contrib/views/pig,ambari-server,ambari-agent,ambari-client,ambari-shell -Dviews -DskipTests
NOTE: Run everything as root
below.
Building Ambari Metrics
If you plan on installing the Ambari Metrics service, you will also need to build the Ambari Metrics project.
Code Block |
---|
cd ambari-metrics
mvn clean package -Dbuild-rpm -DskipTests
For Ubuntu:
cd ambari-metrics
mvn clean package -Dbuild-deb -DskipTests |
Note:
The metrics rpms will be found at: ambari-metrics-assembly/target/. These would be need for installing the Ambari Metrics service.
Running the Ambari Server
First, install the Ambari Server RPM.
On RHEL/CentOS:
Code Block |
---|
yum install ambari-server/target/rpm/ambari-server/RPMS/noarch/ambari-server-*.noarch.rpm
|
On SUSE/SLES:
Code Block |
---|
zypper install ambari-server/target/rpm/ambari-server/RPMS/noarch/ambari-server-*.noarch.rpm
|
On Ubuntu 12:
Code Block |
---|
dpkg --install ambari-server/target/ambari-server-*.deb # Will fail with missing dependencies errors
apt-get update # Update locations of dependencies
apt-get install -f # Install all failed dependencies
dpkg --install ambari-server/target/ambari-server-*.deb # Will succeed |
Initialize Ambari Server:
Code Block |
---|
ambari-server setup
|
Start up Ambari Server:
Code Block |
---|
ambari-server start
|
See Ambari Server log:
Code Block |
---|
tail -f /var/log/ambari-server/ambari-server.log
|
To access Ambari, go to
Code Block |
---|
http://{ambari-server-hostname}:8080 |
from your web browser and log in with username admin and password admin.
Install and Start the Ambari Agent Manually on Each Host in the Cluster
Install the Ambari Agent RPM.
On RHEL/CentOS:
Code Block |
---|
yum install ambari-agent/target/rpm/ambari-agent/RPMS/x86_64/ambari-agent-*.rpm
|
SUSE/SLES:
Code Block |
---|
zypper install ambari-agent/target/rpm/ambari-agent/RPMS/x86_64/ambari-agent-*.rpm
|
Ubuntu12:
Code Block |
---|
dpkg --install ambari-agent/target/ambari-agent-*.deb |
Edit the location of Ambari Server in /etc/ambari-agent/conf/ambari-agent.ini by editing the hostname line.
Start Ambari Agent:
Code Block |
---|
ambari-agent start
|
See Ambari Agent log:
Code Block |
---|
tail -f /var/log/ambari-agent/ambari-agent.log
|
Setting up Ambari in Eclipse
Code Block |
---|
$ mvn clean eclipse:eclipse
|
...
After doing the above you should be able to import the project via eclipse's import projectEclipse "Import > Maven > Existing Maven Project". Choose the root directory where you cloned the git repository. You should be able to see the following projects on eclipse:>
Code Block |
---|
ambari | |- ambari-project |- ambari-server |
...
|- ambari-agent |- ambari-web |
Select the top-level "ambari pom.xml" and click Finish.