2. LINUX CONTAINERS:
Software packaging concept that typically includes an
application and all of its runtime dependencies
HIGHER quality software releases
SHORTER test cycles
EASIER application management
CONTAINER CONTAINER
APP
LIBS
HOST OS
SERVER
APP
LIBS
BENEFITS
3. WHAT’S THE BIG DEAL?
BARE METAL VIRTUALIZATION CONTAINERS
Deploy in Days or Weeks
Single App Instance
Deploy in Hours or Days
10s or 100s of Apps
Deploy in Seconds or
Minutes
100s or 1000s of Apps
APP
LIBS
HOST OS
SERVER
HOST OS
SERVER
HOST OS, SHARED SVCS
SERVER, CLOUD
APP APP
LIBS LIBS
GUEST OS GUEST OS
VIRTUAL
MACHINE
VIRTUAL
MACHINE
APP APP
LIBS LIBS
CONTAINER CONTAINER
HYPERVISOR
4. CONTAINER WORKLOADS?
“For which workloads or application use cases have you used/do you anticipate to use containers?”
Data Apps
Cloud Apps
Systems of
Engagement
Systems of
Record Web and Commerce
Software
Mobile Apps
Social Apps
77%
71%
62% 62%
57% 52%
46%
Base: 194 IT operations and development decision-makers at enterprise in APAC, EMEA,
and North America Source: A commissioned study conducted by Forrester Consulting on behalf of Red Hat, January 2015
Scalable, Cost Effective, Distributed Storage for Containers
5. THE RED HAT STACK — FROM PAAS TO STORAGE
DevOps Tools and User Experience
Language Runtimes and Middleware
Databases and Other Services
Container Orchestration and Management
Container API Container Host
Storage
6. WHY CONTAINERS REQUIRE PERSISTENT STORAGE
• Web & presentation layers should be stateless ... but ...
• That’s probably < 5% of all application instances in a DC
• Most other infrastructure applications / services require persistence for storing
application and configuration data
• Building a different infrastructure for stateful vs. stateless apps ?
• Modern IT requires Standardization (e.g. Cloud Computing)
• Software-defined DC is a hybrid cloud enabler
7. REQUIREMENTS FOR CONTAINER STORAGE
• Scalable – Scale out capacity & performance
• Resilient – Likely there will be important data
• Flexible – Allow different application access profiles
• Software-defined – To allow flexible deployment models
• Open – For customer choice and lowest TCO
RED HAT
STORAGE
8. PERSISTENT STORAGE REQUIRES REDUNDANCY
• Red Hat Storage includes important data redundancy features
• 2-way and 3-way replication
• Erasure Coding
• Geo-Replication
• Snapshots
9. STORAGE INNOVATION FOR
CONTAINERIZED APPLICATIONS
AUTOMATED CONFIGURATION
SINGLE CONTROL PANEL
CHOICE OF PERSISTENT STORAGE
Ceph RBD
Amazon EBS
Fiber Channel
GCE
iSCSI
NFS
GlusterFS
10. CONTAINER-NATIVE STORAGE
DRIVING THE FUTURE OF STORAGE
Nov 2015 Mar 2016 Summer 2016
RHGS Container
CONVERGENCE OF STORAGE AND COMPUTE
Dedicated storage cluster for containerized
and PaaS environments
Supported for OpenShift Enterprise
Containerized Red Hat Gluster Storage serving
storage from a dedicated storage cluster
Optimized for applications running on RHEL 7,
OpenShift Enterprise, and RHEL Container Host
Containerized Red Hat Gluster Storage inside
OpenShift Container Platform hyper converged with
application containers
Red Hat Gluster Storage cluster
comprised of disks from multiple container
cluster nodes
CONTAINER READY STORAGE CONTAINERIZED RHGS
14. CUSTOMER SUCCESS
APPLICATION
SERVERS
CONVERGED
SERVERS
STORAGE
SERVERS
NEW AGILITIES allowed telco to bring a new offering to market faster and cheaper
LOWER COST than traditional storage and avoiding endless commitment to proprietary vendors
FLEXIBLE geo-replicated architecture can grow/shrink dynamically
OPTION to be tuned for price or performance
BENEFITS
HYPER CONVERGED STORAGE
Applications and storage can co-exist on the same hardware
Higher server utilization and lowers operational costs
Storage generates only 3%-10% overhead on compute servers