The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #15019

Bring memcached up out of horizon and swift to it's own top level module

Added by Robert Starmer over 2 years ago. Updated about 1 year ago.

Status:ClosedStart date:06/13/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-Spent time:-
Target version:-
Keywords: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

Current memcached is set up in both Horizon and Swift modules. This is fine when these services reside on different nodes, but causes a collision when deployed in an “all-in-one” fashion onto one node. It’s not impossible to address, given that memcache is really only called out in the site.pp examples in swift, it can simply be commented out in the short term.

History

#1 Updated by Anonymous about 1 year ago

  • Status changed from Unreviewed to Closed

Current modules depend on saz-memcached module.

OpenStack development and tracking has moved to review.openstack.org. If this issue persists, please submit a new report there.

Also available in: Atom PDF