[jira] [Commented] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
[ https://issues.apache.org/jira/browse/AMBARI-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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=commit=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)
[jira] [Commented] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
[ https://issues.apache.org/jira/browse/AMBARI-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552651#comment-15552651 ] Hudson commented on AMBARI-18516: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #121 (See [https://builds.apache.org/job/Ambari-branch-2.5/121/]) AMBARI-18516. Add ability to have services declare itself as (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8ef3088fe0d1305aceae0f9039a0d0429e572fe4]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackServiceResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java * (edit) ambari-server/src/main/resources/properties.json * (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 * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceResponse.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)
[jira] [Commented] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
[
https://issues.apache.org/jira/browse/AMBARI-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546347#comment-15546347
]
Hadoop QA commented on AMBARI-18516:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831521/AMBARI-18516.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8802//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8802//console
This message is automatically generated.
> 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)
[jira] [Commented] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
[
https://issues.apache.org/jira/browse/AMBARI-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543169#comment-15543169
]
Hadoop QA commented on AMBARI-18516:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831336/AMBARI-18516.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8790//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8790//console
This message is automatically generated.
> 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)
