Bug 1116124
| Summary: | [RFE] cherry-pick REST API exposure of regions/zones | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Luke Meyer <lmeyer> |
| Component: | Node | Assignee: | Luke Meyer <lmeyer> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.1.0 | CC: | adellape, anli, bleanhar, jokerman, libra-onpremise-devel, mmccomas |
| Target Milestone: | --- | Keywords: | Upstream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-openshift-origin-msg-broker-mcollective-1.23.3.2-1.el6op openshift-origin-broker-1.16.1.7-1.el6op rubygem-openshift-origin-controller-1.23.10.4-1.el6op | Doc Type: | Enhancement |
| Doc Text: |
Using the broker REST API directly, developers can now specify the region to which their application is deployed. This allows developers to reduce latency to target users or implement a highly-available application scheme. Developers can also now use the REST API directly to determine the region and zone(s) to which an existing application's gears were deployed. In addition, administrators can now use the DEFAULT_REGION_NAME parameter in the /etc/openshift/broker.conf file to set the default region for new applications. If the parameter is not set, then a region is chosen randomly.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-04 13:27:36 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: | 1115238, 1115244, 1115274, 1115309, 1115321 | ||
| Bug Blocks: | |||
|
Description
Luke Meyer
2014-07-03 19:28:00 UTC
We should be sure to include Bug 1116836 as part of this work. Replacing bug 1116836 with its blockers as I think it makes more sense to just track this feature and its follow-on bugfixes here. Cherry-picking these from origin-server: From PR https://github.com/openshift/origin-server/pull/5555 commit 7079d938b95052f04fcf72e432a0a071b543c418 Author: Lili Nader <lnader> Date: Thu Jun 26 14:27:04 2014 -0700 Expose region and zones of gears in REST API commit a01e57efbed15ac377f53a40640f63eb0ec2428e Author: Lili Nader <lnader> Date: Fri Jun 27 19:08:22 2014 -0700 Enables user to specify a region when creating an application From PR https://github.com/openshift/origin-server/pull/5567 commit e29b2f9cd8637c4953ed8e2efb76b7139ac86b5f Author: Ravi Sankar Penta <rpenta> Date: Wed Jul 2 18:47:06 2014 -0700 Bug 1115321 - Fix zone name in gear_groups rest api response commit 41098c5746efe83947a485cc99a0fe8efbfc7555 Author: Ravi Sankar Penta <rpenta> Date: Wed Jul 2 23:51:45 2014 -0700 Bug 1115244 - Add 'region' as optional param to ADD_APPLICATION link commit 83a1ad0c3f3025e07085cfad9bc6916486c60b20 Author: Ravi Sankar Penta <rpenta> Date: Wed Jul 2 23:55:00 2014 -0700 Bug 1115238 - Add DEFAULT_REGION_NAME param to the broker configuration. commit 0598d3648d0e33052970a83a229296f9cb6396ab Author: Ravi Sankar Penta <rpenta> Date: Wed Jul 2 23:59:46 2014 -0700 Bug 1115274 - Fix 'default' field in /regions REST api commit 3181c5ca9cfb5408a16b194953accde4f2e45ce4 Author: Ravi Sankar Penta <rpenta> Date: Thu Jul 3 00:02:15 2014 -0700 Bug 1115309 - Default region will be selected when optional param 'region' is not set during app creation. *** Bug 1116836 has been marked as a duplicate of this bug. *** Packages available with puddle 2014-07-11.3; I assume the same test cases apply (https://tcms-openshift.rhcloud.com/cases/search/?summary=%5Borigin_broker_241%5D&author=&product=&plan=&is_automated=&category=&case_status=1&case_status=2&component=&bug_id=&tag__name__in=&a=search) as well as regression testing on the blocked bugs. Verified and pass on OSE2.1z/2014-07-11.4. The test cases have been run and passed.No blocked bug issue was found. 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. http://rhn.redhat.com/errata/RHBA-2014-0999.html |