Bug 1131518 - allow scaled app to be ha at creation (via rhc or gui)
Summary: allow scaled app to be ha at creation (via rhc or gui)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 2.1.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Miheer Salunke
QA Contact:
URL:
Whiteboard:
Depends On: 1158704
Blocks: 1139374
TreeView+ depends on / blocked
 
Reported: 2014-08-19 13:24 UTC by August Simonelli
Modified: 2019-08-15 03:56 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1139374 (view as bug list)
Environment:
Last Closed: 2016-01-27 21:26:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 August Simonelli 2014-08-19 13:26:18 UTC
Description of problem:

When a scaled app is created an extra step, after the app is already started, is required to make the app "HA" (ie min 2 x LB gears).

Version-Release number of selected component (if applicable):

2.1

How reproducible:

Create a scaled app. It won't be HA. Make HA via REST call.

Steps to Reproduce:
1. rhc create-app testha ruby-1.9 -s
2. app is NOT HA 
3. curl -k -H 'Accept: application/xml' --user demo:changeme https://broker.example.com/broker/rest/domains/NAMESPACE/applications/testha/events -XPOST -d event=make-ha
4. App is now HA (ie has 2 x LB gears)

see: http://sosiouxme.wordpress.com/2014/07/21/ha-applications-on-openshift/

Actual results:

As above.

Expected results:

A scaled app should be able to be HA from the start. In an enterprise install the expectation of HA is paramount; it should be part of the app creation (imho). Ideally, the RESTful call should be encapsulated in the app create command, for example:

rhc create-app testha ruby-1.9 -s --make-ha

This would ensure "true" HA and would kick off the already built in HA DNS, etc processes. Additionally, in a multi zone situation this would help ensure each zone gets an gear (assuming ZONES_REQUIRE_FOR_APP_CREATE=true, ZONES_MIN_PER_GEAR_GROUP=2). This is important for cross-datacenter (truly HA) deployments. Without this, the scalable app will be only ONE gear until it needs to scale. That's not HA. 

Additional info:

Comment 4 Eric Rich 2014-09-19 11:18:33 UTC
I think https://github.com/miheer/rhc/commit/299f771be46669a1c1d46731e8c3b0215f4526bf completes this.

Comment 5 Miciah Dashiel Butler Masters 2014-09-19 15:25:21 UTC
There is still discussion at the pull request for that commit regarding the user interface for exposing the make-ha feature (<https://github.com/openshift/rhc/pull/647>), as well as an independently developed pull request that implements a slightly different user interface (<https://github.com/openshift/rhc/pull/649>).  It has not yet been decided which approach to the UI will be used.

Comment 6 chris alfonso 2014-10-23 16:33:49 UTC
This is no longer relevant, the design is to split out the commands. There is now an rhc app enable-ha which is executed after rhc create-app has completed.


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