You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Trevor McKay (JIRA)" <ji...@apache.org> on 2013/04/23 20:25:15 UTC
[jira] [Updated] (AMBARI-1995) Allow RoleCommandOrder objects to be
created dynamically with a StackId and AmbariMetaInfo as context
[ https://issues.apache.org/jira/browse/AMBARI-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trevor McKay updated AMBARI-1995:
---------------------------------
Attachment: RCO.patch
RCO.patch is a protoytype for this against branch-1.2, with log messages in RoleCommandOrder.initialize() for proof of concept.
> Allow RoleCommandOrder objects to be created dynamically with a StackId and AmbariMetaInfo as context
> -----------------------------------------------------------------------------------------------------
>
> Key: AMBARI-1995
> URL: https://issues.apache.org/jira/browse/AMBARI-1995
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Environment: Fedora/RHEL (but should be generally applicable)
> Reporter: Trevor McKay
> Attachments: RCO.patch
>
>
> Currently, the RoleCommandOrder object is created statically and defines fixed dependencies used for stage generation.
> It should be possible to create RoleCommandOrder objects with AmbariMetaInfo (injected by Guice) and a StackId argument to initialize(). This would allow the dependencies for stage planning to be generated relative to the particular stack being used.
> Generated RCOs can be cached against the StackId so they can be created once per StackId.
--
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