Bug 1398691 - [RFE] Allow to define region name for deployment
Summary: [RFE] Allow to define region name for deployment
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 8.0 (Liberty)
Hardware: x86_64
OS: Linux
Target Milestone: Upstream M1
: 12.0 (Pike)
Assignee: Rob Crittenden
QA Contact: Prasanth Anbalagan
Depends On:
Blocks: 1468945
TreeView+ depends on / blocked
Reported: 2016-11-25 15:27 UTC by Pablo Iranzo Gómez
Modified: 2023-02-22 23:02 UTC (History)
13 users (show)

Fixed In Version: openstack-tripleo-heat-templates-6.0.0-4.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 20:52:28 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Pablo Iranzo Gómez 2016-11-25 15:27:16 UTC
Description of problem:

As we don't yet provide multiple regions (BZ 1294818), we would like to be able to define region name on installation, but apparently as per bz 1357579 there are also some issues with capitalization of regionOne vs RegionOne.

Requirement is to be able to define Region name via heat templates before deployment.

Is that something that should be supportable

Comment 20 Prasanth Anbalagan 2017-10-25 01:27:34 UTC
Verified as follows - Region name was changed as follows in the puppet yaml file.

    type: string
    default: 'regionX'
    description: Keystone region for endpoint

MariaDB [keystone]> select * from region where id="regionX";
| id      | description | parent_region_id | extra |
| regionX |             | NULL             | {}    |
1 row in set (0.01 sec)

Comment 24 errata-xmlrpc 2017-12-13 20:52:28 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.


Note You need to log in before you can comment on or make changes to this bug.