[
https://issues.apache.org/jira/browse/HAWQ-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435462#comment-15435462
]
Vineet Goel commented on HAWQ-1013:
-----------------------------------
This JIRA is actually not related to moving Ambari plugin to HAWQ repo, perhaps
the description should be changed.
Ambari plugin requires Ambari to be aware of a service, and that plugin code
already resides in Apache Ambari repo, here:
https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0
In order to enable the Ambari plugin, a script is required during HAWQ
install-time to make an Ambari “Stack” aware of the service being managed. That
script and implementation is tightly coupled with the service (HAWQ) itself and
should be managed in the service (HAWQ) repo. Hope this helps.
> Move HAWQ Ambari plugin to Apache HAWQ
> --------------------------------------
>
> Key: HAWQ-1013
> URL: https://issues.apache.org/jira/browse/HAWQ-1013
> Project: Apache HAWQ
> Issue Type: New Feature
> Components: Ambari
> Reporter: Matt
> Assignee: Alexander Denissov
> Labels: UX
> Fix For: backlog
>
>
> To add HAWQ and PXF to Ambari, users have to follow certain manual steps.
> These manual steps include:
> - Adding HAWQ and PXF metainfo.xml files (containing metadata about the
> service) under the stack to be installed.
> - Adding repositories, where HAWQ and PXF rpms reside so that Ambari can use
> it during installation. This requires updating repoinfo.xml under the stack
> HAWQ and PXF is being added to.
> - Adding repositories to an existing stack managed by Ambari requires adding
> the repositories using the Ambari REST endpoint.
> The HAWQ Ambari plugin automates the above steps using a script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
