openstack/kayobe
Code Issues Proposed changes

Update documentation for container-image-builders group

Browse Source
This commit is contained in:
Mark Goddard 2017-11-23 09:54:17 +00:00
parent 5f6c181c69
commit 610c8a9566
3 changed files with 19 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/architecture.rst
View File

@ -12,8 +12,8 @@ Control host
be installed, and is typically where the cloud will be managed from. be installed, and is typically where the cloud will be managed from.
Seed host Seed host
The seed host runs the bifrost deploy container and is used to provision The seed host runs the bifrost deploy container and is used to provision
the cloud hosts. Typically the seed host is deployed as a VM but this is the cloud hosts. By default, container images are built on the seed.
not mandatory. Typically the seed host is deployed as a VM but this is not mandatory.
Cloud hosts Cloud hosts
The cloud hosts run the OpenStack control plane, network, monitoring, The cloud hosts run the OpenStack control plane, network, monitoring,
storage, and virtualised compute services. Typically the cloud hosts run storage, and virtualised compute services. Typically the cloud hosts run

16
doc/source/deployment.rst
View File

@ -117,8 +117,11 @@ Building Container Images
It is possible to use prebuilt container images from an image registry such as It is possible to use prebuilt container images from an image registry such as
Dockerhub. In some cases it may be necessary to build images locally either to Dockerhub. In some cases it may be necessary to build images locally either to
apply local image customisation or to use a downstream version of kolla. To apply local image customisation or to use a downstream version of kolla.
build images locally:: Images are built by hosts in the ``container-image-builders`` group, which by
default includes the ``seed``.
To build container images::
(kayobe) $ kayobe seed container image build (kayobe) $ kayobe seed container image build
@ -289,8 +292,13 @@ Building Container Images
as Dockerhub. In this case, this step can be skipped. as Dockerhub. In this case, this step can be skipped.
In some cases it may be necessary to build images locally either to apply local In some cases it may be necessary to build images locally either to apply local
image customisation or to use a downstream version of kolla. To build images image customisation or to use a downstream version of kolla. Images are built
locally:: by hosts in the ``container-image-builders`` group, which by default includes
the ``seed``. If no seed host is in use, for example in an all-in-one
controller development environment, this group may be modified to cause
containers to be built on the controllers.
To build container images::
(kayobe) $ kayobe overcloud container image build (kayobe) $ kayobe overcloud container image build

5
doc/source/release-notes.rst
View File

@ -46,6 +46,11 @@ Upgrade Notes
from ``kolla_config_path`` to ``kolla_build_config_path``. This provides a from ``kolla_config_path`` to ``kolla_build_config_path``. This provides a
cleaner separation of kolla and kolla-ansible configuration options. The cleaner separation of kolla and kolla-ansible configuration options. The
default value is ``{{ config_path }}/kolla``. default value is ``{{ config_path }}/kolla``.
* Adds a group ``container-image-builders``, which defaults to containing the
seed. Hosts in this group will build container images. Previously, container
images for the seed were built on the seed, and container images for the
overcloud were built on the controllers. The new design is intended to
encourage a build, push, pull workflow.
Kayobe 3.0.0 Kayobe 3.0.0
============ ============