Project

Profile

Help

Task #3733

Story #3716: As a production Pulp user, I have an Ansible installer

Have playbooks use a Redis role

Added by bmbouter almost 2 years ago. Updated 12 days ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Category:
Installer
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Find a Redis role on Galaxy that we can use to install Redis with.

Our playbook should depend on that role and include variables to install Redis listening without authentication on localhost. It should also be configured to autostart.

This will ensure that in basic installs on the same host, the Pulp defaults will cause all services to connect to Redis correctly. In the case of multi-host installs, the server.yaml will need it's redis configuration set by the user.

History

#1 Updated by amacdona@redhat.com over 1 year ago

  • Status changed from NEW to MODIFIED

A pulp3-redis role was added (rather than using a 3rd party role)

#2 Updated by daviddavis about 1 year ago

  • Sprint/Milestone set to 3.0.0

#3 Updated by bmbouter about 1 year ago

  • Tags deleted (Pulp 3)

#4 Updated by bmbouter 5 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

#5 Updated by bmbouter 12 days ago

  • Category set to Installer
  • Tags deleted (Pulp 3 installer)

Please register to edit this issue

Also available in: Atom PDF