Global Production Overview
Resource Requirements per Pod
The following table outlines the recommended resource requests for each pod. These recommendations assume:
-
No CPU limits[1] are configured.
-
The underlying infrastructure does not employ CPU over-provisioning.
-
The CPU request values are intentionally set low because they represent resources exclusively reserved for the Pod. However, since Pods may occasionally require additional CPU, it’s important to keep extra CPU capacity available to accommodate these temporary spikes and ensure smooth performance.
Failure to meet these recommendations may result in instability or performance degradation. Volume storage is not required.
CPU Request[2] (milliCPU) |
200m |
|---|---|
Minimum memory |
500 MB |
Maximum memory |
8192 MB |
Mounted Volume Storage |
None |
Required software on cluster
Operating System |
Kubernetes 1.25+ |
|---|---|
IAS Helm Schema Version |
2.4 |
Further Software |
None |
Ports which need to be open
GPO uses .NET Orleans internally and this uses the following ports for communication between pods:
-
11111
-
30000
Any service mesh which intercepts the traffic between the pods will need to switch to "passthrough" or "permissive" mode for these ports, otherwise the communication will not work correctly.
Optional infrastructure services
Data Publisher, Shopfloor Management Essentials Configbridge
Databases
Microsoft SQL Server
-
Supported Versions: SQL Server 2016+
-
DBs / Schemas / Users: Single DB with default schema (or shared DB with dedicated schema) with dedicated user for schema.
-
Required Privileges: db_owner (required for bootstrapping the DB tables)
-
Relative Capacity: 3 GB / 1 line / year
Oracle
-
Supported Versions: Oracle 19c+
-
DBs / Schemas / Users: Single schema with dedicated user for schema.
-
Required Privileges: NEXEED_BASIC_ROLE, NEXEED_EXTENDED_ROLE, NEXEED_MONITORING_ROLE. The roles are defined in the Nexeed IAS Operations Manual, Chapter 6.10. Database User Setup and Configuration.
-
Relative Capacity: 3 GB / 1 line / year
Messaging Middleware
RabbitMQ as AMQP broker
-
Supported Versions: Any version supporting AMQP 0.9.1
-
Extensions: None
-
Queues / Topics / Exchanges: The exchange x.nexeed.integration on the RabbitMQ instance and a corresponding MACMA instance for emitting the integration events is required for receiving the tenant deletion events. No other events are received by Global Production Overview. It will also set up its own exchange and queue when starting up for receiving events, no events are emitted.
-
Required Privileges: The user used by GPO to connect to RabbitMQ needs to have the following permissions on the x.nexeed.ias.gpo.* exchanges to publish data:
-
read
-
write
-
configure
-
Relative Capacity: 1 incoming message per tenant, 1 outgoing message per master data changed event and 1 per replicated shift event