The Ambari MPack (management pack) is also packaged as an RPM, having a dependency on ambari-server. Given a proper yum repo file,
traf_ambari rpm can be installed directly and it pulls in ambari-server. If ambari-server is previously installed and running, it must be restarted to pick up the Trafodion management pack.
Part of Ambari‘s job is to set up yum repo files on each node in order to install packages. The default URLs are for Hortonworks’ public repos. But since your custom-built Trafodion is not hosted there, you need to specify a URL for your local yum repo server.
The default value is built into the
traf_ambari RPM. This default value can be changed at install time in the Ambari GUI. The default URL value can also be set when building the
traf_ambari package. Use make to specify value of
make package-all REPO_URL=http://my.repo.server/repo/...
Setting default value can be done either at the top-level (package-all) or from install directory (“make pkg-ambari REPO_URL=...”).
This is not necessarily the URL where
traf_ambari is hosted, but rather where the
apache-trafodion_server is hosted.
Once you build the RPM packages, you need to copy them to a web server accessible location and then use createrepo command to set up the yum meta-data. (sudo yum install createrepo)
The code for the ambari mpack is here in the install tree, but files that are distributed to each node are part of the trafodion server RPM, and are located in core/sqf/sysinstall
The trafodion user environment is set using ~trafodion/.bashrc, which sources in values set by the RPM installation, values set by the Ambari install, and values from the installed Trafodion software.
/etc/trafodion/trafodion_config- RPM sets the
TRAF_HOMEvalue, which is location of Trafodion installation.
/etc/trafodion/conf/trafodion-env.sh- user-specified values set by Ambari trafodion-node install step.
/etc/trafodion/conf/traf-cluster-env.sh- node list info set by Ambari trafodion-master install step.
/home/trafodion/.../sqenv.sh- various derived values.