Grounded in the Cloud
cancel
Showing results for 
Search instead for 
Did you mean: 

4 Database Deployment Solutions for HPE Helion OpenStack

Stephen_Spector

Guest Post: Tim Cuddy, HPE Helion Product Management

four.jpg

One of the primary goals for most organizations planning cloud deployments is to provide a self-service deployment system that enables users to very quickly create and access infrastructure services in minutes without having to use traditional ticketing-based services that often take days, weeks, and possibly months before the requested service is provisioned.  At the same time, organizations often want to collect usage metrics to either publicly monetize services for public access or provide usage showback and possibly even chargeback invoices to internal users.  This deployment flexibility is very appealing to organizations because the benefits of faster deployments can often provide direct benefit to the bottom line of an organization increased productivity and profit.

Cloud architects are now expanding services beyond infrastructure to functions like self-service database deployments.  The primary purpose of a database system is to be a repository for application data.  The challenge of providing a cloud-based, database deployment service is to balance the flexibility of self-service with well-known and common database system production requirements that include functions like predictable performance, standardized provisioning and configuration, high availability including disaster recovery functions and planning, data replication and encryption, policy and certification compliance, software patching processes and upgrades, and active monitoring and usage metrics collection.

To facilitate a deployment decision it is always best to focus on the desired use cases, identify the requirements of those use cases, blend in organizational policies and the choose the database deployment model that best fits all of those parameters.  The following are common database deployment use cases and some recommendations for supporting those use cases.

  • Complying with existing enterprise database deployment standards and processes - Enterprise IT organizations may already have a set of organizational policy and requirements that include standardized provisioning, supported database systems, and access control.  The combination of the HPE Cloud System or CSA and Database and Middleware Automation or DMA products enable a cloud administrator to provide a self-service deployment system with many common database systems via pre-designed and supported deployment models while maintaining access control, tracking licensing, providing updates, patches and upgrades,  and ensuring organizational policy compliance.  More about the HPE DMA product can be found at http://www.hp.com/go/dma.
  • OpenStack service focused on database deployment - The OpenStack Trove service provides a REST API that enables the deployment of a variety of SQL and NoSQL database systems.  Developers can create new databases via the OpenStack Horizon web interface or via the Trove API and CLI.  A company called Tesora provides a Database as a Service product that includes the installation of the Trove service alongside the Helion OpenStack control plane and integrates the Trove service with the OpenStack identity, networking, and compute services.  More information about the Tesora Database as a Service product can be found at http://www.tesora.com.
  • Basic, image-based deployment - An alternative to a full orchestration system such as CSA and DMA or the OpenStack Trove service is to create images that can be chosen by users from the Helion OpenStack image library when creating a new compute instance.  These images would continue the supporting operating system and a pre-configured database system.  This option may be desirable for deployment use cases where only a single database system is required and concerns about licensing and other common deployment requirements are not as stringent.
  • Use existing database systems – An alternative to deploying database system in Helion OpenStack is to simply use existing database systems.  These database systems can be accessed by Helion OpenStack-hosted applications using common connection methods like ODBC or JDBC.  This option is particularly appealing for multi-staged Helion OpenStack deployments where the focus is initially standing up a self-service infrastructure to support the deployment of existing applications or new cloud native applications.

In summary, providing a self-service, “database as a service” should be carefully considered based on current organizational IT policies and requirements, target use cases, and the available deployment options.

Senior Manager, Cloud Online Marketing
  • HPE Cloud
0 Kudos
About the Author

Stephen_Spector

I manage the HPE Helion social media and website teams promoting the enterprise cloud solutions at HPE for hybrid, public, and private clouds. I was previously at Dell promoting their Cloud solutions and was the open source community manager for OpenStack and Xen.org at Rackspace and Citrix Systems. While at Citrix Systems, I founded the Citrix Developer Network, developed global alliance and licensing programs, and even once added audio to the DOS ICA client with assembler. Follow me at @SpectorID

Events
28-30 November
Madrid, Spain
Discover 2017 Madrid
Join us for Hewlett Packard Enterprise Discover 2017 Madrid, taking place 28-30 November at the Feria de Madrid Convention Center
Read more
See posts for dates
Online
HPE Webinars - 2017
Find out about this year's live broadcasts and on-demand webinars.
Read more
View all