Architecture

Learn about <service_name's> architecture.

Explain the architecture of all services in the container. Note whether the service supports autoscaling. Link to "suite-level" Architecture page:

Include a logical architecture diagram. You'll need to work with the diagram team so that all Genesys Engage cloud private edition architecture diagrams are consistent.

Containers and Helm charts

Container	Type	Functionality	Jfrog Container	Helm charts
RS Init	initialization container	Is responsible for the following before starting the RS process. Initializes the RS DB and creates the read-only user for the billing team. Registers the host as a new Host object on the configuration server Registers RS instance as a new RS application object. If the RS application exits for that particular pod, update the host IP. Registers SNMP Master Agent as new SNMP Agent application object. Connects the SNMP object in the RS object.	https://pureengage.jfrog.io/artifactory/docker-stage/gvp/gvp_rs_init	https://pureengage.jfrog.io/artifactory/helm-staging/gvp/gvp-rs-<*.*.*>.tgz
gvp-rs	main container	The RS container is responsible for starting the RS process by pointing the RS object created by RS Init container.	https://pureengage.jfrog.io/artifactory/docker-stage/gvp/gvp_rs_init
gvp-snmp	sidecar container	SNMP Master Agent in Docker container sends the monitoring data to the Prometheus server. Python log parser runs in the container and sends the log to kibana.	https://pureengage.jfrog.io/artifactory/docker-stage/gvp/gvp_rs_snmp