The reason for not-much activity on that JIRA is because Ambari seems to be
drifting away from real-life orchestration systems like Puppet toward
something else. And that's exactly why I prefer to use Puppet or Chef
orchestration - you have a state machine that works in the same way on every
In 20 years of doing system and network administration as well as software
development I've seen times and again how the fancy UI applications fail to
deliver on their promise. Main reason is in the shifting of the focus on the
bling instead of the core functionality.
Cloudera's CM is a perfect example of my point, because it is doing totally
heinous things with standard Linux services, their life-cycle and
configurations up to the point where any sane Hadoop devops would be helpless
to do anything without CM. Ambrai seems to be a bit better in this respect.
However, with the development above and replacement of the Puppet I am not
sure how much longer it will be the case.
Happy New Year everyone!
On Tue, Dec 31, 2013 at 03:10PM, Steven Núñez wrote:
> Thanks. That issue answers pretty much all the questions. I’d certainly give
> it a +1 if I had a login. That definitely seems like the right direction to
> move in. I don’t know the internals, but if everyone is using BigTop for
> packaging, perhaps there’s some way to read the manifest files (if that’s
> what they’re called) to produce what Ambari needs for management.
> From: Chris Mildebrandt <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
> Reply-To: "[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
> Date: Tuesday, 31 December 2013 7:57
> To: "[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
> Cc: "[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
> Subject: Re: Cluster Management: OpenSource & Vendor Options
> You may want to watch this: https://issues.apache.org/jira/browse/AMBARI-3524
> and include it in your write-up for future considerations. Though there hasn't been much activity on it.
> On Mon, Dec 30, 2013 at 8:32 AM, Steven Núñez <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
> Seasons Greetings All,
> I’m doing a bit of a write-up on the various Hadoop distributions and would like to understand exactly what packages are installed by the Apache version of Ambari. It’s an exciting place to be working (big data & Hadoop) but the lines are blurred in many ways. The way I see the open source landscape now is something like this (from a management/installation/configuration perspective):
> BigTop -> RPM like packaging for Hadoop
> Ambari -> GUI management/monitoring/provisioning
> Looking at it from a vendor perspective, we’ve got (I know there are others, this is just for discussion):
> BigTop (packaging)
> Apache Bigtop
> Cloudera Manager (closed source, commercial)
> Hortonworks / Apache
> Ambari(open source)
> The CDH, BigTop and HDP (I assume) base distributions require a lot of manual configuration, so the best way to spin up a cluster with a reasonable set of applications (say HDFS, YARN, Hive, HCatalog, HBase, ZooKeeper, Oozie, Pig, Sqoop) is to use CDH + CM or Ambari + HDP.
> Is there an equivalent for Apache? If I use the kit found at ambari.apache.org<http://ambari.apache.org> to spin up a cluster, do I get Apache components, or the HDP distribution? I’m trying to define the ‘Apache distribution’ in my mind, if there is one, and understand exactly what its capabilities are, and cluster management is rather fundamental, since not many folks have the luxury of spending time climbing the long, steep learning curve of Hadoop ecosystem configuration.
> - SteveN