[jira] [Created] (AMBARI-6015) Provide topology validation when creating blueprint

["John Speidel (JIRA)" <ji...@apache.org>]

John Speidel created AMBARI-6015:
------------------------------------

             Summary: Provide topology validation when creating blueprint
                 Key: AMBARI-6015
                 URL: https://issues.apache.org/jira/browse/AMBARI-6015
             Project: Ambari
          Issue Type: Improvement
            Reporter: John Speidel
            Assignee: John Speidel
             Fix For: 1.6.1


Provide topology validation when a blueprint is being created.
Topology is validated based on dependency and cardinality information provided in the associated Ambari stack definition.  I addition to validation, some components, mostly clients, are auto-deployed if not present in the topology. Again, this behavior is specified in the corresponding stack.

If topology validation fails, a 400 response is returned with a descriptive message:

{
status: 400
message: "Cluster Topology validation failed. Invalid service component count: [MYSQL_SERVER(actual=0, required=1), HIVE_METASTORE(actual=0, required=1), HIVE_SERVER(actual=0, required=1)]. To disable topology validation and create the blueprint, add the following to the end the url: '?validate_topology=false'"
}

To create a blueprint that doesn't validate, a user can disable topology validation in the URL via '?validate_topology=false'.

The following cases are not currently supported by blueprint topology validation and will require a user to disable validation when creating a blueprint.
- external reference to MYSQL_SERVER or HIVE_METASTORE
- HA topology with > 1 NN and < 1SNN
- any other topology in which the default cardinality is is conditional on other topology information.  HA is one example of this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)