Add option to enable/disable the nova v2.1 API

Code Issues Proposed changes

In the kilo release the nova v2.1 API is tied to the v3 API, so v3 needs
to be enabled for v2.1 to be enabled as well. This change adds a setting
to control whether the v2.1 API should be enabled or disabled. If v2.1
is enabled then v3 will be enabled as well, but without registering it
with the keystone catalog.
Change-Id: I1e80189bbcbef1dd712cd6a527b5b59aa939e9e1
Closes-Bug: #1445524

This commit is contained in:

Miguel Grinberg

2015年04月17日 10:42:26 -07:00

parent cf68c09363

commit 43a18646c7

3 changed files with 9 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

7
templates/nova.conf.j2

View File

@@ -142,7 +142,12 @@ workers = {{ nova_conductor_workers | default(api_threads) }}

[osapi_v3]

enabled = {{ nova_v3_deprecated_but_enabled }}

# note that this setting enables both the v3 and v2.1 APIs in kilo

{% if nova_v3_deprecated_but_enabled == true or nova_v3_deprecated_but_enabled == 'True' or nova_v21_enabled == true or nova_v21_enabled == 'True' %}

enabled = true

{% else %}

enabled = false

{% endif %}

[keystone_authtoken]

Add option to enable/disable the nova v2.1 API

7 templates/nova.conf.j2 Unescape Escape View File

7
templates/nova.conf.j2

View File