You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Luca Burgazzoli (JIRA)" <ji...@apache.org> on 2015/12/30 22:19:49 UTC

[jira] [Created] (KARAF-4245) Generic discovery service

Luca Burgazzoli created KARAF-4245:
--------------------------------------

             Summary: Generic discovery service
                 Key: KARAF-4245
                 URL: https://issues.apache.org/jira/browse/KARAF-4245
             Project: Karaf
          Issue Type: New Feature
          Components: cellar-cloud
            Reporter: Luca Burgazzoli


I'm wondering if it would make sense to extend current discovery service to make it more generic and shareable among other services that need discovery capabilities. 

This may be achieved by adding some filtering capability to discoverMembers i.e. 

Collection<DiscoveredMember> discoverMembers(String domain)

How domain is used is implementation dependant (labels for kubernetes, path for etcd, etc). Domain used by karaf clustering may be then defined in hazelcast's service configuration file or wherever it make sense.

It would also be useful to have additional info about the discovery services like all the kubernetes label or any additional attribute associated with the discovered service.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)