Red Hat Bugzilla – Bug 807560
haproxy-1.4 should be hidden from user interface.
Last modified: 2013-11-17 19:39:03 EST
Description of problem:
As far as I know, haproxy-1.4 is used for scaling functionality.
Now when user get embed cartridge list whatever from CLI or rest api,
haproxy-1.4 is always listed there.
If some user embed this cartridge, his app will can not be available, his app does not become scalable either.
So I think we should hide "haproxy-1.4" from user interface.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Also think should be hidden from site as well.
We support converting an existing application to scalable by embedding haproxy. It has to be offered as an option.
Re-test this bug on devenv_1976, according to "We support converting an existing application to scalable by embedding haproxy", so I tried it.
1. Create a non-scalable app
2. Embed haproxy to this app.
$ rhc-ctl-app -L
List of supported embedded cartridges:
Obtaining list of cartridges (please excuse the delay)...
mongodb-2.0, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4
$ rhc-ctl-app -a phptest -e add-haproxy-1.4 -p xx
$ rhc-domain-info -p xx
Git URL: ssh://firstname.lastname@example.org/~/git/phptest.git/
Public URL: http://phptest-jialiu.dev.rhcloud.com/
3. Access this app's URL, only happroxy-status page is seen.
4. Try to scale-up, still failed.
$ curl -k -X POST -H 'Accept: application/xml' -d event=scale-up --user email@example.com:214214 https://ec2-75-101-219-128.compute-1.amazonaws.com/broker/rest/domains/jialiu/applications/phptest/events
<?xml version="1.0" encoding="UTF-8"?>
<text>Failed to add event scale-up to application phptest due to: Cannot scale a non-scalable application</text>
This app looks like still a non-scalable app, that means an existing app is not converted to scalable by embedding haproxy.
I am not sure if this converting functionality is aleady completed, if not, this bug should not be closed as "NOTABUG".
*** This bug has been marked as a duplicate of bug 895269 ***