[jira] [Commented] (AMBARI-14600) Ability to set rack_info with blueprint

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-14600:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12781457/AMBARI-14600.v1.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/4842//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4842//console

This message is automatically generated.

> Ability to set rack_info with blueprint
> ---------------------------------------
>
>                 Key: AMBARI-14600
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14600
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 1.2.1
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>             Fix For: 1.2.1
>
>         Attachments: AMBARI-14600.v1.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Rack information (rack_info) can be set up with API call:
> {code}
> {
>   "RequestInfo": {
>     "context": "Set Rack",
>     "query": "Hosts/host_name.in(host-10-0-0-4.node.dc1.consul)"
>   },
>   "Body": {
>     "Hosts": {
>       "rack_info": "/dc1/rack1"
>     }
>   }
> }
> {code}
> If the cluster was created with a blueprint and the rack information is set up afterwards with the above API call, then the services needs to be restarted. It would be better if we could set up rack_info immediately with blueprint something like this:
> {code}
> {
>   "blueprint" : "multi-node-hdfs-yarn",
>   "default_password" : "my-super-secret-password",
>   "host_groups" :[
>     {
>       "name" : "master", 
>       "hosts" : [         
>         {
>           "fqdn" : "amb1.service.consul",
>           "rack_info": "/dc1/rack1"
>         }
>       ]
>     },
>     {
>       "name" : "slave_1", 
>       "hosts" : [         
>         {
>           "fqdn" : "amb2.service.consul",
>           "rack_info": "/dc1/rack1"
>         }
>       ]
>     }
>   ]
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)