High Availability Deployment

Service Overview

The EDB EFM Deployment Jump Start helps customers quickly deploy a highly available Postgres architecture using EDB Failover Manager (EFM) or Patroni. EDB Professional Services will leverage the EDB Trusted Postgres Architect (TPA) tool to ensure a repeatable, automated, and best-practice deployment.

The engagement includes the deployment of a High Availability (HA) cluster. The specific architecture depends on the selected complexity tier:

Scope of Service

Our Consultant will validate the prerequisites, configure and deploy the TPA tool, and validate Standard Operating Procedures (SOPs) for the agreed architecture:

• Onboard: Engagement preparation, review of prerequisites, and scope alignment
• Configuration: Configuration of EDB TPA for the specific EFM/Patroni architecture
• Deployment: Deployment of the EDB- supported Postgres cluster, including HA configuration, backups, and Postgres Enterprise Manager (PEM) for monitoring (if applicable)
• Validation: Quality checks, demonstration of the architecture, and review of Standard Operating Procedures (SOPs)
• Project Closure: Formal review of completion status and hand-off

Deliverables

• One (1) installed and operational EDB Postgres cluster

• EDB TPA configuration files (delivered electronically)

Roles and Responsibilities

EDB Project Manager:  Responsible for initial planning, task alignment, and project closeout.

EDB Senior Consultant: Technical Lead, responsible for prerequisite validation, TPA config and deployment, SOP Validation and documentation.

Customer Team: Responsible for providing the main point of contact for design requirements. Resources and Roles (or similar Technical Stakeholders) where input may be needed for the engagement include:

• Database Administrator
• System Architect
• Infrastructure Manager 
• Network Administrator
• Security Officer

Assumptions

• A project kickoff will be conducted to review the service scope and confirm the schedule
• This service is delivered remotely unless otherwise agreed
• EDB will deploy the architecture with any EDB-supported version of Postgres. 
• Deployment is for a non-production environment (no live traffic)
• EDB TPA will be used for deployment
• Customer environment is not air-gapped (unless "Air Gapped Repo Setup" is purchased separately)
• Performance testing and application readiness are not in scope
• Customer will provide the names, title, email, phone number, and area of responsibility of those participating. One person will be designated as the main contact, and will be able to provide access to the people most knowledgeable about the topics to be discussed or examined. 
• Customer will make appropriate personnel available to assist EDB in the performance of the services as needed and requested by EDB in a timely manner so as not to disrupt the project schedule. 
• Customer will not provide Personal Data (as defined in applicable law). Customer agrees that it will work with EnterpriseDB to ensure that all such data is not provided.  
• Customer will ensure timely access to all systems through screen sharing and experts including third parties as required. 
• Customer will assign the appropriate resources with the appropriate privileges for the task being planned for any screen sharing sessions as needed throughout the engagement.
• Customer will provide timely feedback on all deliverables. Deliverables without commentary within 5 business days will be deemed as delivered.
• Security integration (LDAP/AD) is not included.
• EDB will configure the HA software on the database nodes. The Customer is responsible for configuring application-side connection strings, Virtual IPs (VIPs), or external Load Balancers to route traffic to the active Primary node or, when "Connection Pooling" is explicitly included in the tier, to the active connection pooler instance.

Prerequisites

• Customer will provide resource availability for workshop planning and a point of contact for coordination. 
• Server prerequisites will be prepared by the customer team before the kickoff of the project.
• Customer is responsible for providing all necessary internal design and project related documentation and requirements where EDB is required to analyze, operate, or modify customer implemented systems.
• A separate server is allocated for the deployment of EDB TPA.
• The TPA user must have password-less SSH and sudo privileges to perform package installation and service management across all target nodes.
• Customer security team has approved all required software packages.
• Customer to provide a minimum of three (3) server nodes to achieve a quorum-based HA architecture (e.g., 2 Data Nodes + 1 Witness or 3 Data Nodes).

Standard Operating Procedures

EDB will validate the below test cases as part of the validation process: