Cloud Standards [electronic resource] : Agreements That Hold Together Clouds /
Waschke, Marvin.author.
Cloud computing is often described as providing computing resources the way electric utilities provide energy. In theory, anyone with an adequate connection to the Internet should be able to tap into a cloud provider and get exactly the computing resources they want when they want it, just like plugging into the electricity grid and getting exactly the energy you want when you want it. But to get that electricity, there are many standards: voltage, frequency, phase, motors constructed in standard ways-there is a long list; there is an equally long list for cloud computing. Many of the standards are already in place. Others are being developed; some in contention.   Cloud Standards is a broad discussion of important existing and future standards. For existing standards, the discussion focuses on how they are used, providing practical advice to engineers constructing clouds and services to be deployed on clouds. For future standards, the discussion is on why a standard is needed, what the benefits will be, and what is being done now to fill the gap. No current book provides this information in the depth and detail necessary for an engineer in his work, an architect in designing cloud systems, a product manager collecting and evaluating products, or an executive evaluating the feasibility of a project. A second benefit from this book is that it provides insight into cloud implementations. Cloud implementations can be seen as the culmination of many trends in software and hardware engineering. Much of the foundation for these developments have been crystallized in the form of standards like TCP/IP (Transmission Control Protocol/Internet Protocol) and HTTP (Hypertext Transmission Protocol). The book leads readers to understand how these contribute to and affect cloud implementations. Unfortunately, emerging standards are often messy. Cloud implementers may need to choose between competing proposed standards. Sometimes it is better to reject the standard entirely and "roll your own." This book provides background for intelligent decisions. Keeping a cloud, or an application implemented on a cloud, running well requires careful tuning of the implementation. Tuning often involves adjusting controls that are in the standard or applying the standard in less well-known ways. This book is an aid in tuning cloud systems for maximum benefits.
Description based upon print version of record.
Title Page; Copyright Page; Table of Contents; Foreword; About the Author; About the Technical Reviewer; Acknowledgments; Introduction; CHAPTER 1 Setting the Scene A Brief and Informal History andIntroduction to the Cloud; History: Evolution of the Cloud; The Network and Distributed Systems; Virtualization; The Need for Clouds Today; Cloud Scenarios; Scenarios for Individuals; Backing Up; Sharing Documents; Cloud Scenarios for Enterprises; Cloud Service Models; Infrastructure as a Service (IaaS); Platform as a Service (PaaS); Software as a Service (SaaS); Testing in the Cloud
Developing In the CloudCustomer Relations Management in the Cloud; CHAPTER 2 Standards What and Why; What Are Standards?; Why Are Standards Hard to Read?; The Scope of Standards; De Facto and De Jure Standards; De Facto Standards; The IBM PC; Windows Operating System; Amazon.com EC2; Representational State Transfer; De Jure Standards; De Jure Standards Administration; Clear Sources; Version Control; Compatibility Rules; Error Management; Open Standards; Open Participation; Transparent Process; Unencumbered Standard; Freely Accessible; Public Standards Organizations
National and International Standards OrganizationsCloud SDOs; CHAPTER 3 Cloud Architecture in the Stratosphere; Architecture; Service-Oriented Architecture (SOA); Service Models; Deployment Scenarios; Private Cloud; Public Cloud; Community Cloud; Hybrid Cloud; Roles; Consumer; Provider; Auditor; Broker; Carrier; Developer; CHAPTER 4 Security and Governance Managing Risk; Governance; Security; The Information Security Management System (ISMS); The ISO/IEC 27001 Deming Cycle; Plan Phase; Do Phase; Check Phase; Act Phase; Statement on Audit Standards No. 70 (SAS 70); The SAS 70 Audit
SAS 70 ExampleCloud and ISMS; Data; Loss; Risks; De-perimeterization; De-perimeterization as a Strategy; Cloud Security Practice; IaaS Practice; PaaS Practice; SaaS Practice; Governance and Security Standards; Basic Authentication; Digest Authentication; Open Authorization; OpenID; Security Assertion Markup Language (SAML); Conclusion; CHAPTER 5 Cloud Implementation Implementation Architecture and Cloud-Related Technologies; Functional and Management Interfaces; NIST Cloud Implementation Architecture; Service Layer; IaaS Service Layer; PaaS Service Layer; SaaS Service Layer
Resource Abstraction LayerPhysical Layer; Energy; Power Usage Effectiveness; Cooling; Power Conditioning; Location; Cloud Datacenter as Computer; Cloud Datacenter Loads; Datacenter Networks; Grids, Supercomputers, and Datacenters; Grids; Interconnect Fabrics; A LAN Compared to an Interconnect; Processing Power in Cloud Architecture; CHAPTER 6 Cloud Storage and Cloud Network; Cloud Storage; Storage Device Networking; Network Attached Storage; Storage Area Networks; Disk Arrays; Striping; Mirroring; Parity; Limitations; Cloud Data Management; ACID; CAP; Storage in the Cloud; Cloud Networks
OSI Layers
Includes bibliographical references and index.
Cloud computing is often described as providing computing resources the way electric utilities provide energy. In theory, anyone with an adequate connection to the Internet should be able to tap into a cloud provider and get exactly the computing resources they want when they want it, just like plugging into the electricity grid and getting exactly the energy you want when you want it. But to get that electricity, there are many standards: voltage, frequency, phase, motors constructed in standard ways-there is a long list; there is an equally long list for cloud computing. Many of the standards are already in place. Others are being developed; some in contention.   Cloud Standards is a broad discussion of important existing and future standards. For existing standards, the discussion focuses on how they are used, providing practical advice to engineers constructing clouds and services to be deployed on clouds. For future standards, the discussion is on why a standard is needed, what the benefits will be, and what is being done now to fill the gap. No current book provides this information in the depth and detail necessary for an engineer in his work, an architect in designing cloud systems, a product manager collecting and evaluating products, or an executive evaluating the feasibility of a project. A second benefit from this book is that it provides insight into cloud implementations. Cloud implementations can be seen as the culmination of many trends in software and hardware engineering. Much of the foundation for these developments have been crystallized in the form of standards like TCP/IP (Transmission Control Protocol/Internet Protocol) and HTTP (Hypertext Transmission Protocol). The book leads readers to understand how these contribute to and affect cloud implementations. Unfortunately, emerging standards are often messy. Cloud implementers may need to choose between competing proposed standards. Sometimes it is better to reject the standard entirely and "roll your own." This book provides background for intelligent decisions. Keeping a cloud, or an application implemented on a cloud, running well requires careful tuning of the implementation. Tuning often involves adjusting controls that are in the standard or applying the standard in less well-known ways. This book is an aid in tuning cloud systems for maximum benefits.
Computer communication systems.
Computers.
Computer Communication Networks.
Information Systems and Communication Service.