Architecture - Configuration Server

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Genesys Voice Platform Private Edition Guide for version Current of Genesys Voice Platform.

Learn about Genesys Voice Platform- configuration server architecture

Introduction

The following diagram displays the architecture of GVP Configuration Server.

For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.

See also High availability and disaster recovery for information about high availability/disaster recovery architecture.

Architecture diagram — Connections

The numbers on the connection lines refer to the connection numbers in the table that follows the diagram. The direction of the arrows indicates where the connection is initiated (the source) and where an initiated connection connects to (the destination), from the point of view of Genesys Voice Platform as a service in the network.

Pe-gvp-configserver.png

Connections table

The connection numbers refer to the numbers on the connection lines in the diagram. The Source, Destination, and Connection Classification columns in the table relate to the direction of the arrows in the Connections diagram above: The source is where the connection is initiated, and the destination is where an initiated connection connects to, from the point of view of Genesys Voice Platform as a service in the network. Egress means the Genesys Voice Platform service is the source, and Ingress means the Genesys Voice Platform service is the destination. Intra-cluster means the connection is between services in the cluster.

Connection Source Destination Protocol Port Classification Data that travels on this connection
1 CS PostgreSQL TCP 5432 Egress TCP messages. GVP Config Server connection to database.
2 Kubelet SH HTTP 8300 Ingress HTTP GET Requests and for liveness and readiness checks.
3 DB-Init PostgreSQL TCP 5432 Egress TCP messages.
4 RM CS TCP 8888 Egress TCP messages. RM connects to GVP Configuration Server connects to get configuration data.
5 MCP CS TCP 8888 Egress TCP messages. MCP connects to Configuration Server to get recording certificate details and Google keys.
6 RS CS TCP 8888 Egress TCP messages. RS connects to configuration server to fetch configuration data.
7 SD CS TCP 8888 Egress TCP messages. Service Discovery connects to Configuration Server to Check/Add/Delete MCP applications.