DOCSLIB.ORG

Scalable Cloud-Based Services for Flexible Storage: Implementation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Scalable Cloud-Based Services for Flexible Storage: Implementation IMPLEMENTATION GUIDE Service Provider Data Center For Disclosure under NDA Only Scalable Cloud-based Services for Flexible, Robust, Cost- Effective Storage Discover how to improve storage utilization, reduce cost and improve scalability with a Ceph*-based storage-as-a-service (STaaS) solution optimized for Intel® technology Introduction This implementation guide provides key learnings and configuration Storage-as-a-service (STaaS) uses software-defined storage (SDS) to abstract insights to integrate technologies storage software from the storage hardware. By providing a shared pool of storage with optimal business value. capacity that can be used across service offerings, SDS eliminates storage silos If you are responsible for… and helps improve utilization ratios. Intelligent, automated orchestration reduces • Technology decisions: operating costs and can speed provisioning from several weeks to a few minutes. You will learn how to implement a storage-as-a-service (STaaS) Ceph* is an open source STaaS solution that supports object, block and file storage. solution using Ceph*. You’ll Using an open source solution can help you lower costs and avoid vendor lock-in. also find tips for optimizing It also enables you to deploy new technology quickly. Ceph is well supported by performance with Intel® the open source community, and commercial distributions are also available. Intel, technologies and best practices the community and Independent Software Vendors (ISVs) have worked closely to for deploying Ceph. develop reference architectures and best practices for deploying a Ceph-based STaaS platform that is optimized to run on Intel® Xeon® processors and take advantage of other Intel® technologies such as Intel® SSD Data Center Family for NVMe* (Non-Volatile Memory Express*) Solid State Drives (SSDs), Intel® Ethernet Products and software optimizations such as Intel® Intelligent Storage Acceleration Library (Intel® ISA-L) and Intel® Cache Acceleration Software (Intel® CAS). Overview Requirements Configuration Operation Use Cases Validation For Disclosure under NDA Only Implementation Guide | Scalable Cloud-based Services for Flexible, Robust, Cost-Effective Storage 2 Table of Contents Solution Overview Introduction . 1 A Ceph-based STaaS deployment consists of the Ceph software, several types of Solution Overview . 2 nodes (servers), and Intel software optimization products. Ceph Software. .2 Ceph Software Node Types. .2 Intel® Technologies ..................2 Ceph’s foundation is the Reliable Autonomic Distributed Object Store* (RADOS*), which provides your applications with object, block and file system storage in System Requirements . 3 a single unified storage cluster—making Ceph flexible, highly reliable and easy Software Requirements ..............3 for you to manage. Each one of your applications can use the object, block or Minimum Hardware Requirements ...3 file system interfaces to the same RADOS cluster simultaneously, which means Installation and Configuration . 5 your Ceph storage system serves as a flexible foundation for all of your data Get Ceph ............................5 storage needs. You can use Ceph for free because it is open source, and deploy Install Ceph .........................5 it on economical industry-standard hardware. Or you can opt for a commercially Deploy Storage Clusters .............6 supported Ceph distribution if you prefer. Deploy Ceph Clients .................6 The various storage access modes use different components of Ceph: Configuration Considerations ........6 • Object storage uses the Ceph Object Gateway daemon, radosgw* (RGW*). Ceph Operation and Utilization . 8 • File storage (CephFS*) can use a Ceph filesystem kernel driver or the user space Ceph Topologies .....................8 FUSE* client. Using Intel CAS ....................10 • Block storage uses RADOS Block Devices (RBDs*). Using Intel ISA-L ...................10 Integrating with OpenStack ........10 • All storage is ultimately stored by Ceph Object Storage Daemons (Ceph OSDs). Orchestration ..................... 11 • All data is stored as “objects” which are randomly distributed across the cluster Ceph-Based STaaS Use Cases . 11 by the CRUSH* (Controlled Replication Under Scalable Hashing*) algorithm. Validation . .. 13 To efficiently compute information about object placement and location, Ceph uses the CRUSH algorithm instead of a central lookup table. CRUSH enables Ceph Best Practices . 13 performance to scale linearly by ensuring that data is always retrieved directly from Planning. 13 the primary OSD where it is stored—avoiding bottlenecks created by centralized Nodes ............................. 13 metadata lookups. Journaling ......................... 14 Network ........................... 14 Node Types Summary . 14 As you build your Ceph cluster using the guidelines in this document, you will be References . 14 working with several types of “nodes” (sometimes referred to as “hosts”). A node is simply any single machine or server in a Ceph system. Appendix A: Ceph Tuning Details . 15 • Storage nodes (sometimes called “OSD nodes” or simply “OSDs”) are where the Solutions Proven by Your Peers . 17 actual data is stored. • Monitor nodes track the health and configuration of the Ceph cluster by maintaining copies of the cluster maps. • RGW nodes serve as HTTP proxies for object storage workloads. • Metadata nodes map the directories and filenames from CephFS to objects stored within RADOS clusters. • Client nodes request data. See Figure 1 for an overview of how all these fit together into a Ceph cluster. Intel® Technologies Several Intel technologies, both hardware and software, contribute to the reliability and performance of a Ceph-based STaaS solution. See the “References” section for links. • Intel® Xeon® processors and Intel® Xeon® processor Scalable family provide the compute power needed to process vast amounts of data. • Intel® SATA-based SSDs, Intel® NVMe*-based SSDs and Intel® Optane™ SSDs provide performance, stability, efficiency and low power consumption. For Disclosure under NDA Only Implementation Guide | Scalable Cloud-based Services for Flexible, Robust, Cost-Effective Storage 3 Ceh oftwre omponents App Host/VM Client RadosGW* RBD* CephFS* S3* Swift* Librados RADOS Metadata Monitors Servers Pool Pool Pool Pool n MD ON CRUS ap MD n ON n P P P P P n 1 n 1 n 1 n Cluster Node Cluster Node Cluster Node [OSDs] [OSDs] [OSDs] PG lacemen roup Figure 1 . Software Elements of a Ceph Cluster • Intel® Cache Acceleration Software (Intel® CAS) improves CephFS performance—by as much as 550 percent for reads and 400 percent for writes, compared to running CephFS without Intel CAS.1 • Intel® Intelligent Storage Acceleration Library (Intel® ISA-L) enables Ceph to more easily use features of Intel Xeon processors for tasks such as data protection, data integrity and data security. Intel ISA-L enables Ceph to offer erasure coding without negatively affecting performance. • Intel® Ethernet Network Adapters, Controllers and Accessories enable agility within the data center to effectively deliver services efficiently and cost-effectively. Worldwide availability, exhaustive testing for compatibility, and 35 years of innovation mean that Intel Ethernet products are an excellent choice when building your Ceph clusters. System Requirements Software Requirements • Ceph software . The current version of Ceph is v12.2.4 Luminous RC. See Ceph Releases. • Compatible OS . Intel recommends you deploy Ceph on one of the three major Linux* distributions; SUSE Enterprise Storage 4*, Ubuntu*, or CentOS*/Red Hat Enterprise Linux* (RHEL*). And you should deploy Ceph on the latest releases. The choice of a specific distribution is often determined by your existing install base or a preference for interfaces like sysvinit, upstart, or systemd. For full details, visit Ceph Dependencies. • OpenStack* . Although optional, OpenStack integrates well with Ceph and extends its capabilities. See “Integrating with OpenStack” later in this document. Minimum Hardware Requirements2 Ceph was designed to run on industry-standard hardware, which makes building and maintaining PB-scale data clusters economically feasible. When planning your cluster hardware, you will need to balance a number of considerations, including failure domains and potential performance issues. Hardware planning should include distributing Ceph daemons and other processes that use Ceph across many hosts. Generally, we recommend running Ceph daemons of a specific type on a host configured for that type of daemon. We recommend using other hosts for processes that use your data cluster (such as OpenStack or CloudStack*). For Disclosure under NDA Only Implementation Guide | Scalable Cloud-based Services for Flexible, Robust, Cost-Effective Storage 4 The hardware requirements of Ceph depend on the I/O workload. Use the following hardware recommendations as a starting point only. The recommendations given in this section are on a per- process basis. If several processes are co-located on the same server, each process’ CPU, RAM, disk and network requirements should be totaled. CPU Requirements: Ceph metadata servers (MDS) dynamically redistribute their load, which is CPU- intensive. Therefore, your MDS should have significant processing power (for example, quad-core processors or better). Ceph OSDs run the RADOS service, calculate data placement with CRUSH, replicate data and maintain their own copy of the cluster map. Therefore, storage nodes should have a reasonable amount
Load more

