Thursday, 18 August 2016

Running Infinispan cluster on Kubernetes

In the previous post we looked how to run Infinispan on OpenShift. Today, our goal is exactly the same, but we'll focus on Kubernetes.

Running Infinispan on Kubernetes requires using proper discovery protocol. This blog post uses Kubernetes Ping but it's also possible to use Gossip Router.

Our goal

We'd like to build Infinispan cluster based on Kubernetes hosted locally (using Minikube). We will expose a service and route it to our local machine. Finally, we will use it to put data into the grid.




Spinning local Kubernetes cluster

There are many ways to spin up a local Kubernetes cluster. One of my favorites is Minikube. At first you will need the 'minikube' binary, which can be downloaded from Github releases page. I usually copy it into '/usr/bin' which makes it very convenient to use. The next step is to download 'kubectl' binary. I usually use Kubernetes Github releases page for this. The 'kubectl' binary is stored inside the release archive under 'kubernetes/platforms/<your_platform>/<your_architecture>/kubectl'. I'm using linux/amd64 since I'm running Fedora F23. I also copy the binary to '/usr/bin'.

We are ready to spin up Kubernetes:


Deploying Infinispan cluster

This time we'll focus on automation, so there will be no 'kubectl edit' commands. Below is the yaml file for creating all necessary components in Kubernetes cluster:

  • (lines 28 - 30) - We added additional arguments to the bootstrap scipt
  • (lines 31 - 36) - We used Downward API for pass the current namespace to the Infinispan
  • (lines 41 - 52) - We defined all ports used by the Pod
  • (lines 60 - 78) - We created a service for port 8080 (the REST interface)
  • (line 76) - We used NodePort service type which we will expose via Minikube in the next paragraph

Save it somewhere on the disk and execute 'kubectl create' command:


Exposing the service port

One of the Minikube's limitations is that it can't use Ingress API and expose services to the outside world. Thankfully there's other way - use Node Port service type. With this simple trick we will be able to access the service using '<minikube_ip>:<node_port_number>'. The port number was specified in the yaml file (we could leave it blank and let Kubernetes assign random one). The node port can easily be checked using the following command:


In order to obtain the Kubernetes node IP, use the following command:


Testing the setup

Testing is quite simple and the only thing to remember is to use the proper address - <minikube_ip>:<node_port>:


Clean up

Minikube has all-in-one command to do the clean up:


Conclusion

Kubernetes setup is almost identical to the OpenShift one but there are a couple of differences to keep in mind:
  • OpenShift's DeploymentConfiguration is similar Kubernetes Deployment with ReplicaSets
  • OpenShift's Services work the same way as in Kubernetes
  • OpenShift's Routes are similar to Kubernetes' Ingresses
Happy scaling and don't forget to check if Infinispan formed a cluster (hint - look into the previous post).

Friday, 12 August 2016

Infinispan Cloud Cachestore 8.0.1.Final

After bringing the MongoDB up-to-date a few days ago, this time it's the turn of the Cloud Cache Store, our JClouds-based store which allows you to use any of the JClouds BlobStore providers to persist your cache data. This includes AWS S3, Google Cloud Storage, Azure Blob Storage and Rackspace Cloud Files.
In a perfect world this would have been 8.0.0.Final, but Sod's law rules, so I give you 8.0.1.Final instead :) So head on over to our store download page and try it out.

The actual configuration of the cachestore depends on the provider, so refer to the JClouds documentation. The following is a programmatic example using the "transient" provider:
 

And this is how you'd configure it declaratively:

This will work with any Infinispan 8.x release.

Enjoy !

Infinispan 8.2.4.Final released!

Dear Infinispan community,

We are proud to announce a new micro release of our stable 8.2 branch. Download it here and try it out!

This maintenance release includes a handful of bug fixes and a bonus new feature. If you are using any other 8.x release, we recommend to upgrade to 8.2.4.Final.

Check out the fixed issues, download the release and tell us all about it on the forum, on our issue tracker or on IRC on the #infinispan channel on Freenode.

We are currently busy working on the upcoming beta release of the 9.0 stream.

Cheers,
The Infinispan team

Tuesday, 9 August 2016

