OpenShift for Developers

Chapter 3. Installing the All-in-One VM

For the exercises in this book we will be using a virtual machine (VM) that has all the pieces of an OpenShift server already installed and configured. This machine will be routable from your local system so you can treat it like a hosted version of OpenShift and can view the URLs you create.

This image is based off of OpenShift Origin and is a fully functioning OpenShift instance with an integrated Docker registry. The aim of this project is to allow web developers and other interested parties to run OpenShift V3 on their own computer. The VM is configured by default to have a separate IP address (10.2.2.2) from your local machine, and it includes a network configuration that assigns each new container deployed on the platform its own unique IP address. This gives the illusion that the VM is running on separate hardware in a data center or public cloud while in fact it’s running locally on your machine.

The OpenShift master, node, Docker registry, and other pieces run on one VM. Given its focus on application developers, it should NOT be used in production. While the Vagrantfile only specifies 2 gigs of RAM, you can edit the file to increase this setting if you want to run more containers concurrently in your instance.

The VM uses xip.io to provide DNS resolution with application URLs. The advantage of this is that you actually get routable URLs to your local machine without browser or Vagrant plug-ins that may not work on your machine. ...