[1026] | 1 | HANDLING CNAME REQUESTS |
---|
| 2 | |
---|
| 3 | When someone e-mails scripts.mit.edu asking for a foo.mit.edu hostname: |
---|
| 4 | |
---|
| 5 | 1. 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 the name back unless they can |
---|
| 26 | negotiate with the current owner of the name |
---|
| 27 | |
---|
| 28 | 2. 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 | 3. E-mail jweiss. |
---|
| 39 | * Open the ticket in RT |
---|
| 40 | * Click 'Comment' to the right of the body of the e-mail they sent |
---|
| 41 | * CC: jweiss@mit.edu (Don't use "To:", there's a bug) |
---|
| 42 | * Write something nice. I typically use |
---|
| 43 | Subject: scripts CNAME request: foo.mit.edu |
---|
| 44 | |
---|
| 45 | At your convenience, please make foo.mit.edu an alias of scripts.mit.edu. |
---|
| 46 | (or) |
---|
| 47 | At your convenience, please move the alias foo.mit.edu from bar.mit.edu to |
---|
| 48 | scripts.mit.edu. |
---|
| 49 | (or) |
---|
| 50 | At your convenience, please rename the current host foo.mit.edu to |
---|
| 51 | foo-old.mit.edu and make foo.mit.edu an alias of scripts.mit.edu. |
---|
| 52 | (or) |
---|
| 53 | If the request below is sufficient authorization, please remove.... |
---|
| 54 | |
---|
| 55 | * Set Status => Waiting and Blocking On => Moira |
---|
| 56 | |
---|
| 57 | Occasionally jweiss is on vacation; check /mit/ops/Pager.Schedule for |
---|
| 58 | "!jweiss" entries. It's worth asking him ahead of time if he's around. If |
---|
| 59 | not, see if zacheiss or cfox or computing-help will handle the requests. |
---|
| 60 | (zacheiss has been willing to do them in the past.) |
---|
| 61 | |
---|
| 62 | 4. Reply to the requestor (from either RT or your e-mail client), with |
---|
| 63 | something like "We've forwarded the hostname request to IS&T; it should take |
---|
| 64 | effect in 2-3 business days." |
---|
| 65 | |
---|
| 66 | 5. After the name updates (jweiss replies, and DNS updates - which you can |
---|
| 67 | check on -i dns), ask someone with root access to run |
---|
| 68 | |
---|
| 69 | vhostadd foo.mit.edu |
---|
| 70 | |
---|
| 71 | 6. Reply to the requestor again, and help them with stuff like MediaWiki URLs |
---|
| 72 | or RewriteRules if they're having trouble. |
---|
| 73 | |
---|
| 74 | --geofft, last updated 2008-08-02 |
---|