[
https://issues.apache.org/jira/browse/HADOOP-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056315#comment-13056315
]
Jagane Sundar commented on HADOOP-7417:
---------------------------------------
The goal of HMS is to provide a Hadoop specific management platform. While
chef/puppet/bcfg2 and other scripted deployment tools are useful for simpler
software, a complex software platform such as Hadoop could benefit from a
management platform that is custom built for it.
With the hadoop.next platform starting to take shape, the job of installing and
configuring Hadoop is going to need even more sophisticated technology. It is
critical to look at management of Hadoop from a holistic perspective.
HMS plays nice with existing packaging mechanisms such as .rpms, .debs and tar
files, which are the finest granularity building blocks.
Alan - I don't understand your comparison of Whirr with HMS. HMS has the
potential to provide the ability for cloud service providers to provide a clone
of Elastic Map Reduce. Correct me if I am wrong, but isn't Whirr a set of
scripts for deploying Hadoop on an IaaS cloud?
> Hadoop Management System (Umbrella)
> -----------------------------------
>
> Key: HADOOP-7417
> URL: https://issues.apache.org/jira/browse/HADOOP-7417
> Project: Hadoop Common
> Issue Type: New Feature
> Environment: Java 6, Linux
> Reporter: Eric Yang
> Assignee: Eric Yang
>
> The primary goal of Hadoop Management System is to build a component around
> management and deployment of Hadoop related projects. This includes software
> installation, configuration, application orchestration, deployment automation
> and monitoring Hadoop.
> Prototype demo source code can be obtained from:
> http://github.com/macroadster/hms
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira