Jump to: navigation, search
(→‎Working with GWS Infrastructure)
Line 54: Line 54:
 
{{NoteFormat|{{Editgrn_open}}XR: Is there a sequence to be followed? What needs to be deployed first?{{Editgrn_close}}|}}
 
{{NoteFormat|{{Editgrn_open}}XR: Is there a sequence to be followed? What needs to be deployed first?{{Editgrn_close}}|}}
  
−
=== Working with GWS Infrastructure===
+
=== Deploying GWS Infrastructure===
 
{{Editgrn_open}}XR: Should we delete first before deploying?{{Editgrn_close}}
 
{{Editgrn_open}}XR: Should we delete first before deploying?{{Editgrn_close}}
 
<pre>
 
<pre>
Line 61: Line 61:
 
</pre>
 
</pre>
  
−
=== Working with GWS Application Stack===
+
=== Deploying  GWS Application Stack===
 
<pre>
 
<pre>
 
./gws-app-deploy.sh delete
 
./gws-app-deploy.sh delete
Line 67: Line 67:
 
</pre>
 
</pre>
  
−
=== Working with Prometheus and Grafana ===
+
=== Deploying  Prometheus and Grafana ===
−
{{NoteFormat|These services are deployed clusterwide and do not depend on GWS-applications' loads. }}
+
{{NoteFormat|These services are deployed cluster-wide and do not depend on GWS-applications' loads. }}
 
<pre>
 
<pre>
 
$ ./monitoring-deploy.sh delete
 
$ ./monitoring-deploy.sh delete

Revision as of 08:05, November 21, 2018

Deploying with bash scripts

The following Kubernetes distributions are supported:

  • OpenShift (Fully Supported)
  • Google Kubernetes Engine (Partially Supported)

Requirements

  1. Kubectl and Helm client utilities
    • Tiller is not required.
    1. For OpenShift deployments, install the oc utility.
    2. For Google Kubernetes Engine deployments, install and configure the gcloud utility.
  2. The scripts reside in the gws-microservices hg repository.

Deploying GWS with OpenShift Platform

  • Copy your configuration to ~/.kube/config.
  • Type kubectl get nodes to list the nodes in your cluster.
  • Type cd gws-microservices/production/premise/kubernetes to go to the kubernetes directory.
  • Create your own environment configuration file and put it to env-examples directory. Or use the ones available.
    • Type . env-examples/<YOUR ENVIRONMENT SOURCE FILE> to source the cluster environment variables.
  • Import GWS-applications docker images to your container registry or add the GWS registry keys to /etc/docker.d.
    • Get the registry keys and add them to /etc/docker.d on all hosts.
  • Restart docker.

Deploying GWS with Google Kubernetes Engine

  • Follow the registration web-UI steps.
  • Type gcloud container clusters list to list existing clusters for running containers.
  • Type cd gws-microservices/production/premise/kubernetes to go to the kubernetes directory.
  • Create your own environment configuration file and put it to "env-examples" directory. Or use the ones available.
  • Type . env-examples/<YOUR ENVIRONMENT SOURCE FILE> to source the cluster environment variables.
    • Import GWS-applications docker images to your container registry or add the GWS registry keys to /etc/docker.d.
  • Get the GWS-microservices docker images tarball via any Genesys supply channel and import it to Google Container Registry: "TARBALL=/full/path/to/GWS/apps/tarball push-containers-to-gke.sh"


Important
XR: Is there a sequence to be followed? What needs to be deployed first?

Deploying GWS Infrastructure

XR: Should we delete first before deploying? 

./gws-infra-deploy.sh delete 
./gws-infra-deploy.sh

Deploying GWS Application Stack

./gws-app-deploy.sh delete
./gws-app-deploy.sh

Deploying Prometheus and Grafana

Important
These services are deployed cluster-wide and do not depend on GWS-applications' loads. 
$ ./monitoring-deploy.sh delete
$ ./monitoring-deploy.sh

Pulling Current GWS Applications Container

$ STACK_DOCKER_IMAGE_PATH=gws-registry-usw1.genhtcc.com ./pull-containers.sh
Comments or questions about this documentation? Contact us for support!