Red Hat OpenShift Database Access Service Definition

Updated -

Introduction

Database is one of the key building blocks for a variety of applications. Currently most openshift customers run their databases on the same cluster, manage it themselves and provide access to developers. Database as a service makes this much simpler, allowing databases to run at a central location managed by database administrators allowing business to focus on their applications.

The Red Hat Database as a service add-on enables:

  • Easy consumption of Database as a service from ISVs like MongoDB Atlas, Crunchy Bridge, and CockroachCloud on kubernetes clusters
  • Easy management, monitoring and control by administrators of DBaaS consumption, usage, status across cluster and clouds
  • Enables end to end managed support experience

For Alpha release DBaaS Add-on enables ease of consumption for developers and simple management for administrators on one managed OpenShift Platform (OSD and ROSA) . There is a prerequisite that a customer has bought (or enrolled in a trial version for) the DBaaS instances from ISV vendor MongoDB Atlas or Crunchy Bridge.

DBaaS project is developed and productized using iterative development processes to allow feedback from users, enable/help ISV develop the required functionality and quickly release those to users. Following sections are focussed on the service definition as planned for Alpha release of DbaaS.

Red Hat Database as a Service Add-On Functionality

Administrator (Database/Cluster Admin) - Discovery /Provider Account Creation

Red Hat Database as a Service operator enables admins to discover purchased DBaaS instances on the managed cluster and enable developers/users of managed cluster to consume/connect to them.

For alpha release, the discovered instances and the privileges to use them will be dependent on the admin privilege with the ISV SaaS vendors. Admin needs to use the ISV specific credentials and assign those privileges to developers.

Administrator (Database/Cluster Admin) - Monitoring

Red Hat Database as a Service operator enables admins to monitor all the DBaaS instances that are discovered, used (by whom and how) through the admin dashboard.

Developer (Database/Namespace users) - Discovery / Provider Account Creation

Red Hat Database as a Service operator enables developers/namespace users to discover and connect to DBaaS instances assigned/allocated by admins. In the workflow developers will have MongoDB Atlas instances available and can create connections to them.

Developer (Database/Namespace users) - Application Binding using Service binding operators

From the developer catalogue topology view, developers can simply connect their services/applications to a database (discovered earlier) by drag and connect options. This uses a service binding operator framework to connect the application to the instance, restart the app pod if needed.

Configuration/Deployment of DBaaS Operator - Alpha

DBaaS uses managed services add-on workflow. Customers need to purchase the DBaaS add-on SKU. This SKU will enable customers to deploy the DBaaS operator on their cluster. DBaaS operator will deploy needed MongoDB Atlas and Crunchy Bridge Operator.

Supported ISV DBaaS

For the Alpha release we will support MongoDB Atlas and Crunchy Bridge DBaaS. For Beta, we will extend this to CockroachCloud.

Provisioning, Billing - Alpha

Red Hat Database as a Service for Alpha release will not support provisioning, metering or billing of DBaaS ISV instances. Users need to provision and purchase DBaaS instances from ISV and use $0 trial DBaaS add-on to consume this service.

Red Hat OpenShift Dedicated -Alpha

The Red Hat DBaaS add-on will be available only on the AWS versions of Red Hat OpenShift Dedicated.

Red Hat OpenShift Dedicated can be configured to be private, public, or public/private. Red Hat DBaaS Add-On is available in all of those configurations. However, if Red Hat DBaaS Add-On is configured to be private, the service will not be able to integrate with DBaaS backend instances (services not on Red Hat OpenShift Dedicated).

Environment Isolation for Development, Testing/Staging, and Production

DBaaS add-on works on DBaaS Control planes. Database instances are hosted and managed by corresponding ISV. Any isolation, testing/staging etc planning need to be done with specific instances independent of DBaaS Add-On path.

Security and Compliance - Alpha

DBaaS add-on works on DBaaS Control planes without interfering or getting into data pathways.. Database instances are hosted and managed by corresponding ISV. These instances are provisioned, configured and billed at the ISV site inheriting the configured attributes.

The Red Hat managed services and applications inherit the security and compliance protocols from the Red Hat OpenShift Dedicated environment. As such, ISO 27001 and PCI certifications are in process, with future work planned for FedRAMP.

Logging & Metrics

Red Hat DBaaS add-on plans to collect usage metrics. Exact metrics and mechanisms are being defined.

Red Hat DBaaS add-on will use the operator framework to collect metrics and logs.

Resource Requirements and Recommendations

When you install and configure the Red Hat DBaaS add-on, on a given cluster, users will have access to DBaaS instances as long as they have a valid network path. We recommend connecting to the DBaaS instance on your AZ, Region, Cloud for latency sensitive applications.

Red Hat DBaaS add-on consumes negligible resources.

Backups
Database instances are hosted and managed by corresponding ISV. These instances are provisioned, configured and billed at the ISV site inheriting the configured attributes. We recommend configuring backup of the database instances when provisioned at ISV site.

Independent of the above, core infrastructure components of the OpenShift cluster are backed up using the snapshots functionality of the underlying AWS EBS instances. These snapshots are stored in the AWS account that the OpenShift cluster is deployed into. As such, sufficient AWS quota for EBS functionality is required.

Default Resource Requirements
Negligible.

Scalability and Service Levels

The Red Hat Database as a Service add-on does not have any defined limits on the number of DBaaS instances it can support. Any limitations are based on resources available in the cluster and usability limits on OpenShift Console.

Updates and Upgrades

Upgrades of the Red Hat Database as a Service add-on operator can be applied manually or automatically.

Availability

Red Hat Database as a Service add-on only works on the control path of DBaaS instances. The availability of DBaaS instances will be dependent on what user has configured at the ISV backend independent of Managed OpenShift clusters.

Backups and Disaster Recovery

The Red Hat OpenShift Dedicated environment is backed up daily. Note that this does not include user data stored in database instances. Database instances are hosted and managed by corresponding ISV outside OSD clusters. These instances are provisioned, configured and billed at the ISV site inheriting the configured attributes. We recommend configuring backup of the database instances when provisioned at ISV site.

In the event of a catastrophic failure, Red Hat SREs will use a [commercially reasonable approach[(https://access.redhat.com/solutions/710953) to recover your Red Hat OpenShift Dedicated environment.

Service Removal

You can remove Red Hat Database as a Service add-on from your Red Hat OpenShift Dedicated cluster via the standard add-on deletion flows. Once this operation is invoked, this action is non-reversible and cannot be undone. Deletion includes the automatic removal of all Red Hat DBaaS add-on components. This deletion does not impact DBaaS instances or data stored in them as they are hosted and managed by ISV in their environment.

Getting Support

As a Red Hat Database as a Service add-on Trial customer, you have access to the Red Hat Engineering who will be directly supporting this via the email - dbaas-alpha-support@redhat.com. To achieve the best resolutions, open a case whenever you have a question or issue. When opening a support case for the Red Hat Database as a Service add-on, select the product named “Red Hat OpenShift Database Access.”

Comments