source: branches/locker-dev/locker/doc/tickets/cnames.txt @ 1414

Last change on this file since 1414 was 1414, checked in by ezyang, 13 years ago
Merged in changes from trunk --- Merging r1262 through r1413 into 'deploy/bin': U deploy/bin/django C deploy/bin/rails > Resolved by accepting working copy --- Merging r1221 through r1413 into '.': U sql/bin/get-password U sql/bin/save-password U doc/tickets/rt.txt U doc/tickets/cnames.txt U bin/fix-php-ini C bin/scripts-rails > Resolved by accepting working copy Skipped 'bin/for-each-server' U bin U sbin/parallel-find.pl U sbin/commit-email.pl U sbin/commit-zephyr Summary of conflicts: Tree conflicts: 2 Skipped paths: 1
File size: 3.7 KB
Line 
1HANDLING CNAME REQUESTS
2
3When someone e-mails scripts.mit.edu asking for a foo.mit.edu hostname:
4
51. Check that the hostname is not currently in use. The commands
6     stella foo.mit.edu
7     athrun ops qy ghal foo.mit.edu \*
8   should both say the name is not in use. (The latter checks for aliases of
9   deleted or otherwise inactive hostnames that stella ignores.)
10
11   If the name is currently an alias of a name they own, make sure to forward
12   to jweiss the permission to move that name around.
13
14   If the name is the primary name of a machine they own, ask them what they
15   would like to rename the machine to, and make it clear that they'll need to
16   have another name associated with that IP address. Or (especially if the
17   machine doesn't ping) ask them to confirm they're no longer using that IP
18   address. If they're totally confused and keep insisting they want scripts
19   to serve that name, go ahead and tell them you'll rename the current foo to
20   foo-old.
21
22   If the name belongs to a deleted host on a dorm network, e-mail rccsuper to
23   reap it; they should do so quickly. If it belongs to an FSILG, e-mail
24   ht-$ILG-acl (ht-et-acl, ht-pika-acl, etc.) and ask nicely. If it belongs
25   to an academic network, they're not getting even deleted names back unless
26   they can negotiate with the current owner of the name.
27
282. Check that they're requesting a scripts.mit.edu path that they control
29   (preferably, they'll give you a locker.scripts.mit.edu/something URL). If
30   they want a web.mit.edu path, you'll need to tell them to set up a redirect
31   according to http://scripts.mit.edu/faq/63/ in a directory in their
32   web_scripts, and ask them to tell us the directory. This doesn't block
33   requesting the hostname.
34
35   If they want something more outlandish, make sure they're not confused
36   before proceeding.
37
38   Confirm that they're signed up for scripts. http://locker.scripts.mit.edu/
39   should give something that isn't the "Account unknown" page.
40
413. E-mail jweiss.
42   * Open the ticket in RT
43   * Click 'Comment' to the right of the body of the e-mail they sent
44   * CC: jweiss@mit.edu (Don't use "To:", there's a bug)
45   * Write something nice, preferably including the stella command line.
46   I typically use
47   Subject: scripts CNAME request: foo.mit.edu
48
49   At your convenience, please make foo.mit.edu an alias of scripts-vhosts.mit.edu.
50
51   stella scripts-vhosts -a foo
52       (or)
53   At your convenience, please move the alias foo.mit.edu from bar.mit.edu to
54     scripts-vhosts.mit.edu.
55
56   stella bar -d foo
57   stella scripts-vhosts -a foo
58       (or)
59   At your convenience, please rename the current host foo.mit.edu to
60   foo-old.mit.edu and mark it as deleted, and make foo.mit.edu an
61   alias of scripts-vhosts.mit.edu.
62
63   stella foo -S 3 -R foo-old
64   stella scripts-vhosts -a foo
65       (or)
66   If the request below is sufficient authorization, please remove....
67
68   * Set Status => Waiting and Blocking On => Moira
69
70   Occasionally jweiss is on vacation; generally he sets an auto-responder,
71   so you can just try emailing him and hoping, or ask him if he's around. If
72   not, see if zacheiss or cfox or computing-help will handle the requests.
73   (zacheiss has been willing to do them in the past.)
74
754. Reply to the requestor (from either RT or your e-mail client), with
76   something like "We've forwarded the hostname request to IS&T; it should take
77   effect in 2-3 business days."
78
795. After the name updates (jweiss replies, and DNS updates - which you can
80   check on -i dns), ask someone with root access to run
81
82   vhostadd foo.mit.edu
83
846. Reply to the requestor again, and help them with stuff like MediaWiki URLs
85   or RewriteRules if they're having trouble.
86
87--geofft with minor edits by adehnert, last updated 2009-12-01
Note: See TracBrowser for help on using the repository browser.