Comment 3 for bug 1698302

Note that at least for the environment files list, this is already how we work when deploying from the UI, and I believe shardy is working on making the CLI play more nicely with the list of environments as well (though I don't remember as part of which bug). Currently the CLI mangles all the environments into one big file.

If I define the environments via the UI, plan-environment.yaml in Swift is updated with the list of individual environments:

name: demo-overcloud
environments:
- path: overcloud-resource-registry-puppet.yaml
- path: environments/tls-endpoints-public-ip.yaml
- path: environments/enable-tls.yaml
parameter_defaults:
  BlockStorageCount: 0
  CephStorageCount: 1
[...]

This can also be used directly to deploy from the CLI by using the "openstack overcloud plan deploy <plan_name>" (as opposed to "openstack overcloud deploy").

Though of course that doesn't include all of the CLI switches from "overcloud deploy", if they don't translate to a parameter_defaults.

About the suggested "templates" field, ideally we should be assuming the deployment is happening based on the templates & environments uploaded to the Swift container, rather than local files - jtomasek wrote a good email about it: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118213.html

I'm not saying this solves everything described here, just that this looks like a good starting point that is also compatible with the UI and existing tripleo-common workflows.