Great work Isuru & Vishanth!!
On Wed, Feb 3, 2016 at 4:31 PM, Vishanth Balasubramaniam <[email protected]
> wrote:
> Hi Isuru,
>
> With those changes in the Kubernetes Membership Scheme, now the
> worker/manager separation is working fine. I have tested this with WSO2 AS.
>
> In the log now I am able to see the manager is being elected as a
> coordinator node.
>
> TID: [-1234] [] [2016-02-03 08:16:09,373] INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>> Local member: [cf010018-3cf6-4a44-8f6a-5b72043017e2] - Host:10.244.86.4,
>> Remote Host:null, Port: 4000, HTTP:9763, HTTPS:9443, Domain:
>> wso2.carbon.domain, Sub-domain:mgt, Active:true
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>> TID: [-1234] [] [2016-02-03 08:16:09,457] INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>> Elected this member [cf010018-3cf6-4a44-8f6a-5b72043017e2] as the
>> Coordinator node
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>> TID: [-1234] [] [2016-02-03 08:16:09,564] INFO
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>> Cluster initialization completed
>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>
>
> Regards,
> Vishanth
>
> On Wed, Feb 3, 2016 at 7:50 AM, Isuru Haththotuwa <[email protected]> wrote:
>
>>
>>
>> On Tue, Feb 2, 2016 at 10:47 PM, Imesh Gunaratne <[email protected]> wrote:
>>
>>>
>>>
>>> On Wed, Feb 3, 2016 at 1:13 AM, Isuru Haththotuwa <[email protected]>
>>> wrote:
>>>
>>>>
>>>> AFAIK this is the correct way. If we start the manager first, there is
>>>> no worker pod at that moment. So the manager can start on its own. When the
>>>> worker pod is being created, it can add both manager and worker services'
>>>> IPs and connect to the manager node.
>>>>
>>>
>>> No Isuru, this is the list of services [1] given to each Carbon server
>>> instance to query Pods. So ideally it should have both worker service and
>>> manager service.
>>>
>> Thanks Imesh. I was of the idea that we should add individual pod IPs.
>>
>>>
>>> [1]
>>> https://github.com/wso2/kubernetes-artifacts/blob/master/common/kubernetes-membership-scheme/src/main/java/org/wso2/carbon/membership/scheme/kubernetes/KubernetesMembershipScheme.java#L141
>>>
>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, Feb 3, 2016 at 12:19 AM, Vishanth Balasubramaniam <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have been working on WSO2 AS worker/manager separated cluster in
>>>>>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>>>>>> CoreOs [1].
>>>>>> I built the docker images for manager and worker with the following
>>>>>> Kubernetes membership scheme configurations in the profile.
>>>>>>
>>>>>> wso2::clustering :
>>>>>>> enabled : true
>>>>>>> local_member_host : local.as.wso2.com
>>>>>>> local_member_port : 4000
>>>>>>> membership_scheme : kubernetes
>>>>>>> k8 :
>>>>>>> k8_master : http://172.17.8.101:8080
>>>>>>> k8_namespace : default
>>>>>>> k8_services : wso2as-manager,wso2as-worker
>>>>>>> subDomain : mgt
>>>>>>
>>>>>>
>>>>>> wso2::clustering :
>>>>>>> enabled : true
>>>>>>> local_member_host : worker.as.wso2.com
>>>>>>> local_member_port : 4000
>>>>>>> membership_scheme : kubernetes
>>>>>>> k8 :
>>>>>>> k8_master : http://172.17.8.101:8080
>>>>>>> k8_namespace : default
>>>>>>> k8_services : wso2as-manager,wso2as-worker
>>>>>>> subDomain : worker
>>>>>>
>>>>>>
>>>>>> I SCP-ed the saved zip file of built images and loaded them in the
>>>>>> Kubernetes minion. Then I deployed the worker/manager service and
>>>>>> controller. I SSH-ed into the container where the manager node is
>>>>>> running,
>>>>>> and there are no error logs as you can see below.
>>>>>>
>>>>>> TID: [-1234] [] [2016-02-02 12:43:53,892] INFO
>>>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>>>>>> Using kubernetes based membership management scheme
>>>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>>>>>>> TID: [-1234] [] [2016-02-02 12:43:53,905] INFO
>>>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>>>>>> - Initializing kubernetes membership scheme...
>>>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>>>>>> TID: [-1234] [] [2016-02-02 12:43:53,909] INFO
>>>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>>>>>> - Kubernetes clustering configuration: [master]
>>>>>>> http://172.17.8.101:8080 [namespace] default [services]
>>>>>>> wso2as-manager
>>>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>>>>>> TID: [-1234] [] [2016-02-02 12:43:54,499] INFO
>>>>>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console
>>>>>>> URL
>>>>>>> : https://10.244.78.4:9443/carbon/
>>>>>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>>>>>
>>>>>>
>>>>>> But it doesn't become the cluster coordinator node and there is no
>>>>>> any other log after this. Also I am not able to access the carbon
>>>>>> management console from my local machine.
>>>>>>
>>>>>> But whereas, when I deploy only the default profile (not cluster),
>>>>>> then it runs fine and I am able to access the carbon management console
>>>>>> from my local machine with the provided nodeport.
>>>>>>
>>>>>> Have I misconfigured anything in worker/manager cluster setup?
>>>>>>
>>>>>> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>>>>>>
>>>>>> Regards,
>>>>>> Vishanth
>>>>>>
>>>>>> --
>>>>>> *Vishanth Balasubramaniam*
>>>>>> Committer & PMC Member, Apache Stratos,
>>>>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>>>>>
>>>>>> mobile: *+94 77 17 377 18*
>>>>>> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Imesh Gunaratne*
>>>>> Senior Technical Lead
>>>>> WSO2 Inc: http://wso2.com
>>>>> T: +94 11 214 5345 M: +94 77 374 2057
>>>>> W: http://imesh.gunaratne.org
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> [email protected]
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>
--
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
