openstack/charm-guide
Code Issues Proposed changes

Update openstack-on-lxd section

Browse Source 
Add pike and related comments to document

Change-Id: Ide157e43a827ac468923ab27dec1ce3ab4a1cfec
This commit is contained in:
Andrew McLeod
2018-01-12 12:13:01 +01:00
parent 759e6405c2
commit abfab7799f
1 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/openstack-on-lxd.rst
View File

@@ -20,7 +20,7 @@ The tools in the openstack-on-lxd git repository require the use of Juju 2.x, wh
.. code:: bash .. code:: bash
sudo add-apt-repository cloud-archive:ocata -y && sudo apt update sudo add-apt-repository cloud-archive:pike -y && sudo apt update
sudo apt-get install juju lxd zfsutils-linux squid-deb-proxy \ sudo apt-get install juju lxd zfsutils-linux squid-deb-proxy \
python-novaclient python-keystoneclient python-glanceclient \ python-novaclient python-keystoneclient python-glanceclient \
@@ -159,6 +159,11 @@ For amd64, arm64, or ppc64el Ocata:
juju deploy bundle-ocata.yaml juju deploy bundle-ocata.yaml
For amd64, arm64, or ppc64el Pike:
.. code:: bash
juju deploy bundle-pike.yaml
For s390x Mitaka: For s390x Mitaka:
.. code:: bash .. code:: bash
@@ -177,6 +182,12 @@ For s390x Ocata:
juju deploy bundle-ocata-s390x.yaml juju deploy bundle-ocata-s390x.yaml
For s390x Pike:
.. code:: bash
juju deploy bundle-pike-s390x.yaml
You can watch deployment progress using the 'juju status' command. This may take some time depending on the speed of your system; CPU, disk and network speed will all effect deployment time. You can watch deployment progress using the 'juju status' command. This may take some time depending on the speed of your system; CPU, disk and network speed will all effect deployment time.
Using the Cloud Using the Cloud
@@ -202,6 +213,9 @@ Upload an image
Before we can boot an instance, we need an image to boot in Glance. Before we can boot an instance, we need an image to boot in Glance.
Note: If you are using a ZFS backend for this deployment, force-raw-images must be disabled on the nova-compute charm in Pike and later.
We have made this the default in our bundles - however, be aware that using this setting in a production environment is discouraged as it may have an impact on performance.
For amd64: For amd64:
.. code:: bash .. code:: bash