openshift origin multi-master manually deployment part-5

8,deply route and docker registry service.
deploy a router, running on three master nodes

oadm policy add-scc-to-user hostnetwork -z router
oadm router router --replicas=3 --selector='region=infra' \

deploy docker registry running on node1, on node1:

mkdir -p /opt/openshift-registry
chown 1001:root /opt/openshift-registry

on master1, deploy docker registry service and secure it:

oadm registry --service-account=registry --mount-host=/opt/openshift-registry --selector='region=primary'
oadm policy add-scc-to-user privileged system:serviceaccount:default:registry
oc create route passthrough --service docker-registry -n default 

Continue reading

openshift origin multi-master manually deployment part-1

i have deployed an openshift origin muliti-master cluster successfully on centos and suse enterprise server.
Since the deployment is done manually, i will describe it in detail as possibly as i can.

first, take a whole view of architecture,
we have three master nodes, all of them are in active state. the number of nodes is according to your cluster size. we do not need a lb node, so no haproxy is needed. we setup a VIP floating in three master nodes. for this architecture, no loadbanlance muchinasm is provided, but it is okay for high availibilty. If you realy need a loadbanlance, it is easy to deploy one after the whole cluster is up.

next, for deployment environment.
three master nodes, based on centos minimal installation, with static ip address.
hostname: ip address

i will break this deployment into four parts.
part1: deploy named, keepalived, and docker
part2: deploy master service
part3: deploy etcd cluster with ssl enabled
part4: deploy node service
part5: deploy router and docker registry service

okay, let’s start.
Continue reading

Page 1 of 71234567