source: trunk/server/doc/install-fedora @ 2348

Last change on this file since 2348 was 2348, checked in by adehnert, 9 years ago
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 size: 3.1 KB
Line 
1Installing a Scripts guest on a Xen host
2----------------------------------------
3
4You need to create the volumes to use:
5
6    lvcreate -n $MACHINE-root --size 50.00G $HOST
7    lvcreate -n $MACHINE-swap --size 10.00G $HOST
8    lvcreate -n $MACHINE-cache --size 11.00G $HOST
9
10/-------------------------------------------------------------------\
11    Note: If you need to manually format the the swap and cache
12    partitions (for example, you are migrating a host from 'migrate'),
13    these commands should work.  If in doubt, consult the kickstart.
14
15        # Use fdisk to generate a DOS partition table, and a single
16        # partition extending the entire volume.
17        fdisk /dev/$HOST/$MACHINE-swap
18        fdisk /dev/$HOST/$MACHINE-cache
19        # Figure out what kpartx is going to make the devices as
20        # (e.g. $SWAP_DEV and $CACHE_DEV)
21        kpartx -l /dev/$HOST/$MACHINE-swap
22        kpartx -l /dev/$HOST/$MACHINE-cache
23        # Read out the partition tables
24        kpartx -a /dev/$HOST/$MACHINE-swap
25        kpartx -a /dev/$HOST/$MACHINE-cache
26
27        # FORMAT!
28        mkswap $SWAP_DEV
29        mkfs.ext4 -O ^has_journal -m 0 -N 1000000 $CACHE_DEV
30
31        # Remove the devices
32        kpartx -d /dev/$HOST/$MACHINE-swap
33        kpartx -d /dev/$HOST/$MACHINE-cache
34\-------------------------------------------------------------------/
35
36Make sure that the console has an entry for this host:
37
38    vim /etc/conserver/conserver.cf
39
40If it doesn't, add:
41
42    console $MACHINE {
43        master $HOST;
44        include xen;
45    }
46
47We use Kickstart to to initial Fedora configuration.  Installing a new
48vanilla machine is as easy as:
49
50    xm create scripts-server machine_name=$MACHINE install=fXX && console $MACHINE
51
52The only prompt (near the beginning of the install process) should be
53for the root password, and at the end, when it asks you to reboot.
54Say yes, and the machine will power down, and then restart without
55the install parameter:
56
57    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 TracBrowser for help on using the repository browser.