Using container-native storage: Myths and best practices

Container-native storage (CNS) provides vendor-agnostic persistent storage for Red Hat OpenShift on private or public clouds. It has a broad set of features that administrators can easily use immediately and is flexible enough to meet a variety of deployment scenarios. However, this flexibility can lead to confusion around what you need or what resources you'll use.

This mini-session will focus on common myths and provide an overview of best practices for deploying and running CNS, such as:

- Does storage need to be collocated with OpenShift applications?

- How much memory and CPU is needed?

- Where should CNS run within the OpenShift cluster?

Learn about all this and more to demystify storage for containers and provide an optimal experience for your OpenShift developers.

  • Date:Thursday, May 10
  • Time:11:15 AM - 11:35 AM
  • Room:2010
  • Location:Moscone West - 2010
  • Session Type:Mini Session
  • Session Code:M1795
  • Best for people who:Manage infrastructure, Design application/system architectures
  • Products and Services:Red Hat OpenShift Container Platform, Red Hat Gluster Storage
  • Primary solution:Storage
  • Technical difficulty:Working knowledge required
  • Industry:
  • Session Includes:None of the above
  • Topic(s):Containers, Infrastructure modernization and optimization, Software-defined storage
  • Time slot:Morning
Jose Rivera
Red Hat, Inc.