[ 
https://issues.apache.org/jira/browse/STRATOS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Imesh Gunaratne updated STRATOS-98:
-----------------------------------

    Description: 
In Stratos, topology defines the services, clouds (IaaS), regions, clusters, 
tenants and many other information about application deployment. A common 
domain model is needed to manage this data structure to be used by any given 
load balancer or any other Stratos module which requires topology information.

The proposal is to design this data structure as follows:
Topology - (1:M) -> Service - (1:M) -> Cluster - (1:M) -> Member

  was:
In Stratos, topology defines the services, clouds (IaaS), regions, clusters, 
tenants and many other information about application deployment. A common 
domain model is needed to manage this data structure to be used by any given 
load balancer or any other Stratos module which requires topology information.

The proposal is to design this data structure as follows:
Topology - (1:M) -> Service - (1:M) -> Cloud - (1:M) -> Region - (1:M) -> 
Cluster - (1:M) -> Member


> Implement a Domain Model for managing the Topology Data Structure
> -----------------------------------------------------------------
>
>                 Key: STRATOS-98
>                 URL: https://issues.apache.org/jira/browse/STRATOS-98
>             Project: Stratos
>          Issue Type: Sub-task
>            Reporter: Imesh Gunaratne
>            Assignee: Imesh Gunaratne
>             Fix For: 4.0.0
>
>
> In Stratos, topology defines the services, clouds (IaaS), regions, clusters, 
> tenants and many other information about application deployment. A common 
> domain model is needed to manage this data structure to be used by any given 
> load balancer or any other Stratos module which requires topology information.
> The proposal is to design this data structure as follows:
> Topology - (1:M) -> Service - (1:M) -> Cluster - (1:M) -> Member



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to