[
https://issues.apache.org/jira/browse/HBASE-12869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285981#comment-14285981
]
Dima Spivak commented on HBASE-12869:
-------------------------------------
So I spent a few days investigating the possibility of implementing a single
"RESTApiClusterManager" class and realized it can't be done in a very clean
way. In short, the different APIs (i.e. Cloudera Manager, Ambari) have very
different ways of running commands (e.g. Cloudera Manager acts on host IDs,
which need a separate API call to discover from a hostname, but that requires
parsing JSON). So two ways forward:
1) I can Implement RESTApiClusterManager1 that's Cloudera Manager-specific, but
which doesn't bring in any Cloudera dependencies and only specifies that it's
for Cloudera Manager in a comment. This has the advantage of being an example
for others who want to see how ClusterManager can be implemented and would open
the door for anyone interested in modifying and creating RESTApiClusterManager2
that can handle Ambari.
2) Just close this out as won't fix and let each user deal with implementing
the interface themselves if they want to run integration tests.
What do you think, [~apurtell]?
> Add a ClouderaManager implementation of the ClusterManager interface
> --------------------------------------------------------------------
>
> Key: HBASE-12869
> URL: https://issues.apache.org/jira/browse/HBASE-12869
> Project: HBase
> Issue Type: New Feature
> Components: integration tests
> Reporter: Dima Spivak
> Assignee: Dima Spivak
>
> ChaosMonkey doesn't work on HBase/CDH clusters set up using Cloudera Manager
> because Cloudera Manager doesn't make use of hbase-daemon.sh (so killed
> RegionServers can't be started up again). To fix this, I want to implement
> ClouderaManagerClusterManager. I could just as well keep this internal (or
> only include it in Cloudera's distribution), but seeing as how it would open
> up more people across the community to run hbase-it, I'd like to commit it
> upstream. Anyone object?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
