CSC/ECE 517 Spring 2023- NTNX-4. Extend NDB operator provision postregresql aws: Difference between revisions
(→Github) |
|||
| Line 16: | Line 16: | ||
==Test Plan== | ==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=== | ===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=== | ===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== | ==Future implementation== | ||
Revision as of 00:38, 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
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