OpenShift as a Sevice (OSS)
OpenShift is a platform as a service for container management, using Docker containerization and Kubernetes orchestration tools.
The service allows to deploy the necessary environments in container-based infrastructure, without need to look for higher hardware capacities.
- Currently, we strongly recommend to run the service in EPAM-BY2 region, where it can perform in a stable and reliable manner.
- OpenShift as a Service is based on Ansible configuration management solution, thus it is recommended to use Linux-based workstations to set up the service.
Due to Ansible limitations, the service cannot be run from Windows workstations
To run the service, you need Ansible to be setup on your workstation. The detailed instructions on this and other steps related
to the service are described in the
OpenShift as a Service Configuration Guide attached to this page.
Have a Question?
The current page gives the general information on the service and the main workflows. However, while working with the
services, our users encounter new questions they need assistance with. The most frequently asked questions on EPAM Cloud
Services are gathered on the
Cloud Services FAQ page.
Visit the page to check whether we have a ready answer for your question.
Related CLI Commands
The table below provides the list of service-related commands and their descriptions:
|or2-manage-service...-s open-shift -v 3.7 -a
||or2ms...-s open-shift -v 3.7 -a
||Activates the OpenShift service in the specified project and region.
||Used to install and configure OpenShift Ansible client to manage OpenShift services.
Further on this page, you can find more details on the OpenShift service manipulation.
Service Activation and Configuration
To activate OpenShift as a Service, use the or2-manage-service (or2ms) command with the -a/--activate flag and the -s/--service-name parameter
with kubernetes value:
or2ms -p project -r region -a -s open-shift -v 3.7 -k key_name
When the command is run, Orchestrator starts four LARGE CentOS 7 64-bit VMs, each with additional 30GB storage attached:
- Master Node
- Wildcard Node
- Work node 1
- Work node 2
To see the details on the VMs created for the service, use the or2din command. The --full parameter will be helpful to see all the necessary details
on the main Master and Wildcard nodes.
or2din -p project -r -region
To install the Ansible client that will be used to configure the service VMs and to configure it, use the or2-openshift-client (or2osc) command with different
or2osc -a install -- to install the client
or2-openshift-client -a configure -p project -r region -w wildcard --to configure the wildcard (which should be previously registered by the support team)
To install OpenShift on the prepared VMs, call the necessary playbooks:
ansible-playbook -v -i inventory/byo/service -u EPAM_email --private-key path_to_private_key playbooks/byo/config.yml
For more detailed steps on the service setup, please see the attached OpenShift as a Service Configuration Guide attached to this page.
The OpenShift service has a web UI which is available with the credentials that should be previously specified from within the Master node.
To set up the login credentials, login ti the Master node and run the following command:
htpasswd -c /etc/origin/master/htpasswd admin
The command responce will prompt you to set up the password for the admin user:
The OpenShift UI link is included to the OpenShift status details retrieved by following command, run in the Master node console:
Following the link, you can get to the OpenShift login page. To login, use the credentials that were set up on the previous step.
Service includes four Large Linux instances, each having additional 30GB storage volumes. When you start the service, you pay only for the used virtual
resources. As of March 26, 2018, the approximate monthly price in EPAM-BY2 region is about $260.29.
Below is a list of documents related to this section. You can find the full list of our documents
in the Documentation Storage.
Please select a required document: