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 over 1 year ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 3 installer
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 about 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 6 months ago

  • Sprint/Milestone set to 3.0

#3 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF