Hi Luca,
Discovery comes from cloud and we extended later to kubernetes. It makes
sense to extend the API to support domains/filters.
As it could be backward compatible, it's something that we can include
in next minor release.
Can you create a Jira about that, I will do it ?
Thanks,
Regards
JB
On 12/30/2015 01:53 PM, lb wrote:
Hi all,
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.
What do you think ?
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
