Looping AmilaM, Hi Amila,
Could you please add your opinion on this, as we discussed? Thanks. Madhawa On Sat, Jul 26, 2014 at 6:18 AM, Dimuthu Leelarathne <[email protected]> wrote: > Hi all, > > Sorry for stealing the thread with the JNDI concern. So my question is > what is the business model we want to support? It would be easy and cheap > to support per app cartridge but here are some questions running through my > head, > > - What is the business model we want to support in cloud? Per app > containers? Or per tenant containers? Will the decision be based on the > tier level, as in Silver vs. Platinum? If it is per app, are we going to > limit the number of instances per tenant? > - Since this is tomcat, we can support both business model because looks > like we can achieve JNDI runtime isolation > - If (and only if) we want different business models then we need to be > able to enable them based on configurations > - If a cartridge is not being used is it going to be taken down? This is > analogous to tenant being unloaded > > I think before finalising we have to answer these questions. > > In addition we need to change code-snippets on how to use resources. > Because now it should be a single REST call to get the properties from the > registry - we have to give a sample of JSON string of property-value pairs. > > thanks, > dimuthu > > > > > On Fri, Jul 25, 2014 at 6:15 PM, Ajanthan Balachandran <[email protected]> > wrote: > >> >> >> >> On Fri, Jul 25, 2014 at 3:38 PM, Dimuthu Leelarathne <[email protected]> >> wrote: >> >>> Hi Ajanthan, >>> >>> Please see my answers inline. >>> >>> >>> On Fri, Jul 25, 2014 at 3:24 PM, Ajanthan Balachandran < >>> [email protected]> wrote: >>> >>>> Hi, >>>> >>>> >>>> On Fri, Jul 25, 2014 at 2:40 PM, Ramith Jayasinghe <[email protected]> >>>> wrote: >>>> >>>>> Addition to this, >>>>> When application is deleted Appfactory should remove the subscription >>>>> made for this application ( a.k.a unsubscribe from the cartridge) >>>>> >>>>> >>>>> On Fri, Jul 25, 2014 at 2:34 PM, Madhawa Bandara <[email protected]> >>>>> wrote: >>>>> >>>>>> User story: >>>>>> >>>>>> When user creates a web application (app type : war), he should be >>>>>> able to select the runtime on which he wants his application to be >>>>>> deployed. >>>>>> >>>>>> Application Creation: Steps: >>>>>> >>>>>> 1. A user navigates to ‘Create Application’ page. >>>>>> >>>>>> 2. Selects the application type as Web Application (app type = war). >>>>>> >>>>>> 3. Appfactory would populate a drop down list that displays the >>>>>> available runtimes: >>>>>> >>>>>> WSO2 Application Server v 5.1.0 >>>>>> >>>>>> Apache Tomcat v 7.0.54 >>>>>> >>>>>> 4. User selects ‘Apache Tomcat’ as his preferred runtime and creates >>>>>> the application >>>>>> >>>>>> (Appfactory will record this information for later use). >>>>>> >>>>>> >>>>>> Application Deployment: >>>>>> >>>>>> 1. Upon the very first deployment of any application version onto a >>>>>> particular stage, Appfactory would make a subscription in Stratos, based >>>>>> on >>>>>> the selected runtime during the application creation (git repository >>>>>> containing the war artifact is provided during the subscription). >>>>>> >>>>>> Examples: >>>>>> >>>>>> a) A trunk version of the application is auto-built and auto-deployed >>>>>> onto the ‘Development’ stage. Before the very first deployment happens >>>>>> (after the auto build) Appfactory should make the subscription. >>>>>> >>>>>> b) Promotion of an application >>>>>> >>>>>> >>>>>> - A developer promotes a particular version of an application >>>>>> from the Development stage to the Testing stage. >>>>>> - A QA Engineer clicks on the ‘Deploy’ button of that version. >>>>>> - Appfactory checks whether there is a subscription available for >>>>>> this application in Testing stage. >>>>>> - If there is no such subscription already, then Appfactory would >>>>>> make a new subscription based on the runtime selected during the >>>>>> application creation. >>>>>> - Appfactory would deploy the particular application version onto >>>>>> the server in the Test Stage. >>>>>> >>>>>> >>>>>> 2. If the runtime selected by the user is based on a single tenanted >>>>>> cartridge, Stratos will spin up a new cartridge once a subscription is >>>>>> made. If the runtime provided is a multi-tenanted cartridge, the >>>>>> instances >>>>>> are created when cartridge definition is provisioned (as specified by >>>>>> the >>>>>> autoscaling and deployment policy). >>>>>> >>>>> Here what is the strategy for spawning single tenant cartridges?Is it >>>> cartridge per application? Or one cartridge per tenant? >>>> >>> >>> What about the JNDI look up isolation we have done in App Server? Is it >>> portable to Tomcat? >>> >> In tomcat each web app will get their own JNDI context but the problem is >> Tomcat does not allow adding/editing and deleting JNDI resource without a >> redeploy.So we will not able to register datasources for web app >> dynamically.We can port the same idea to tomcat ,we may need to extend >> tomcat's JNDI factory and plug. >> >>> >>> thanks, >>> dimuthu >>> >>> >>> >>>> >>>>>> Improvements: >>>>>> >>>>>> User could be given the option to select the runtime per application >>>>>> per stage. >>>>>> >>>>>> (e.g. Apache tomcat dev/test stages , WSO2 Application server for >>>>>> Production stage) >>>>>> >>>>>> >>>>>> >>> >>>> >>>>>> -- >>>>>> Regards, >>>>>> >>>>>> *Madhawa Bandara* >>>>>> Software Engineer >>>>>> WSO2, Inc. >>>>>> lean.enterprise.middleware >>>>>> >>>>>> Mobile - *+94777487726 <%2B94777487726>* >>>>>> Blog* - *classdeffound.blogspot.com >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ramith Jayasinghe >>>>> Technical Lead >>>>> WSO2 Inc., http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> E: [email protected] >>>>> P: +94 777542851 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> ajanthan >>>> -- >>>> Ajanthan Balachandiran >>>> Senior Software Engineer; >>>> Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ >>>> >>>> email: ajanthan <http://goog_595075977>@wso2.com; cell: +94775581497 >>>> blog: http://bkayts.blogspot.com/ >>>> >>>> Lean . Enterprise . Middleware >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Dimuthu Leelarathne >>> Architect & Product Lead of App Factory >>> >>> WSO2, Inc. (http://wso2.com) >>> email: [email protected] >>> Mobile : 0773661935 >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> ajanthan >> -- >> Ajanthan Balachandiran >> Senior Software Engineer; >> Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ >> >> email: ajanthan <http://goog_595075977>@wso2.com; cell: +94775581497 >> blog: http://bkayts.blogspot.com/ >> >> Lean . Enterprise . Middleware >> > > > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > -- Regards, *Madhawa Bandara* Software Engineer WSO2, Inc. lean.enterprise.middleware Mobile - *+94777487726* Blog* - *classdeffound.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
