Bug 1398691

Summary: [RFE] Allow to define region name for deployment
Product: Red Hat OpenStack Reporter: Pablo Iranzo Gómez <pablo.iranzo>
Component: openstack-tripleo-heat-templatesAssignee: Rob Crittenden <rcritten>
Status: CLOSED ERRATA QA Contact: Prasanth Anbalagan <panbalag>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0 (Liberty)CC: jcoufal, jschluet, jstransk, mburns, mcornea, ochalups, panbalag, rcernin, rcritten, rhel-osp-director-maint, rhos-flags, sclewis, scohen, ykheddac
Target Milestone: Upstream M1Keywords: FutureFeature, Triaged
Target Release: 12.0 (Pike)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-6.0.0-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 20:52:28 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:
Bug Depends On:    
Bug Blocks: 1468945    

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.

..
...
  KeystoneRegion:
    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.

https://access.redhat.com/errata/RHEA-2017:3462