Blogging is fun and it takes time. Leaving aside the research part, preparing all prerequisites takes a lot of time – also fun and educational. I have a few permanent clusters spread across cloud vendors and little more than a half rack of servers in my garage. Development VMs and Kubernetes clusters on AWS, a bare-metal VMware cluster mostly used for NFV testing and few old applications on Windows VMs, an IBM Cloud private cluster, an OpenStack cluster for a various break and fix experiments, a scale-out NAS and SAN providing storage for all servers in the garage.
I started to think I should consider hiring an IT admin to keep all up-to-date for me. Since my wife didn’t like the idea – scratching my head – I need to increase my garage lab operation productivity. I need to use Vagrant and Terraform more often.
This time, I will deploy OpenShift locally, using Vagrant and Minishift. Vagrant continues to be my favorite. It’s fast, good enough for testing and validation. I don’t have to pay cloud fees until I decide to move this into production.
FYI, there are few other options to install OpenShift including Minishift, Container Development Kit and “oc cluster up”. Here I will explain Vagrant and Minishift deployment option for an all-in-one VM running on Virtualbox.
Install OpenShift Origin using Vagrant
Just two commands and you will have an Openshift cluster running locally in :
$ vagrant up --provider=virtualbox
Vagrant box download may take few minutes. After it’s provisioned you will get a message like below:
default: Running: inline script
default: Successfully started and provisioned VM with 2 cores and 5 G of memory.
default: To modify the number of cores and/or available memory modify your local Vagrantfile
default: You can now access the OpenShift console on: https://10.2.2.2:8443/console
default: Configured users are (<username>/<password>):
default: But, you can also use any username and password combination you would like to create
default: a new user.
default: You can find links to the client libraries here: https://www.openshift.org/vm
default: If you have the oc client library on your host, you can also login from your host.
default: To use OpenShift CLI, run:
default: $ oc login https://10.2.2.2:8443
Now open https://10.2.2.2:8443 in your browser. Use the default username and password
admin/admin to login.
This is possibly the fastest to get a functional test environment. From here you can create a New Project and play with it.
The current vagrant box is Openshift Origin 1.3.
Install OpenShift Origin using Minishift
I like this option more since Minishift project is more active and images are updated for frequently.
Extract this under your
%USERPROFILE% folder. For example,
Default hypervisor for Minishift on Windows is Hyper-V. To install OpenShift Origin using Virtualbox type the command below in command line:
After few minutes you will have the VM image up and running.
- Downloading OpenShift v3.6.0 checksums ... OK
-- OpenShift cluster will be configured with ...
-- Checking `oc` support for startup flags ...
host-pv-dir ... OK
host-volumes-dir ... OK
routing-suffix ... OK
host-config-dir ... OK
host-data-dir ... OK
Starting OpenShift using openshift/origin:v3.6.0 ...
Pulling image openshift/origin:v3.6.0
Pulled 1/4 layers, 26% complete
Pulled 2/4 layers, 62% complete
Pulled 3/4 layers, 91% complete
Pulled 4/4 layers, 100% complete
Image pull complete
OpenShift server started.
The server is accessible via web console at:
You are logged in as:
Password: <any value>
To login as administrator:
oc login -u system:admin
Now open https://192.168.99.100:8443 in your browser. Use the default username and password
developer/any value to login.
At the time I tried Minishift v1.9 was the latest version and it installed the below versions of OpenShift and Kubernetes:
OpenShift Master: v3.6.0+c4dd4cf
Kubernetes Master: v1.6.1+5115d708d7
Click on Add Project button and chose from web frameworks, databases, and other components to add content to your project.
If you deploy stateful workloads like the database solutions listed in the data stores catalog, it’s recommended to have a persistent storage available.
On my next blog post, I will explain how to install OpenEBS on OpenShift and deploy workloads on persistent volumes.