Added vendor_data.json support
This patch adds the ability for a deployer to add vendor_data.json for deployments. It can make things configurable via a simple dictionary. Change-Id: If5b061776120c3d7a7ff763eb2757c0b5b184000
This commit is contained in:
5 changed files with 12 additions and 0 deletions
@@ -557,6 +557,7 @@ nova_nova_conf_overrides: {}
nova_rootwrap_conf_overrides:{}
nova_api_paste_ini_overrides:{}
nova_policy_overrides:{}
nova_vendor_data_overrides:{}
nova_placement_uwsgi_ini_overrides:{}
nova_api_metadata_uwsgi_ini_overrides:{}
nova_api_os_compute_uwsgi_ini_overrides:{}
@@ -0,0 +1,4 @@
---
features:
- Added the ability to configure vendor data for Nova in order to be able to
push things via the metadata service or config drive.
@@ -47,6 +47,10 @@
dest:"/etc/nova/api-paste.ini"
config_overrides:"{{ nova_api_paste_ini_overrides }}"
config_type:"ini"
- src:"vendor_data.json.j2"
dest:"/etc/nova/vendor_data.json"
config_overrides:"{{ nova_vendor_data_overrides }}"
config_type:"json"
- src:"policy.json.j2"
dest:"/etc/nova/policy.json-{{ nova_venv_tag }}"
config_overrides:"{{ nova_policy_overrides }}"
@@ -295,6 +295,7 @@ secure_proxy_ssl_header = {{ nova_secure_proxy_ssl_header }}
auth_strategy = keystone
enable_instance_password = {{ nova_enable_instance_password }}
use_forwarded_for = {{ nova_network_services[nova_network_type]['use_forwarded_for'] | bool }}
vendordata_jsonfile_path = /etc/nova/vendor_data.json
[scheduler]
max_attempts = {{ nova_scheduler_max_attempts }}
2
templates/vendor_data.json.j2
Normal file
2
templates/vendor_data.json.j2
Normal file
@@ -0,0 +1,2 @@
{
}
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.