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 AAB1017F4E for ; Sun, 4 Jan 2015 12:14:18 +0000 (UTC) Received: (qmail 42267 invoked by uid 500); 4 Jan 2015 12:14:19 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 42211 invoked by uid 500); 4 Jan 2015 12:14:19 -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 42201 invoked by uid 99); 4 Jan 2015 12:14:19 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Jan 2015 12:14:19 +0000 Received: from mail-ob0-f177.google.com (mail-ob0-f177.google.com [209.85.214.177]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 1B3BB1A012A for ; Sun, 4 Jan 2015 12:14:18 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id va2so56736213obc.8 for ; Sun, 04 Jan 2015 04:14:18 -0800 (PST) X-Received: by 10.202.107.138 with SMTP id g132mr47040760oic.105.1420373658422; Sun, 04 Jan 2015 04:14:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.202.171.147 with HTTP; Sun, 4 Jan 2015 04:13:58 -0800 (PST) From: Imesh Gunaratne Date: Sun, 4 Jan 2015 17:43:58 +0530 Message-ID: Subject: [Discuss] Multi-Tenancy Support for Applications To: dev Content-Type: multipart/alternative; boundary=001a11416a125bd704050bd2831f --001a11416a125bd704050bd2831f Content-Type: text/plain; charset=UTF-8 Hi Devs, At present with service grouping functionality an application can have only one subscription. This subscription may include multiple subscribable information blocks for multiple cartridges. To support Multi-Tenant applications which may include Multi-Tenant cartridges we should be able to manage multiple subscriptions for each cartridge. Currently we do not have a concept of subscribing to applications. Shall we introduce a new artifact called Application Subscription and move subscribable information blocks from Application definition to it? Then the workflow may change as follows: - Add autoscaling policy - Add cartridges - Add groups - Add application - Deploy application - Subscribe to application: Thanks -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos --001a11416a125bd704050bd2831f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi Devs,

At present with service groupi= ng functionality an application can have only one subscription. This subscr= iption may include multiple subscribable information blocks for multiple ca= rtridges.

To support Multi-Tenant applications whi= ch may include Multi-Tenant cartridges we should be able to manage multiple= subscriptions for each cartridge. Currently we do not have a concept of su= bscribing to applications.=C2=A0

Shall we introduc= e a new artifact called Application Subscription and move subscribable info= rmation blocks from Application definition to it?

= Then the workflow may change as follows:

- Add autoscaling policy=

- Add cartridges

- Add groups

- Add applicat= ion

- Deploy application

- Subscribe to application:

Thanks

--
=

Imesh Gunaratne

Technical Lead, WSO2

Committer & PMC Mem= ber, Apache Stratos

--001a11416a125bd704050bd2831f--