api-guide: remove empty sections about inter-service interactions

The todos here are just kind of embarrassing so rather than try
to flesh these out we should just remove them.

The alternative would be writing something at a very high level
like 'the compute service works with the image service to get
the guest operating system image and create snapshots', 'the
compute service works with the block storage service to use
persistent volumes as root volumes with an operating
system image or data volumes', 'the compute service works with
the networking service to provide network access to the server
and firewall rules using security groups' and then link to the
glance, cinder and neutron docs, but I'm not sure it's worth it.

Change-Id: I7f7ca4cc5781a93c0b7b508b5c29e1f6f28194ad
This commit is contained in:
Matt Riedemann 2019-11-22 16:45:33 -05:00
parent 173831558f
commit 1319931f46
1 changed files with 0 additions and 27 deletions

View File

@ -276,30 +276,3 @@ on compute hosts rather than servers.
Administrators are able to query the records in database for information
about migrations. For example, they can determine the source and
destination hosts, type of migration, or changes in the server's flavor.
Relationship with Volume API
============================
Here we discuss about Cinder's API and how Nova users volume UUIDs.
.. todo:: add more details.
Relationship with Image API
===========================
Here we discuss about Glance's API and how Nova uses image UUIDs.
We also discuss how Nova proxies setting image metadata.
.. todo:: add more details.
Interactions with neutron and nova-network (deprecated)
=======================================================
We talk about how networking can be provided be either neutron or
nova-network (deprecated).
Here we discuss about Neutron's API and how Nova users port UUIDs.
We also discuss Nova automatically creating ports, proxying security groups,
and proxying floating IPs. Also talk about the APIs we do not proxy.
.. todo:: add more details.