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.6 KiB
1.6 KiB
Specialized cases
specialized-multi-hypervisor.rst specialized-networking.rst specialized-software-defined-networking.rst specialized-desktop-as-a-service.rst specialized-openstack-on-openstack.rst specialized-hardware.rst
Although most OpenStack architecture designs fall into one of the seven major scenarios outlined in other sections (compute focused, network focused, storage focused, general purpose, multi-site, hybrid cloud, and massively scalable), there are a few use cases that do not fit into these categories. This section discusses these specialized cases and provide some additional details and design considerations for each use case:
Specialized networking <specialized-networking>
: describes running networking-oriented software that may involve reading packets directly from the wire or participating in routing protocols.Software-defined networking (SDN) <specialized-software-defined-networking>
: describes both running an SDN controller from within OpenStack as well as participating in a software-defined network.Desktop-as-a-Service <specialized-desktop-as-a-service>
: describes running a virtualized desktop environment in a cloud (Desktop-as-a-Service
). This applies to private and public clouds.OpenStack on OpenStack <specialized-openstack-on-openstack>
: describes building a multi-tiered cloud by running OpenStack on top of an OpenStack installation.Specialized hardware <specialized-hardware>
: describes the use of specialized hardware devices from within the OpenStack environment.