Task #3696: Add the streamer's settings to settings.yaml in the content app area - Pulp

Actions

Send by e-mail Copy link

Task #3696

closed

Story #3693: Lazy for Pulp3

Add the streamer's settings to settings.yaml in the content app area

Added by dkliban@redhat.com almost 6 years ago. Updated over 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

jortel@redhat.com

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

Sprint:

Sprint 41

Quarter:

Description

These settings would be added to the settings.py and server.yaml file with defaults.

redirect_host: The hostname to use when redirecting the client. This is required when using lazy.
redirect_port: The port to use when redirecting the client. This is required when using lazy.
redirect_prefix_path: The prefix path to prepend the to the URL when redirecting. This allows you to reroot squid. Defaults to None.
https_retrieval: If true, use https as the protocol the client should use, otherwise http. Defaults to True.

Related issues

Actions

Copy link

Updated by bmbouter almost 6 years ago

Subject changed from Add the squid settings to settings.yaml in the content app area to Add the streamer's settings to settings.yaml in the content app area

squid's config is read by squid.conf and is in another story.

Actions

Copy link

Updated by bmbouter almost 6 years ago

What exactly are the settings we need? I think this ticket still needs that level of planning.

Actions

Copy link

Updated by dkliban@redhat.com almost 6 years ago

The following settings from pulp 2 are applicable to pulp 3.

[lazy]

redirect_host:
redirect_port:
redirect_path:
https_retrieval: true

Actions

Copy link

Updated by bmbouter almost 6 years ago

Description updated (diff)

I agree those are the right settings. I'm adding them to the description along with some descriptions.

I renamed redirect_path to redirect_prefix_path because I thought it more clearly called out that it's only the prefix. I believe that's correct.

I want to retell what I think https_retrieval does for the users. It allows them to force https or http to match how they've configured their squid. It's a global setting which is kind of unfortunate because if you have some clients that can't support https you have to disable https globally. At some point in the future we may consider an option that would allow this setting at a distribution level.

Also for https_retrieval, we can't rely on "use the same protocol the client used to contact Pulp with" because when deploying Pulp behind a reverse proxy that provides TLS termination (for example) would always appear to pulp as http when the client is actually requesting https.

Actions

Copy link