Hi Reka, CC is the one who builds the topology after extracting information from other components right? So, CC should definitely persist the full topology information in a registry, so that Startos can recover from a restart of CC, IMO.
On Tue, Nov 5, 2013 at 4:52 PM, Reka Thirunavukkarasu <[email protected]> wrote: > Hi > > Can we go ahead with the subject? Since we have introduced the Topology > with all sort of information which is relevant to Cloud Controller, I hope > that we can remove the data persistence in registry from the Cloud > Controller. > > From the Topology, now we can access the node related information such > state, member Id and Node Id. If we need more information on a particular > Node, then we can get it via the jcloud at any point, if we have the nodeId > with us. Please see the below for more information from the Member in the > Topology: > > Member { > > private String serviceName; > private String clusterId; > private String memberId; > private MemberStatus status; > private float loadAverage; > private float memoryConsumption; > private String memberIp; > private Map<String, Port> portMap; > private Properties properties; > private String iaasNodeId; > > ......... > } > > Also, we can refactor the Data publish to publish all the state changes of > the Topology for a particular member. > > Please provide your feedback on this and also correct me, if i missed any > important points here? > > Thanks, > Reka > > > -- > Reka Thirunavukkarasu > Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
