DOCSLIB.ORG

Openstack Administrator Guide Openstack Administrator Guide SUSE Openstack Cloud 8

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Openstack Administrator Guide Openstack Administrator Guide SUSE Openstack Cloud 8 SUSE OpenStack Cloud 8 OpenStack Administrator Guide OpenStack Administrator Guide SUSE OpenStack Cloud 8 ABSTRACT OpenStack oers open source software for OpenStack administrators to manage and troubleshoot an OpenStack cloud. This guide documents OpenStack Newton and Mitaka releases. Publication Date: 07/29/2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License : http://creativecommons.org/licenses/by/3.0/legalcode Contents 1 Documentation Conventions 1 2 Get started with OpenStack 2 2.1 Conceptual architecture 6 2.2 Logical architecture 6 2.3 OpenStack services 7 Compute service overview 8 • Storage concepts 10 • Object Storage service overview 11 • Block Storage service overview 12 • Shared File Systems service overview 13 • Networking service overview 14 • Dashboard overview 15 • Identity service overview 16 • Image service overview 17 • Telemetry service overview 18 • Orchestration service overview 19 • Database service overview 20 • Data Processing service overview 22 2.4 Feedback 22 3 Identity management 23 3.1 Identity concepts 23 User management 25 • Service management 28 • Groups 29 3.2 Certificates for PKI 30 Sign certificate issued by external CA 32 • Request a signing certificate from an external CA 33 • Install an external signing certificate 33 • Switching out expired signing certificates 34 3.3 Domain-specific configuration 35 Enable drivers for domain-specific configuration files 35 • Enable drivers for storing configuration options in SQL database 36 • Migrate domain-specific configuration files to the SQL database 36 3.4 External authentication with Identity 36 Use HTTPD authentication 36 • Use X.509 37 iii OpenStack Administrator Guide 3.5 Integrate Identity with LDAP 37 Identity LDAP server set up 38 • Integrate Identity back end with LDAP 40 • Secure the OpenStack Identity service connection to an LDAP back end 44 3.6 Keystone tokens 46 Authorization scopes 46 • Token providers 47 3.7 Configure Identity service for token binding 48 3.8 Fernet - Frequently Asked Questions 49 What are the dierent types of keys? 49 • So, how does a staged key help me and why do I care about it? 50 • Where do I put my key repository? 50 • What is the recommended way to rotate and distribute keys? 51 • Do fernet tokens still expire? 51 • Why should I choose fernet tokens over UUID tokens? 51 • Why should I choose fernet tokens over PKI or PKIZ tokens? 51 • Should I rotate and distribute keys from the same keystone node every rotation? 52 • How do I add new keystone nodes to a deployment? 52 • How should I approach key distribution? 52 • How long should I keep my keys around? 54 • Is a fernet token still a bearer token? 54 • What if I need to revoke all my tokens? 54 • What can an attacker do if they compromise a fernet key in my deployment? 54 • I rotated keys and now tokens are invalidating early, what did I do? 55 3.9 Use trusts 57 3.10 Caching layer 58 Caching for tokens and tokens validation 59 • Caching for non-token resources 60 • Configure the Memcached back end example 60 3.11 Security compliance and PCI-DSS 61 Setting the account lockout threshold 61 • Disabling inactive users 62 • Configuring password expiration 62 • Indicating password strength requirements 62 • Requiring a unique password history 63 3.12 Example usage and Identity features 64 Logging 64 • User CRUD 65 3.13 Authentication middleware with user name and password 65 iv OpenStack Administrator Guide 3.14 Identity API protection with role-based access control (RBAC) 67 3.15 Troubleshoot the Identity service 69 Debug PKI middleware 70 • Debug signing key file errors 72 • Flush expired tokens from the token database table 73 4 Dashboard 74 4.1 Customize and configure the Dashboard 74 4.2 Set up session storage for the Dashboard 74 Local memory cache 75 • Cached database 78 • Cookies 78 4.3 Create and manage images 78 Create images 79 • Update images 81 • Delete images 82 4.4 Create and manage roles 82 Create a role 82 • Edit a role 83 • Delete a role 83 4.5 Manage instances 83 Create instance snapshots 84 • Control the state of an instance 84 • Track usage 85 4.6 Manage flavors 85 Create flavors 85 • Update flavors 87 • Update Metadata 88 • Delete flavors 89 4.7 Manage volumes and volume types 90 Create a volume type 90 • Create an encrypted volume type 90 • Delete volume types 93 • Delete volumes 93 4.8 Manage shares and share types 94 Create a share type 94 • Update share type 94 • Delete share types 95 • Delete shares 95 • Delete share server 96 • Delete share networks 96 4.9 View and manage quotas 97 View default project quotas 98 • Update project quotas 98 4.10 View cloud resources 99 View services information 99 • View cloud usage statistics 99 v OpenStack Administrator Guide 4.11 Create and manage host aggregates 100 To create a host aggregate 100 • To manage host aggregates 101 4.12 Launch and manage stacks using the Dashboard 102 5 Compute 103 5.1 System architecture 103 Hypervisors 104 • Projects, users, and roles 104 • Block storage 105 • EC2 compatibility API 107 • Building blocks 108 • Compute service architecture 109 5.2 Images and instances 111 Instance Launch 112 • Image properties and property protection 114 • Image download: how it works 117 • Instance building blocks 117 • Instance management tools 119 • Control where instances run 119 • Launch instances with UEFI 119 5.3 Networking with nova-network 120 Networking concepts 120 • DHCP server: dnsmasq 124 • Configure Compute to use IPv6 addresses 125 • Metadata service 126 • Enable ping and SSH on VMs 131 • Configure public (floating) IP addresses 131 • Remove a network from a project 134 • Multiple interfaces for instances (multinic) 135 • Troubleshooting Networking 138 5.4 System administration 143 Manage Compute users 144 • Manage volumes 144 • Flavors 145 • Compute service node firewall requirements 157 • Injecting the administrator password 158 • Manage the cloud 159 • Logging 163 • Secure with rootwrap 167 • Configure migrations 169 • Migrate instances 177 • Configure remote console access 180 • Configure Compute service groups 188 • Security hardening 190 • Recover from a failed compute node 195 • Advanced configuration 201 5.5 Troubleshoot Compute 216 Compute service logging 217 • Guru Meditation reports 217 • Common errors and fixes for Compute 218 • Credential errors, 401, and 403 forbidden errors 218 • Instance errors 219 • Empty log output for vi OpenStack Administrator Guide Linux instances 220 • Reset the state of an instance 220 • Injection problems 221 • Disable live snapshotting 221 6 Object Storage 222 6.1 Introduction to Object Storage 222 6.2 Features and benefits 222 6.3 Object Storage characteristics 224 6.4 Components 225 Proxy servers 227 • Rings 227 • Zones 228 • Accounts and containers 229 • Partitions 230 • Replicators 230 • Use cases 231 6.5 Ring-builder 233 Ring data structure 233 • Partition assignment list 234 • Overload 234 • Replica counts 235 • Partition shift value 235 • Build the ring 236 6.6 Cluster architecture 237 Access tier 237 • Storage nodes 240 6.7 Replication 242 Database replication 243 • Object replication 244 6.8 Large object support 244 Large objects 245 6.9 Object Auditor 245 6.10 Erasure coding 246 6.11 Account reaper 246 6.12 Configure project-specific image locations with Object Storage 248 6.13 Object Storage monitoring 248 Swift Recon 249 • Swift-Informant 250 • Statsdlog 250 • Swift StatsD logging 251 6.14 System administration for Object Storage 253 vii OpenStack Administrator Guide 6.15 Troubleshoot Object Storage 253 Drive failure 254 • Server failure 254 • Detect failed drives 255 • Emergency recovery of ring builder files 256 7 Block Storage 259 7.1 Increase Block Storage API service throughput 259 7.2 Manage volumes 260 Boot from volume 261 • Configure an NFS storage back end 261 • Configure a GlusterFS back end 264 • Configure multiple-storage back ends 268 • Back up Block Storage service disks 272 • Migrate volumes 277 • Gracefully remove a GlusterFS volume from usage 281 • Back up and restore volumes and snapshots 281 • Export and import backup metadata 285 • Use LIO iSCSI support 286 • Configure and use volume number weigher 286 • Consistency groups 287 • Configure and use driver filter and weighing for scheduler 294 • Rate-limit volume copy bandwidth 302 • Oversubscription in thin provisioning 303 • Image- Volume cache 306 • Volume-backed image 308 • Get capabilities 309 • Generic volume groups 315 7.3 Troubleshoot your installation 323 Troubleshoot the Block Storage configuration 323 • Multipath call failed exit 327 • Addressing discrepancies in reported volume sizes for EqualLogic storage 328 • Failed to Attach Volume, Missing sg_scan 332 • HTTP bad request in cinder volume log 332 • Duplicate 3PAR host 334 • Failed to attach volume after detaching 334 • Failed to attach volume, systool is not installed 335 • Failed to connect volume in FC SAN 336 • Cannot find suitable emulator for x86_64 336 • Non-existent host 337 • Non-existent VLUN 337 8 Shared File Systems 338 8.1 Introduction 338 viii OpenStack Administrator Guide 8.2 Key concepts 339 Share 339 • Share instance 339 • Snapshot 339 • Storage Pools 340 • Share Type 340 • Share Access Rules 340 • Security Services 340 • Share Networks 340 • Share Servers 341 8.3 Share management 341 Share basic operations 342 • Manage and unmanage share 357 • Manage and unmanage share snapshot 361 • Resize share 363 • Quotas and limits 367 8.4 Migrate shares 370 8.5 Share types 370 Share
Load more

