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

Nate Cole commented on AMBARI-2714:
-----------------------------------

@Erin - initially it will be configuring XML and have the UI recognize it as an 
addable service.  The capability exists to reload stack definitions already, so 
that's no big deal.  Long term I agree - we want to be supply new services 
using the UI itself.  You are also correct in that we want to be able to supply 
all the artifacts surrounding a new service including tarballs, scripts etc.  
To start with, at least, we'll probably focus on defining a service without 
modifying code.  Then we can start adding real capability.

@Abhishek - I think a great use-case will be to try to add Storm without 
modifying Ambari code.

@K. Eric - I'm not too familiar with Supervisor - how would you envision that 
fitting with Ambari (it handles monitoring and control already)?
                
> Ability to dynamically add services to a stack.
> -----------------------------------------------
>
>                 Key: AMBARI-2714
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2714
>             Project: Ambari
>          Issue Type: Improvement
>          Components: controller
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>         Attachments: Stack Definitions.docx
>
>
> Simplifying adding a new service and allowing it to be a simple admin task to 
> add his own service.  The first attempt at this will be to define a service 
> outside Ambari, such that it becomes a "zero code" effort.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to