Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA65717537 for ; Mon, 16 Mar 2015 10:36:38 +0000 (UTC) Received: (qmail 45385 invoked by uid 500); 16 Mar 2015 10:36:38 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 45354 invoked by uid 500); 16 Mar 2015 10:36:38 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 45342 invoked by uid 99); 16 Mar 2015 10:36:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Mar 2015 10:36:38 +0000 Date: Mon, 16 Mar 2015 10:36:38 +0000 (UTC) From: =?utf-8?Q?Fl=C3=A1vio_Ferreira_=28JIRA=29?= To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KARAF-3609) Kubernetes/Cloud Service Discovery isn't working in Immutable applications MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-3609?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Fl=C3=A1vio Ferreira updated KARAF-3609: ----------------------------------- Description:=20 I=E2=80=99m using Karaf Cellar 3.0.1 using Hazelcast with network TCP-IP en= abled instead of Multicast. I=E2=80=99m trying to run immutable application= s (running inside Docker containers). To discover Hazelcast Instances in the cluster I=E2=80=99m using cellar-kub= ernetes feature. However, I tried to use cellar-cloud and the problem is th= e same. I belive that, as my applications are immutable and the karaf configuration= is never updated, the update in Managed Service Factories was never called= . Thus, the DiscoveryTask can=E2=80=99t find the Karaf Cellar instances in = the cluster since there are no Service Discovery Implementations registered= . In short, the update in this [class|https://github.com/apache/karaf-cellar/= blob/master/cloud/src/main/java/org/apache/karaf/cellar/cloud/BlobStoreDisc= overyServiceFactory.java] is never called. Therefore, this never happens: bq. newRegistration =3D bundleContext.registerService(DiscoveryService.clas= s.getName(), service, (Dictionary) serviceProperties); I have an exemple to test it, in my github, under this repository: [karaf-c= ellar-kubernetes-example|https://github.com/FlavioF/karaf-cellar-kubernetes= -example] I can=E2=80=99t understand if there is anything that I am missing or if thi= s is an issue in Service Discovery registry process. Is there anyone I can chat about this in IRC or any other real time chat? [~ppires] [~albertocsm] was: I=E2=80=99m using Karaf Cellar using Hazelcast with network TCP-IP enabled = instead of Multicast. I=E2=80=99m trying to run immutable applications (run= ning inside Docker containers). To discover Hazelcast Instances in the cluster I=E2=80=99m using cellar-kub= ernetes feature. However, I tried to use cellar-cloud and the problem is th= e same. I belive that, as my applications are immutable and the karaf configuration= is never updated, the update in Managed Service Factories was never called= . Thus, the DiscoveryTask can=E2=80=99t find the Karaf Cellar instances in = the cluster since there are no Service Discovery Implementations registered= . In short, the update in this [class|https://github.com/apache/karaf-cellar/= blob/master/cloud/src/main/java/org/apache/karaf/cellar/cloud/BlobStoreDisc= overyServiceFactory.java] is never called. Therefore, this never happens: bq. newRegistration =3D bundleContext.registerService(DiscoveryService.clas= s.getName(), service, (Dictionary) serviceProperties); I have an exemple to test it, in my github, under this repository: [karaf-c= ellar-kubernetes-example|https://github.com/FlavioF/karaf-cellar-kubernetes= -example] I can=E2=80=99t understand if there is anything that I am missing or if thi= s is an issue in Service Discovery registry process. Is there anyone I can chat about this in IRC or any other real time chat? [~ppires] [~albertocsm] > Kubernetes/Cloud Service Discovery isn't working in Immutable application= s > -------------------------------------------------------------------------= - > > Key: KARAF-3609 > URL: https://issues.apache.org/jira/browse/KARAF-3609 > Project: Karaf > Issue Type: Bug > Environment: Karaf Cellar > Reporter: Fl=C3=A1vio Ferreira > > I=E2=80=99m using Karaf Cellar 3.0.1 using Hazelcast with network TCP-IP = enabled instead of Multicast. I=E2=80=99m trying to run immutable applicati= ons (running inside Docker containers). > To discover Hazelcast Instances in the cluster I=E2=80=99m using cellar-k= ubernetes feature. However, I tried to use cellar-cloud and the problem is = the same. > I belive that, as my applications are immutable and the karaf configurati= on is never updated, the update in Managed Service Factories was never call= ed. Thus, the DiscoveryTask can=E2=80=99t find the Karaf Cellar instances i= n the cluster since there are no Service Discovery Implementations register= ed. > In short, the update in this [class|https://github.com/apache/karaf-cella= r/blob/master/cloud/src/main/java/org/apache/karaf/cellar/cloud/BlobStoreDi= scoveryServiceFactory.java] is never called. Therefore, this never happens: > bq. newRegistration =3D bundleContext.registerService(DiscoveryService.cl= ass.getName(), service, (Dictionary) serviceProperties); > I have an exemple to test it, in my github, under this repository: [karaf= -cellar-kubernetes-example|https://github.com/FlavioF/karaf-cellar-kubernet= es-example] > I can=E2=80=99t understand if there is anything that I am missing or if t= his is an issue in Service Discovery registry process. > Is there anyone I can chat about this in IRC or any other real time chat? > [~ppires] > [~albertocsm] -- This message was sent by Atlassian JIRA (v6.3.4#6332)