92a432fde7
Turns out we've a *lot* of disparate metadata systems. Attempt to both link them somewhat through extensive cross-referencing and extract out deployment-specific stuff from user-facing docs. Lots of changes here, but in summary: - Split out admin-focused content from the metadata API, config drive, user data and vendordata docs. - Merge the config drive, metadata service, vendordata and user-data user docs, which are mostly talking about the same thing and are fairly barren without the deployment components - Make use of various oslo.config and Sphinx roles Side note: I miss when we have tech writers to do this stuff for us :( Change-Id: I4fb2b628bd93358a752e2397ae353221758e2984 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
1.5 KiB
Compute
The OpenStack Compute service allows you to control an Infrastructure-as-a-Service (IaaS) cloud computing platform. It gives you control over instances and networks, and allows you to manage access to the cloud through users and projects.
Compute does not include virtualization software. Instead, it defines drivers that interact with underlying virtualization mechanisms that run on your host operating system, and exposes functionality over a web-based API.
admin-password-injection.rst adv-config.rst arch.rst availability-zones.rst cells.rst config-drive.rst configuration/index.rst configuring-migrations.rst cpu-topologies.rst default-ports.rst evacuate.rst flavors.rst huge-pages.rst live-migration-usage.rst manage-logs.rst manage-the-cloud.rst manage-users.rst manage-volumes.rst metadata-service.rst migration.rst migrate-instance-with-snapshot.rst networking-nova.rst networking.rst node-down.rst pci-passthrough.rst quotas2.rst quotas.rst remote-console-access.rst root-wrap-reference.rst security-groups.rst security.rst service-groups.rst services.rst ssh-configuration.rst support-compute.rst system-admin.rst secure-live-migration-with-qemu-native-tls.rst mitigation-for-Intel-MDS-security-flaws.rst vendordata.rst