Description of problem:
Customers such as those in C2S use different amazon regions than the ones available in the UI when creating a new AWS Provider.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. Configuration->Add New Cloud Provider
3. Type=Amazon EC2
Region selector is limited to specific values.
Ability to specify a custom AWS region that is not listed.
Custom amazon region strings are required when deploying to specific versions of AWS. Right now the current AWS provider has a list of region strings to choose from, but no ability to specify one directly in the UI. Expect to see a dropdown list that can also be manually be changed to set a custom Amazon region string.
New commit detected on ManageIQ/manageiq/master:
Author: Adam Grare <email@example.com>
AuthorDate: Thu Dec 1 08:34:32 2016 -0500
Commit: Adam Grare <firstname.lastname@example.org>
CommitDate: Sun Dec 11 14:13:35 2016 -0500
Add an additional_regions key for amazon EC2
config/settings.yml | 1 +
1 file changed, 1 insertion(+)
New commit detected on ManageIQ/manageiq-providers-amazon/master:
Author: Adam Grare <email@example.com>
AuthorDate: Fri Dec 2 12:03:39 2016 -0500
Commit: Adam Grare <firstname.lastname@example.org>
CommitDate: Wed Dec 14 12:58:55 2016 -0500
Include additional_regions from settings
app/models/manageiq/providers/amazon/regions.rb | 5 +-
.../manageiq/providers/amazon/regions_spec.rb | 60 ++++++++++++++++++++++
2 files changed, 64 insertions(+), 1 deletion(-)
Additional regions can be added to the config/settings.yml file with the following format:
:name: Special Region
:description: Super Special Region
Verified in 188.8.131.52. I am able to add custom EC2 region.
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.