stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "reka thirunavukkarasu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STRATOS-124) Remove PortMapping and deploymnet from cartridge definition
Date Thu, 24 Oct 2013 07:57:05 GMT

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

reka thirunavukkarasu commented on STRATOS-124:
-----------------------------------------------

Yah..We have to consider your thought here...In the case of automating the cartridges using
puppet or scripts, we need to pass the ports to the cartridge instance via the payload. But
we can remove the proxy port from the portMapping element, since we can get the proxyport
from LB or from the LB cartridge definition when we introduce LB as a cartridge.

The deployment section, we will move it under the dynamic payload. So that the user can define
cartridge related deployment artifacts and other configuration there..

> Remove PortMapping and deploymnet from cartridge definition
> -----------------------------------------------------------
>
>                 Key: STRATOS-124
>                 URL: https://issues.apache.org/jira/browse/STRATOS-124
>             Project: Stratos
>          Issue Type: Improvement
>            Reporter: reka thirunavukkarasu
>            Assignee: reka thirunavukkarasu
>              Labels: CC, LB
>             Fix For: 4.0.0 M2
>
>
> Need to remove the portmapping from cartridge definition and handle the portmapping in
topology with the events received from LB and from the member.
> Need to remove the deployment from the cartridge definition and handle it in the cartridge
agent level.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message