Add NovaApiMaxLimit configure max_limit for nova
Currently, we can't set Nova [api]/max_limit using a supplied Heat parameter. This change adds a Heat parameter that will make it easier for users to configure max_limit in nova.conf. Conflicts: deployment/nova/nova-api-container-puppet.yaml Change-Id: I4c28c6c90c52f22d4fa81d13e85842ce876ec2b9 closes-bug: 1904096 (cherry picked from commit603530c711
) (cherry picked from commiteccd5435d9
) (cherry picked from commit92e7af3954
)
This commit is contained in:
parent
43049567a7
commit
8bc8771bc7
|
@ -109,6 +109,10 @@ parameters:
|
|||
default: false
|
||||
description: Allow destination machine to match source for resize.
|
||||
type: boolean
|
||||
NovaApiMaxLimit:
|
||||
default: 1000
|
||||
description: Max number of objects returned per API query
|
||||
type: number
|
||||
|
||||
conditions:
|
||||
|
||||
|
@ -194,6 +198,7 @@ outputs:
|
|||
nova::keystone::authtoken::auth_uri: {get_param: [EndpointMap, KeystoneInternal, uri_no_suffix] }
|
||||
nova::keystone::authtoken::auth_url: {get_param: [EndpointMap, KeystoneInternal, uri_no_suffix]}
|
||||
nova::keystone::authtoken::region_name: {get_param: KeystoneRegion}
|
||||
nova::api::max_limit: {get_param: NovaApiMaxLimit}
|
||||
nova::api::enabled: true
|
||||
nova::api::default_floating_pool: {get_param: NovaDefaultFloatingPool}
|
||||
nova::api::sync_db_api: true
|
||||
|
|
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
The NovaApiMaxLimit parameter allows the operator to set Nova API
|
||||
max_limit using a Heat parameter in their templates.
|
Loading…
Reference in New Issue