On Tuesday, January 27, 2015 at 6:39:00 PM UTC, Lvc@ wrote:
>
> Hi Paulo,
> I think this is SUPER interesting. To be honest, I didn't know Kubernetes 
> before, it would be wonderful if this was supported by Amazon and other 
> Cloud providers natively.
>

Currently, it's deployed on GKE (Google Containers Engine on top of Compute 
Engine), Azure and others. You can deploy it in AWS, but you still need to 
provision the VMs - which is rather easy actually. I've contributed some 
stuff on getting Kubernetes running on top of CoreOS (and CoreOS on top of 
AWS & GCE).
 

>
> So I'm definitely interested on it.
>

Sad that Hazelcast just ignored my PR that would bring support for multiple 
IaaS (as many as supported by jclouds), so I'm not really interested in 
contributing with it or the Kubernetes part. But I'm willing to find a way 
with you guys to have all this working for OrientDB.
 

>
> Question: do you know if OpenStack supports it in any way?
>

Since OpenStack is simply IaaS, yes it should be easily supported. Quick 
search proves it is 
https://developer.rackspace.com/blog/running-coreos-and-kubernetes/
 

>
> Lvc@
>
>
> On 27 January 2015 at 19:30, Paulo Pires <[email protected] <javascript:>> 
> wrote:
>
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
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.

Reply via email to