Project

Profile

Help

Story #3721

closed

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

Story #3723: Create the pulp3 role

As a role user, server.yml behaviors are sane

Added by bmbouter almost 6 years ago. Updated over 3 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

Overall Behaviors

If a user supplies a server.yaml file it is overwritten on all target machines. The user is assumed to know what they are doing. The file provided by the user is never modified.

If the user does nothing a server.yaml containing a generated SECRET_KEY is placed on the target systems. This is a sparse file, it is not the fully commented file. If a server.yaml already exists, there no changes are ever made. This ensures idempotent behavior.

Technical Implementation

If `pulp3_settings_source_path` is defined:
    Install file to `server_settings_target_path | default('/etc/pulp/settings.yaml')` on target host.
    Don't alter the file that's being copied to the target host. (i.e. don't insert a SECRET_KEY)
Else:
    If `server_settings_target_path | default('/etc/pulp/settings.yaml')` exists on the target host:
        Do nothing.
    Else:
        Create `server_settings_target_path | default('/etc/pulp/settings.yaml')` on target host.
        Make sure to insert SECRET_KEY into file.

Notes

  • server.yaml is required due to SECRET_KEY
  • we don't want to fully template server.yaml. Fully templating would mean that for every update to Pulp's settings file syntax, there would need to be a corresponding update to this Ansible role.
Actions #1

Updated by bmbouter almost 6 years ago

  • Description updated (diff)
Actions #2

Updated by bmbouter almost 6 years ago

  • Description updated (diff)
Actions #3

Updated by amacdona@redhat.com almost 6 years ago

  • Subject changed from As a role user, settings.py behaviors are sane to As a role user, server.yml behaviors are sane
  • Description updated (diff)
Actions #4

Updated by amacdona@redhat.com almost 6 years ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes
Actions #5

Updated by rchan almost 6 years ago

  • Sprint set to Sprint 38
Actions #6

Updated by bmbouter almost 6 years ago

  • Parent issue changed from #3716 to #3723
Actions #7

Updated by rchan almost 6 years ago

  • Sprint changed from Sprint 38 to Sprint 39
Actions #8

Updated by dkliban@redhat.com over 5 years ago

  • Sprint changed from Sprint 39 to Sprint 40
Actions #9

Updated by rchan over 5 years ago

  • Sprint changed from Sprint 40 to Sprint 41
Actions #10

Updated by rchan over 5 years ago

  • Sprint changed from Sprint 41 to Sprint 42
Actions #11

Updated by rchan over 5 years ago

  • Sprint changed from Sprint 42 to Sprint 43
Actions #12

Updated by bmbouter over 5 years ago

  • Sprint deleted (Sprint 43)

Removing from sprint until the current branched installer is sent out for testing and we can re-assess the settings needs based on the dynaconf work.

Actions #13

Updated by bmbouter over 5 years ago

  • Groomed changed from Yes to No
  • Sprint Candidate changed from Yes to No
Actions #14

Updated by amacdona@redhat.com over 5 years ago

Actions #15

Updated by amacdona@redhat.com over 5 years ago

  • Related to deleted (Task #4275: Remove settings.py)
Actions #16

Updated by bmbouter almost 5 years ago

  • Tags deleted (Pulp 3)
Actions #17

Updated by bmbouter almost 4 years ago

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

Updated by daviddavis over 3 years ago

  • Status changed from NEW to CLOSED - CURRENTRELEASE

Also available in: Atom PDF