openstack/openstack-helm
Code Issues Proposed changes

Fix AIO docs to reference ceph.enabled flags for libvirt

Browse Source 
Libvirt uses ceph to back pvcs by default.  To minimalize the
requirements for a development all in one installation, include
flags for disabling ceph for libvirt

Change-Id: I3aba5deb9a972111bf5dde8b8f97a4ac40cd842b
This commit is contained in:
Steve Wilkerson 2017-11-13 14:25:33 -06:00
parent f8377b1258
commit dc6e14e246
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/install/developer/all-in-one.rst
View File

@ -233,9 +233,23 @@ OpenStack services depend upon them.
helm install --name=etcd-rabbitmq ./etcd --namespace=openstack
helm install --name=rabbitmq ./rabbitmq --namespace=openstack
helm install --name=ingress ./ingress --namespace=openstack
helm install --name=libvirt ./libvirt --namespace=openstack
helm install --name=openvswitch ./openvswitch --namespace=openstack
Libvirt backs persistent volume claims with Ceph by default. To run libvirt
in an all-in-one environment without Ceph, ceph for libvirt must be disabled.
.. code-block:: shell
helm install --name=libvirt ./libvirt --namespace=openstack \
--set ceph.enabled=false
If Ceph is included as part of an all-in-one deployment, libvirt can be
installed as normal.
.. code-block:: shell
helm install --name=libvirt ./libvirt --namespace=openstack
Once the OpenStack infrastructure components are installed and running, the
OpenStack services can be installed. In the below examples the default values
that would be used in a production-like environment have been overridden with