To get started, you’ll need an OpenShiftV3 environment with a valid user account. This project also expects the basic set of openshift builder images to have been installed under the openshift namespace.

You can create your own OpenShiftV3 environment in Amazon EC2 using the demo-ansible playbook.

To create your own local OpenShift VM with Vagrant, see openshift.org/vm/.

Authentication

oc login <openshift-cluster-ip>

oc whoami -t

Create a project

oc new-project hexboard

oc new-app -f https://raw.githubusercontent.com/2015-Middleware-Keynote/hexboard/master/app_template.json -p ACCESS_TOKEN=$(oc whoami -t)

oc create -f https://raw.githubusercontent.com/2015-Middleware-Keynote/hexboard/master/app_template.json

oc new-app -l servicegroup=sketchpod openshift/nodejs~http://github.com/2015-Middleware-Keynote/sketchpod
oc new-app -e "ACCESS_TOKEN=${ACCESS_TOKEN}" openshift/nodejs~http://github.com/2015-Middleware-Keynote/hexboard

oc get builds -w

Docker image builds can be initiated by navigating to the "Builds" tab in the V3 web console. Click on the Start Build button for each service.

You can also initiate the builds from the command line:

Watch the progress:

In order to view the hexboard, you’ll need to expose your service by setting up a Route. The optional --hostname flag allows you to create a custom route to an existing service:

Make sure this route is addressable from wherever you are running your browser (an /etc/hosts entry in your client may be required).

Excluding the --hostname flag should generate a default route that automatically takes advantage of your cluster’s wildcard DNS (if available):

Now, try listing your existing routes:

The service configuration is provided via environment variables. These configs can be set while loading a project from a template via the web console or via the oc process command.

You can also add environment keys to an existing deployment config using the oc env command. Setting new configuration details will trigger a deployment to distribute your changes (if needed).

API Access Token

oc env dc/hexboard ACCESS_TOKEN=$(oc whoami -t)

Admin Controls

oc env dc/hexboard ADMIN_TOKEN="${ADMIN_TOKEN}"

Winner Count

oc env dc/hexboard WINNER_COUNT=3

Hexboard Size

oc env dc/hexboard HEXBOARD_SIZE=<hexboard-size>
oc get pods -w

Animations of falling hexagons are triggered as the number of pods is scaled. To scale the number of hexagons (either up or down) run the command:

After scaling up, try submitting sketches by visiting the hexboard’s bundled mobile web submission form, at http://your-hexboard-hostname/mobile/.

After scaling up, the hexboard provides a nice way to visualize Kubernetes' support for auto-healing the containerized environments.

You can show this functionality by deleting a group of pods. This example makes it easy find and delete five pods:

WARNING: There is a known issue that may cause display errors when pods are deleted.

Workaround: Instead of showing autorecovery on the hexboard, show this feature using the OpenShift web console. Your project Overview page’s view modes (list, topographical) both nicely illustrate how this feature works.

Pre-Requisutes

Installation

npm install

Run the hexboard locally

PORT=8081 PROXY="localhost:1080" ACCESS_TOKEN="${ACCESS_TOKEN}" OPENSHIFT_SERVER="localhost:8443" NAMESPACE=hexboard gulp

To delete all sketchpods using a labelselector, try this:

You can clean out the entire contents of the hexboard project by running the following:

Or, delete the entire project and any included resources: