You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Reka Thirunavukkarasu (JIRA)" <ji...@apache.org> on 2015/05/22 14:30:17 UTC

[jira] [Resolved] (STRATOS-1180) Modify extension execution structure in Python Cartridge Agent

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

Reka Thirunavukkarasu resolved STRATOS-1180.
--------------------------------------------
    Resolution: Fixed
      Assignee: Chamila de Alwis

Resolving the jira, as it is fixed according to the above comment.

> Modify extension execution structure in Python Cartridge Agent
> --------------------------------------------------------------
>
>                 Key: STRATOS-1180
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1180
>             Project: Stratos
>          Issue Type: Task
>          Components: Cartridge Agent
>            Reporter: Chamila de Alwis
>            Assignee: Chamila de Alwis
>             Fix For: 4.1.0 RC1
>
>
> Currently we have bash scripts as extensions however if we could introduce a python extension layer in between that would make it much easier to implement extension logic.
> The current extension setup is as follows. A set of bash scripts are available in the <PCA_HOME>/extensions. The file name of the extension that should be executed for each event is defined in the agent configuration (agent.conf in PCA, stratos.sh in JCA). The event handler executes these bash scripts as new shell commands when the respective events are received.
> We can introduce a layer between the bash scripts and the python code that calls them. The names of the python scripts corresponding to each event can be defined as before. 
> Additionally we can extend this behavior to the Git artifact management component of the PCA. The contract that the artifact management component should adhere to is "checkout" and "push". We can separate the current python code relating to these two operations in to two extension scripts.



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