Running Infinispan cluster on OpenShift

Did you know that it's extremely easy to run Infinispan in OpenShift? Infinispan 9.0.0.Alpha4 adds out of the box support for OpenShift (and Kubernetes) discovery!

Our goal

We'd like to build an Infinispan cluster on top of OpenShift and expose a Service for it (you may think about Services as Load Balancers). A Service can be exposed to the outside world using Routes. Finally, we will use REST interface to PUT and GET some data from the cluster.


Accessing the OpenShift cloud

Of course before playing with Infinispan, you will need an OpenShift cluster. There are number of options you can investigate. I will use the simplest path - OpenShift local cluster.

The first step is to download OpenShift Client Tools for your platform. You can find them on OpenShift releases Github page. Once you download and extract the 'oc' binary, make it accessible in your $PATH. I usually copy such things into my '/usr/bin' directory (I'm using Fedora F23). 

Once everything is set and done - spin up the cluster:


Note that you have been automatically logged in as 'developer' and your project has been automatically set to 'myproject'. 

Spinning an Infinispan cluster

The first step is to create an Infinispan app:


Now you need to modify the Deployment Configuration (use 'oc edit dc/infinispan-server' for this) and tell Infinispan to boot up with Kubernetes' discovery protocol stack by using the proper namespace to look up other nodes (unfortunately this step can not be automated, otherwise a newly created Infinispan node might try to join an existing cluster and this is something you might not want). Here's my modified Deployment Configuration:


There is one final step - Kubernetes' PING protocol uses the API to look up other nodes in the Infinispan cluster. By default API access is disabled in OpenShift and needs to be enabled. This can be done by this simple command:


Now we can redeploy the application (to ensure that all changes were applied) and scale it out (to 3 nodes):


Now let's check if everything looks good - you can do it either through the OpenShift web console or by using 'oc get pods' and 'oc logs' commands:


Accessing the cluster

In order to access the Infinispan cluster from the outside world we need a Route:


The newly created Route needs small changes - we need to change the target port to 8080 (this is the REST service). The 'oc edit route/infinispan-server' command is perfect for it. Below is my updated configuration:

  • (line 17) - Modified to 8080 TCP port

Testing the setup

You can easily see how to access the cluster by describing the Route:


Now let's try to play with the data:

Cleaning up

Finally, when you are done with experimenting, you can remove everything using 'oc delete' command:

Conclusion

Running Infinispan cluster inside an OpenShift cloud is really simple. Just 3 steps to remember:
  1. Create an Infinispan app ('oc new-app')
  2. Tell it to use Kubernetes JGroups Stack and in which project look for other cluster members ('oc edit dc/infinispan-server')
  3. Allow access to the OpenShift API ('oc policy add-role-to-user')
Happy scaling!

Monday, 8 August 2016

Infinispan Spark connector 0.4 released!

This release is compatible with Apache Spark 2.0.0 and has support to connect to secured Infinispan Servers; for a full list of changes, please see the release notes.

For more information about the connector, including Maven and sbt coordinates, consult the getting start guide.

To get help, go to the usual Infinispan channels: #infinispan on freenode, user forum and the dev list.

Cheers,
Gustavo

Friday, 5 August 2016

MongoDB Cache Store 8.2.1.Final

In the storm of the persistence SPI rework that happened during Infinispan 6.0, the MongoDB cache store, among others, was left in a state of semi-abandonment for a long time.

Fortunately a few brave souls came to its rescue and have breathed new life into it so that it can be used with Infinispan 8.x

In particular I wish to thank Kurt Lehrke for doing most of the work !!!

Get it from the dedicated cache store download page.

Thursday, 4 August 2016

Infinispan 9.0.0.Alpha4

Dear Infinispan users,

I am glad to announce that we have released 9.0.0.Alpha4 for you!


A brand new Alpha release from our development branch: 9.0.0.Alpha4 has a slew of bug fixes, and some more enhancements, among which we single out: transactional JDBC cache store and Kubernetes PING support.  We also have added quite a bit of documentation around querying to help users better understand how to use it.

Download it now, try it and tell us what you think on the infinispan forums or come and meet us on IRC: channel #infinispan on Freenode.