Bug 996616
Summary: | Magento quickstart - not able to create scalable app | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | david.collen |
Component: | Templates | Assignee: | Dan McPherson <dmcphers> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.x | CC: | david.collen, nduong, wsun |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-04-09 15:17:32 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: |
Description
david.collen
2013-08-13 14:29:39 UTC
It seems that this Quickstart needs OPENSHIFT_MYSQL_DB_SOCKET to be set, but this appears to be unset in a scaled app Thanks @David! I attempted to modify the quickstart to deploy on a single-gear scalable app by updating a couple of lines: 1) Update: mysql --socket=${OPENSHIFT_MYSQL_DB_SOCKET} -u${OPENSHIFT_MYSQL_DB_USERNAME} -p${OPENSHIFT_MYSQL_DB_PASSWORD} ${OPENSHIFT_APP_NAME} < ${OPENSHIFT_TMP_DIR}magento-sample-data-1.6.1.0/magento_sample_data_for_1.6.1.0.sql To: mysql -u${OPENSHIFT_MYSQL_DB_USERNAME} -p${OPENSHIFT_MYSQL_DB_PASSWORD} -h${OPENSHIFT_MYSQL_DB_HOST} -P${OPENSHIFT_MYSQL_DB_PORT} ${OPENSHIFT_APP_NAME} < ${OPENSHIFT_TMP_DIR}magento-sample-data-1.6.1.0/magento_sample_data_for_1.6.1.0.sql 2) Update: --db_host "$OPENSHIFT_MYSQL_DB_HOST" \ To: --db_host "$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT" \ That got the quickstart to deploy, but on scale-up, it errors out due to the deploy hook being triggered. The quickstart needs to be revisited for scalable apps. I've fixed it so you can at least create a scalable app now so if you want your db on a separate gear. As far as actually scaling, I have made it work if you git push before you scale up and anything you change in media is oh the head gear. So if you: create app change whatever you want in app-root/data/media or app-root/data/local.xml git push then scale up It will be synced to all the gears. You can scale up all you want after that but in order to change anything in media you would have to git push again. So basically scaling up is still for experts/limited use cases. Verified on devenv_4509 Now could create a scalable magento app successfully. Change something in app-root/data/local.xml and git push,then scale up.Could scale up successfully. |