Before installing and deploying AOC, you should first familiarize yourself with the relevant concepts. This will help you better understand the installation and deployment process, as well as the functionalities of AOC.
AOC (Arcfra Operation Center)
A centralized management platform providing unified management of Arcfra clusters and their resources across multiple data centers.
ACOS (Arcfra Cloud Operating System) cluster
A logical concept. In a production environment, an ACOS cluster consists of at least three interconnected nodes.
AOC standalone mode
AOC is deployed as a single virtual machine instance. This deployment mode features a lightweight architecture, low resource consumption, and easy deployment, but it introduces the risk of a Single Point of Failure (SPOF). It is suitable for POC testing, edge sites, or non-critical scenarios where high continuity of the management platform is not required.
AOC high-availability cluster
A AOC high-availability cluster consists of an active node, a passive node, and a witness node, and adopts an active-passive architecture to provide continuous availability for the management platform. Through data synchronization and automatic failover mechanisms, the witness node monitors the cluster status and triggers automatic failover when the active node or its hosting environment fails. The passive node then takes over services, ensuring uninterrupted AOC management capabilities.
Active node
The core worker node of the high-availability cluster. This node handles all service traffic, processes user API requests, and issues commands to managed clusters. It is also responsible for synchronizing data changes to the passive node.
Passive node
A hot standby node of the high-availability cluster. This node maintains strong data consistency (RPO=0) with the active node through synchronous replication. Under normal circumstances, the passive node does not directly handle workload traffic. However, when the active node fails, the passive node will be automatically promoted to the active node to take over services.
Witness node
The arbitrator of the high-availability cluster. The witness node does not store service data and is primarily responsible for monitoring the health status of the active and passive nodes and responding accordingly. In specific failure scenarios, it initiates automatic failover to ensure the continuous availability of AOC.
Failover
Failover refers to the process in which services are switched from the active node to the passive node when the active node or its hosting environment fails, ensuring service continuity. This mechanism guarantees continuity for the management platform in failure scenarios with an RTO of less than 5 minutes.
AOC management IP
The IP address used for external access to AOC.
AOC HA IP
The IP address is used for internal communication between nodes, including status synchronization, heartbeat monitoring, and health reporting.
