[AG-DEV] Bridge Registry information via a text file

[Jason Bell]

G'day Ben

Thanks for your email....  My comment wasn't about forcing users to use
one bridge....  It was more the comment that if, for whatever reason, a
user cannot access the URL directly to get to the "bridge registry",
then no bridges are listed.

The use of vv3.mcs.anl.gov:8030 is just an example.  

What would be nice is if you can associate "vv3.mcs.anl.gov:8030" or
"sam.ag.manchester.ac.uk:8030" directly without having to access a
remote webpage to obtain this information.

The reason why this is important and is some locations pass port 80
(http) through a proxy, whereas they can directly access port 8030.

It has come to my attention that you could probably use something like
file:///C:/mydir/peers.txt with those addresses and it should work,
though I need to try it.  Unfortunately this isn't obvious.

Anyway, instead of pointing to a external web URL, it would be nice to
be able to directly point to a local file.

I hope this clarifies my request.

Cheers,
Jason.

-----Original Message-----
From: Ben Green [mailto:Ben.Green at manchester.ac.uk] 
Sent: Monday, 29 October 2007 8:50 PM
To: Jason Bell; ag-dev at mcs.anl.gov
Subject: RE: [AG-DEV] Bridge Registry information via a text file

Hi Jason,

The reason we get UK users to point their clients at our own registry
peers file is so that they connect to our bridge registry first.

It reads as follows:

sam.ag.manchester.ac.uk:8030
fraser.ag.manchester.ac.uk:8030
vv3.mcs.anl.gov:8030

So our peers.txt file is *not* the same as the default registry address.
The whole point is that it guarantees users will always have a working
bridge registry in the unlikely event of the ANL bridge registry going
down.

The other reason we do this is that the current client can only display
about 10 bridges and because the default ANL registry lists more than
this, the client would sometimes omit the AGSC bridges. Our bridge
registry only contains a small number of bridges, so they will always be
displayed.

But I think client v3.1 overcomes these issues....

Cheers, Ben. 

|=============================|
| Ben Green                   |
| Access Grid Support Centre  |      
| Room G49-H                  |
| Research Computing Services |
| Kilburn Building            |
| University of Manchester    |
| Oxford Road                 |
| Manchester                  |
| M13 9PL                     |
|-----------------------------|
| Tel. 0161 306 6621          |
| Fax. 0161 275 0637          |
| ben.green at manchester.ac.uk  |
| http://www.agsc.ja.net      |
|=============================| 
-----Original Message-----
From: owner-ag-dev at mcs.anl.gov [mailto:owner-ag-dev at mcs.anl.gov] On
Behalf Of Jason Bell
Sent: 29 October 2007 06:42
To: ag-dev at mcs.anl.gov
Subject: [AG-DEV] Bridge Registry information via a text file

G'day all

I'm not sure if I should submit this as a feature request or not... (Let
me know and I will submit it to bugzilla)

There are some AG's around the place that have problems connecting to
Bridge Registries, thereby not getting a list of unicast bridges.

As a workaround, they run their own webserver that contains a peers.txt
file that points to the same information as the default registry address
(Example vv3.mcs.anl.gov:8030).   Would it be possible to include adding
a bridge registry using a text file, rather than a URL only???

As I know this "work around" overcomes some of the proxy issues.

I'm hoping someone could implement this.

Cheers,
Jason.

--------------------------------------------
Jason Bell, B.I.T.

B. Info. Tech. (Honours) Student

High Performance Computing Support Officer,
Network Engineer
Information Technology Division
Central Queensland University

E-mail : j.bell at cqu.edu.au
Phone : 07 4930 9229
--------------------------------------------
Patience is a virtue.

But if I wanted Patience,
I would have become a Doctor.
--------------------------------------------