[
https://issues.apache.org/jira/browse/STRATOS-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347541#comment-14347541
]
ASF GitHub Bot commented on STRATOS-1180:
-----------------------------------------
GitHub user chamilad opened a pull request:
https://github.com/apache/stratos/pull/257
[STRATOS-1180] - Extension execution in addition to plugins
In this fix, the bash extensions are allowed to execute being mapped to the
events they are related by the extension name.
ex:
ArtifactUpdatedEvent.sh will be executed at the ArtifactsUpdatedEvent.
A plugin called ExtensionExecutor will be executing the extensions, based
on the event upon which it is called on.
Additionally, the server start logic has been included in the Agent, and
PCA plugins for PHP and Tomcat Docker images are included.
Verified using local Kubernetes vagrant setup.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chamilad/stratos stratos-1180-02
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/stratos/pull/257.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #257
----
commit ca54710b9d0b7ee6d7e764f207c21c9330517b40
Author: Chamila de Alwis <chami...@wso2.com>
Date: 2015-02-23T09:09:09Z
PCA - Renamed SubscriptionDomain*Event to DomainMapping*Event, replaced
extension scripts
commit da47d70ae743e1f28a08acca9ebaf08911fb632c
Author: Chamila de Alwis <chami...@wso2.com>
Date: 2015-02-23T09:29:32Z
JCA - Renamed SubscriptionDomain*Event to DomainMapping*Event
PCA - Refactored constant names, event names related to above change
commit d67eabfe4ad7ae1c592c1e894b908ed418f79796
Author: Chamila de Alwis <chami...@wso2.com>
Date: 2015-02-24T08:15:19Z
PCA - Moved bash extensions to extensions/bash
PCA - Added ExtensionExecutor to run extension bash scripts
PCA - Integration test, change extension permissions
commit 3037c5656e2f8bbef252fae23fca63ecc5b5cfb4
Author: Chamila de Alwis <chami...@wso2.com>
Date: 2015-02-24T09:51:56Z
PCA - ExtensionExecutor plugin improvments.
commit 4e57b31b4696d70d65263ab407bab65d8d1504b1
Author: Chamila de Alwis <chami...@wso2.com>
Date: 2015-02-24T10:00:31Z
PCA - removed extension conf and const entries
commit c8141e262c7afa17912fae9e5425805d6dace521
Author: Chamila de Alwis <chami...@wso2.com>
Date: 2015-03-04T20:25:32Z
PCA - ExtensionExecutor improved
Dockerfile - PHP and Tomcat dockerfiles updated and server start plugins
included
----
> 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
> Fix For: 4.1.0 Beta
>
>
> 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)
