incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-3548) Changes to stacks definitions to allow custom services support (needed by an ambari-agent)
Date Tue, 22 Oct 2013 19:30:43 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802162#comment-13802162
] 

Nate Cole commented on AMBARI-3548:
-----------------------------------

* The ability to provide repository information exists with the stack, and several repos may
be used per OS.  I hesitate on putting repos at the service layer.  In addition, repos at
the service layer conflicts with custom repo-base-url functionality.
* The Spec indicates artifacts to the agent ({{script}}, {{templates}}) go in their own {{PACKAGE}}
directory.  This would make it easy to bundle up into a tar and send down. (We can still read
the metainfo from Ambari for the commands/actions available).
* I think JSON vs XML is a good question.  We can pick either, but should be consistent. 
The question is - which format will authors have an easier time with?
* Patch name says AMBARI-2036 - is that for this issue?

> 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)

Mime
View raw message