Use config drive in the vm plugged directly to the external network
In such networks there is a problem with providing metadata service without enabling isolated_metadata in the dhcp agent. So easier way to make it working in all deployments is to use config drive. That patch is doing exactly that. Change-Id: Icf5df07fb02e84fafb49e5c1813d1aed59a03249
This commit is contained in:
parent
27e0ce5ef3
commit
46353126fc
|
@ -314,6 +314,8 @@ class ExternalServerStackFixture(ServerStackFixture):
|
|||
# external servers doesn't need floating IPs
|
||||
has_floating_ip = False
|
||||
|
||||
config_drive = True
|
||||
|
||||
@property
|
||||
def floating_network(self):
|
||||
return self.network_stack.network_id
|
||||
|
|
|
@ -57,6 +57,11 @@ parameters:
|
|||
type: json
|
||||
description: Hints to create server
|
||||
|
||||
config_drive:
|
||||
type: boolean
|
||||
description: Whenever server should use config drive with metadata or not
|
||||
default: false
|
||||
|
||||
user_data:
|
||||
type: string
|
||||
default: ''
|
||||
|
@ -95,6 +100,7 @@ resources:
|
|||
networks:
|
||||
- port: {get_resource: port}
|
||||
scheduler_hints: {get_param: scheduler_hints}
|
||||
config_drive: {get_param: config_drive}
|
||||
user_data_format: RAW
|
||||
user_data: {get_param: user_data}
|
||||
|
||||
|
|
Loading…
Reference in New Issue