Solution Brief: + Ceph done right for OpenStack The rise of OpenStack For years, the desire to standardize on an OpenStack deployments vary drastically open platform and adopt uniform APIs was as business and application needs vary the primary driver behind OpenStack’s rise By its nature and by design from the outset, OpenStack introduces across public and private clouds. choice for every aspect and component that comprises the cloud system. Cloud architects who deploy OpenStack enjoy Deployments continue to grow rapidly; with more and larger a cloud platform that is flexible, open and customizable. clouds, deep adoption throughout users’ cloud infrastructure and maturing technology as clouds move into production. Compute, network and storage resources are selected by business requirement and application needs. For storage needs, OpenStack OpenStack’s top attributes are, not surprisingly, shared by the most cloud architects typically choose Ceph as the storage system for its popular storage software for deployments: Ceph. With Ceph, users scalability, versatility and rich OpenStack support. get all the benefits of open source software, along with interfaces for object, block and file-level storage that give OpenStack what While OpenStack cloud architects find Ceph integrates nicely it needs to run at its best. Plus, the combination of OpenStack without too much effort, actually configuring Ceph to perform and Ceph enables clouds to get faster and more reliable requires experienced expertise in Ceph Software Defined Storage the larger they get. (SDS) itself, hardware architecture, storage device selection and networking technologies. Once applications are deployed It sounds like a match made in heaven - and it is - but it can also be within an OpenStack cloud configured for Ceph SDS, running a challenge if you have your heart set on a DIY approach. Or worse, workloads will quickly highlight the necessity for Ceph optimization. you could find yourself locked into a contract whose only interests Cloud architects and administrators who design and operate being take care of, are the vendor’s. OpenStack cloud deployments ultimately seek out architecture with predictable performance and reliable integration with So, where to begin? OpenStack services. softiron.com [email protected] @SoftIron @SoftIron @SoftIronNews Focus on storage for OpenStack Volume storage, most commonly associated with the OpenStack Cinder service, facilitates many use cases including user OpenStack deployments depend upon block and object storage volumes and general purpose block volume based virtual disks. services for regular and common cloud platform operations. Volume storage in OpenStack is very common as most users In some deployments, the cloud architect may choose a design are familiar with the concept of virtual disks and their role in where block and object storage are deployed independently virtualization environments. Commonly, applications that maintain of one another. This approach adds complexity, requiring the statefulness will leverage volume storage, as stateful application ongoing monitoring, servicing and support capabilities for not data tends to reside within a holistic volume. only one storage subsystem, but also perhaps two, or more storage subsystems. Rather than deploying a storage subsystem for only object storage, and another for only block storage, an SDS OpenStack Storage Solutions option coupled with an appropriate hardware design can eliminate through Software Defined Storage the need for independent, dissimilar storage silos. Given the flexible and open approach to IT infrastructure embraced OpenStack deployments utilize block and object storage in by OpenStack, traditional storage subsystems are often sized, specific ways. There are three primary categories for OpenStack selected, configured and provisioned based on known needs at the storage and each facilitate a particular purpose within the time of procurement and projected needs measured by existing OpenStack cloud infrastructure. These are not exclusive for applications with forecast exercises applied. OpenStack cloud infrastructure use, and user workloads may utilize block and object storage for cloud user and application Cloud infrastructure requirements will vary and applications will purposes, as well. likely have requirements for the infrastructure to scale along with business demands. Software Defined Storage typically excels in these environments, given the ability to grow and scale with the Category Purpose Default provider needs of the business. Many OpenStack deployments have selected Ceph as the SDS implementation of choice. When architected and Image storage Object storage Swift deployed properly, Ceph delivers performance and scale rivaled Ephemeral storage Block storage Linux LVM only by some of the largest data center storage installations. Volume storage Block storage Linux LVM or iSCSI Ceph SDS exhibits impressive performance when deployed with an optimal configuration. Ceph itself is highly tunable and leverages standard storage media types including traditional spinning disk Table 1: Storage services and their default storage providers. drives, NAND-based solid-state flash, and NVMe flash technology. Ceph utilizes a distributed topology across many nodes, and by leveraging a distributed architecture Ceph deployments often Image storage serves the OpenStack Glance service. The data store place requirements on connectivity with an emphasis on solid here are those of machine images, which provide the content for networking choices (see Figure 1). operating system and what some virtualization administrators may refer to as a disk file. The size and amount of image storage will depend on the use cases for an OpenStack deployment. OpenStack Storage Solutions OTHER APPS S3 CLIENTS OPENSTACK SMB/NFS For example: powered by SoftIron (OPTIONAL) CLIENT ACCESS (OPTIONAL) » An OpenStack cloud with many users in a development Best of both worlds: Highly scalable, open SDS meets organization may host multiple images per user. building-block style, purpose-built, environmentally efficient storage servers with HyperDrive®. » With Virtual Desktop Instance (VDI), users may have several shared images across thousands of users. In OpenStack, as with other centralized cloud infrastructure S3 API KEYSTONE API SWIFT API CINDER API GLANCE API environments, storage capacity needs tend to increase with time. » In Continuous Integration and Continuous Delivery (CI/CD) As more applications and more users consume OpenStack RADOS GW RBD CEPH FS environments, there may be thousands of machine images or compute and storage, it is inevitable that more storage capacity OBJECT STORAGE BLOCK STORAGE BLOCK STORAGE intermediate build images in varying states of development will be required. Consider the building block concept for adding and iterative workflows. storage capacity: where capacity is added as needed and storage LIBRADOS building blocks – which form the storage subsystem – are specific to Ephemeral storage provides a non-persistent space for compute application requirements. These storage building blocks are added RADOS instances and can often be thought of as a boot disk for an to your OpenStack cloud storage infrastructure without disruption to individual instance. When an instance is launched, the operating compute resources or existing storage footprint. SoftIron’s approach MONITOR SERVICES OSD (OBJECT STORAGE DAEMON SERVICES) system will load and operate from ephemeral storage for the life to storage leverages Ceph, combining the flexibility, scalability and of the instance. The data host by ephemeral storage can be stored open architecture of the technology. using a snapshot and is written to a persistent volume. MONITOR MONITOR MONITOR OSD OSD NODE 1 NODE 2 NODE 3 NODE 1 NODE N Figure 1: Common Ceph Software Defined Storage integration points with OpenStack cloud deployments. Volume storage, most commonly associated with the SoftIron pairs Ceph with HyperDrive, a storage appliance custom- OpenStack resource consumption over time OpenStack Cinder service, facilitates many use cases including user designed with Ceph in mind, to deliver solid performance, volumes and general purpose block volume based virtual disks. reliable and predictable operations, and a highly efficient power Applications and users will consume more capacity over time Volume storage in OpenStack is very common as most users and thermal profile. and quite likely quicker than originally anticipated by cloud are familiar with the concept of virtual disks and their role in architects and IT infrastructure designers. SDS helps address the virtualization environments. Commonly, applications that maintain HyperDrive offers flexible configuration and can be customized situation through quick and low overhead provisioning of new statefulness will leverage volume storage, as stateful application to deliver performance, capacity or a combination of both storage capacity. data tends to reside within a holistic volume. performance and capacity. The unique storage server design developed by SoftIron enables cloud architects to decide how With the ability to add storage capacity independently of compute storage nodes should be allocated. In high performance workloads, resources, the OpenStack cloud infrastructure will accommodate OpenStack Storage Solutions perhaps all-flash storage is required by intensive I/O applications, the growing storage demand placed on cloud administrators by application and business