openstack/tripleo-docs
Code Issues Proposed changes

Clarify docker vs moby containers runtime/images

Browse Source 
For containerized undercloud as a good start, avoid using
references to Docker if only not limited to the docker CLI
commands.

Whenever we refer to *architecture* for containers runtime and
images (CRI & OCI), refer to Moby instead.

This creates less confusion for readers might be expecting more
features of Docker is used, like Swarm as COE, while it is not.

Eventually, this replacement should happen to all places.

Change-Id: Ia731d7a151f0a294297b0528173e36577ad0dfeb
This commit is contained in:
Bogdan Dobrelya 2018-06-05 11:56:15 +02:00
parent 64163d1a1c
commit f7b65798aa
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/install/containers_deployment/undercloud.rst
View File

@ -5,9 +5,11 @@ The requirements for a containerized undercloud are the same as for any other
undercloud deployment. The real difference is in where the undercloud services
will be deployed (containers vs base OS).
The docker based undercloud architecture is not very different from the
baremetal/VM based one. The services deployed in the traditional baremetal
undercloud are also deployed in the docker based one.
The undercloud architecture based on Moby_ containers is not very different from
the baremetal/VM based one. The services deployed in the traditional baremetal
undercloud are also deployed in the containers based one.
.. _Moby: https://mobyproject.org/
One obvious difference between these two types of deployments is that the
openstack services are deployed as containers in a container runtime rather than