Jump to: navigation, search
Line 29: Line 29:
  
 
== Deploying GWS ==
 
== Deploying GWS ==
−
{{Editgrn_open}}To be updated{{Editgrn_close}}
+
===Implementation Steps===
−
 
+
Unpack installation package (Example: IP_HTCCDev_9000197b1_ENU_dockerlinux.zip file) and navigate to "ip" folder which should contain following files:
−
 
+
gws-microservices.tgz
−
====DNS  and Storage Requirements====
+
exported microservices in tar.gz format (e.g. gws-platform-configuration_9.0.000.42.tar.gz)
−
All of the services ingresses require DNS names to be pre-populated to get access to.
+
Unpack gws-microservices.tgz archive to /opt/genesys/gws directory.
−
 
+
<source lang="text">
−
* Openshift: the GlusterFS storage should be pre-populated manually.
+
mkdir -p /opt/genesys/gws
−
* NFS (for premise deployments) - should be pre-populated manually.
+
tar xvf gws-microservices.tgz -C /opt/genesys/gws
−
* GKE - just works out of the box, no further interaction required.
+
</source>
−
* AWS - dynamic storage provisioning works out of the box.
+
Populate the Docker images (presented in *.tar.gz format) from installation package to your corporate docker registry.
−
* No storage - just set the <tt>PERSISTENT_STORAGE</tt> to ''false'' variable in your environment file.  
+
<source lang="text">
−
 
+
for i in *.tar.gz; do /opt/genesys/gws/kubernetes/bin/push-containers-to-local-registry.sh $i %corporate_registry_address% --push; done
 +
</source>
 +
{{NoteFormat|This script must be run with Docker capable privileges and you must login to your registry before pushing.}}
  
  
 
[[Category:V:HTCC:9.0.0DRAFT]]
 
[[Category:V:HTCC:9.0.0DRAFT]]

Revision as of 04:53, February 5, 2020

Deployment of Web Services and Applications in Kuberbetes

Important: This content is restricted and not viewable without a login supplied by Genesys. The information contained in this documentation is not considered final and is managed under the terms and conditions found in the Pre-release Agreement. This documentation provides the most up-to-date reference information available for this pre-release version and is restricted for use by those who have signed the Pre-release Agreement with Genesys to acquire an early version of the software.

Prerequisites

Hardware Requirements

The solution can be deployed at a Kubernetes cluster with a minimal size of 3 nodes with an overall amount of 64 GB RAM. Recommended hardware requirements for each Kubernetes node:

  • Nodes: 3 nodes (Virtual Machines)
  • RAM: Approximately 22 GB for each node (64 GB in total)
  • CPU: 15 cores for each node (45 cores in total)
  • HDD: 100 GB for each node

Software Requirements

  • OS: CentOS-7

Kubernetes cluster:

  • Rancher Kubernetes Deployment
  • Client-side utilities installed at deployment host:

Workspace Web Requirements

  • Browser:
    • Google Chrome 75+
    • Mozilla Firefox 68+
    • Firefox ESR 60.9
    • Microsoft Internet Explorer 11
    • Microsoft Edge

Configuring Web Services Applications

To configure Web services and applications, refer to Configuring Web Services and Applications.

Deploying GWS

Implementation Steps

Unpack installation package (Example: IP_HTCCDev_9000197b1_ENU_dockerlinux.zip file) and navigate to "ip" folder which should contain following files: gws-microservices.tgz exported microservices in tar.gz format (e.g. gws-platform-configuration_9.0.000.42.tar.gz) Unpack gws-microservices.tgz archive to /opt/genesys/gws directory. 

mkdir -p /opt/genesys/gws
tar xvf gws-microservices.tgz -C /opt/genesys/gws

Populate the Docker images (presented in *.tar.gz format) from installation package to your corporate docker registry. 

for i in *.tar.gz; do /opt/genesys/gws/kubernetes/bin/push-containers-to-local-registry.sh $i %corporate_registry_address% --push; done
Important
This script must be run with Docker capable privileges and you must login to your registry before pushing.
Comments or questions about this documentation? Contact us for support!