Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1131518

Summary:	allow scaled app to be ha at creation (via rhc or gui)
Product:	OpenShift Container Platform	Reporter:	August Simonelli <asimonel>
Component:	RFE	Assignee:	Miheer Salunke <misalunk>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.1.0	CC:	bleanhar, erich, jokerman, libra-onpremise-devel, mbarrett, mmasters, mmccomas, pep
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1139374 (view as bug list)		Environment:
Last Closed:	2016-01-27 21:26: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:	1158704
Bug Blocks:	1139374

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.