ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krisztian Horvath (JIRA)" <>
Subject [jira] [Commented] (AMBARI-7246) Ability to know the host-hostgroup relationship
Date Mon, 15 Sep 2014 22:09:35 GMT


Krisztian Horvath commented on AMBARI-7246:

Hi John,

Thank you for your comment, yes, I'm aware its only relevant when the clusters is installed
from blueprint just like the cluster-blueprint relation. It doesn't make any sense when no
blueprint is used at all, but if it is I think it should be part of the meta information.
Right now it you install a cluster from a blueprint later you don't have any information what
blueprint was used and which services of a host group was installed to a host. 

> Ability to know the host-hostgroup relationship
> -----------------------------------------------
>                 Key: AMBARI-7246
>                 URL:
>             Project: Ambari
>          Issue Type: Technical task
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Krisztian Horvath
>            Assignee: Krisztian Horvath
>             Fix For: 1.7.0
>         Attachments: AMBARI-7246-0.patch, AMBARI-7246-0.png
> Use case: A cluster is installed from a blueprint thus every host belongs to a host group.
We created an open source project Periscope which can scale up or down based on host groups.
Currently the association is stored at Cloudbreak side which actually installed the cluster.
It would be much convenient if we could ask Ambari which node(s) can we delete from a host
group in case of a scale down.
> For example if we'd say we want to remove 2 nodes from slaves host group we could ask
ambari which nodes belong to that group.

This message was sent by Atlassian JIRA

View raw message