Depending on you OpenStack configuration, you might need additional configuration options for the validator to run. Note that all of these settings need to be done similarly for BOSH once you deploy a Director or Cloud Foundry.
You can add your certificate chain in the property openstack.connection_options.ca_cert. Read more on the topic at bosh.io.
By default, hypervisor-local storage is used for a VMs boot disk. If your OpenStack setup requires you to use disks from block storage instead, you can set openstack.boot_from_volume: true.
By default, the size of the boot disk is determined by the root disk size of the flavor you are using. If you're using flavors with a root disk size of 0, you need to specify the desired root disk size in cloud_config.vm_types.['default'].cloud_properties.root_disk. We recommend a minimum size of 10GB.
By default, the validator uses an external ntp server from pool.ntp.org. If your OpenStack installation cannot access external ntp servers, e.g. firewall restrictions, you need to specify an internal ntp server in the property validator.ntp. Working time synchronization is necessary for many security concepts, such as token expiration time.
By default, the VMs created try to receive data from OpenStack's HTTP metadata service. If your OpenStack installation doesn't provide medata and userdata over HTTP, but requires you to a config-drive instead, you need to specify this in the property openstack.config_drive: cdrom