d7b5e0eaa9
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
1.4 KiB
Design
Designing an OpenStack cloud requires a understanding of the cloud user's requirements and needs to determine the best possible configuration. This chapter provides guidance on the decisions you need to make during the design process.
To design, deploy, and configure OpenStack, administrators must understand the logical architecture. OpenStack modules are one of the following types:
- Daemon
-
Runs as a background process. On Linux platforms, a daemon is usually installed as a service.
- Script
-
Installs a virtual environment and runs tests.
- Command-line interface (CLI)
-
Enables users to submit API calls to OpenStack services through commands.
logical_architecture
shows one example of the most common integrated services within
OpenStack and how they interact with each other. End users can interact
through the dashboard, CLIs, and APIs. All services authenticate through
a common Identity service, and individual services interact with each
other through public APIs, except where privileged administrator
commands are necessary.
design-compute.rst design-storage.rst design-networking.rst design-identity.rst design-images.rst design-control-plane.rst design-cmp-tools.rst