This post appeared originally in our sysadvent series and has been moved here following the discontinuation of the sysadvent microsite
The intention of this post is to get oneself kick-started into playing with Platform as a Service (PaaS) by interacting with a lab environment that is running in a VM on your local machine. It relies heavily on other parties (OpenShiftOrigin, jmorales, Red Hat and JavaZone) prior work that I “abuse” in this post.
The environment consists of CentOS Linux, OpenShift Origin with master/node roles, GitLab, Sonatype Nexus Repository Manager and Lab contents.
Do not Get PaaS-ed By
In order to play along locally with the activities in this post one needs OpenShift Origin up and running. We will address this with a VM running on VirtualBox with Vagrant. So, get hold of VirtualBox (version 5.0) and Vagrant (version 1.8.4) for your OS, download the “box”, start it and check that it’s alive:
$ vagrant box add jmorales/origin-labs --provider virtualbox
$ cd ~/vagrant/origin-labs
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
...
==> default: Machine booted and ready!
...
$ vagrant box list
jmorales/origin-labs (virtualbox, 1.3.0-alpha.3)
Enter PaaS-ground
Test SSH login to your VM:
$ ssh vagrant@127.0.0.1 -p 2222 -i \
~/vagrant/origin-labs/.vagrant/machines/default/virtualbox/private_key
Last login: Wed Nov 23 05:19:52 2016 from 10.0.2.2
$
Access the Web Console by directing your browser to https://10.2.2.2:8443 and logging in as both
Username: dev
Password: dev
and
Username: admin
Password: admin
You are good to go, yay :-)
Let the PaaS fun begin
Direct your browser to your VM with this URL http://labs.apps.10.2.2.2.xip.io/ and work through the exercises, starting with Installing the oc client tool.
Have fun!
Just-Make-toolbox
make
is a utility for automating builds. You specify the source and the build file and make
will determine which file(s) have to be re-built. Using this functionality in make as an all-round tool for command running as well, is considered common practice. Yes, you could write Shell scripts for this instead and they would be probably equally good. But using make
has its own charm (and gets you karma points).
Even this ... [continue reading]