From f7b65798aad6dd8f8d73537d2533aad7066b5c1e Mon Sep 17 00:00:00 2001 From: Bogdan Dobrelya Date: Tue, 5 Jun 2018 11:56:15 +0200 Subject: [PATCH] Clarify docker vs moby containers runtime/images 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 --- doc/source/install/containers_deployment/undercloud.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/source/install/containers_deployment/undercloud.rst b/doc/source/install/containers_deployment/undercloud.rst index dcb898e7..6f7a1e3c 100644 --- a/doc/source/install/containers_deployment/undercloud.rst +++ b/doc/source/install/containers_deployment/undercloud.rst @@ -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