Red Hat release OpenShift PaaS as opensource, and ability to run your own PaaS with OpenShift Origin

Yesterday Red Hat announced at the Open Cloud Conference in Sunnyvale, CA, the release of OpenShift as open source, and the ability to take OpenShift and use it to run your own PaaS.

What does this mean? Firstly, you can take the source for OpenShift and view or modify it (under the Apache 2 license) as you please. Secondly, if you have a need to run your systems using a private cloud model locally or hosted using your own hosting provider, you can take OpenShift and deploy it where ever you need, and still take advantage of the ability to dynamically provision/deploy apps and services using the OpenShift toolset.

This is very similar to the approach VMWare have taken with Micro Cloud Foundry, which is also open source, and also available so you can run the PaaS yourself.

Setting JAVA_HOME on Mac OS X

Some time ago I had set JAVA_HOME in my .profile on Mac OS X to the following:

JAVA_HOME=/Library/Java/Home; export JAVA_HOME

To some extent this works, but it doesn’t apparently pick up your preferred JDK version that you can set via the Java Preferences app in /Applications/Utilities (you set your preferred version by dragging your choice to the top of the list).

To set JAVA_HOME to be set to your preferred version, use this instead:

JAVA_HOME=`/usr/libexec/java_home`; export JAVA_HOME

This post here talks about the first approach, but there’s a comment in response to the post that points out the second point.

Android SDK INSTALL_FAILED_MISSING_SHARED_LIBRARY error

If you’re installing an apk into the Android Emulator and seeing this error (INSTALL_FAILED_MISSING_SHARED_LIBRARY), it may mean that the app relies on the Google APIs (e.g. for Google Maps and the other Google Android apps) and your AVD that you’re running was created without the Google APIs.

Create a new AVD from the AVD Manager using the one of the Google API targets at the API level that you need and you should be good to go.