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

Bug 1063372

Summary:	No option to specify memcache details for Horizon in manifests
Product:	Red Hat OpenStack	Reporter:	Rhys Oxenham <roxenham>
Component:	rubygem-staypuft	Assignee:	Jason Guiditta <jguiditt>
Status:	CLOSED WONTFIX	QA Contact:	Ido Ovadia <iovadia>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	4.0	CC:	aberezin, mburns, morazi, pasik, rhos-maint, roxenham, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-29 14:48:42 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 Rhys Oxenham 2014-02-10 15:11:11 UTC

Description of problem:

There's no way to specify a remote memcached server using the puppet manifests despite there being an entry within the /etc/openstack-dashboard/local_settings erb  template file.

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

openstack-foreman-installer-1.0.3-1.el6ost.noarch
foreman-installer-1.3.0-1.el6sat.noarch
foreman-1.3.0.2-1.el6sat.noarch
RHEL 6.5 x86_64 with RHEL OSP 4.0

How reproducible:

Every time.

Steps to Reproduce:
1. Apply 'controller' host group to a server
2. Run the puppet agent
3. Observe /etc/openstack-dashboard/local_settings for memached server.

Actual results:

No option to override the parameter in Foreman as it doesn't exist in the puppet manifests

Expected results:

Option provided to override the parameter with user-chosen options.

Additional info:

Patch proposed to upstream and already tested at customer site: https://github.com/redhat-openstack/astapor/pull/123

Comment 2 Jason Guiditta 2014-05-22 20:22:41 UTC

Rhys, if you would like this included in a release, would you be willing to update the patch above, (which I commented on a while back, but think it got lost).