tripleo-heat-templates/firstboot/conntectx3_streering.yaml
Carlos Camacho 44ef2a3ec1 Change template names to rocky
The new master branch should point now to rocky.

So, HOT templates should specify that they might contain features
for rocky release [1]

Also, this submission updates the yaml validation to use only latest
heat_version alias. There are cases in which we will need to set
the version for specific templates i.e. mixed versions, so there
is added a variable to assign specific templates to specific heat_version
aliases, avoiding the introductions of error by bulk replacing the
the old version in new releases.

[1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky
Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b
2018-05-09 08:28:42 +02:00

32 lines
978 B
YAML

heat_template_version: rocky
description: >
This's a temporary workaround for adding this option
"log_num_mgm_entry_size=-1" to /etc/modprobe.d/mlx4.conf file in order to
allow steering in ConnectX-3 devices
resources:
userdata:
type: OS::Heat::MultipartMime
properties:
parts:
- config: {get_resource: allow_steering}
allow_steering:
type: OS::Heat::SoftwareConfig
properties:
config: |
#!/bin/bash
set -x
echo "options mlx4_core log_num_mgm_entry_size=-1" >> /etc/modprobe.d/mlx4.conf
/sbin/dracut --force
outputs:
# This means get_resource from the parent template will get the userdata, see:
# http://docs.openstack.org/developer/heat/template_guide/composition.html#making-your-template-resource-more-transparent
# Note this is new-for-kilo, an alternative is returning a value then using
# get_attr in the parent template instead.
OS::stack_id:
value: {get_resource: userdata}