Five Acceptance Steps as a Script: GBase Database Deployment Validation

Deploying a GBase Database does not guarantee readiness for use. To ensure a successful installation, a series of acceptance steps must be followed. This article outlines five essential steps for validating a GBase Database deployment, along with a Bash script to automate the process.

Step 1: Verify the Installation Result

After running the installation command, examine its output. A successful installation returns a specific JSON structure. The script should focus on the return code, rather than simply checking for output. While installation success is the first checkpoint, it does not confirm all components are running or clients can connect.

Step 2: Check Cluster Health

Use the gha_ctl command to inspect the cluster's health. Review four key sections: gha_server, gtm, coordinator, and datanode. The acceptance criteria require no stopped or unstable instances, exactly one primary in each Data Node (DN) group, and all DCS nodes in a healthy state. The script should parse the monitoring output by section, rather than relying on fixed line numbers, as deployment layouts may vary.

Step 3: Verify Listening Ports

Confirm that the expected database services are listening for connections. Use the ss command to check for specific ports, such as 5432 or 15432, which should be defined in the deployment configuration. Additionally, check the listening address to ensure it matches the intended network access configuration. Simply verifying the port number may produce a false sense of readiness.

Step 4: Test Database Connectivity

Use the gsql command to execute a simple SQL statement, verifying that the target database instance can accept a client connection and execute a basic query. This step is more reliable for automation than waiting for an interactive prompt or manually checking the terminal. For GBase Database (8c), this step confirms the database can handle client connections and execute queries.

Step 5: Validate Read and Write Operations

The final acceptance step should execute a complete create-insert-select sequence. Create a temporary database, table, insert data, then query the table to verify the operations succeed. After validation, remove the temporary database to clean up. This step provides stronger evidence that the database is ready for basic application integration.

Building the Acceptance Script

The acceptance script follows a simple structure, with one function for each step. Functions include:

- check_install: Verifies the installation result

- check_cluster: Inspects the cluster's health using gha_ctl

- check_ports: Validates expected listening ports and addresses

- check_connection: Tests database connectivity with gsql

- check_read_write: Validates read and write operations using create-insert-select

The script should print a PASS or FAIL message for each step, indicating success or failure. A log file is created to record execution details, including hostname and timestamp. The script adheres to three implementation principles: fail fast (stop when a critical step fails), keep execution records, and reuse deployment configuration.