openstack/tripleo-heat-templates
Code Issues Proposed changes

Add plan-environment.yaml

Browse Source 
This file is needed for plan import and export features. We want to enable the
user to store the selection of environment options, so that it can be
re-imported, and it does not have to be perfmed manually multiple times.

The plan create workflow will look into the Swift
container for this file, and import its contents into the Mistral
environment. Conversely, plan export will create this file from the Mistral
environment contents, so that it can later be re-imported.

For more information, see the related blueprint, and the spec at
https://specs.openstack.org/openstack/tripleo-specs/specs/ocata/gui-plan-import-export.html

Partially implements: blueprint enhance-plan-creation-with-plan-environment

Change-Id: I95e3e3a25104623d6fcf38e99403cebbd591b92d
This commit is contained in:
Ana Krivokapic 2017-01-06 14:58:33 +01:00
parent d0d3403854
commit e405a74048
2 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
plan-environment.yaml Normal file
View File

@ -0,0 +1,5 @@
version: 1.0
template: overcloud.yaml
environments:
- path: overcloud-resource-registry-puppet.yaml

2
releasenotes/notes/6.0.0-b52a14a71fc62788.yaml
View File

@ -64,6 +64,8 @@ features:
- Support for Octavia composable services for LBaaS with Neutron. - Support for Octavia composable services for LBaaS with Neutron.
- Support for Collectd composable services for performance monitoring. - Support for Collectd composable services for performance monitoring.
- Support for Tacker composable service for VNF management. - Support for Tacker composable service for VNF management.
- Add the plan-environment.yaml file which will facilitate deployment plan
import and export.
upgrade: upgrade:
- Update OpenDaylight deployment to use networking-odl v2 as a mechanism - Update OpenDaylight deployment to use networking-odl v2 as a mechanism
driver. driver.