Add authentication parameters for novajoin vendordata plugin

With nova's vendordata plugin supporting authentication, we need to
specify the authentication parameters on the metadata side. This will be
used to get a keystone token, and will subsequently be validated by
novajoin's middleware, where keystone authtoken middleware is. This way
we can asure that log that requests actually come from an authenticated
source (nova).

Change-Id: I78bb217c485bad342e7ce8d60786fe1e5acf55a4
Depends-On: I870e244aff97439143b58e9b2284830b4388cc5f

elements/puppet-stack-config/puppet-stack-config.yaml.template

@@ -790,6 +790,14 @@ nova::api::vendordata_jsonfile_path: '/etc/nova/cloud-config-novajoin.json'
 nova::api::vendordata_providers: ['StaticJSON', 'DynamicJSON']
 nova::api::vendordata_dynamic_targets: ["join@http://{{LOCAL_IP}}:%{hiera('novajoin_listen_port')}/v1/"]
 nova::api::vendordata_dynamic_failure_fatal: true
+nova::api::vendordata_dynamic_auth_auth_type: 'password'
+nova::api::vendordata_dynamic_auth_auth_url: "%{hiera('keystone_auth_uri')}"
+nova::api::vendordata_dynamic_auth_os_region_name: "%{hiera('keystone_region')}"
+nova::api::vendordata_dynamic_auth_username: 'nova'
+nova::api::vendordata_dynamic_auth_project_name: 'service'
+nova::api::vendordata_dynamic_auth_project_domain_name: 'Default'
+nova::api::vendordata_dynamic_auth_user_domain_name: 'Default'
+nova::api::vendordata_dynamic_auth_password: {{UNDERCLOUD_NOVA_PASSWORD}}
 nova::notification_topics: ['notifications', 'novajoin_notifications']
 nova::notify_on_state_change: 'vm_state'
 {{/ENABLE_NOVAJOIN}}