With the release of Era version 2.3 in late September 2021, which i wrote a blog post about here, the Era Management Plane was improved when it comes to providing high availability (HA) meaning it does not include any single point of failure (SPOF) anymore.
Era Management Plane consists of two service groups:
- Front-end services (API, agent, web service).
- Back-end service (database or repository).
Prior to Era 2.3. there was an option to deploy the Era Management Plane in HA mode for both back-end and front-end services which according to the above mentioned service groups should have been enough:)
When deploying Era in HA mode there is also a logical component called HA proxy which is used by the front-end services to communicate with the back-end service. With Era version 2.3 you can deploy the HA Proxy VMs in different Nutanix clusters hence no SPOF based on Nutanix clusters exists anymore.
The below figure describes the logical architecture.
The number of virtual machines required for an Era Management Plane HA configuration are listed in the below table.
| HA configuration, single Nutanix cluster |
At least nine: — Three VMs providing the front-end services (API, agent, web). — Two VMs providing an HA proxy service. Used by the front-end services to communicate with the back-end service. — Three VMs providing the back-end service (Postgres DB cluster). — One VM runs the Era management agent. |
| HA configuration, multiple Nutanix clusters |
At least ten: — Three VMs providing the front-end services (API, agent, web). — Two VMs providing an HA proxy service. Used by the front-end services to communicate with the back-end service. — Three VMs providing the back-end service (Postgres DB cluster). — One VM in each Nutanix cluster that runs the Era management agent. |
Download your copy of the Era Management Plane Availability document i have updated to reflect the Era 2.3 capabilities.
————————————————————————————————————————————————————————-
