Imesh, Thanks for bringing this up.
Few suggestions; 1. serviceId, domainName, name why we need those? IMO we just need serviceName. 2. service can have set of properties. 3. clusterId, domainName - IMO we just need clusterId which will be used to uniquely identify a service cluster. 4. CartridgeType == serviceName, hence I don't think we need it in the cluster model. 5. Again, cluster can have a set of properties. 6. In Port; /s/name/protocol 7. I don't think the life cycle of a Member is correct. A member would never subscribe/unsubscribe. Member cannot be in a Starting state, cause it is the member itself let Stratos know that it is started and then only we should add a Member to the model. Hence, IMO member's life cycle states would be Active, Suspended, Terminated. 8. I don't think the cardinality is correct in any of these. 1 --> n should be in all of them other than 'Member -> MemberStatus'. On Mon, Oct 14, 2013 at 5:32 PM, Imesh Gunaratne <[email protected]> wrote: > Hi, > > Please find the initial version of proposed Topology Domain Model below. I > have now added this model to org.apache.stratos.messaging component and > committed to git. > > [image: Inline image 2] > > I'm currently working on improving the model where clusters/members are > connected to different Clouds (IaaSs), Regions and Zones. Once it's done I > will send another update. > > Please feel free to add your thoughts. > > Thanks > Imesh > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
<<topology-domain-model1.png>>
