cloud foundry summit 2015: using service brokers to manage data lifecycle
TRANSCRIPT
3
Primary
Primary
DR Backup
Snapshots
Business Critical Data LifecycleRTO 00:05 RPO 01:00First 12 hours
Replica
Backup
4
Primary
Backup Backup
Primary
Snapshots
Replica
Backup
Business Critical Data LifecycleRTO 00:05 RPO 01:00First 24 hours
DR
14
0 5475 copies doing nothing
for your business
16
Good code needs good tests.Good tests need good data.Good data needs… a copy.
A play in 3 acts
so lets get one!
21
Once you find a copy, it needs a curatorSizing (don’t use all of 10 TB of prod to test)
But your sample must represent the entirety of the dataset.
Representative curation is futile with most datasets (unknown unknowns).
Sizing means you restrict your tests to what you left in.
Sizing hides performance issues (missing index)
So maybe it’s not worth it….
27
The sum of the mess is worth more than its parts
There’s 5475 secondary copies with no load, can we leverage them for testing?
Fix: Let CF manage your data.
30
cf create-service
Copy Data
Sanitize Data
cf push <app>
Test
cf delete app -r -f
cf delete-service
Pattern:
32
Putting the E in Enterprise
Buy a CDM Product
Actifio, Delphix, ViPR
Great if they support your workloads!
And you can consume the form factors they deliver
33
Based on technology to allow layered writes
Layered FS (Docker, Docker, Docker)?
Clones, Linked Clones, VM Snaps
Writeable Snapshots (FlexClone, XtremIO, LVM Snaps)
Building is harder than buying
BYO
34
cf create-service
Snap Prod VM
Spin up VM
Allocate IP
Sanitize Data in PG
cf push demo
Test
Dispose
AMI and Postgres Demo
35
https://github.com/krujos/data-lifecycle-service-brokerplease help!