Return-Path: X-Original-To: apmail-stratos-dev-archive@minotaur.apache.org Delivered-To: apmail-stratos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9FC0110E3E for ; Wed, 3 Dec 2014 10:43:55 +0000 (UTC) Received: (qmail 5240 invoked by uid 500); 3 Dec 2014 10:22:42 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 86984 invoked by uid 500); 3 Dec 2014 10:22:29 -0000 Mailing-List: contact dev-help@stratos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stratos.apache.org Delivered-To: mailing list dev@stratos.apache.org Received: (qmail 68289 invoked by uid 99); 3 Dec 2014 09:00:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Dec 2014 09:00:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_FILL_THIS_FORM_SHORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of reka@wso2.com designates 209.85.216.45 as permitted sender) Received: from [209.85.216.45] (HELO mail-qa0-f45.google.com) (209.85.216.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Dec 2014 09:00:26 +0000 Received: by mail-qa0-f45.google.com with SMTP id x12so10086760qac.18 for ; Wed, 03 Dec 2014 01:00:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ngWQRpS/9sRJmwpSXcfNdxpaGSYdithAymaEjJMdaZQ=; b=XnBWJlKoPTuwLEJ+BNYDhSidhtWaNKWB85XIaMKIZOys+Pbyc9ot17BXUMBPBGH175 jyRovkbvcVOomprdPe55LLVZ8yQsQ+vVIOuaEFhcnDrN0gZ6tycPl87EMCqedDMkVcC8 TjbcYLpnEfFkRcB3QYnfhC3AlSL9ehMJJ97fs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=ngWQRpS/9sRJmwpSXcfNdxpaGSYdithAymaEjJMdaZQ=; b=jwDEpdSwksMCpTs9CSBeMdxKqm8OYci+5DqnHCtgWfcKhfkey9AezXsobC1TpBvxAo l1+zUtjAGWtutR1otf4IfRpwmCyyKnjtUF0oMEJmtr7nEeo6cpSpUdi3RWtB+tPAfyIV TvDm6BEKLTwahTUQZqeAoJOjlA/PDPqJ6jLekN/CKMNxdTUipMmWqaH0PQTPqelwDK9L vW37WZHg5qos84fMS9+dnZ3R1q2HEy5M7ynWB4tP9oe2OkzqPrU/Dgzdh/NVdpQ3bPsP jfDnAYCtYxd5avVevR8B2EhQC7F78vs17gXEhN8XOL4+VzG2igRYP+Y4gV6jh8sK+wQp Q+Zw== X-Gm-Message-State: ALoCoQl0WphHM2kBcb5BJQEbLR11pOoah/8Qr4DyqpJqcPMEE5AgA02tCwyQ+AoJ9/ZVtILHjcQT X-Received: by 10.140.107.37 with SMTP id g34mr6249083qgf.38.1417597225258; Wed, 03 Dec 2014 01:00:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.179.7 with HTTP; Wed, 3 Dec 2014 01:00:05 -0800 (PST) In-Reply-To: References: From: Reka Thirunavukkarasu Date: Wed, 3 Dec 2014 14:30:05 +0530 Message-ID: Subject: Re: Undeployment of Application or Application Deployment Policy To: Lakmal Warusawithana Cc: Nirmal Fernando , dev , Lahiru Sandaruwan , Isuru Haththotuwa Content-Type: multipart/alternative; boundary=001a113a19260be6e605094c1346 X-Virus-Checked: Checked by ClamAV on apache.org --001a113a19260be6e605094c1346 Content-Type: text/plain; charset=UTF-8 Hi On Wed, Dec 3, 2014 at 2:27 PM, Lakmal Warusawithana wrote: > > > On Wed, Dec 3, 2014 at 2:24 PM, Lakmal Warusawithana > wrote: > >> >> >> On Wed, Dec 3, 2014 at 2:23 PM, Reka Thirunavukkarasu >> wrote: >> >>> Hi >>> >>> On Wed, Dec 3, 2014 at 2:19 PM, Lakmal Warusawithana >>> wrote: >>> >>>> >>>> >>>> On Wed, Dec 3, 2014 at 2:18 PM, Nirmal Fernando >>>> wrote: >>>> >>>>> Hi Lakmal, >>>>> >>>>> >>>>> On Wed, Dec 3, 2014 at 2:14 PM, Lakmal Warusawithana >>>>> wrote: >>>>> >>>>>> I think we need to understand terminology correctly. >>>>>> >>>>>> - Application create - create application json >>>>>> >>>>>> If the >>>>> >>>>>> >>>>>> - deployment policy - deployment pattens of the application >>>>>> >>>>>> shouldn't we remove the deployment policy, once the application >>>>> undeployed ? >>>>> >>>> +1 >>>> >>> >>> We are removing the deployment policy once the application is >>> underplayed. >>> >>> Another thing is that, can the users be able to remove the created >>> application at some point? >>> >> >> Yes, IMO. >> > > Shall we have another action > > - application delete. -which will delete application > > application un deploy only remove deployment policy? wdyt ? > +1. sure. I already implemented like that..Will update REST EP with the correct terminology. Thanks, Reka > > > >> >> >>> >>> Thanks, >>> Reka >>> >>>> >>>> >>>>> >>>>>> - application deploy - combine application json+deployment >>>>>> policy. - this is the time we are actually spin instances/containers. >>>>>> - application un deploy - remove all instances/containers/monitors >>>>>> >>>>>> Are we clear now? >>>>>> >>>>>> >>>>>> On Wed, Dec 3, 2014 at 10:48 AM, Reka Thirunavukkarasu >>>>> > wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> As from earlier model, we were wiping out the monitors when we >>>>>>> undeploy the application. But we are currently starting the monitors when >>>>>>> we deploy the deployment policy. So, when undeploying the policy only, we >>>>>>> will have to wipe out all the clusters and the monitors. In that case, the >>>>>>> flow for the undeployment of the policy will be as below: >>>>>>> >>>>>>> Undeployment of policy >>>>>>> ------------------------------ >>>>>>> >>>>>>> - Update the application monitor with the flag saying >>>>>>> terminating=true >>>>>>> - All Application instances will get updated as state = terminating >>>>>>> - Underlying groups instances and cluster instances will be updated >>>>>>> as state = terminating by the parent notification >>>>>>> - Upon cluster instance terminating event, all the members will get >>>>>>> to wiped out in the cluster instance >>>>>>> - Cluster Instance will get to Terminated once all the members are >>>>>>> wiped out >>>>>>> - Once all the clusters instances are wiped out, cluster monitor >>>>>>> will get wiped out >>>>>>> - Upon cluster Instance terminated, group instance and then >>>>>>> application instance will be terminated >>>>>>> - Once all the application instances are wiped out, app monitor will >>>>>>> get to removed and send application Terminated event. >>>>>>> - Call CC to remove all the clusters related to application in >>>>>>> Topology >>>>>>> - Autosclaer will remove the in-memory clusters upon Topology >>>>>>> ClustersRemovedEvent >>>>>>> >>>>>>> Please share your concerns whether we can go ahead with this flow. >>>>>>> >>>>>>> Thanks, >>>>>>> Reka >>>>>>> >>>>>>> -- >>>>>>> Reka Thirunavukkarasu >>>>>>> Senior Software Engineer, >>>>>>> WSO2, Inc.:http://wso2.com, >>>>>>> Mobile: +94776442007 >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Lakmal Warusawithana >>>>>> Vice President, Apache Stratos >>>>>> Director - Cloud Architecture; WSO2 Inc. >>>>>> Mobile : +94714289692 >>>>>> Blog : http://lakmalsview.blogspot.com/ >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Thanks & regards, >>>>> Nirmal >>>>> >>>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc. >>>>> Mobile: +94715779733 >>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Lakmal Warusawithana >>>> Vice President, Apache Stratos >>>> Director - Cloud Architecture; WSO2 Inc. >>>> Mobile : +94714289692 >>>> Blog : http://lakmalsview.blogspot.com/ >>>> >>>> >>> >>> >>> -- >>> Reka Thirunavukkarasu >>> Senior Software Engineer, >>> WSO2, Inc.:http://wso2.com, >>> Mobile: +94776442007 >>> >>> >>> >> >> >> -- >> Lakmal Warusawithana >> Vice President, Apache Stratos >> Director - Cloud Architecture; WSO2 Inc. >> Mobile : +94714289692 >> Blog : http://lakmalsview.blogspot.com/ >> >> > > > -- > Lakmal Warusawithana > Vice President, Apache Stratos > Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > -- Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007 --001a113a19260be6e605094c1346 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi

On Wed, Dec 3, 2014 at 2:27 PM, Lakmal Warusawithana &l= t;lakmal@wso2.com&= gt; wrote:


On= Wed, Dec 3, 2014 at 2:24 PM, Lakmal Warusawithana <lakmal@wso2.com><= /span> wrote:


On Wed, Dec 3, 20= 14 at 2:23 PM, Reka Thirunavukkarasu <reka@wso2.com> wrote:
<= /span>
Hi

On Wed, Dec 3, 2014 at 2= :19 PM, Lakmal Warusawithana <lakmal@wso2.com> wrote:

<= br>
On Wed, Dec 3, 2014 at 2:18 PM, Nirmal = Fernando <nirmal@wso2.com> wrote:
Hi Lakmal,

=
On Wed, Dec 3, 2014 at 2:14 PM, Lakmal= Warusawithana <lakmal@wso2.com> wrote:
I think we need to understand ter= minology correctly.=C2=A0
  • Application create - create applicati= on json
If the =C2=A0
  • deployment= policy - deployment pattens of the application
shouldn't we remove the deployment policy, once the = application undeployed ?=C2=A0
<= div>+1

We ar= e removing the deployment policy once the application is underplayed.
=

Another thing is that, can the users be able to remove = the created application at some point?

Yes, IMO.

Shall we have another action
  • app= lication delete. -which will delete application
application u= n deploy only remove deployment policy? wdyt ?

+1. sure.=C2=A0 I already implemented lik= e that..Will update REST EP with the correct terminology.

Thanks,
Reka

=C2=A0
<= div dir=3D"ltr">
=
=C2=A0

Thanks= ,
Reka
= =C2=A0
  • application deploy - combine application= json+deployment policy. - this is the time we are actually spin instances/= containers.
  • application un deploy - remove all instances/containers= /monitors
Are we clear now?=C2=A0


On Wed, Dec 3= , 2014 at 10:48 AM, Reka Thirunavukkarasu <reka@wso2.com> wrote:=
Hi All= ,

As from earlier model, we were wiping out the monitors= when we undeploy the application. But we are currently starting the monito= rs when we deploy the deployment policy. So, when undeploying the policy on= ly, we will have to wipe out all the clusters and the monitors. In that cas= e, the flow for the undeployment of the policy will be as below:
=
Undeployment of policy
---------------------------= ---

- Update the application monitor with the flag= saying terminating=3Dtrue
- All Application instances will get u= pdated as state =3D terminating
- Underlying groups instances and= cluster instances will be updated as state =3D terminating by the parent n= otification
- Upon cluster instance terminating event, all the me= mbers will get to wiped out in the cluster instance
- Cluster Ins= tance will get to Terminated once all the members are wiped out
-= Once all the clusters instances are wiped out, cluster monitor will get wi= ped out
- Upon cluster Instance terminated, group instance and th= en application instance will be terminated
- Once all the applica= tion instances are wiped out, app monitor will get to removed and send appl= ication Terminated event.
- Call CC to remove all the clusters re= lated to application in Topology
- Autosclaer will remove the in-= memory clusters upon Topology ClustersRemovedEvent

Please share your concerns whether we can go ahead with this flow.

Thanks,
Reka

--
Reka Thirunavukkaras= u
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007





--
Lakmal WarusawithanaVice President, Apache Stratos
Director - Cloud Architecture; WS= O2 Inc.
Mobile : +94714289692



--

Thanks & regar= ds,
Nirmal

Senior Software Engineer- Platform Technologies Team, = WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/





--
Lakmal Warusawithana
Vice President, Ap= ache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mob= ile : +94714289692



--
Reka Thirunavukkarasu
Senior Softwa= re Engineer,
WSO2, Inc.:ht= tp://wso2.com,
Mobile: +94776442007





--
Lakmal Warusawithana
Vice President, Ap= ache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mob= ile : +94714289692



--
Lakmal Warusawithana
Vice = President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.<= /div>
Mobile : +94714289692



--
Reka Thirunavukkarasu
Senior = Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007


--001a113a19260be6e605094c1346--