Hi,

Thanks for the quick feedback!

On Thu, Jul 23, 2015 at 8:00 AM, Sameera Jayasoma <[email protected]> wrote:
>
>
> From Hazelcast 3.6 release, they are introducing a new Hazelcast discovery
> API. This will allow us to plug different membership schemes easily. Imesh,
> Can you create a Jira in the Carbon product 4.5 version?
>
>>
>> Great! Nice to hear this! Here [1] I can see that they have mentioned
about this feature.

Yes for sure, I will create a JIRA for this. Just to clarify the approach,
for existing Carbon products shall we go with this approach and introduce a
new Membership Scheme together with the Membership Scheme extension model
and later when we move to Hazelcast 3.6 try to use the new Hazelcast
Discovery API?

On Thu, Jul 23, 2015 at 8:55 AM, Afkham Azeez <[email protected]> wrote:

> The Hazelcast community is also working on implementing a Kubernetes based
> discovery implementation.
>

Thanks Azeez! Yes Pires has written a Hazelcast Discovery feature for
Kubernetes and it can be found here [2], [3].

On Thu, Jul 23, 2015 at 10:14 AM, Akila Ravihansa Perera <[email protected]
> wrote:

> Hi Imesh,
>
> Is there a repo for Carbon kernel extension point implementation? I would
> like to contribute :)
>
> https://github.com/imesh/carbon4-kernel


> I think we can push this feature to a P2 repo and install it when we are
> building the product (for eg: Stratos) distribution. That would be cleaner
> than copying the jar to dropins.
>

Yes, it would be better to package the Stratos Membership Scheme bundle in
each carbon product.

[1] http://www.slideshare.net/Hazelcast/hazelcast-36-roadmap-preview
[2] https://github.com/pires/hazelcast-kubernetes
[3] https://github.com/pires/hazelcast-kubernetes-bootstrapper

Thanks

-- 
*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
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to