Project

Profile

Help

Task #3733

closed

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

Have playbooks use a Redis role

Added by bmbouter over 6 years ago. Updated over 4 years ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

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.

Actions #1

Updated by amacdona@redhat.com over 6 years ago

  • Status changed from NEW to MODIFIED

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

Actions #2

Updated by daviddavis over 5 years ago

  • Sprint/Milestone set to 3.0.0
Actions #3

Updated by bmbouter over 5 years ago

  • Tags deleted (Pulp 3)
Actions #4

Updated by bmbouter almost 5 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions #5

Updated by bmbouter over 4 years ago

  • Category set to Installer - Moved to GitHub issues
  • Tags deleted (Pulp 3 installer)

Also available in: Atom PDF