[
https://issues.apache.org/jira/browse/AMBARI-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888695#comment-13888695
]
Eric Yang commented on AMBARI-4467:
-----------------------------------
The first part host group to component mapping is the troubled part. The third
part of host-groups to host representation is fine. Any effort to make
blueprint organization cleaner for the structure, it would be easier for
implementation developer to adopt. Just throwing in my two cents.
> 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)
