[
https://issues.apache.org/jira/browse/AMBARI-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18516:
---------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Add ability to have services declare itself as tech-preview or mandatory
> ------------------------------------------------------------------------
>
> Key: AMBARI-18516
> URL: https://issues.apache.org/jira/browse/AMBARI-18516
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18516.patch
>
>
> When a service is added to a stack, it should be identified as:
> default/regular - service is optional on the cluster, UI usually shows it as
> tech-preview - service may be deployed, UI will not auto-select these
> services and mark them as TechPreview
> mandatory - service need to be deployed and all deployment should fail is the
> service is not selected during deployment
> Lets create a proposal of what changes are needed in the services'
> metainfo.xml? Note that a service can change its attribute between stack
> versions - e.g. move from "tech-preview" to "mandatory".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
