From 2c13a5f2583f10e104b6220daf8c61d0273dc733 Mon Sep 17 00:00:00 2001 From: yufei <zhangyf@rc.inesa.com> Date: Mon, 19 Mar 2018 11:26:33 +0800 Subject: [PATCH] s/openstack_version/openstack_release/g replace openstack_version with openstack_release Change-Id: Ib7cb3ae220971bbfdaf5e1e382333f6c62fd130a --- doc/source/user/operating-kolla.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/user/operating-kolla.rst b/doc/source/user/operating-kolla.rst index ddbaa7b1b6..56a941639c 100644 --- a/doc/source/user/operating-kolla.rst +++ b/doc/source/user/operating-kolla.rst @@ -28,13 +28,13 @@ choosing. If the alpha identifier is not used, Kolla will deploy or upgrade using the version number information contained in the release. To customize the -version number uncomment openstack_version in globals.yml and specify +version number uncomment openstack_release in globals.yml and specify the version number desired. For example, to deploy a custom built Liberty version built with the ``kolla-build --tag 1.0.0.0`` operation, change globals.yml:: - openstack_version: 1.0.0.0 + openstack_release: 1.0.0.0 Then run the command to deploy:: @@ -43,7 +43,7 @@ Then run the command to deploy:: If using Liberty and a custom alpha number of 0, and upgrading to 1, change globals.yml:: - openstack_version: 1.0.0.1 + openstack_release: 1.0.0.1 Then run the command to upgrade:: -- GitLab