ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
Date Thu, 06 Oct 2016 20:09:20 GMT

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

Hudson commented on AMBARI-18516:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5771 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5771/])
AMBARI-18516. Add ability to have services declare itself as (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=56e00acdc8d7357ba811fcd4dca4fbb23bad33be])
* (edit) ambari-server/src/main/resources/properties.json
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackServiceResourceProvider.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceResponse.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/state/ServiceInfoTest.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java


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

Mime
View raw message