Learn about the division of responsibilities between Genesys and your organization in deploying Genesys Engage cloud private edition.
Genesys Engage services are containerized and delivered to your organization through the JFrog Artifactory Edge repository. Genesys ensures that the containers can run on infrastructure such as a public or private cloud (refer to the release notes for the complete list of supported platforms), or bare metal servers that resides within your corporate data center. However, it is your responsibility to set up the infrastructure that is suitable for deploying Genesys Engage services including deployment of Genesys recommended third-party prerequisites in your clusters.
After your clusters and third-party prerequisites are set up, you can proceed with deploying Genesys Engage services.
The following table presents the responsibilities between Genesys and your organization in deploying Genesys Engage cloud private edition.
|Deploys and manages your Kubernetes technology stack.||Provides containerized software that support multiple Kubernetes-certified environments. Provides sizing calculator to determine the cluster size, number of nodes and so on, to set up the infrastructure.|
|Deploys and manages all Genesys recommended third-party services such as PostgreSQL, Redis, Elasticsearch, NFS, and so on. Check Software requirements for more information.||Provides documentation that lists the recommended third-party services and their supported versions. Provides guidance or the need for any Genesys-specific configuration in the third-party services.|
|Provides environment specific values to override the default values.||Ensures that Genesys Engage services and their Helm charts are accessible to your organization through the JFrog Artifactory Edge repository. Provides the ability to override the Helm charts with environment specific values.|
|Provides the network infrastructure with required access to manage voice and data traffic.||Provides network requirements information such as Ingress controller, load balancers and so on for each service in the service-level documentation.|
|Ensures security of their infrastructure by implementing security protocols.||Ensures that Genesys provided container images and artifacts enable your organization to implement your security policies and guidelines that are based on industry best practices and security standards.|
|Configures the preferred logging software to capture Genesys Engage services logs.||Provides support to standard out/standard error logging which enables your organization to use popular logging software like FluentD, for this purpose. Explains the configuration procedure with FluentD as an example.|
|Configures the preferred monitoring software to capture Genesys Engage services metrics.||Provides support to popular monitoring software like Prometheus, for this purpose. Explains the configuration procedure with Prometheus as an example.|
|Manages upgrades by setting a continuous deployment (CD) pipeline and performs timely deployment testing.||Provides new software updates through our repository which have the capabilities to perform in-service upgrades using the documented steps a CD pipeline should implement. Also provides a sample procedure that helps to set up a CD pipeline in your environment.|