[jira] [Updated] (AMBARI-10424) Views : Auto create

["Tom Beerbower (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-10424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Beerbower updated AMBARI-10424:
-----------------------------------
    Attachment: AMBARI-10424.patch

> Views : Auto create
> -------------------
>
>                 Key: AMBARI-10424
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10424
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10424.patch
>
>
> Ability to automatically instantiate a view instance for a cluster during create based on the stack and services included in the cluster -- whether using blueprints or install wizard (so views are created automatically with a cluster create). The view itself should describe what stack and services it is associated with, and when a cluster is created in the ambari the view is deploy in, a view instance is automatically created. Ambari Admins should have an option to override this setting in case they do not want the view instances automatically created. This includes support for designating in the view.xml stack and services support for a view. Similar to the way min-ambari-version is specified, the view developer needs a way to identify that the view works with stack(s) (such as "HDP-2.2" or "HDP-2.2, HDP 2.3" or "HDP-2*") and what services need to be in the cluster ("YARN" or" YARN, HIVE"). Once a cluster is created matching those stack + service requirements, the view is automatically instantiated (and uses the "local ambari cluster" configuration option in #2 below).
> {code}
> - view.xml to describe stack(s) and service(s)
> - if that information is there, it’s available for auto-create
> - after auto-create, default permissions are blank (only ambari admin can access)
> - Auto-create event = on create cluster
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)