如何将josn / list值传递给HEAT中的模板user_data

时间:2016-09-26 17:31:34

标签: openstack openstack-heat

需要使用comma_delimited_list中的资源组中的动态值替换user_data。

%index%无效。

heat_template_version: 2015-10-15

test_parameter:
type: comma_delimited_list
label: test param  list
description: test descr
default: 'test_param_1,test_param_2'
.......
...... 

type: OS::Heat::ResourceGroup
properties:
.........
.........
user_data:
    str_replace:
      template: |
        get the local value of the instance : $val
      params:
        $val: { get_param: [ test_parameter, %index% ] } 

如何将josn / list值传递给HEAT-user_data

中的模板

1 个答案:

答案 0 :(得分:0)

可悲的是,基于aws-cloudformation仍然局限于你通常可以做的事情,而特定于热量的语言(仍然基于aws-cloudformation)受到同样的限制。

通常情况下,您可以拥有的最佳解决方案是选择"列表位于模板顶部,并将一些选择传递给您的资源。在以下示例中,其中一个选项要求安装特定的Web应用程序(来自nginx和apache),并将其作为变量传递给模板的用户数据部分:

heat_template_version: 2015-04-30

description: >
  Hello world HOT template that just defines a single server.
  Contains just base features to verify base HOT support.

parameters:
  key_name:
    type: string
    description: Name of an existing key pair to use for the server
    default: "topcat-01"
    constraints:
      - custom_constraint: nova.keypair
  flavor:
    type: string
    description: Flavor for the server to be created
    default: m1.normal
    constraints:
      - custom_constraint: nova.flavor
  image:
    type: string
    description: Image ID or image name to use for the server
    default: Ubuntu-1404lts-32-Cloud
    constraints:
      - custom_constraint: glance.image
  my_network:
    type: string
    description: Neutron Network
    default: public-internet-access
    constraints:
      - custom_constraint: neutron.network
  application-install:
    type: string
    default: apache
    constraints: 
      - allowed_values: [apache, nginx]
        description: Value must be one of 'apache', or 'nginx'

resources:
  server:
    type: OS::Nova::Server
    properties:
      key_name: { get_param: key_name }
      image: { get_param: image }
      flavor: { get_param: flavor }
      security_groups: 
        - default
      name: test-single-topcat-instance
      networks:
        - network: { get_param: my_network }
      user_data_format: RAW
      user_data:
        str_replace:
          template: |
            #!/bin/bash
            myapp="$selectedapp01"
            echo "MY APP IS $myapp"
            PATH=$PATH:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
            case $myapp in
            apache)
                echo "INSTALLING APACHE"
                if [ -f /etc/debian_version ]
                then
                   aptitude -y update
                   aptitude -y install apache2
                fi
                if [ -f /etc/redhat-release ]
                then
                   yum -y install httpd
                   chkconfig httpd on
                   echo "" >> /var/www/html/index.html
                   service httpd start
                fi
                ;;
            nginx)
                echo "INSTALLING NGINX"
                if [ -f /etc/debian_version ]
                then
                   aptitude -y update
                   aptitude -y install nginx-full
                fi
                if [ -f /etc/redhat-release ]
                then
                   yum -y install nginx
                   chkconfig nginx on
                   service nginx start
                fi
                ;;
            esac
          params:
            $selectedapp01: {get_param: application-install}

outputs:
  server_networks:
    description: The networks of the deployed server
    value: { get_attr: [server, networks] }

从上面的示例中," application-install"参数(可以是apache或nginx)将被解释为" $ selectedapp01"在用户数据部分的末尾,以及" $ myapp" (myapp =" $ selectedapp01")在用户数据的开头。

这不是完美的,但这是正常的方式。大多数云形成部署工具都是从一组"问题和答案"中构建最终模板。你完成了静态(半静态)模板。

这个我在这里添加的例子,会问你很多东西并设置一些默认值。

希望它有所帮助。