Postgres Distributed (PGD) Deployment

Service Overview

The EDB PGD Deployment Jump Start delivers an extreme high-availability architecture using EDB Postgres Distributed (PGD) software. Designed for mission-critical always-on capabilities, this engagement uses EDB TPA to deploy a distributed cluster across single or multiple locations, in single or multi master configurations.

The engagement deploys an Always-On PGD architecture based 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 PGD architecture
• Deployment: Deploy PGD architecture (Data nodes, Proxy nodes, and Witness nodes as required), backups, and monitoring.
• Validation: Quality checks, demonstration of the architecture, review of Standard Operating Procedures (SOPs) and briefing on PGD Conflict Resolution and its impact on application behavior.
• Project Closure: Formal review of completion status and hand-off

Deliverables

• One (1) installed and operational EDB Postgres Distributed 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
• 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.

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.
• The TPA user must have password-less SSH and sudo privileges on all target nodes (including Data, Proxy, and Witness nodes) to perform automated software installation, configuration, and service management.
• Customer security team has approved all required software packages.
• Customer to provide a minimum of three (3) server nodes per data center to achieve a quorum-based HA architecture (e.g., 2 Data Nodes + 1 Witness or 3 Data Nodes).
• Customer will set an umask of 022 on all servers.
• Customer confirms that all tables in the target database(s) have Primary Keys, as required for PGD logical replication
• For the Medium and Large tiers - In order to validate the data center failure SOP,  customer agrees to simulate a network outage between sites.

Standard Operating Procedures

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