Bug 841749

Summary: [RFE] server config parameter to set external URL
Product: [Retired] Beaker Reporter: Jun'ichi NOMURA <junichi.nomura>
Component: lab controllerAssignee: Bill Peck <bpeck>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.9CC: bpeck, dcallagh, rmancy, stl
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: 2012-08-09 08:06:59 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:
Embargoed:

Description Jun'ichi NOMURA 2012-07-20 06:53:00 UTC
[RFE] server config parameter to set external URL

Suppose following network configuration for testing lab:

  +---------+
  | desktop |
  +----+----+                            external network
       |
       |
       | www.testlab.com
  +----+-----+
  |  rproxy  | = = = = = = = = = = = = = = = = = = = = =
  +----+-----+
       | rproxy.localdomain
       |
       +---------------------------+     lab-private network
       |                           |
       | beaker.localdomain        |
  +----+-----+                     |
  |  beaker  |                     |
  +----------+                     |
                    +--------------+-------------------
                    |              |
             +------+-----+  +-----+------+
             |testmachine1|  |testmachine2|   ........
             +------------+  +------------+


In this case, the beaker server is accessed from test machines
as "http://beaker.localdomain" (= internal URL),
while it is accessed from the user's desktop machines as
"https://www.testlab.com" (= external URL).

Since we can't set external URL, notification e-mail from beaker
contains internal URL like this:

  JobID: 2254 Status: Completed Result: Fail <https://beaker.localdomain/bkr/jobs/2254>

that is not very useful for the user working on his desktop.

It is nice to have a config parameter to set up such an external URL.


With beaker 0.6, tg.url_domain and tg.url_scheme could be used
to setup the external URL.
However, with beaker 0.9, those parameters are used also to
construct internal URL. So we can no longer use them for this purpose.

Comment 1 Bill Peck 2012-07-24 19:15:31 UTC
http://gerrit.beaker-project.org/#/c/1239/

Comment 3 Dan Callaghan 2012-08-09 08:06:59 UTC
Beaker 0.9.2 has been released.

Comment 4 Jun'ichi NOMURA 2012-08-16 06:56:04 UTC
(Sorry, solution is not clear and I'm not very confident about my guess below.
 Please confirm/correct below.)

For the example case in comment#0, we should set:
  tg.url_domain = www.testlab.com
  tg.lab_domain = beaker.localdomain
  tg.url_scheme = https

  (For lab_domain, it's always 'http' regardless tg.url_scheme.)

Comment 5 Dan Callaghan 2012-08-16 22:47:16 UTC
(In reply to comment #4)

That's right.