10 things we learned about devops and data

15
Top 10 Things We Learned About DevOps and Data Val Bercovici Cloud Czar, NetApp @ valb00

Upload: perforce

Post on 22-Jan-2018

341 views

Category:

Software


0 download

TRANSCRIPT

Top 10 Things We Learned About DevOps and DataVal Bercovici

Cloud Czar, NetApp

@valb00

Top 10 Things We LearnedAbout DevOps and Data

Val Bercovici

Cloud Czar, NetApp

@valb00

Full Stack / #NoStack / #ThreeStack (Storage)

12factor

Automation

Infrastructure

• I – Codebase

• IV – Backing Services

• XI – Logs

• Ephemeral, Persistent, Shared

• Perf, Capacity, Quota COST

• Build, Test, Deploy, Monitor

• Protocol, Media, Volumes

• Tiering, QoS, MP-HA, RepCount

• RAID, EC, (T10,11,13)

@earlruby

SNIA NVM Summit

1. Storage is Different

2. (Code & Data) Size Matters

Applications are getting bigger

Backing Service (data) growth

Results in

Longer code checkout, build and test time

Bigger load on revision control systems

Git, RCS, SVN, Perforce

Testing Sample vs Real data

Larger storage debt

Checkout Build Test

3. Speed Matters (UX, Dev Team Iteration)

FEEDBACK DEVELOP

TEST

DEPLOY

MONITOR

Measure and Monitor

4. Globalization Matters

Distributed development

Multiple business units, geographies

Global Consistency

Long repo / dependency sync times

Reproducibility

Compute and storage requirements

Infrastructure Debt

Maintaining, managing servers, storage (build farms)

Slower development time, time to market

Inelastic resources requires sizing for peak workloads

5. We’re in the 2nd inning (Land Grab)

@kvaes - Data Persistence Semantics:Container : An upgrade of the container will not scratch the dataHost : A host failure will not result in data loss

Default : No Data PersistenceData Volumes : Container PersistenceData Only Container : Container PersistenceHost Mapped Volume : Container PersistenceHost Mapped Volume,backed by Shared Storage : Host Persistence

Extensions:Convoy Volume Plugin : Host PersistenceClusterHQ/Flocker Plugin : Host PersistenceSolidFire Native Docker Plugin : Host PersistenceEMC REX-Ray Volume Plugin : Host Persistence

VIII. App Concurrency / Data Consistency @ScaleIX. Disposability

Automatically Register Containerized Applications with Snap Creator

9. Data Lifecycle has Many PhasesNot yet incorporated into Container Frameworks

• Creation / Capture• Resiliency / Availability• Protection (RPO/RTO)• Management• Governance• Control• Transparency• Authenticity• Retirement• Destruction

10. Coding Containers (@Scale) Can Be Easy

Key Benefits 10x Faster workspaces from

SCM Under two minutes for large

codebases

40x Faster builds with prebuilt object files

NFS directories for developer sandboxes

Distributed software development environment (2000 Dev’s!)

Continuous integration with minimal storage foot print

Faster feedback loop Keep the code lines stable

Resources / Credits

Manifestos:http://12factor.net/

Blogs:https://kvaes.wordpress.com/2016/02/11/docker-storage-patterns-for-persistence/

Infra Developer Resources:https://github.com/NetApp/CodeEasy

https://netapp.github.io/openstack/2015/12/15/building-a-distributed-docker-registry-at-scale/

https://netapp.github.io/openstack/2015/12/08/containers-mongodb-mesos-marathon/

https://netapp.github.io/openstack/2015/11/12/containers-snapcreator/

http://www.solidfire.com/blog/now-available-solidfire-plug-in-for-docker/

http://www.slideshare.net/Apcera/policybased-cloud-storage-persisting-data-in-a-multisite-multicloud-world

http://pmem.io/

Storage (NV)Memory:http://www.snia.org/events/non-volatile-memory-nvm-summit

Val Bercovici

Cloud Czar, NetApp

@valb00

Thank You