You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Isuru Haththotuwa <is...@apache.org> on 2014/09/07 20:38:02 UTC
[Discuss] Initial Topology Changes for Composite Application Support
(Service Grouping)
This is to discuss $subject.
I have attached the class diagram which shows the proposed Topology changes
for Composite App support. Please note that this design is not finalized
yet, might need to tweak this a bit as we go on.
I have only shown the Composite App related Topology related changes here.
The basic idea is as follows:
- Topology will contain Applications, identified by a unique application
id (specified in the Application Definition)
- The Application can contain any number of Groups (set of Services
and/or Groups) and/or Clusters.
- The Groups correspond to a particular Group Definition that has been
deployed before.
- Applications and Groups might have a Dependency Order; a set of
Startup Orders and a Kill Behavior which corresponds to the order that
services in the particular App/Group is started and how to handle
dependency termination.
--
Thanks and Regards,
Isuru H.
+94 716 358 048* <http://wso2.com/>*
* <http://wso2.com/>*
Re: [Discuss] Initial Topology Changes for Composite Application
Support (Service Grouping)
Posted by Isuru Haththotuwa <is...@apache.org>.
Hi Lahiru,
Sorry for the late response.
On Tue, Sep 9, 2014 at 3:11 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi Isuru,
>
> Regarding the services,
>
> It should have relationship as follows, right?
>
> Topology 1: 0..n Services
> Group 1: 1..n Services
>
Did you mean a Service Cluster? The Topology can have zero or more
Applications, and for each Application,
Application 1: 0..n Group
Application 1: 0..n Cluster
Group 1: 0..n Group (nested Groups)
Group 1: 0..n Cluster
Basically, an Application can have zero or more of Groups and Clusters. A
Group itself can have zero or more of Groups (nested Groups), and a Group
can have zero or more Clusters as well.
>
>
> On Mon, Sep 8, 2014 at 12:08 AM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>>
>> This is to discuss $subject.
>>
>> I have attached the class diagram which shows the proposed Topology
>> changes for Composite App support. Please note that this design is not
>> finalized yet, might need to tweak this a bit as we go on.
>>
>>
>>
>>
>> I have only shown the Composite App related Topology related changes
>> here. The basic idea is as follows:
>>
>> - Topology will contain Applications, identified by a unique
>> application id (specified in the Application Definition)
>> - The Application can contain any number of Groups (set of Services
>> and/or Groups) and/or Clusters.
>> - The Groups correspond to a particular Group Definition that has
>> been deployed before.
>> - Applications and Groups might have a Dependency Order; a set of
>> Startup Orders and a Kill Behavior which corresponds to the order that
>> services in the particular App/Group is started and how to handle
>> dependency termination.
>>
>> Can services take part in dependency order too?
>
> Thanks.
>
>>
>> -
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>> * <http://wso2.com/>*
>>
>>
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
> --
> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
> Thanks and Regards,
>
> Isuru H.
> <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>
> +94 716 358 048 <http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146>*
> <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: [Discuss] Initial Topology Changes for Composite Application
Support (Service Grouping)
Posted by Lahiru Sandaruwan <la...@wso2.com>.
Hi Isuru,
Regarding the services,
It should have relationship as follows, right?
Topology 1: 0..n Services
Group 1: 1..n Services
On Mon, Sep 8, 2014 at 12:08 AM, Isuru Haththotuwa <is...@apache.org>
wrote:
>
> This is to discuss $subject.
>
> I have attached the class diagram which shows the proposed Topology
> changes for Composite App support. Please note that this design is not
> finalized yet, might need to tweak this a bit as we go on.
>
>
>
>
> I have only shown the Composite App related Topology related changes here.
> The basic idea is as follows:
>
> - Topology will contain Applications, identified by a unique
> application id (specified in the Application Definition)
> - The Application can contain any number of Groups (set of Services
> and/or Groups) and/or Clusters.
> - The Groups correspond to a particular Group Definition that has been
> deployed before.
> - Applications and Groups might have a Dependency Order; a set of
> Startup Orders and a Kill Behavior which corresponds to the order that
> services in the particular App/Group is started and how to handle
> dependency termination.
>
> Can services take part in dependency order too?
Thanks.
>
> -
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146