stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pradeep Fernando <pradee...@gmail.com>
Subject Re: Removing the persistence of data in registry from the Cloud Controller
Date Wed, 06 Nov 2013 03:41:33 GMT
Hi Nirmal,

Why we want to persist in two locations ? (both registry and file-system)


--Pradeep


On Wed, Nov 6, 2013 at 9:07 AM, Nirmal Fernando <nirmal070125@gmail.com>wrote:

>
>
>
> On Wed, Nov 6, 2013 at 8:53 AM, Pradeep Fernando <pradeepfn@gmail.com>wrote:
>
>> Hi,
>>
>> if we are persisting. Then why not registry ?
>>
>
> Yes, we should persist in registry. Earlier we have persisted both in the
> file system and registry. May be we should do the same?
>
>
>>  or else are we re-using some FileSystem based persistor available in
>> Carbon ? ...
>>
>> thanks,
>> --Pradeep
>>
>>
>> On Tue, Nov 5, 2013 at 5:16 PM, Reka Thirunavukkarasu <reka@wso2.com>wrote:
>>
>>> Yah..We persist the whole topology in the file system in CC in order to
>>> recover from a restart.
>>>
>>> Thanks,
>>> Reka
>>>
>>>
>>> On Tue, Nov 5, 2013 at 5:06 PM, Nirmal Fernando <nirmal070125@gmail.com>wrote:
>>>
>>>> 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 <reka@wso2.com>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/
>>>>
>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Pradeep Fernando.
>> http://pradeepfernando.blogspot.com/
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>



-- 
Pradeep Fernando.
http://pradeepfernando.blogspot.com/

Mime
View raw message