Recommended publications
  • Optimizing the Ceph Distributed File System for High Performance Computing
    Optimizing the Ceph Distributed File System for High Performance Computing Kisik Jeong Carl Duffy Jin-Soo Kim Joonwon Lee Sungkyunkwan University Seoul National University Seoul National University Sungkyunkwan University Suwon, South Korea Seoul, South Korea Seoul, South Korea Suwon, South Korea [email protected] [email protected] [email protected] [email protected] Abstract—With increasing demand for running big data ana- ditional HPC workloads. Traditional HPC workloads perform lytics and machine learning workloads with diverse data types, reads from a large shared file stored in a file system, followed high performance computing (HPC) systems consequently need by writes to the file system in a parallel manner. In this case, to support diverse types of storage services. Ceph is one possible candidate for such HPC environments, as Ceph provides inter- a storage service should provide good sequential read/write faces for object, block, and file storage. Ceph, however, is not performance. However, Ceph divides large files into a number designed for HPC environments, thus it needs to be optimized of chunks and distributes them to several different disks. This for HPC workloads. In this paper, we find and analyze problems feature has two main problems in HPC environments: 1) Ceph that arise when running HPC workloads on Ceph, and propose translates sequential accesses into random accesses, 2) Ceph a novel optimization technique called F2FS-split, based on the F2FS file system and several other optimizations. We measure needs to manage many files, incurring high journal overheads the performance of Ceph in HPC environments, and show that in the underlying file system.
    [Show full text]
  • Proxmox Ve Mit Ceph &
    PROXMOX VE MIT CEPH & ZFS ZUKUNFTSSICHERE INFRASTRUKTUR IM RECHENZENTRUM Alwin Antreich Proxmox Server Solutions GmbH FrOSCon 14 | 10. August 2019 Alwin Antreich Software Entwickler @ Proxmox 15 Jahre in der IT als Willkommen! System / Netzwerk Administrator FrOSCon 14 | 10.08.2019 2/33 Proxmox Server Solutions GmbH Aktive Community Proxmox seit 2005 Globales Partnernetz in Wien (AT) Proxmox Mail Gateway Enterprise (AGPL,v3) Proxmox VE (AGPL,v3) Support & Services FrOSCon 14 | 10.08.2019 3/33 Traditionelle Infrastruktur FrOSCon 14 | 10.08.2019 4/33 Hyperkonvergenz FrOSCon 14 | 10.08.2019 5/33 Hyperkonvergente Infrastruktur FrOSCon 14 | 10.08.2019 6/33 Voraussetzung für Hyperkonvergenz CPU / RAM / Netzwerk / Storage Verwende immer genug von allem. FrOSCon 14 | 10.08.2019 7/33 FrOSCon 14 | 10.08.2019 8/33 Was ist ‚das‘? ● Ceph & ZFS - software-basierte Storagelösungen ● ZFS lokal / Ceph verteilt im Netzwerk ● Hervorragende Performance, Verfügbarkeit und https://ceph.io/ Skalierbarkeit ● Verwaltung und Überwachung mit Proxmox VE ● Technischer Support für Ceph & ZFS inkludiert in Proxmox Subskription http://open-zfs.org/ FrOSCon 14 | 10.08.2019 9/33 FrOSCon 14 | 10.08.2019 10/33 FrOSCon 14 | 10.08.2019 11/33 ZFS Architektur FrOSCon 14 | 10.08.2019 12/33 ZFS ARC, L2ARC and ZIL With ZIL Without ZIL ARC RAM ARC RAM ZIL ZIL Application HDD Application SSD HDD FrOSCon 14 | 10.08.2019 13/33 FrOSCon 14 | 10.08.2019 14/33 FrOSCon 14 | 10.08.2019 15/33 Ceph Network Ceph Docs: https://docs.ceph.com/docs/master/ FrOSCon 14 | 10.08.2019 16/33 FrOSCon
    [Show full text]
  • Red Hat Openstack* Platform with Red Hat Ceph* Storage
    Intel® Data Center Blocks for Cloud – Red Hat* OpenStack* Platform with Red Hat Ceph* Storage Reference Architecture Guide for deploying a private cloud based on Red Hat OpenStack* Platform with Red Hat Ceph Storage using Intel® Server Products. Rev 1.0 January 2017 Intel® Server Products and Solutions <Blank page> Intel® Data Center Blocks for Cloud – Red Hat* OpenStack* Platform with Red Hat Ceph* Storage Document Revision History Date Revision Changes January 2017 1.0 Initial release. 3 Intel® Data Center Blocks for Cloud – Red Hat® OpenStack® Platform with Red Hat Ceph Storage Disclaimers Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software, or service activation. Learn more at Intel.com, or from the OEM or retailer. You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548-4725 or by visiting www.intel.com/design/literature.htm.
    [Show full text]
  • Red Hat Data Analytics Infrastructure Solution
    TECHNOLOGY DETAIL RED HAT DATA ANALYTICS INFRASTRUCTURE SOLUTION TABLE OF CONTENTS 1 INTRODUCTION ................................................................................................................ 2 2 RED HAT DATA ANALYTICS INFRASTRUCTURE SOLUTION ..................................... 2 2.1 The evolution of analytics infrastructure ....................................................................................... 3 Give data scientists and data 2.2 Benefits of a shared data repository on Red Hat Ceph Storage .............................................. 3 analytics teams access to their own clusters without the unnec- 2.3 Solution components ...........................................................................................................................4 essary cost and complexity of 3 TESTING ENVIRONMENT OVERVIEW ............................................................................ 4 duplicating Hadoop Distributed File System (HDFS) datasets. 4 RELATIVE COST AND PERFORMANCE COMPARISON ................................................ 6 4.1 Findings summary ................................................................................................................................. 6 Rapidly deploy and decom- 4.2 Workload details .................................................................................................................................... 7 mission analytics clusters on 4.3 24-hour ingest ........................................................................................................................................8
    [Show full text]
  • Unlock Bigdata Analytic Efficiency with Ceph Data Lake
    Unlock Bigdata Analytic Efficiency With Ceph Data Lake Jian Zhang, Yong Fu, March, 2018 Agenda . Background & Motivations . The Workloads, Reference Architecture Evolution and Performance Optimization . Performance Comparison with Remote HDFS . Summary & Next Step 3 Challenges of scaling Hadoop* Storage BOUNDED Storage and Compute resources on Hadoop Nodes brings challenges Data Capacity Silos Costs Performance & efficiency Typical Challenges Data/Capacity Multiple Storage Silos Space, Spent, Power, Utilization Upgrade Cost Inadequate Performance Provisioning And Configuration Source: 451 Research, Voice of the Enterprise: Storage Q4 2015 *Other names and brands may be claimed as the property of others. 4 Options To Address The Challenges Compute and Large Cluster More Clusters Storage Disaggregation • Lacks isolation - • Cost of • Isolation of high- noisy neighbors duplicating priority workloads hinder SLAs datasets across • Shared big • Lacks elasticity - clusters datasets rigid cluster size • Lacks on-demand • On-demand • Can’t scale provisioning provisioning compute/storage • Can’t scale • compute/storage costs separately compute/storage costs scale costs separately separately Compute and Storage disaggregation provides Simplicity, Elasticity, Isolation 5 Unified Hadoop* File System and API for cloud storage Hadoop Compatible File System abstraction layer: Unified storage API interface Hadoop fs –ls s3a://job/ adl:// oss:// s3n:// gs:// s3:// s3a:// wasb:// 2006 2008 2014 2015 2016 6 Proposal: Apache Hadoop* with disagreed Object Storage SQL …… Hadoop Services • Virtual Machine • Container • Bare Metal HCFS Compute 1 Compute 2 Compute 3 … Compute N Object Storage Services Object Object Object Object • Co-located with gateway Storage 1 Storage 2 Storage 3 … Storage N • Dynamic DNS or load balancer • Data protection via storage replication or erasure code Disaggregated Object Storage Cluster • Storage tiering *Other names and brands may be claimed as the property of others.
    [Show full text]
  • Evaluation of Active Storage Strategies for the Lustre Parallel File System
    Evaluation of Active Storage Strategies for the Lustre Parallel File System Juan Piernas Jarek Nieplocha Evan J. Felix Pacific Northwest National Pacific Northwest National Pacific Northwest National Laboratory Laboratory Laboratory P.O. Box 999 P.O. Box 999 P.O. Box 999 Richland, WA 99352 Richland, WA 99352 Richland, WA 99352 [email protected] [email protected] [email protected] ABSTRACT umes of data remains a challenging problem. Despite the Active Storage provides an opportunity for reducing the improvements of storage capacities, the cost of bandwidth amount of data movement between storage and compute for moving data between the processing nodes and the stor- nodes of a parallel filesystem such as Lustre, and PVFS. age devices has not improved at the same rate as the disk ca- It allows certain types of data processing operations to be pacity. One approach to reduce the bandwidth requirements performed directly on the storage nodes of modern paral- between storage and compute devices is, when possible, to lel filesystems, near the data they manage. This is possible move computation closer to the storage devices. Similarly by exploiting the underutilized processor and memory re- to the processing-in-memory (PIM) approach for random ac- sources of storage nodes that are implemented using general cess memory [16], the active disk concept was proposed for purpose servers and operating systems. In this paper, we hard disk storage systems [1, 15, 24]. The active disk idea present a novel user-space implementation of Active Storage exploits the processing power of the embedded hard drive for Lustre, and compare it to the traditional kernel-based controller to process the data on the disk without the need implementation.
    [Show full text]
  • Design and Implementation of Archival Storage Component of OAIS Reference Model
    Masaryk University Faculty of Informatics Design and implementation of Archival Storage component of OAIS Reference Model Master’s Thesis Jan Tomášek Brno, Spring 2018 Masaryk University Faculty of Informatics Design and implementation of Archival Storage component of OAIS Reference Model Master’s Thesis Jan Tomášek Brno, Spring 2018 Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Jan Tomášek Advisor: doc. RNDr. Tomáš Pitner Ph.D. i Acknowledgement I would like to express my gratitude to my supervisor, doc. RNDr. Tomáš Pitner, Ph.D. for valuable advice concerning formal aspects of my thesis, readiness to help and unprecedented responsiveness. Next, I would like to thank to RNDr. Miroslav Bartošek, CSc. for providing me with long-term preservation literature, to RNDr. Michal Růžička, Ph.D. for managing the very helpful internal documents of the ARCLib project, and to the whole ARCLib team for the great col- laboration and willingness to meet up and discuss questions emerged during the implementation. I would also like to thank to my colleagues from the inQool com- pany for providing me with this opportunity, help in solving of practi- cal issues, and for the time flexibility needed to finish this work. Last but not least, I would like to thank to my closest family and friends for all the moral support. iii Abstract This thesis deals with the development of the Archival Storage module of the Reference Model for an Open Archival Information System.
    [Show full text]
  • IBM Red Hat Ansible Health Check Is Your Red Hat Ansible Environment Working As Hard As You Are?
    IBM Red Hat Ansible health check Is your Red Hat Ansible environment working as hard as you are? Highlights Your journey to cloud has many stops along the way. And, as with all journeys, it’s crucial to know where you want to be and how you’ll get there. No one solution is perfect without some tweaking of the software and tools. And, not all individuals Understand your progress and have experience in Red Hat® solutions and cloud environment management to align to your vision and roadmap. finetune tools as they progress. And, that’s where IBM can help. IBM Services® offers IBM Red Hat Ansible Health Check service to help you get Work to further achieve the goals the most from your Red Hat Ansible®, Ansible Tower and cloud investments by of Ansible and Ansible Tower— highlighting areas for you to adjust. The IBM specialists perform an assessment simplicity, security and stability. based on common challenges, such as provisioning, orchestration, automation, playbooks and processes, including continuous integration or continuous delivery Gain operational efficiencies (CI/CD). Following the 2.5-hour assessment session, you’ll receive a report that with Ansible in the areas of: will identify areas of concern, provide recommendations and help you make more – Infrastructure as code informed decisions for your enterprise and cloud environment. and provisioning – Compliance as code, Helping understand the complexities of automating, configuration management and security automation optimizing and allocating resources – Application deployment, While Ansible is incredibly flexible and adaptable, automation and provisioning orchestration and CI/CD can be complex with the number of technologies that are required to complete the tasks across multiple vendor environments, operating systems, hybrid clouds, – Network automation networks, plugins, modules and APIs.
    [Show full text]
  • Release 3.11.0
    CEKit Release 3.11.0 May 17, 2021 Contents 1 About 3 2 Main features 5 3 I’m new, where to start? 7 4 Releases and changelog 9 5 Contact 11 6 Documentation 13 6.1 Getting started guide........................................... 13 6.2 Handbook................................................ 19 6.3 Guidelines................................................ 61 6.4 Descriptor documentation........................................ 75 6.5 Contribution guide............................................ 137 7 Sponsor 143 8 License 145 i ii CEKit, Release 3.11.0 Contents 1 CEKit, Release 3.11.0 2 Contents CHAPTER 1 About Container image creation tool. CEKit helps to build container images from image definition files with strong focus on modularity and code reuse. 3 CEKit, Release 3.11.0 4 Chapter 1. About CHAPTER 2 Main features • Building container images from YAML image definitions using many different builder engines • Integration/unit testing of images 5 CEKit, Release 3.11.0 6 Chapter 2. Main features CHAPTER 3 I’m new, where to start? We suggest looking at the getting started guide. It’s probably the best place to start. Once get through this tutorial, look at handbook which describes how things work. Later you may be interested in the guidelines sections. 7 CEKit, Release 3.11.0 8 Chapter 3. I’m new, where to start? CHAPTER 4 Releases and changelog See the releases page for latest releases and changelogs. 9 CEKit, Release 3.11.0 10 Chapter 4. Releases and changelog CHAPTER 5 Contact • Please join the #cekit IRC channel on Freenode • You can always mail us at: cekit at cekit dot io 11 CEKit, Release 3.11.0 12 Chapter 5.
    [Show full text]
  • Ceph Done Right for Openstack
    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.
    [Show full text]
  • Shared File Systems: Determining the Best Choice for Your Distributed SAS® Foundation Applications Margaret Crevar, SAS Institute Inc., Cary, NC
    Paper SAS569-2017 Shared File Systems: Determining the Best Choice for your Distributed SAS® Foundation Applications Margaret Crevar, SAS Institute Inc., Cary, NC ABSTRACT If you are planning on deploying SAS® Grid Manager and SAS® Enterprise BI (or other distributed SAS® Foundation applications) with load balanced servers on multiple operating systems instances, , a shared file system is required. In order to determine the best shared file system choice for a given deployment, it is important to understand how the file system is used, the SAS® I/O workload characteristics performed on it, and the stressors that SAS Foundation applications produce on the file system. For the purposes of this paper, we use the term "shared file system" to mean both a clustered file system and shared file system, even though" shared" can denote a network file system and a distributed file system – not clustered. INTRODUCTION This paper examines the shared file systems that are most commonly used with SAS and reviews their strengths and weaknesses. SAS GRID COMPUTING REQUIREMENTS FOR SHARED FILE SYSTEMS Before we get into the reasons why a shared file system is needed for SAS® Grid Computing, let’s briefly discuss the SAS I/O characteristics. GENERAL SAS I/O CHARACTERISTICS SAS Foundation creates a high volume of predominately large-block, sequential access I/O, generally at block sizes of 64K, 128K, or 256K, and the interactions with data storage are significantly different from typical interactive applications and RDBMSs. Here are some major points to understand (more details about the bullets below can be found in this paper): SAS tends to perform large sequential Reads and Writes.
    [Show full text]
  • Cs 5412/Lecture 24. Ceph: a Scalable High-Performance Distributed File System
    CS 5412/LECTURE 24. CEPH: A Ken Birman SCALABLE HIGH-PERFORMANCE Spring, 2019 DISTRIBUTED FILE SYSTEM HTTP://WWW.CS.CORNELL.EDU/COURSES/CS5412/2019SP 1 HDFS LIMITATIONS Although many applications are designed to use the normal “POSIX” file system API (operations like file create/open, read/write, close, rename/replace, delete, and snapshot), some modern applications find POSIX inefficient. Some main issues: HDFS can handle big files, but treats them as sequences of fixed-size blocks. Many application are object-oriented HDFS lacks some of the “file system management” tools big-data needs HTTP://WWW.CS.CORNELL.EDU/COURSES/CS5412/2019SP 2 CEPH PROJECT Created by Sage Weihl, a PhD student at U.C. Santa Cruz Later became a company and then was acquired into Red Hat Linux Now the “InkStack” portion of Linux offers Ceph plus various tools to leverage it, and Ceph is starting to replace HDFS worldwide. Ceph is similar in some ways to HDFS but unrelated to it. Many big data systems are migrating to the system. HTTP://WWW.CS.CORNELL.EDU/COURSES/CS5412/2019SP 3 CEPH HAS THREE “APIS” First is the standard POSIX file system API. You can use Ceph in any situation where you might use GFS, HDFS, NFS, etc. Second, there are extensions to POSIX that allow Ceph to offer better performance in supercomputing systems, like at CERN. Finally, Ceph has a lowest layer called RADOS that can be used directly as a key-value object store. HTTP://WWW.CS.CORNELL.EDU/COURSES/CS5412/2019SP 4 WHY TALK DIRECTLY TO RADOS? SERIALIZATION/DESERIALIZATION! When an object is in memory, the data associated with it is managed by the class (or type) definition, and can include pointers, fields with gaps or other “subtle” properties, etc.
    [Show full text]