Bug 1042929

Summary: Admins/Gears need the ability to manipulate mod_proxy on the node
Product: OpenShift Container Platform Reporter: Keith Robertson <kroberts>
Component: RFEAssignee: jofernan
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: low    
Version: 2.0.0CC: ansilva, bleanhar, jkeck, jmoran, jstrong, kroberts, libra-onpremise-devel, lphiri
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-22 16:08:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Keith Robertson 2013-12-13 16:20:08 UTC
Description of problem:
There needs to be a flexible way for either a gear or an OSE admin to manipulate the mod_proxy settings in a node's VirtualHost configuration for an individual gear.

Without this ability certain gears (e.g. JBoss with HA proxy) will not be able to proxy CSS/JavaScript easily from other sites.  This makes it difficult for OSE hosted applications to share common site themes.

Version-Release number of selected component (if applicable):
All


Expected results:
An easy way for either a gear or an OSE admin to manipulate mod_poxy settings for an individual VirtualHost on a node.  

Additional info:
Here is an example of what a gear would want to do...
<IfModule mod_proxy.c>  
 ProxyRequests On  
 SSLProxyEngine On  
 ProxyPass /css/ https://example.com/css/  
 ProxyPass /javascript/ https://example.com/javascript/  
</IfModule>