You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2018/01/25 10:52:00 UTC
[jira] [Created] (AMBARI-22845) Update service metainfo schema
Dmytro Sen created AMBARI-22845:
-----------------------------------
Summary: Update service metainfo schema
Key: AMBARI-22845
URL: https://issues.apache.org/jira/browse/AMBARI-22845
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 3.0.0
An mpack is composed on multiple modules. Modules could be categorized as "SERVER" module or a "CLIENT" module. In Ambari an mpack represents a stack and a module represents a service definition. We need to update the service metainfo schema to be able to specify the module category.
{code}
<service>
<name>MODULE-NAME</name>
<category>LEGACY|SERVER|CLIENT</category>
</service>
{code}
LEGACY category should be the default to support old stacks (HDP-2.6).
Also an mpack could ship with different version of datanode and namenode (hotfix release for a component). Apart from having a service version, we should also be able to specify the component version in the mpack. If component version is not specified then componentVersion == serviceVersion
{code}
<service>
<name>HDFS</service>
<category>SERVER</category>
<version>3.0.0.0-b123</version>
<components>
<component>
<name>DATANODE</name>
<version>3.0.0.0-h7-b5</version>
</component>
<component>
<name>NAMENODE</name>
</component>
</components>
</service>
{code}
In the example above DATANODE is 3.0.0.0-h7-b5 whereas all other HDFS components are 3.0.0.0-b123.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)