[
https://issues.apache.org/jira/browse/AMBARI-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802917#comment-13802917
]
Dmitry Lysnichenko commented on AMBARI-3548:
--------------------------------------------
Regarding switching from XML to JSON, it is possible. But work with XML/JAXB is
hardcoded at StackExtensionHelper, so we will have to support two different
implementations for JSON and for XML (to support also old-style services). I'd
vote for doing that on later development phases. Agent does not have to work
with metadata.xml file directly, it receives all relevant information as
command parameters from the server.
> Changes to stacks definitions to allow custom services support (needed by an
> ambari-agent)
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-3548
> URL: https://issues.apache.org/jira/browse/AMBARI-3548
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 1.5.0
>
> Attachments: AMBARI-2036-preview.patch, hbase_new_metainfo.json,
> hbase_new_metainfo.xml, hbase_old_metainfo.xml, service_metainfo_changes.patch
>
>
> Stack definitions for custom services should contain fields:
> - service metadata
> -- list of repositories
> - component metadata should contain fields:
> -- scriptType (possible values: "python", "puppet")
> -- taskTimeout (per-component value)
> Except metadata files, custom service directory should contain:
> - script directory that contains separate python files for components (e.g.
> namenode.py, datanode.py etc.) and service.py file.
> - a separate directory for templates
> Patch is so large because I've created a separate stack dir with modified
> HBase metadata.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
