Project

Profile

Help

Story #3721

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

Status:
NEW
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

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.

History

#1 Updated by bmbouter over 1 year ago

  • Description updated (diff)

#2 Updated by bmbouter over 1 year ago

  • Description updated (diff)

#3 Updated by amacdona@redhat.com over 1 year 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)

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

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

#5 Updated by rchan over 1 year ago

  • Sprint set to Sprint 38

#6 Updated by bmbouter over 1 year ago

  • Parent task changed from #3716 to #3723

#7 Updated by rchan over 1 year ago

  • Sprint changed from Sprint 38 to Sprint 39

#8 Updated by dkliban@redhat.com over 1 year ago

  • Sprint changed from Sprint 39 to Sprint 40

#9 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 40 to Sprint 41

#10 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 41 to Sprint 42

#11 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 42 to Sprint 43

#12 Updated by bmbouter about 1 year 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.

#13 Updated by bmbouter about 1 year ago

  • Groomed changed from Yes to No
  • Sprint Candidate changed from Yes to No

#14 Updated by amacdona@redhat.com 10 months ago

#15 Updated by amacdona@redhat.com 10 months ago

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

#16 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF