Hi Madhawa, Some missing points what happens application becomes idle? There are several options that comes into my head.
1 - Ideally, when an application becomes idle for sometime (15 minutes) we have to undeploy the cartridge. We can do this by CEP listening to events published by load balancer. After certain time if the app gets a request again, we should automatically start the cartridge 2 - However even if un-deployment is possible after idle time, I don't think we can do dynamic deployment on the first request after idle time. One problem is the time we take to start up the startos instance. So if we look at the PaaS market there is an option to activate application when it becomes inactive (because it was idle) at least for free cloud accounts we have now. 3 - But 2 will not be feasible if a person has to manually click the activate button if his cloud account is gold/platinum. So I believe the undeployment policy should be based on account, eventually. Giving an activate button for now should be ok failing 1st option. Ideas? thanks, dimuthu On Wed, Jul 30, 2014 at 11:40 AM, Madhawa Bandara <madh...@wso2.com> wrote: > Hi all, As a part of our effort to make the Appfactory support more > application types, we are going to facilitate PHP. > > PHP support becomes important since it is one of the most popular > server-side scripting languages. > > Appfactory would help the developers, QA engineers and other stakeholders > automate > and accelerate the application life-cycle management of their PHP web > applications. > Problem: > > At the moment, PHP applications are not supported by Appfactory. > User story: > > When user creates a php web application and performs application lifecycle > management operations on his application. > > Application Creation: > > 1. A user navigates to ‘Create Application’ page. > > 2. Selects the application type as PHP Application. > > 3. Creates the application. > > Application Deployment: > > Subscription would be per-application, hence the following workflows. > > 1. Upon the deployment of the first version of an application onto a > particular stage, Appfactory would make a subscription in Stratos to the > PHP cartridge during the application creation (git repository containing > the web application artifacts 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 > > e.g. > > - > > 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. > - > > Appfactory would deploy the particular application version onto the > web server in the Test Stage. > > 2. Any subsequent app versions deployed after the deployment of the > first version would use the same subscription if there is any subscriptions > available. > > > Optional/Improvements: > > Demoting an application > > e.g. > > - > > A QA engineer clicks the ‘demote’ button upon a test failure back to > the dev stage. > - If there are no versions available in the testing stage for that > application, Appfactory would unsubscribe from the PHP cartridge. > > > > > -- > Regards, > > *Madhawa Bandara* > Software Engineer > WSO2, Inc. > lean.enterprise.middleware > > Mobile - *+94777487726 <%2B94777487726>* > Blog* - *classdeffound.blogspot.com > -- Dimuthu Leelarathne Architect & Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
