Credits go to Bryan Sazon (john.bryan.j.sazon@accenture.com) for the original content of his Gist.
I also used reference from https://www.projectatomic.io/blog/2017/05/oo-standalone-registry/
Credits go to Bryan Sazon (john.bryan.j.sazon@accenture.com) for the original content of his Gist.
I also used reference from https://www.projectatomic.io/blog/2017/05/oo-standalone-registry/
The following section describes my experiment on how to add a NEW NODE into your existing OpenShift cluster.
Openshift is designed to be a jungle, with self-contained projects! So for DevOps admins like us, who get knacked on the face by an error code pointing to a Docker containerID, we need to understand how the Docker environment swims inside the World of OpenShift.
yum clean all | |
rm -Rf /var/cache/yum | |
yum clean all | |
yum -y install epel-release | |
yum -y install git | |
yum -y install ansible | |
yum -y --enablerepo=epel install python-pip python-devel python | |
pip install docker-compose | |
docker-compose version |
In case you find yourself using NodeJS for backend scripting, you can use the power of API calls to manage your Docker containers.
Docker has shell bin commands but it's nice to know the remote API calls so an application can remotely control your containers. This document shows how to setup your docker service (inside Centos 7) to expose the API port.