Architecture - Resource Manager
Learn about Genesys Voice Platform- resource manager architecture
The following diagram displays the architecture for Resource Manager.
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.
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||RM||SIP Server||SIP/TCP||5090||Egress||SIP Protocol messages.|
|2||RM||RS||TCP||61616||Egress||ActiveMQ messages. RM posts billing data to RS.|
|3||RM||MCP||SIP/TCP||5070||Egress||SIP Protocol messages.|
|4||RM||Config Server||TCP||8888||Egress||TCP messages. RM connects to GVP CS to get configuration data.|
|5||RM||SNMP Master Agent||TCP||1705||Egress||TCP Messages. RM posts SNMP metric and traps to SNMP MA.|
|6||RM||Other RM||TCP||9801||Egress||TCP messages. Internode communication between RMs.|
|7||Kubelet||RM||HTTP||8300||For liveness and readiness checks|
|8||Prometheus||Log Exporter||HTTP||8200||Ingress||HTTP messages. RM log metric upload to Prometheus.|
|9||Prometheus||SNMP Exporter||HTTP||9116||Ingress||HTTP Messages. RM custom SNMP metric upload to Prometheus.|
|10||Config handler||Config Server||TCP||8888||Egress||TCP messages. Config Handler container connects to GVP CS to create RM application and LRG.|
|11||SIP Server||RM||SIP/TCP||5060||Ingress||SIP Protocol messages.|
|12||MCP||RM||SIP/TCP||5060||Ingress||SIP Protocol messages.|