[
https://issues.apache.org/jira/browse/SLIDER-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393726#comment-14393726
]
thomas liu commented on SLIDER-820:
-----------------------------------
In org.apache.slider.providers.agent.application.metadata.Component, we add a
new String List that keeps track of the order in which master and addon
packages should be installed, configured and started
In AgentProviderService, we keep ComponentInstanceState for each
Component+package. (We use component + '-' + package as the identifier in the
map)
And at the moment when previously we call ComponentInstanceState.getCommand()
to determine the next command for the component, now we first query Component
which package comes next, and then we call getCommand() on the package's
ComponentInstanceState to get the next command to run.
So we are issuing commands 'master package INSTALL', 'addon package 1 INSTALL',
... 'master package START', one by one. Only after previous command got
successfully executed on the SliderAgent side, we start to execute the next
command. We still rely on existing ComponentCommandOrder to enforce component
instantiation order. So on the SliderAgent side, it will install packages one
by one and then start the master.
> Enable AgentProviderService issue INSTALL and CONFIGURE command for addon
> packages
> ----------------------------------------------------------------------------------
>
> Key: SLIDER-820
> URL: https://issues.apache.org/jira/browse/SLIDER-820
> Project: Slider
> Issue Type: Sub-task
> Components: app-package, client
> Reporter: thomas liu
> Fix For: Slider 0.80
>
>
> Enable AgentProviderService issue INSTALL and CONFIGURE command for addon
> packages, with parameters in the commands to install and configure addon
> packages onto master package directories, for lib, conf, bin...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
