Bug 1537725

Summary:	Deployment templates for unsupported components causing some confusion
Product:	Red Hat OpenStack	Reporter:	Mark McLoughlin <markmc>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	Gurenko Alex <agurenko>
Severity:	high	Docs Contact:
Priority:	high
Version:	12.0 (Pike)	CC:	ahrechan, aschultz, dnavale, emacchi, mburns, rhel-osp-director-maint
Target Milestone:	z2	Keywords:	Triaged, ZStream
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-7.0.3-24.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1538752 1538753 (view as bug list)		Environment:
Last Closed:	2018-03-28 17:16:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1538752, 1538753

Description Mark McLoughlin 2018-01-23 18:34:03 UTC

Feedback from field engineers that our shipping deployment templates for e.g. Tacker, Neutron BGP, and Octavia is causing some confusion. It's not immediately clear those components are not supported.

Specifically, these files in the environments subdirectory in the openstack-tripleo-heat-templates package. For example:
- /usr/share/openstack-tripleo-heat-templates/environments/enable_tacker.yaml
- /usr/share/openstack-tripleo-heat-templates/environments/neutron-bgpvpn-opendaylight.yaml
- /usr/share/openstack-tripleo-heat-templates/environments/neutron-bgpvpn.yaml

Solutions could include:

- Do not package templates for unsupported components (except Tech Preview)
- Add a new sub-package for Tech Preview components
- Put tech preview components in a different subdirector
- Add a README file in the directory listing the support status of each

But anything that would reduce confusion for anyone poking around would be great.

Comment 2 Emilien Macchi 2018-01-23 19:54:48 UTC

Some questions I've been asking to myself too:

- Should we find a solution that also mention that services aren't supported by TripleO upstream?
- If not, then I guess our solution is to either avoid shipping the files or document in OSP that these services aren't supported by Red Hat OpenStack.

I'll add that for OSP14 backlog, thanks.

Comment 9 Artem Hrechanychenko 2018-02-28 09:46:22 UTC

VERIFIED


(undercloud) [stack@undercloud-0 ~]$ sudo rpm -qa "openstack-tripleo-heat-templates"
openstack-tripleo-heat-templates-7.0.9-2.el7ost.noarch


(undercloud) [stack@undercloud-0 ~]$ cat /usr/share/openstack-tripleo-heat-templates/environments/README.md 
This directory contains Heat environment file snippets which can
be used to enable features in the Overcloud.

Configuration
-------------

These can be enabled using the -e [path to environment yaml] option with
heatclient.

Below is an example of how to enable the Ceph template using
devtest\_overcloud.sh:

    export OVERCLOUD\_CUSTOM\_HEAT\_ENV=$TRIPLEO\_ROOT/tripleo-heat-templates/environments/ceph_devel.yaml


Services support in OSP
-----------------------

While TripleO provides environment files that can deploy many services, not all of
them are supported by [Red Hat OpenStack Platform](https://www.redhat.com/en/technologies/linux-platforms/openstack-platform).

Before proceeding to an OSP deployment, it's suggested to read
[what services](https://access.redhat.com/articles/1535373) are actually supported.

Comment 13 errata-xmlrpc 2018-03-28 17:16:42 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0602