Hi Jayanga, >From the beginning of C5, we tried to achieve a clear separation between, > User(Custom) space and Server space. > IMO, having just a single deployment directory (for both custom and server > artifacts) won't help to maintain that separation.
We are having 2 deployment directories. 1. <server-home>/<runtime-home>/deployment 2. <server-home>/deployment The issue is in existing API we have a method to deploy/upload the given artifact to the deployment directory. This was not an issue previously coz we had only single deployment dir. But since now we have multiple deployment dirs, where should we deploy the artifact? Thanks Thusitha On Mon, Aug 14, 2017 at 11:15 AM, Jayanga Dissanayake <jaya...@wso2.com> wrote: > Hi Thusitha/Nira, > > From the beginning of C5, we tried to achieve a clear separation between, > User(Custom) space and Server space. > IMO, having just a single deployment directory (for both custom and server > artifacts) won't help to maintain that separation. > > WDYT? > > Thanks, > Jayanga. > > *Jayanga Dissanayake* > Associate Technical Lead > WSO2 Inc. - http://wso2.com/ > lean . enterprise . middleware > email: jaya...@wso2.com > mobile: +94772207259 <+94%2077%20220%207259> > <http://wso2.com/signature> > > On Mon, Aug 14, 2017 at 10:53 AM, Niranjan Karunanandham < > niran...@wso2.com> wrote: > >> Hi, >> >> On Fri, Aug 11, 2017 at 11:24 AM, Thusitha Thilina Dayaratne < >> thusit...@wso2.com> wrote: >> >>> Hi All, >>> >>> In c5 carbon-deployment we have a method to manually deploy artifacts >>> where we only provide artifact's path and artifact type. This was no issue >>> until 5.2.0-m3 since we only had a single deployment directory. >>> public void deploy(String artifactPath, ArtifactType artifactType)[1] >>> >>> But since we have 2 deployment directories with the new >>> runtime architecture. So how should we handle this deployment? >>> AFAIU options would be as follows >>> >>> 1. Add a new API(method) to get the relevant deployment dir and >>> deploy to that >>> 2. We have to prioritize a deployment directory (Server or runtime) >>> and deploy only to the prioritized one >>> 3. Deploy to both deployment dirs >>> >>> >>> >> In the new deployment directory, each runtime will have a deployment >> directory and there will be on outside. The runtime deployment will be for >> wso2 artifacts. AFAIU with previous model (C4), the above method is used by >> when a user uploads the artifact from a UI. Therefore IMO the default >> method should deploy the artifact to the deployment directory outside the >> runtime, i.e., <ServerHome>/deployment. >> >> >>> [1] - https://github.com/wso2/carbon-deployment/blob/master/comp >>> onents/org.wso2.carbon.deployment.engine/src/main/java/org/w >>> so2/carbon/deployment/engine/DeploymentService.java#L43 >>> >>> Thanks >>> Thusitha >>> >>> >>> On Fri, Jun 2, 2017 at 10:23 AM, Danesh Kuruppu <dan...@wso2.com> wrote: >>> >>>> Hi all, >>>> >>>> Correction: Proposed directory structure needed to be change as below. >>>> instead of having deployment directory per runtime, we will have only >>>> deployment directory per server distribution. This deployment directory >>>> contains custom deployable artifacts. So ideally there won't be any >>>> artifact in default distribution. >>>> >>>> Though we have packaging all runtimes in one distribution. we are not >>>> encouraging to run all runtime from the single pack. So we are going to >>>> provide a script to exact runtime from the distribution pack. >>>> >>>> ServerHome >>>>> |_________ bin >>>>> | |_______ runtime1.sh >>>>> | |_______ runtime2.sh >>>>> | |_______ start-all.sh (start all the runtimes except >>>>> default in separate JVMs) >>>>> | |_______ default.sh (start required runtimes in a >>>>> single JVM) >>>>> | |_______ jartobundle.sh >>>>> | >>>>> | >>>>> |_________ deployment (This will contains custom deployable >>>>> artifacts) >>>>> | |_______ uuf >>>>> | |_______ microservices >>>>> | >>>>> |_________ lib >>>>> | >>>>> |_________ conf >>>>> | |________ runtime1 >>>>> | | |________ deployment.yaml >>>>> | | |________ master-keys.yaml >>>>> | | |________ secrets.properties >>>>> | | |________ log4j2.xml >>>>> | | |________ etc >>>>> | | | |______ >>>>> pax-logging.properties >>>>> | | |________ osgi >>>>> | | |______ launch.properties >>>>> | | |______ osgi-debug.options >>>>> | |________ runtime2 >>>>> | |________ deployment.yaml >>>>> | |________ master-keys.yaml >>>>> | |________ secrets.properties >>>>> | |________ log4j2.xml >>>>> | |________ etc >>>>> | | |______ >>>>> pax-logging.properties >>>>> | |________ osgi >>>>> | |______ launch.properties >>>>> | |______ osgi-debug.options >>>>> | >>>>> |_________ resources >>>>> | |________ security >>>>> | |________ wso2secvault.jks >>>>> | |________ wso2carbon.jks >>>>> | >>>>> |_________ wso2 >>>>> |_______ Default (this can be used to combine several >>>>> runtimes e.g in IoT) >>>>> | |_______ bin >>>>> | | |_____ carbon.sh >>>>> | |_______ deployment >>>>> | >>>>> |_______ Runtime1 >>>>> | |_______ bin >>>>> | | |______ carbon.sh >>>>> | |_______ deployment >>>>> | >>>>> |_______ Runtime2 >>>>> | |_______ bin >>>>> | | |_____ carbon.sh >>>>> | |_______ deployment >>>>> | >>>>> |_______ lib (this will contains common jars) >>>>> >>>>> >>>> Thanks >>>> -- >>>> >>>> *Danesh Kuruppu* >>>> Senior Software Engineer | WSO2 >>>> >>>> Email: dan...@wso2.com >>>> Mobile: +94 (77) 1690552 <+94%2077%20169%200552> >>>> Web: WSO2 Inc <https://wso2.com/signature> >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Thusitha Dayaratne >>> WSO2 Inc. - lean . enterprise . middleware | wso2.com >>> >>> Mobile +94712756809 <+94%2071%20275%206809> >>> Blog alokayasoya.blogspot.com >>> About http://about.me/thusithathilina >>> <http://wso2.com/signature> >>> >>> >> Regards, >> Nira >> >> -- >> >> >> *Niranjan Karunanandham* >> Associate Technical Lead - WSO2 Inc. >> WSO2 Inc.: http://www.wso2.com >> >> > -- Thusitha Dayaratne WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com About http://about.me/thusithathilina <http://wso2.com/signature>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