Recommended publications
  • Building Your Hybrid Cloud Strategy with AWS Ebook
    Building Your Hybrid Cloud Strategy with AWS eBook A Guide to Extending and Optimizing Your Hybrid Cloud Environment Contents Introduction 3 Hybrid Cloud Benefits 4 Common AWS Hybrid Cloud Workloads 6 Key AWS Hybrid Cloud Technologies and Services 6 VMware Cloud on AWS 18 AWS Outposts: A Truly Consistent Hybrid Experience 21 Becoming Migration Ready 23 Hybrid Cloud Enablement Partners 24 Conclusion 26 Further Reading and Key Resources 27 © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Introduction Optimizing IT Across Cloud and On-Premises Environments Public sector organizations continue to do more with less, find ways to innovate and bring new ideas to their organizations while dealing with security and maintaining mission-critical legacy systems. Evolving cloud capabilities are transforming the IT landscape for many public sector organizations, some use cases a hybrid cloud approach can help ease and accelerate a path to modernization and cloud adoption. For some use cases a hybrid cloud approach became a more feasible path to IT modernization and cloud adoption. For example, some customers have applications that require the lowest network latency possible, or they already achieve consistent and predicable performance in an on- premises environment, but want to use new cloud tools to enhance the application (e.g. Enterprise Resource Planning systems, real-time sensor data processing, industrial automation and transaction processing). Some customers may encounter unique challenges such as federal regulations associated with data residency, or limitations on their use of the cloud. A hybrid cloud (the use of both on-premises and cloud resources), allows IT organizations to optimize the performance and costs of every application, project and system in either the cloud, on-premises datacenters, or a combination of both.
    [Show full text]
  • Magic Quadrant for Enterprise High-Productivity Application Platform As a Service
    This research note is restricted to the personal use of [email protected]. Magic Quadrant for Enterprise High- Productivity Application Platform as a Service Published: 26 April 2018 ID: G00331975 Analyst(s): Paul Vincent, Van Baker, Yefim Natis, Kimihiko Iijima, Mark Driver, Rob Dunie, Jason Wong, Aashish Gupta High-productivity application platform as a service continues to increase its footprint across enterprise IT as businesses juggle the demand for applications, digital business requirements and skill set challenges. We examine these market forces and the leading enterprise vendors for such platforms. Market Definition/Description Platform as a service (PaaS) is application infrastructure functionality enriched with cloud characteristics and offered as a service. Application platform as a service (aPaaS) is a PaaS offering that supports application development, deployment and execution in the cloud. It encapsulates resources such as infrastructure. High- productivity aPaaS (hpaPaaS) provides rapid application development (RAD) features for development, deployment and execution — in the cloud. High-productivity application platform as a service (hpaPaaS) solutions provide services for declarative, model-driven application design and development, and simplified one-button deployments. They typically create metadata and interpret that metadata at runtime; many allow optional procedural programming extensions. The underlying infrastructure of these solutions is opaque to the user as they do not deal with servers or containers directly. The rapid application development (RAD) features are often referred to as "low-code" and "no-code" support. These hpaPaaS solutions contrast with those for "high-control" aPaaS, which need professional programming — "pro-code" support, through third-generation languages (3GLs) — and provide transparent access to the underlying infrastructure.
    [Show full text]
  • An Introduction to Cloud Databases a Guide for Administrators
    Compliments of An Introduction to Cloud Databases A Guide for Administrators Wendy Neu, Vlad Vlasceanu, Andy Oram & Sam Alapati REPORT Break free from old guard databases AWS provides the broadest selection of purpose-built databases allowing you to save, grow, and innovate faster Enterprise scale at 3-5x the performance 14+ database engines 1/10th the cost of vs popular alternatives - more than any other commercial databases provider Learn more: aws.amazon.com/databases An Introduction to Cloud Databases A Guide for Administrators Wendy Neu, Vlad Vlasceanu, Andy Oram, and Sam Alapati Beijing Boston Farnham Sebastopol Tokyo An Introduction to Cloud Databases by Wendy A. Neu, Vlad Vlasceanu, Andy Oram, and Sam Alapati Copyright © 2019 O’Reilly Media Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://oreilly.com). For more infor‐ mation, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Development Editor: Jeff Bleiel Interior Designer: David Futato Acquisitions Editor: Jonathan Hassell Cover Designer: Karen Montgomery Production Editor: Katherine Tozer Illustrator: Rebecca Demarest Copyeditor: Octal Publishing, LLC September 2019: First Edition Revision History for the First Edition 2019-08-19: First Release The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. An Introduction to Cloud Databases, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. The views expressed in this work are those of the authors, and do not represent the publisher’s views.
    [Show full text]
  • Price-Performance in Modern Cloud Database Management Systems
    Price-Performance in Modern Cloud Database Management Systems McKnight Consulting Group December 2019 www.m c k n i g h t c g . c o m Executive Summary The pace of relational analytical databases deploying in the cloud are at an all-time high. And industry trends indicate that they are poised to expand dramatically in the next few years. The cloud is a disruptive technology, offering elastic scalability vis-à-vis on-premises deployments, enabling faster server deployment and application development, and allowing less costly storage. The cloud enables enterprises to differentiate and innovate with these database systems at a much more rapid pace than was ever possible before. For these reasons and others, many companies have leveraged the cloud to maintain or gain momentum as a company. The cost profile options for these cloud databases are straightforward if you accept the defaults for simple workload or POC environments. However, it can be enormously expensive and confusing if you seek the best price-performance for more robust, enterprise workloads and configurations. Initial entry costs and inadequately scoped POC environments can artificially lower the true costs of jumping into a cloud data warehouse environment. Cost predictability and certainty only happens when the entire picture of a production data warehouse environment is considered; all workloads, a true concurrency profile, an accurate assessment of users and a consideration of the durations of process execution. Architects and data warehouse owners must do their homework to make the right decision. With data warehouses, it is a matter of understanding the ways they scale, handle performance issues and concurrency.
    [Show full text]
  • The Impact of the Google Cloud to Increase the Performance for a Use Case in E-Commerce Platform
    International Journal of Computer Applications (0975 – 8887) Volume 177 – No. 35, February 2020 The Impact of the Google Cloud to Increase the Performance for a Use Case in E-Commerce Platform Silvana Greca Anxhela Kosta Department of Informatics Department of Informatics Faculty of Natural Sciences Faculty of Natural Sciences University of Tirana University of Tirana Tirana, Albania Tirana, Albania ABSTRACT Storing the unstructured and complex data in traditional SQL A massive amount of complex and huge digital data storing is database is very difficult[13]. For this reason, it was necessary caused due to the development of intelligent environments to create many types of database. NoSQL databases are useful and cloud computing. Today the organizations are using for applications that deal with very large semi-structured and Google Cloud platform to store and retrieve of all amount of unstructured data. NoSQL databases do not require a default their data at any time. Google offers database storage schema associated with the data. The purpose of the NoSQL like:Cloud Datastore for NoSQL non-relational database and databases is to increase the performance and scalability of a Cloud SQL for MySQL fully relational database. During specific application and service. years, enterprise organizations have accumulated growing Nowadays, e-commerce platform is very popular and is going stores of data, running analytics on that data to gain value through a transformation driven by customers who expect a from large information sets, and developing applications to seamless experience between online and in store. As a result, manage data exclusively. Traditional SQL databases are used many retailers are turning to cloud technologies in order to for storing and managing content of structured data, but with meet these needs.
    [Show full text]
  • Database Solutions on AWS
    Database Solutions on AWS Leveraging ISV AWS Marketplace Solutions November 2016 Database Solutions on AWS Nov 2016 Table of Contents Introduction......................................................................................................................................3 Operational Data Stores and Real Time Data Synchronization...........................................................5 Data Warehousing............................................................................................................................7 Data Lakes and Analytics Environments............................................................................................8 Application and Reporting Data Stores..............................................................................................9 Conclusion......................................................................................................................................10 Page 2 of 10 Database Solutions on AWS Nov 2016 Introduction Amazon Web Services has a number of database solutions for developers. An important choice that developers make is whether or not they are looking for a managed database or if they would prefer to operate their own database. In terms of managed databases, you can run managed relational databases like Amazon RDS which offers a choice of MySQL, Oracle, SQL Server, PostgreSQL, Amazon Aurora, or MariaDB database engines, scale compute and storage, Multi-AZ availability, and Read Replicas. You can also run managed NoSQL databases like Amazon DynamoDB
    [Show full text]
  • Performance Evaluation of Nosql Databases As a Service with YCSB: Couchbase Cloud, Mongodb Atlas, and AWS Dynamodb
    Performance Evaluation of NoSQL Databases as a Service with YCSB: Couchbase Cloud, MongoDB Atlas, and AWS DynamoDB This 24-page report evaluates and compares the throughput and latency of Couchbase Cloud, MongoDB Atlas, and Amazon DynamoDB across four varying workloads in three different cluster configurations. By Artsiom Yudovin, Data Engineer ​ ​ Uladzislau Kaminski, Senior Software Engineer ​ Ivan Shryma, Data Engineer ​ Sergey Bushik, Lead Software Engineer ​ Q4 2020 Table of Contents 1. Executive Summary 3 2. Testing Environment 3 2.1 YCSB instance configuration 3 2.2 MongoDB Atlas cluster configuration 4 2.3 Couchbase Cloud cluster configuration 5 2.4 Amazon DynamoDB cluster configuration 6 2.5 Prices 6 2.5.1 Couchbase costs 7 2.5.2 MongoDB Atlas costs 7 2.5.3 Amazon DynamoDB costs 8 3. Workloads and Tools 8 3.1 Workloads 8 3.2 Tools 8 4. YCSB Benchmark Results 10 4.1 Workload A: The update-heavy mode 10 4.1.1 Workload definition and model details 10 4.1.2 Query 10 4.1.3 Evaluation results 11 4.1.4 Summary 12 4.2 Workload E: Scanning short ranges 12 4.2.1 Workload definition and model details 12 4.2.3 Evaluation results 14 4.2.4 Summary 15 4.3 Pagination Workload: Filter with OFFSET and LIMIT 15 ​ 4.3.1 Workload definition and model details 15 4.3.2 Query 17 4.3.3 Evaluation results 17 4.3.4 Summary 18 4.4 JOIN Workload: JOIN operations with grouping and aggregation 18 ​ ​ 4.4.1 Workload definition and model details 18 4.4.2 Query 19 4.4.3 Evaluation results 20 4.4.4 Summary 20 5.
    [Show full text]
  • Run Critical Databases in the Cloud
    Cloud Essentials Run Critical Databases in the Cloud Oracle has the most complete data management portfolio for any enterprise workload. Cloud computing is transforming business practices and simplifying data center operations. However, when it comes to moving critical database assets to the cloud, many IT leaders are cautious—and rightly so. They have seen the limitations of popular commodity cloud solutions, which mostly consist of fragmented hardware and software offerings that must be manually configured. IT pros must build their own platforms on top of the service provider’s commodity infrastructure, migrate their data, and then figure out how to keep everything in sync with the apps and data still maintained on premise. Oracle Autonomous Database provides enterprise-level scalability, security, performance, and automation—at a level that often exceeds what you can achieve in your own data center. You can subscribe to complete database platforms with a few clicks, eliminating the need to provision, build, and manage in-house databases and storage systems. With pay-as-you-grow configurations—all managed by Oracle experts— your organization will obtain operational flexibility with zero up-front capital expenses. It’s a great way to lower operational costs because you pay only for what you use. Read on to discover what a powerful cloud database can do for your business. Migrating to a Cloud Computing Model Modern businesses depend on their data more than cloud services work together automatically— ever before. That data is coming at an alarming rate, and in many cases, autonomously. placing crushing demands on data marts, enterprise data warehouses, and analytics systems.
    [Show full text]
  • Cloud Database Battle: AWS Vs. DIY Vs. Oracle
    Cloud Database Battle: AWS vs. DIY vs. Oracle Cloud Database Battle: AWS vs. DIY vs. Oracle by, David Floyer January 18th, 2021 The first premise of this research is that architecting the Oracle Cloud Database service to run on specialized hardware and software, either on-premises or in Oracle Cloud Infrastructure (OCI), allows the cloud database vendor to reduce costs significantly. This approach also allows the vendor to provide autonomous services based on economies of scale that further reduce the operational support costs. The combination of the two methods leads to halving the cost of running today’s cloud database application suites. The second premise is that future synchronous automation of business processes will require real-time integration between systems-of-record, advanced analytic/AI inference systems, and other data and cloud database types. This integration can only be achieved by sharing data between database types. Also, the operation of synchronous applications is too complex for traditional operational processes. Therefore, high levels of cloud database and application automation, and machine learning are imperatives for synchronous application deployment. Oracle Cloud Database is Tier-1 and in a class of its own. Wikibon recommends that larger enterprises with mission-critical workloads should not convert from Oracle to other databases. Instead, Wikibon recommends migrating to Autonomous Cloud Database on Oracle Exadata Cloud@Customer X8M, Oracle Exadata Cloud Service on OCI, or other Oracle Database cloud services. Wikibon recommends that enterprises minimize the number of separate databases and data types and use the converged Oracle Cloud Database instead. © 2021 Wikibon Research | Page 1 Cloud Database Battle: AWS vs.
    [Show full text]
  • Planning and Designing Databases on Aws(Awss04)Englisch
    PLANNING AND DESIGNING DATABASES ON AWS (AWSS04) ENGLISCH In this course, you will learn about the process of planning and designing both relational and nonrelational AWS databases. It will teach you how to use workload requirements to define database design considerations and also explore the features and capabilities of the eight AWS database services. By the end of the course, you will be able to determine which AWS database service is right for your workloads, and design the database to meet your requirements. Target Group • Data Engineers who are new to designing cloud databases or nonrelational databases • Solutions Architects who are designing services or architectures that are integrated with databases • Developers that are building cloud database-enabled applications Prerequisites • Familiarity with AWS Database Services, equivalent to AWS Database Offerings digital training • Understanding of database design concepts, and/or data modeling for relational or nonrelational databases • Familiarity with cloud computing concepts • Familiarity with general networking and encryption concepts • Understanding of the three V’s of data (volume, velocity, and variety) • Familiarity with basic data analytics concepts, equivalent to Data Analytics Fundamentals digital training • Understanding of general architecting best practices and the AWS Well-Architected Framework, equivalent to Architecting on AWS classroom training Main Topics • Apply database concepts, database management, and data modeling techniques • Evaluate hosting databases on
    [Show full text]
  • Recent Trends for Efficient and Secure Accessing Scheme for Cloud Database
    © 2017 IJEDR | Volume 5, Issue 4 | ISSN: 2321-9939 Recent Trends for Efficient and Secure Accessing Scheme for Cloud Database Dr. Santosh S. Lomte1, Swati V. Khidse2 1Principal VDF’s School of Engineering & Technology, Latur, India, 2 PhD Student 1, 2 Department of Computer Science & Engineering, 2Dr. B. A. M. University, Aurangabad, Maharashtra, India. ________________________________________________________________________________________________________ Abstract - Cloud computing provides an enormous amount of virtual storage, it provides access to servers, storage, databases and a broad set of application services over the Internet. Its popularity is growing day by day. Consequently, there is a need for strong authentication schemes for securing access to cloud database. Data protection and security are the primary factors in cloud database for gaining user's trust and making successful use of cloud technology. There are number of data protections and data security techniques that have been proposed in the research field of cloud computing. However, there is need for enhancing data protection techniques. Index Terms—Encryption, Data Protection, Confidentiality, Obfuscation; ________________________________________________________________________________________________________ I. INTRODUCTION Cloud computing allows their users to store and access computing resources and data over INTERNET rather than from the local hard drive. It also helps to increase the storage capacity because users can use more than one cloud services for storing their data and thus reduce the cost because there is no need for owning an expensive computer with larger memory. According to the US National Institute of Standards and Technology (NIST), cloud computing is a model enabling ubiquitous, convenient, on- demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction [1].
    [Show full text]
  • Database High Availability As a Service for Cloud
    DBHAAAS – DATABASE HIGH AVAILABILITY AS A SERVICE FOR CLOUD COMPUTING A DISSERTATION IN Computer Science and Telecommunications and Computer Networking Presented to the Faculty of the University of Missouri-Kansas City in partial fulfillment of the requirements for the degree DOCTOR OF PHILOSOPHY by CHETAN JAISWAL B.E., Rajiv Gandhi Technical University, 2007 Kansas City, Missouri 2016 © 2016 CHETAN JAISWAL ALL RIGHTS RESERVED DBHAAAS – DATABASE HIGH AVAILABILITY AS A SERVICE FOR CLOUD COMPUTING Chetan Jaiswal, Candidate for the Doctor of Philosophy Degree University of Missouri-Kansas City, 2016 ABSTRACT On conventional database systems, the recovery manager applies transaction Undo or Redo operation or a combination of them to recover the last consistent state of the database from a system failure. Transaction redo, compared to undo, helps to shorten the system downtime so the execution of transactions is managed in such a way that majority of transactions require redo to recover the database. To further reduce the recovery time, the recovery module uses “Checkpoint” operation. Even though it is possible to eliminate transaction redo altogether, the conventional system architecture, however, is not capable to deploy innovative approaches. The availability of “Virtual” machines on cloud has given us an architecture that makes it possible to completely do away with transaction redo which allows us to eliminate the effect of system or transaction failure by taking the database to the next consistent state. In this dissertation, we present a novel scheme of eliminating the effect of such failures by applying transaction “roll-forward.” Our approach intelligently applies roll-forward from the iii point of failure which removes the effect of system failure on the database.
    [Show full text]