yahoo-eng-team team mailing list archive

[Steven Hardy <shardy@xxxxxxxxxx>]

Public bug reported:

There is an issue with environment files (and heat templates which
contain a file reference to a nested stack directly), which means that
they don't work via Horizon.

The issue is you pass a template and optionally an environment file to
Horizon via the file dialog, but Horizon doesn't have any way to resolve
the file references and populate the "files" part of the API call to
create the stack.

Additionally, the environment is not passed at all when trying to create
the stack, so template validation actually fails before you hit the
problem above.. ;)

Here are some simple examples which demonstrate the problem:

In all of the following examples, a default nova keypair of "stack_key"
is expected, as is a glance image of "cirros-0.3.2-x86_64-disk", these
can be overridden or modified obviously.

1. Template referencing a nested stack directly (no environment)

https://github.com/hardys/demo_templates/tree/master/juno_summit_intro_to_heat/example2_server_with_volume_nested

This can be launched on the CLI via:

heat --debug template-validate -f server_with_volume.yaml
heat --debug stack-create test1 -f server_with_volume.yaml

The --debug will show the content of the API call, which should
hopefully help see what is missing from the horizon call (files section
missing from the create)

2. Template referencing nested stack via environment

https://github.com/hardys/demo_templates/tree/master/juno_summit_intro_to_heat/example4_provider_environment

This can be launched on the CLI via:

heat --debug template-validate -f server_with_volume_env.yaml -e env_server_with_volume.yaml
heat --debug stack-create test2 -f server_with_volume_env.yaml -e env_server_with_volume.yaml

Currently it's not possible to launch either stack via horizon, unless
the local file references are replaced with URLs.

** Affects: horizon
     Importance: Undecided
     Assignee: Jordan OMara (jomara)
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1322258

Title:
  Heat environments don't work for local files

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  There is an issue with environment files (and heat templates which
  contain a file reference to a nested stack directly), which means that
  they don't work via Horizon.

  The issue is you pass a template and optionally an environment file to
  Horizon via the file dialog, but Horizon doesn't have any way to
  resolve the file references and populate the "files" part of the API
  call to create the stack.

  Additionally, the environment is not passed at all when trying to
  create the stack, so template validation actually fails before you hit
  the problem above.. ;)

  Here are some simple examples which demonstrate the problem:

  In all of the following examples, a default nova keypair of
  "stack_key" is expected, as is a glance image of
  "cirros-0.3.2-x86_64-disk", these can be overridden or modified
  obviously.

  1. Template referencing a nested stack directly (no environment)

  https://github.com/hardys/demo_templates/tree/master/juno_summit_intro_to_heat/example2_server_with_volume_nested

  This can be launched on the CLI via:

  heat --debug template-validate -f server_with_volume.yaml
  heat --debug stack-create test1 -f server_with_volume.yaml

  The --debug will show the content of the API call, which should
  hopefully help see what is missing from the horizon call (files
  section missing from the create)

  2. Template referencing nested stack via environment

  https://github.com/hardys/demo_templates/tree/master/juno_summit_intro_to_heat/example4_provider_environment

  This can be launched on the CLI via:

  heat --debug template-validate -f server_with_volume_env.yaml -e env_server_with_volume.yaml
  heat --debug stack-create test2 -f server_with_volume_env.yaml -e env_server_with_volume.yaml

  Currently it's not possible to launch either stack via horizon, unless
  the local file references are replaced with URLs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1322258/+subscriptions