ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-4467) Create new /blueprints REST endpoint
Date Sat, 01 Feb 2014 07:32:08 GMT

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

Eric Yang commented on AMBARI-4467:
-----------------------------------

The proposed hierarchy is blueprint > host-group > components.  In the first given example,
a blueprint would contain:

A host group contains a list of components.  What if a service that are composed of multiple
host groups, e.g. gateway, master-hosts, and computes.  Each host-group defines the requirement
of hadoop-client component, hdfs component, and job tracker components, datanode component,
task tracker component.

component seems to be more repetitive in host-group than alternate structure:

blueprint > components > host-group > role

The component definition is associated with the service function.  e.g. HDFS is a component,
and master hosts is a kind of host-group, name node is one of the role in master host group.

> Create new /blueprints REST endpoint
> ------------------------------------
>
>                 Key: AMBARI-4467
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4467
>             Project: Ambari
>          Issue Type: New Feature
>            Reporter: John Speidel
>            Assignee: John Speidel
>              Labels: api-addition, blueprints
>             Fix For: 1.5.0
>
>
> Create a new /blueprints REST endpoint. This endpoint represents an 'abstract blueprint'
or 'template' and doesn't contain cluster specific details such specific host information.
> This initial jira will be limited to basic blueprint information and will not contain
configuration elements.  These additional elements will be added in subsequent patches.
> Available operations are get, create and delete.  Update is not supported because blueprints
are immutable.
> Example of a simple blueprint resource:
> {code}
> {
>   "href" : "http://172.18.193.10:8080/api/v1/blueprints/bp1",
>   "host_groups" : [
>     {
>       "name" : "foo",
>       "components" : [
>         {
>           "name" : "component2"
>         },
>         {
>           "name" : "component1"
>         },
>         {
>           "name" : "component4"
>         },
>         {
>           "name" : "component3"
>         }
>       ],
>       "cardinality" : "2"
>     },
>     {
>       "name" : "bar",
>       "components" : [
>         {
>           "name" : "component5"
>         }
>       ],
>       "cardinality" : "1"
>     }
>   ],
>   "Blueprints" : {
>     "blueprint_name" : "bp1",
>     "stack_name" : "HDP",
>     "stack_version" : "1.3.3"
>   }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message