Hi all, Since OrientDB uses Hazelcast as default cluster manager, I'm reaching you to see if you're interested in testing my approach at scaling Hazelcast on Kubernetes.
I've had experience with clustering Hazelcast in Google Cloud Engine before (https://github.com/hazelcast/hazelcast/pull/2313), but right now, in the advent of containers, Kubernetes (http://kubernetes.io) is becoming the standard for app/container orchestration, which kinda deprecates my previous effort - unless you're using VMs in cloud ;-) So, I've assembled a Dockerfile which will run a small app (hazelcast-kubernetes-bootstrapper) on boot. This app discovers all nodes in the Kubernetes cluster that are acting as Hazelcast nodes (based on labels), retrieve their IP addresses, configure and instantiate Hazelcast with TCP configuration, accordingly. A similar approach can work for OrientDB, but right now OrientDB supports loading Hazelcast config from the XML config alone. And since Hazelcast just doesn't seem to care about the community trying to contribute with said discovery mechanisms, would it be possible to add support for it in OrientDB code? I'm willing to help :-) Btw, in case you're wondering about the Hazelcast on Kubernetes thing: https://github.com/pires/hazelcast-kubernetes https://github.com/pires/hazelcast-kubernetes-bootstrapper Cheers, Paulo Pires -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
