Understanding AOS

  • 24 November 2020
  • 0 replies

Userlevel 2
Badge +2
  • Nutanix Employee
  • 12 replies

The Acropolis Operating System (AOS) provides the core functionality leveraged by workloads and services running on the platform



Building upon the distributed nature of everything Nutanix does, we’re expanding this into the virtualization and resource management space.  AOS is a back-end service that allows for workload and resource management, provisioning, and operations. 

This gives workloads the ability to seamlessly move between hypervisors, cloud providers, and platforms.


Acropolis Services: It is an internal service which runs on each CVM
An Acropolis Worker runs on every CVM with an elected Acropolis Leader which is responsible for task scheduling, execution, IPAM.

Acropolis Leader

  • Task scheduling & execution

  • Stat collection / publishing

  • Network Controller (for hypervisor)

Acropolis Worker

  • Stat collection / publishing

  • VNC proxy (for hypervisor)


Above diagram shows conceptual view of the Acropolis Leader / Worker relationship


Dynamic Scheduler

Efficient scheduling of resources is critical to ensure resources are effectively consumed. The AOS Dynamic Scheduler extends the traditional means of scheduling that relies upon compute utilization (CPU/MEM) to make placement decisions


Resource scheduling can be broken down into two key areas:

  • Initial placement

Where an item is scheduled at power-on

  • Runtime Optimization

Movement of workloads based upon runtime metrics

The original AOS Scheduler had taken care of the initial placement decisions since its release. With its release in AOS 5.0, the AOS Dynamic Scheduler expands upon this to provide runtime resources optimization.


For details please refer to 

Book of AOS

ACROPOLIS  Admin Guide


This topic has been closed for comments