Bug #34897
closed
Assign HTTP Proxies to ACSs per smart proxy rather than per ACS
Added by Ian Ballou about 2 years ago.
Updated over 1 year ago.
Category:
Foreman Proxy Content
|
|
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
1 (1 open — 0 closed)
- Triaged changed from No to Yes
- Blocks Tracker #33447: Alternate Content Sources Support Tracker (MVP) added
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.
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?
- Target version changed from Katello 4.6.0 to Katello 4.8.0
- Status changed from New to Ready For Testing
- Assignee set to Ian Ballou
- Pull request https://github.com/Katello/katello/pull/10300 added
- Target version changed from Katello 4.8.0 to Katello 4.7.0
- Fixed in Releases Katello 4.7.0 added
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous