Turning pets into cattle - the stickiness of data

Dr Yih Leong Sun, Chris Cannon, Gerd PrüßmannApril 26th, 2016, 3:40pm-4:20pm

Introduction

Dr Yih Leong SunSenior Cloud Architect

Intel

Gerd PrüßmannDirector Cloud Solutions

Mirantis

Chris Cannon Cloud Engineering ManagerHewlett Packard Enterprise

Reference: https://wiki.openstack.org/wiki/Enterprise_Working_Group

What is this session NOT about?

Continuous Integration and Continuous DeploymentAutomation Techniques for Infrastructure, Deployment, and OperationsAgile Development Practices

It’s an application architecture discussion

Agenda

• Recap of previous presentation• The stickiness of data

– Data challenges– Strategies

• Q & A

Previous presentation

Pets vs Cattle

Reference: https://www.openstack.org/assets/Uploads/presentation-turning-pets-into-cattle.pdf https://www.openstack.org/summit/tokyo-2015/videos/presentation/turning-pets-into-cattle-a-demonstration-to-provoke-discussion

Reference: http://www.openstack.org/assets/pdf-downloads/business-perspectives.pdf

Virtualization vs Cloud

Architecture design

Conventional App ● Monolithic● Centralised state● Tightly coupled● Synchronous● Single tenancy

Cloud-aware App● Distributed● Microservices● Asynchronous● Multi-tenancy● Failure-resilience● Share-nothing● Eventually

consistent

vs

Reference: http://www.opendatacenteralliance.org/docs/architecting_cloud_aware_applications.pdf

Multiple strategies

VM

VM

VM

Web

App

DB

Web

App

VM

VM

VM

Web

App

DB

w1w2a1a2

w1

a1

static content

Data stickiness

Data challenges

• Every Pet is different• Challenges of existing data

– How to migrate existing data to the cloud?• Data migration: file copying, hot/cold export, machine copying,

continuous replication …• Integrity, consistency, licensing & down time

– Data virtualization• SLA (policies, performance, RTO, RPO, etc ...)• What is your current situation and limitation?

Data strategies

Option 1 - No change to backend data store

• Lower migration risk by using existing DB deployments• Most PaaS systems can connect to legacy DB

environments• Continue to leverage capabilities that may not be fully

available in cloud-based DB today

Option 2 - ‘Cloudifying’ RDBMS / Example

*Other names and brands may be claimed as the property of others.

Pros

• Known technology / operational tasks• Leverages DB scalability

Cons

• Limitations / reqs to the schema• Not all engines available• Operational tasks remain• Automation efforts

Option 2 - ‘Cloudifying’ RDBMS / Trove

• Openstack DBaaS project offering self-service provisioning functionality for RDBMS and non-RDBMS

• easy on-demand DB consumption

• multiple DB instances per user• resource isolation• task automation for

deployment, config, patching etc.

Cassandra, CouchBase, CouchDB, DataStax Enterprise, DB2, MariaDB, MongoDB, MySQL, Oracle, Percona Server, PostgreSQL, Redis and Vertica

Option 2 - ‘Cloudifying’ RDBMS / TroveKey Features Capability Client Database

PerformanceGeneral Purpose (SSD) Storage Yes - Relies on OpenStack Cinder storage capabilityProvisioned IOPS (SSD) Storage Yes - Relies on OpenStack Cinder storage capability

ScalabilityPush-button Compute Scaling Limited - Requires manual expansionEasy Storage Scaling Limited - Requires migration to new database

Availability and Durability

Automated Backups Limited- Requires external backup solutionDatabase Snapshots Limited - Requires external backup solution

Multi-AZ DeploymentsYes - Limited to a single OpenStack environment. No option to specify specific AZ.

DR with Multi-Site/multi-Region Deployment NoAutomatic Host Replacement No

Security

Encryption at Rest and In Transit LimitedNetwork Isolation YesResource-level Permissions Yes

Manageability

Monitoring and Metrics No - Requires external monitoring solution. No SLA calculation.Automatic Software Patching No - Requires external patching solutionDB Event Notifications No - Requires external notification solution

Metering Collect usage metrics for billing No current usage metrics are emitted by Trove

Example: WordPress*

• Use alternative ‘cloud-native’ DB backends for WordPress ?– Official WordPress supports MySQL* / MariaDB* engines only– PostgreSQL* ongoing– NoSQL backend not planned

• Codebase: MySQL centric• Approaches:

– Status Quo: Development for MySQL only• Fork necessary for every new database type (costly for porting)

– WordPress specific database abstraction layer– Full database abstraction layer

Reference: https://codex.wordpress.org/Using_Alternative_Databases *Other names and brands may be claimed as the property of others.

Option 3 - RDBMS to NoSQL

• Why should I migrate from RDBMS to NoSQL?

Database Example Use Case

NoSQL Cassandra*, MongoDB*

IoT, BigData, Widely distributed architectureunstructured data

RDBMS MySQL*, MSSQL* OLAP, OLTP, ACID, structured data

Reference: https://www.mongodb.com/collateral/rdbms-mongodb-migration-guide*Other names and brands may be claimed as the property of others.

Option 3 - RDBMS to NoSQL

• Migration tactics– Build your own scripts, ETL, Hadoop– Snapshot and incremental– Application-driven

• Keeping data in both RDBMS & NoSQL concurrently during transition period

• On-demand

Summary

• Understanding your Pets• Some existing database technologies are not designed for Cloud• Differences in design principle between RDBMS & NoSQL• Transformation from existing environment to Cloud ‘culture’• Skillsets and training for Ops and Dev

Q & A

OpenStack Enterprise Working Group

• Objective: To identify and remove barriers to Enterprise adoption and deployment of OpenStack*.

• Mailing List:http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg

• Meeting Logistics: Thursday 1700 UTCCall In Info: (888) 875-9370, Bridge: 3; Passcode: 9518007#

JOIN US!

*Other names and brands may be claimed as the property of others.

Thank you

yih.leong.sun@intel.comccannon@hpe.comgpruessmann@mirantis.com

Legal Disclaimer

OpenStack is a registered trademark of the OpenStack Foundation in the

United States, other countries or both.

Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or

other countries.

Mirantis, and the Mirantis Logo are registered trademarks that belong to

Mirantis Inc.