ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laszlo Puskas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-14600) Ability to set rack_info with blueprint
Date Sun, 10 Jan 2016 15:40:39 GMT
Laszlo Puskas created AMBARI-14600:
--------------------------------------

             Summary: 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


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)

Mime
View raw message