murano hot package can use nested yaml files?

Asked by lanceyang

can murano hot template use nested yaml files?

I mean one hot template refer to another yaml file or hot template.

when I use hot template to compose a murano package and deploy it, murano show an error

"invalid URL scheme,Could not fetch remote template mesosslave.yaml"

how can I resolve this problem?

if need modify the template, what should I do?

thanks!

for example:

https://github.com/openstack/magnum/blob/master/magnum/templates/mesos/mesoscluster.yaml#154

write_params_master:
    type: OS::Heat::SoftwareConfig
    properties:
      group: script
      config: {get_file: fragments/write-heat-params-master.sh}
      inputs:
        - name: MESOS_MASTERS_IPS
          type: String
        - name: CLUSTER_NAME
          type: String
        - name: QUORUM
          type: String

and

https://github.com/openstack/magnum/blob/master/magnum/templates/mesos/mesoscluster.yaml#249

mesos_masters:
    type: OS::Heat::ResourceGroup
    depends_on:
      - extrouter_inside
    properties:
      count: {get_param: number_of_masters}
      resource_def:
        type: mesosmaster.yaml
        properties:

Question information

Language:
English Edit question
Status:
Solved
For:
Murano Edit question
Assignee:
No assignee Edit question
Solved by:
lanceyang
Solved:
Last query:
Last reply:
Revision history for this message
Stan Lagun (slagun) said :
#1

Yes, nested files are supported. The feature was introduced in Liberty. You need to put the files in Resources/HotFiles ( Resources/HotFiles/fragments/write-heat-params-master.sh in your example) and use get_file in HOT template to reference them.

For more details please see
https://murano-specs.readthedocs.org/en/latest/specs/liberty/add-support-for-heat-environments.html
and
https://blueprints.launchpad.net/murano/+spec/add-support-for-heat-environments-and-files

Revision history for this message
lanceyang (332519087-f) said :
#2

This Solved My Problem

thanks !

Revision history for this message
Aqsa Malik (aqsamm) said :
#4

Did you call your mesosmaster.yaml file with something like {get_file: Heat/Environments/mesosmaster.yaml}?