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 60871109FD for ; Wed, 9 Sep 2015 19:59:49 +0000 (UTC) Received: (qmail 28990 invoked by uid 500); 9 Sep 2015 19:59:49 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 28933 invoked by uid 500); 9 Sep 2015 19:59:49 -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 28914 invoked by uid 99); 9 Sep 2015 19:59:48 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 19:59:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 8878CC0184 for ; Wed, 9 Sep 2015 19:59:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.9 X-Spam-Level: *** X-Spam-Status: No, score=3.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, KAM_LIVE=1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=wso2.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id E0-BH--FmpPc for ; Wed, 9 Sep 2015 19:59:38 +0000 (UTC) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 16F9A42B13 for ; Wed, 9 Sep 2015 19:59:38 +0000 (UTC) Received: by lbcjc2 with SMTP id jc2so11982061lbc.0 for ; Wed, 09 Sep 2015 12:59:36 -0700 (PDT) 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 :content-type; bh=KNSRabcIOrb0atFkA7VMQYgZbsFLOGTvYpyu3zsR8YQ=; b=cwjEcBm5up8Bn/fkxEx13UDZi4vSw6yEyJc7KdI7BIw72K4SMFSWGaQfC2dEYS1g+R SBUd3X6wN1SlhJvdW9gz7p0j1YsCDmYGsI20Rau0FsUWWRrjHWto/Ipf9E0tEaJNviu2 JPNbb9nG6agiTjaYYjmKryiA0OSO/53dEaGR0= 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:content-type; bh=KNSRabcIOrb0atFkA7VMQYgZbsFLOGTvYpyu3zsR8YQ=; b=aq/pQ5vkmPPwgJHxmAAwqAK3Ga34z/dv0bpekVPfpeU2xQDAQRRbE5uT7s3GTyF4pm HJ/RK0Rzp+G/c+ExmhLGl9//9np0empIFvadhtB6gCImelfp8Wpq2IOP86Ookc+q6aMP 1Aqas8BPNpkZtX5PQZuR5bjvC4dmQuAkvVXoW+h+B6Cydcmdo8MrAbryqubUEhPSbz83 daF6wPs0HcoLAMrbOb89bQyzgoROqNvD8AgKY1q2E/YlXmVvAusv+8LQTxOkEpjy7I/s 9kd+dSTLhjiIr/1QeJu9kysQxxJJjC5VXcqL+cr6RNzMAWreyZeTuq0Aq3Rw2pLIXtZ2 E55Q== X-Gm-Message-State: ALoCoQmKsrQTO6+7MfpohB+wtZx2gZiGatIxR9ndFDOTiP0BKj0afgKAbRJnnFZw+jZM+00TvhPQ X-Received: by 10.152.43.198 with SMTP id y6mr30166948lal.41.1441828776570; Wed, 09 Sep 2015 12:59:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.28.165 with HTTP; Wed, 9 Sep 2015 12:59:17 -0700 (PDT) In-Reply-To: References: From: Akila Ravihansa Perera Date: Thu, 10 Sep 2015 01:29:17 +0530 Message-ID: Subject: Re: [Dev] Publishing Complete Topology event on Demand To: dev Content-Type: multipart/alternative; boundary=001a11c288900e12e0051f55ec7a --001a11c288900e12e0051f55ec7a Content-Type: text/plain; charset=UTF-8 Hi Imesh, Great thought. This will considerably speed up instance activation process. Shall we call the topic as 'initializer' to be generic? We can further extend this to Application hierarchy model initialization and tenant model initialization using the same topic. These are also published periodically by AS and SM respectively. Thanks. On Thu, Sep 10, 2015 at 1:09 AM, Imesh Gunaratne wrote: > Hi Devs, > > I would like to propose $subject. > > Currently we do this with a one minute interval and its causing the > cartridge agent and the servers to wait for around two minutes (in the > worst case) to start. In Docker this is a considerable amount of delay. > > I think we can implement $subject by introducing another topic (say > topology-init) and asking the clients to request Complete Topology event > via the new topic. This can be done in messaging component without > affecting the main modules (AS, CC, SM, CEP, JCA). PCA needs to be updated > accordingly. WDYT? > > Thanks > > -- > Imesh Gunaratne > > Senior Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com --001a11c288900e12e0051f55ec7a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Imesh,

Great thought. Thi= s will considerably speed up instance activation process.

Shall we call the topic as 'initializer' to be generic? We = can further extend this to Application hierarchy model initialization and t= enant model initialization using the same topic. These are also published p= eriodically by AS and SM respectively.

Thanks.

On Thu, S= ep 10, 2015 at 1:09 AM, Imesh Gunaratne <imesh@apache.org> wr= ote:
Hi Devs,

I would like to propose $subject.=C2=A0

C= urrently we do this with a one minute interval and its causing the cartridg= e agent and the servers to wait for around two minutes (in the worst case) = to start. In Docker this is a considerable amount of delay.

<= /div>
I think we can implement $subject by introducing another topic (s= ay topology-init) and asking the clients to request Complete Topology event= via the new topic. This can be done in messaging component without affecti= ng the main modules (AS, CC, SM, CEP, JCA). PCA needs to be updated accordi= ngly. WDYT?

Thanks

--
Imesh Gunaratne

Senio= r Technical Lead, WSO2
Committer & PM= C Member, Apache Stratos



--
Akila Ravi= hansa Perera
WSO2 Inc.;=C2=A0=C2=A0http:= //wso2.com/

Blog: http://ravihansa3000.blogspot.com
--001a11c288900e12e0051f55ec7a--