-
Notifications
You must be signed in to change notification settings - Fork 154
Conversation
Integrates trafodion with Ambari cluster manager via an mpack (management pack) plug-in. As described in install/README.md file, to leverage this feature, two RPMs are built. One to install the mpack and one used by Amari to install trafodion itself. The mpack plug-in is built with a URL that points to where the trafodion RPM is hosted (a yum repo). It can be specified on the make command line as REPO_URL=...
Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/1509/ |
Test Passed. https://jenkins.esgyn.com/job/Check-PR-master/1509/ |
not hosted there, you need to specify a URL for your local yum repo server. To build that into | ||
the `traf_ambari` package, use make to specify value of `REPO_URL`. | ||
|
||
`make package REPO_URL=http://my.repo.server/repo/...` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this REPO_URL
do? If we set an invalid repo url, does it still work or not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mkby, The URL is what is we plug in to Ambari, so that it will set it up in a repo file on each node where it will install trafodion. Once the repo file is set up on the node, then ambari will do a yum install of apache-trafodion_server package. The only way to work around that is to manually install the RPM on each node. It is much easier to set up a yum repo, if you already have a webserver. If you have a bad URL (including the default one), it will probably break yum install on that cluster. If you have suggestion for better default URL, I'd be glad to hear it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@svarnau, thanks for the explanation. It seems that traf-ambari rpm package is customized with different REPO_URL, so everytime we install on a different envionment, we have to build a new traf-ambari rpm to apply the new URL, is that true?
Can we put this URL into ambari webpage so we can configure the URL from there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ambari seems to only prompt for the HDP and HDP-UTIL repo URLs, and not any repo added in an mpack. It certainly can be changed in the repoinfo.xml file after installing traf_ambari RPM. Trafodion does source code releases, so anyone going to build it to install or distribute it can specify their own web server URL. Also, downstream provider can use it to distribute releases. Just as hortonworks distributes other products. If/when a distributor provides a site for trafodion releases, they can provide this ambari plugin that points to that site.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, sounds good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mkby, I was just testing again today and found what I said earlier is incorrect. Ambari does give a chance to edit the URL in the GUI.
So that helps a lot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! So I think REPO_URL
should only be the default value in the GUI, and user can modify it. It's acceptable to me.
A couple of tweaks to fix problems stop/start/restarting trafodion components via Ambari, particularly to write out any config file changes before they are needed.
New Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/1522/ |
Test Passed. https://jenkins.esgyn.com/job/Check-PR-master/1522/ |
Per review, clarify the readme file to indicate the REPO_URL is to specify the the *default* value of the trafodion repo URL that is built into the traf_ambari RPM.
New Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/1523/ |
Test Passed. https://jenkins.esgyn.com/job/Check-PR-master/1523/ |
Fix a couple issues with ldapcheck command. Also tweak trafodion sudoer permissions to make sure sudo commands will work without a tty.
New Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/1527/ |
Test Passed. https://jenkins.esgyn.com/job/Check-PR-master/1527/ |
New Check Test Started: https://jenkins.esgyn.com/job/Check-PR-master/1532/ |
Test Failed. https://jenkins.esgyn.com/job/Check-PR-master/1532/ |
failure was unrelated timeout |
Integrates trafodion with Ambari cluster manager via an mpack (management
pack) plug-in.
As described in install/README.md file, to leverage this feature, two RPMs
are built. One to install the mpack and one used by Amari to install trafodion
itself. The mpack plug-in is built with a URL that points to where the
trafodion RPM is hosted (a yum repo). It can be specified on the make command
line as REPO_URL=...