'code-block' improves the visibility for the pieces of code. This
commit splits code and result message by using 'code-block: python' and
'code-block: console'.
Change-Id: Id11e0990da4dae8d47c6de7d19479cb9940890b2
Magnum CLI now support cluster-config command. However, the quickstart guide
hasn't been updated to use this command yet. This patch added usage for
cluster-config command in quickstart guide.
Change-Id: I21341fe90c09f8f21e33bda4592c9175f3d16375
Closes-Bug: #1614685
Patch: https://review.openstack.org/#/c/352806 has
set host=None and we don't change this parameter
neither in devstack installation nor in manual installation.
With this patch value of [DEFAULT]/host is set to
hostname of the host on which magnum is setup.
Also, updated manual installation step to set [DEFAULT]/host
to hostname.
Depends-on: I51feb6ccdc0fab91a591568866e6801f2bbb319b
Change-Id: Id43bfcc792b28c98c9bf1d888dd7ddcc167e8ea5
Closes-Bug: #1630190
Update from this commit https://review.openstack.org/#/c/389971/1
in the openstack-manuals project.
Follow-up of I54a104662081ab7b81e200cf6c23f5a8a1e28d61.
Change-Id: Ide7d831a749c394c90ac8303643fd1184bb0c56f
Related-Bug: #1635615
Updates magnum documentation to reflect the changes made for
bp/rename-id-parameter-names.
Change-Id: I7c0d69970b9ac50649cac0e80932b5971ce09c3f
Depends-on: Idc6b9322ec7c0ecb386162ca46c7d49b910685d8
Implements: blueprint rename-id-parameter-names
In the swarm_atomic and k8s_atomic drivers container images are
stored in a dedicated cinder volume per cluster node. It is
proven that this architecture can be a scalability bottleneck.
Make the use of cinder volumes for container images and opt-in
option. If docker-volume-size is not specified no cinder
volumes will be created. Before, if docker-volume-size wasn't
specified the default value was 25.
To use cinder volumes for container storage the user will
interact with magnum as before, (meaning the valid values are
integers starting from 1).
Closes-Bug: #1638006
Change-Id: I3394c62a43bbf950b7cf0b86a71b1d9b0481d68f
This patch fixes the issue when functional tests are run
against a deployment that has https based endpoints.
The insecure option is not being passed when initiating
magnumclient or keystoneclient as a result we get SSL
error.
Change-Id: I35525917b96b64e57c984924c72b3c696949f67f
Closes-Bug: #1640341
The troubleshooting guide has a python script in it which has invalid
syntax. This removes the extra bracket from that script and makes it
function correctly. I also added some more specificity for credentials.
Change-Id: I9c8b8f861b4226d9eddca4ab44c811faa89160bc