Building and Running Microservices on OpenShift: Part IV
April 13, 2016 | by
In this video
Today we continue with Veer Muchandi's series of 4 videos that will guide you through every detail you need to know to start building and running your own Microservices.
In the previous video we talked about how a developer creates microservices and how OpenShift builds the docker images for the microservices and deploys them. This video addresses how to package these microservices as units that can be deployed across environments.
OpenShift templates are used as a packaging format to group an entire microservice (including all tiers) together. Once packaged, we will see how we can use it to deploy each microservice a unit into a project.
1) Tagging the images in the development project
oc describe is
Copy hashtag (only the part that starts after project name.)
Once created edit each microservice template to remove the host entries in the route and change the image trigger to use “promote” label instead of “latest” label. Also add a namespace label to pick up the image from your development project’s image stream.
3) Provide image puller access to the Production project and change to the production project
4) Deploy microservices in your production project
oc process -f emailsvc-microservice.json | oc create -f -
oc process -f userregsvc-microservice.json | oc create -f -
oc process -f userreg-microservice.json | oc create -f -
This series of videos was created by Veer Muchandi in collaboration with Chakradhar Jonagam.
Chakradhar Jonagam works as a Solution Architect at Red Hat. He helps companies architect their PaaS infrastructure, Prior to this he was a full stack developer with some infosec background. In his free time he loves to take long hikes.
You can find many of Veer's blog posts here. He has created a multitude of demos that cover interesting aspects of the OpenShift Platform.
You've probably heard about the growth of edge computing, but what is edge? And what does it mean- especially for OpenShift admins? By moving workloads to the edge of the network, devices spend less ...