Project

General

Profile

Bug #34897

Assign HTTP Proxies to ACSs per smart proxy rather than per ACS

Added by Ian Ballou about 2 months ago. Updated 20 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Foreman Proxy Content
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

We determined that ACS children will likely need different HTTP Proxies depending on what smart proxy they're assigned to. So, we should move the HTTP Proxy selection to the smart proxy from the ACS. It likely doesn't make sense for ACSs on a single smart proxy to be talking to upstream servers via different HTTP Proxies.


Related issues

Blocks Katello - Tracker #33447: Alternate Content Sources Support TrackerNew

History

#1 Updated by Ian Ballou about 2 months ago

  • Triaged changed from No to Yes

#2 Updated by Ian Ballou about 2 months ago

  • Blocks Tracker #33447: Alternate Content Sources Support Tracker added

#3 Updated by Ian Ballou 20 days ago

Simplified ACSs will likely inherit HTTP Proxy config from their respective repositories. I'm thinking that, on the smart proxy page, there could be an option to select:
1) Inherit from repository
2) Use global default
3) Use specific HTTP proxy

This should be further discussed and designed out, however.

#4 Updated by Ian Ballou 20 days ago

Some questions:

Should simplified ACSs inherit HTTP proxy info?

Should ACSs even use the Default Global HTTP proxy?

Would it be likely that users would want to use different HTTP proxies for ACSs within a single smart proxy?

Also available in: Atom PDF