CSC/ECE 517 Spring 2023- NTNX-4. Extend NDB operator provision postregresql aws: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 14: Line 14:
==Implementation==
==Implementation==


1. Get access to Nutanix Database Service SASS and access keys for the AWS EC2 instance.
*Get access to Nutanix Database Service SASS and access keys for the AWS EC2 instance.


2. Add secrets for NDB operator to connect to the Nutanix DB Service - SASS and the postgres DB to the secret.yaml file.
*Add secrets for NDB operator to connect to the Nutanix DB Service - SASS and the postgres DB to the secret.yaml file.


3. Implement code changes for the remote provisioning of databases.
*Implement code changes for the remote provisioning of databases.


4. Analyze common characteristics between the current struct and the structs needed for cloud platform provisioning.
*Analyze common characteristics between the current struct and the structs needed for cloud platform provisioning.


5. Test the API endpoints using postman.
*Test the API endpoints using postman.


6. Implement struct changes in database_types and functions for building provision request.
*Implement struct changes in database_types and functions for building provision request.


==Test Plan==
==Test Plan==

Revision as of 00:49, 22 March 2023

NTNX-4. Extend Nutanix Database Service Kubernetes operator to provision Postgres Single Instance databases on AWS EC2

Problem Statement

Nutanix Database Service is the only hybrid cloud database-as-a-service for Microsoft SQL Server, Oracle Database, PostgreSQL, MongoDB, and MySQL. Efficiently manage hundreds to thousands of databases. We need to extend the Nutanix Database Service Kubernetes operator to provision Postgres Single Instance databases on AWS EC2.

Architecture

Workflow

Implementation

  • Get access to Nutanix Database Service SASS and access keys for the AWS EC2 instance.
  • Add secrets for NDB operator to connect to the Nutanix DB Service - SASS and the postgres DB to the secret.yaml file.
  • Implement code changes for the remote provisioning of databases.
  • Analyze common characteristics between the current struct and the structs needed for cloud platform provisioning.
  • Test the API endpoints using postman.
  • Implement struct changes in database_types and functions for building provision request.

Test Plan

1. Verify the proper functioning of the updated code by creating, deleting, updating, and watching the Database resources using the Kubernetes API.

2. Test the API endpoints using postman to ensure the correct payload is being sent and received.

Actions to be taken before testing

1. Obtain access to Nutanix Database Service SASS and access keys for the AWS EC2 instance.

2. Add the appropriate credentials to the secrets.yaml file.

Things to test

1. Ensure the proper functioning of the updated code with both on-prem and cloud remote types.

2. Verify that the correct API endpoints are being hit based on the remote type specified.

3. Test the connectivity between the K8 service and the deployed DB on EC2.

Future implementation

Github

https://github.com/arvindsrinivas1/ndb-operator/tree/arvind/dbtypes_changes

Contributors