Changeset 2348


Ignore:
Timestamp:
Jan 1, 2013, 8:19:29 PM (9 years ago)
Author:
adehnert
Message:
Add section on the interaction of network and svn

We've talked about why the hostname for the svn repo is complicated repeatedly
in the last few weeks, so document what makes it problematic and how to deal
with it.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/server/doc/install-fedora

    r2066 r2348  
    5656
    5757    xm create scripts-server machine_name=$MACHINE && console $MACHINE
     58
     59Networking and Subversion
     60~~~~~~~~~~~~~~~~~~~~~~~~~
     61
     62Our Subversion repository lives at svn://scripts.mit.edu/. Our hosts bind to
     63scripts.mit.edu on localhost. Unfortunately, this means that checking out the
     64subversion repository on a new server while you're in the process of setting it
     65up sometimes won't work. In particular, if the server is already binding the
     66scripts.mit.edu IP address, but not yet serving svn, your attempt to do the
     67checkout will connect to the local machine and fail.
     68
     69Any of the following should let you evade this issue:
     70* Avoid doing any svn operations between your first reboot and when svn is
     71  working. The networking changes from the install won't take effect until you
     72  reboot. Ordinarily, you won't need to do any commits or updates between the
     73  reboot and when LDAP and svn:// serving are working.
     74* Temporarily down the lo alias with the scripts.mit.edu IP address
     75  (18.181.0.43; seems to be lo:3 semi-consistently)
     76* Do your svn checkout from a current host, instead of scripts.mit.edu
     77  (for example, use svn://whole-enchilada.mit.edu/). Don't forget to
     78  svn switch --relocate to scripts.mit.edu once the server is set up.
Note: See TracChangeset for help on using the changeset viewer.