openstack/openstack-manuals
Code Issues Proposed changes
50166c1f43
openstack-manuals/doc/arch-design-to-archive/source/introduction-how-this-book-is-organized.rst
daz d7b5e0eaa9 [arch-design] Publish draft Arch Guide to docs.openstack.org 
1. Unpublish the current arch-design and temporarily relocate it to a
"to archive" directory until the archiving structure is available
2. Publish the arch-design-draft to docs.openstack.org
3. Unpublish arch-design-draft from https://docs.openstack.org/draft/

Change-Id: Ida5f237d2edce7a83a24c376c355e2c220bc8c28
Implements: blueprint arch-design-pike
2017-03-08 23:02:35 +00:00

1.4 KiB
Raw Blame History

How this book is organized

This book examines some of the most common uses for OpenStack clouds, and explains the considerations for each use case. Cloud architects may use this book as a comprehensive guide by reading all of the use cases, but it is also possible to review only the chapters which pertain to a specific use case. The use cases covered in this guide include:

  • General purpose<generalpurpose>: Uses common components that address 80% of common use cases.
  • Compute focused<compute-focus>: For compute intensive workloads such as high performance computing (HPC).
  • Storage focused<storage-focus>: For storage intensive workloads such as data analytics with parallel file systems.
  • Network focused<network-focus>: For high performance and reliable networking, such as a content delivery network (CDN).
  • Multi-site<multi-site>: For applications that require multiple site deployments for geographical, reliability or data locality reasons.
  • Hybrid cloud<hybrid>: Uses multiple disparate clouds connected either for failover, hybrid cloud bursting, or availability.
  • Massively scalable<massively-scalable>: For cloud service providers or other large installations.
  • Specialized cases<specialized>: Architectures that have not previously been covered in the defined use cases.