+1 to use cluster instance id. It makes more sense..
Thanks,
Reka
On Sun, Dec 21, 2014 at 3:11 AM, Imesh Gunaratne <im...@apache.org> wrote:
> May be we could call this property "clusterInstanceId" because it will
> always get the cluster instance id value:
>
> MemberContext/Member {
> serviceName // Service name
> clusterId // Cluster id
> clusterInstanceId // Cluster instance id
> memberId // Cloud controller generated member id
> instanceId // IaaS generated instance id
> }
>
> On Sun, Dec 21, 2014 at 12:14 AM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
>> Hi Devs,
>>
>> It seems like we have reused the existing Instance Id property in Member
>> Context for defining the Application Hierarchy Instance Id.
>>
>> In cloud controller MemberContext.InstanceId was used earlier to store a
>> unique id based on the node id returned from jclouds. Now there seems to be
>> a conflict here.
>>
>> Shall we introduce a new property to store the Application Hierarchy
>> Instance Id in MemberContext/Member called "hierarchyInstanceId"?
>>
>> MemberContext/Member {
>> serviceName // Service name
>> clusterId // Cluster id
>> memberId // Cloud controller generated id
>> instanceId // IaaS generated id
>> hierarchyInstanceId // Instance id of the hierarchy that member
>> belongs to
>> }
>>
>> Thanks
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
