incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (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 22:05:48 GMT

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

Sumit Mohanty commented on AMBARI-3548:
---------------------------------------

To [~ncole@hortonworks.com]'s comments:

We will definitely have the repo information at the top level. The idea for keeping it at
service level is to allow addition of services that are not released as part of HDP. So we
need a room for repo URL at the level of services. For the next 4-5 services we are adding
we will not need the repo url as they will all, most likely, be part of HDP. Anyway, the custom-url
feature will only work if all services are part of the same repo - in which case we do not
need to specify repo url at the service spec.

I am OK with either creating PACKAGE folder or packing the whole "HBASE" folder including
configuration, metainfo, etc. The later is probably little wasteful.

> 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