|
Size: 3182
Comment: Flesh out email section
|
Size: 9260
Comment: remove link to migrated page, add migration end date
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| For the purposes of this page, we'll use the name New to refer to the servers hosted at Peer 1 (which are deleuze, mire, and eventually abulafia) and Old to refer to any servers that we've used previously. | #pragma section-numbers off |
| Line 3: | Line 3: |
| '''Note''': We are in the process of migrating people who have signed up as guinea pigs. We are not currently accepting new domain requests or providing help to non-guinea-pigs. This will change once we have made reasonable progress in working out the kinks of the new setup. | This page describes the steps that members using the old machines need to take in order to migrate to the new machines. For the purposes of this page, we'll use the name New to refer to the servers hosted at Peer 1 (which are deleuze, mire, and eventually abulafia and krunk) and Old to refer to any servers that we've used previously. |
| Line 7: | Line 9: |
| = Getting login access to mire = | = Status of Migration = '''November 22, 2007''': The last issue blocking migration has been dealt with. Current HCoop people have until '''December 31''' to migrate their setup from the old servers to the new servers. |
| Line 9: | Line 12: |
| For megacz to fill in. | = Summary of what exactly is going on here = |
| Line 11: | Line 14: |
| = Databases = | Having an account on our new machines will allow you to have full access to your space in AFS (currently 400MB per user) and the ability to log in to {{{mire.hcoop.net}}} via ssh. |
| Line 13: | Line 16: |
| ''Here lie interim dbtool docs until migration is done, at which time they will probably move to UsingDatabases.'' | Requesting an account on the new infrastructure will not affect your fyodor account. You will have access to both accounts until after all migration is complete. |
| Line 15: | Line 18: |
| To manage your database user and databases, the basic syntax is `dbtool <DBTYPE> <COMMAND>`, where `<DBTYPE>` is `postgres` or `mysql`. | = Getting started = |
| Line 17: | Line 20: |
| The `adduser` command creates a database user for you, with the same name as your UNIX log-in name. In the case of `mysql`, you will be prompted for a password and confirmation re-entry in the usual manner. | == Step 1: Get a New account == |
| Line 19: | Line 22: |
| The `passwd` command allows you to reset the password. (Useless for `postgres`, where we use only ident authentication) | 1. ssh to `hcoop.net` as usual. 1. Run this command line: `migrationpw` 1. Follow the on-screen directions. 1. Wait for an e-mail from the user creation script. (This stage requires that a human run the script periodically to watch for failures, but one of us should run it several times a day.) |
| Line 21: | Line 27: |
| The `createdb <DBNAME>` command creates a database named `<USERNAME>_<DBNAME>`. | The password you set will go into our new Kerberos database, allowing log-in to mire and any other of our servers that we choose to enable for non-admin shell access. You will also use this password for authentication to other services, like e-mail and members-only HCoop web sites. |
| Line 23: | Line 29: |
| = DNS = | An e-mail will be sent to your HCoop account to let you know that your account has been created. Be sure to memorize your password, as it won't be saved anywhere unencrypted once the account creation script runs! |
| Line 25: | Line 31: |
| We are purposely not sending any DNS data from New to Old, which means that you need to change domains at your registrar if you want New to be authoritative for them. The proper nameservers are ns1.hcoop.net and ns3.hcoop.net, in that order. Keeping ns.hcoop.net and ns2.hcoop.net '''will not work'''. | == Step 2: Try logging in == |
| Line 27: | Line 33: |
| = Domains = | Now you may attempt to login to {{{mire.hcoop.net}}} using your favorite SSH client or the new AJAX SSH service at [http://ssh.hcoop.net/]. The latter requires a modern browser that cooperates with AJAX. === SSH Public Key is Obsoleted === You can no longer use SSH public key authentication. ["Kerberos"] authentication ("`ssh -K`") ''is'' supported, for passwordless log-in. Some day, someone might implement the Kerberos support needed to make SSH public key auth work again. See MemberManual/DistributedSecurity for more information on all of this. That being said, if you've always been typing a password to log in via SSH and don't care to do otherwise, then you don't need to bother reading this section! === DenyHosts === If you fail to log in correctly quite a few times, the Deny``Hosts scripts might lock you out. Currently any blocked IP's are purged after a week, so if you don't want to wait you'll need to submit a ticket, or if you can't access the portal to do this you'll need to send an email to [[MailTo(admins AT hcoop DOT net)]]. == Step 3: Visit the new portal == [https://members2.hcoop.net/ The new portal] uses the same password you use to log in to mire. That is, if you haven't created a New account yet, then you can't access the new portal. You should use the new portal for all administrative requests, except for the specialized request types (e.g., domains, firewall rules, etc.) when they relate to fyodor. == Step 4: Have your mail dual-delivered == We recommend that you tell fyodor to ''dual-deliver'' all of your mail so that one copy goes to deleuze (our new main server) and one copy goes to fyodor. That way you can start reading your email via deleuze, but if anything goes wrong you can just switch back to fyodor. To do this, put the following lines in your {{{~/.forward}}} file ''on fyodor''. Note that the comment on the first line is '''mandatory''' -- it tells exim that this forward file uses special exim features. If your username was {{{fred}}}, you would put this in your {{{~/.forward}}}: {{{ # Exim filter deliver fred deliver fred@deleuze.hcoop.net }}} and you mail will be dual-delivered. == Step 5: Copy your existing email == You can also copy the contents of your mailboxes from fyodor to mire (actually to our shared AFS filesystem by way of mire). To do this, log in to fyodor and type the following. {{{ rsync -are ssh --no-g --progress --verbose ~/Maildir/ mire.hcoop.net:Maildir/ }}} = Migration strategy = == Making a subdomain on fyodor and pointing it at mire == It is possible to test out your setup on the new servers by making a new subdomin on the old machine that points to the new machine. This way you can hone your new setup until it's as good as the old, while still having access to the old. First, make a directory in your {{{/etc/domains/TLD/DOMAIN}}} folder on the old machine. '''TLD''' is the Top-Level Domain of your domain. For example, it might be `com`, `net`, `us`, `in` etc. '''DOMAIN''' is your domain, and '''SUB''' is the new subdomain that you would like to use. '''SUB''' should not include any of the text in '''DOMAIN''', and should have no periods. {{{ mkdir /etc/domains/TLD/DOMAIN/SUB }}} In that directory, make a file called {{{.dns}}} with the following contents. {{{ Primary ns ns Default 69.90.123.68 }}} Then, run the `domtool` command to finalize your changes on Fyodor. Now request control of the '''DOMAIN''' using the new portal (http://members2.hcoop.net). When you receive notification of control, you can then log into mire.hcoop.net and configure DomTool so that Apache knows it can serve your '''SUB'''domain. Please take a look at [:MemberManual/UsingDomtool: using DomTool], the [:DomTool/UserGuide: DomTool user guide], and [:DomTool/Examples: DomTool examples] to learn how to do this. You'll probably want to take a look at the `vhost` directive. = Quickies = Be sure to read through the chapters of the MemberManual that interest you. The following are some very quick overviews of things that have changed. == DNS == We are purposely not sending any DNS data from Old to New, which means that you need to change domains at your registrar if you want New to be authoritative for them. The proper nameservers are `ns1.hcoop.net` and `ns3.hcoop.net`, in that order. Keeping `ns.hcoop.net` and `ns2.hcoop.net` '''will not work'''. == Domains == |
| Line 31: | Line 108: |
| = Home = | == Home == |
| Line 35: | Line 112: |
| = Email = | == OpenAFS and permissions == First of all, UNIX permissions carry no weight with AFS -- therefore they are useless to you. Instead, use Access Control Lists (ACL), which are a far more powerful way of restricting access to parts of a file tree. Read MemberManual/GettingStarted for further information on AFS concepts. |
| Line 37: | Line 115: |
| == .forward == | See the [:../TransferringFiles/OpenAFS:OpenAFS] subpage to find installation directions for various operating systems. |
| Line 39: | Line 117: |
| {{{~/.forward}}} files should have the same effect that they do with our old setup. | == Mailman == |
| Line 41: | Line 119: |
| == IMAP == | See the [:MemberManual/Email/MailingLists:Mailing Lists page] for details, including how to migrate existing lists to the new machines. |
| Line 43: | Line 121: |
| SSL IMAP is available via SSL at port 993, using hostname {{{deleuze.hcoop.net}}}. | == MoinMoin == |
| Line 45: | Line 123: |
| STARTTLS IMAP is available on port 143, using hostname {{{deleuze.hcoop.net}}}. | See the [:MemberManual/ServingWebsites/MoinMoin:MoinMoin configuration page] for details on how to set up MoinMoin and how to migrate data to match the new version of MoinMoin that we have installed. |
| Line 47: | Line 125: |
| == POP3 == POP3 access is available via SSL at port 995, using hostname {{{deleuze.hcoop.net}}}. == procmail == The page ProcmailExample has been updated for the new setup. Basically: * Use the file {{{~/.procmail.d/procmailrc}}} instead of {{{~/.procmailrc}}}. * Write any procmail logs in {{{~/Maildir}}} rather than elsewhere. * Use appropriate values for the HOME, MAILDIR, and DEFAULT options, based on those in ProcmailExample. = rsync = |
== rsync == |
| Line 62: | Line 128: |
== WebDAV == WebDAV is accessible at https://dav.hcoop.net/. WebDAV is useful when working on a website using systems that cannot mount an AFS share. For details on how to setup WebDAV, take a look at http://research.cs.berkeley.edu/doc/dav/ Note that you can only use WebDAV on directories that have {{{system:anyuser rl}}} as part of its ACL. You'll be able to write even if {{{system:anyuser}}} does not. == webmail == A Squirrelmail instance for reading your email on the new servers is available at [https://mail2.hcoop.net/]. == Web sites == Your {{{~/public_html}}} directory is available via HTTP through {{{http://deleuze.hcoop.net/~USER/}}}. Eventually this will change to {{{http://hcoop.net/~USER/}}}. Due to consequences of AFS authentication, we don't plan to allow dynamic content (CGI, PHP, etc.) via hcoop.net/~you/... on New. If you don't have a domain hosted at HCoop, but want to serve dynamic content, then you can request an hcoop.net subdomain (example: {{{USER.hcoop.net}}}, where USER is your username) via [http://bugzilla.hcoop.net/]. See the chapter on [:MemberManual/ServingWebsites:Serving Websites] for more details. |
This page describes the steps that members using the old machines need to take in order to migrate to the new machines.
For the purposes of this page, we'll use the name New to refer to the servers hosted at Peer 1 (which are deleuze, mire, and eventually abulafia and krunk) and Old to refer to any servers that we've used previously.
Status of Migration
November 22, 2007: The last issue blocking migration has been dealt with. Current HCoop people have until December 31 to migrate their setup from the old servers to the new servers.
Summary of what exactly is going on here
Having an account on our new machines will allow you to have full access to your space in AFS (currently 400MB per user) and the ability to log in to mire.hcoop.net via ssh.
Requesting an account on the new infrastructure will not affect your fyodor account. You will have access to both accounts until after all migration is complete.
Getting started
Step 1: Get a New account
ssh to hcoop.net as usual.
Run this command line: migrationpw
- Follow the on-screen directions.
- Wait for an e-mail from the user creation script. (This stage requires that a human run the script periodically to watch for failures, but one of us should run it several times a day.)
The password you set will go into our new Kerberos database, allowing log-in to mire and any other of our servers that we choose to enable for non-admin shell access. You will also use this password for authentication to other services, like e-mail and members-only HCoop web sites.
An e-mail will be sent to your HCoop account to let you know that your account has been created. Be sure to memorize your password, as it won't be saved anywhere unencrypted once the account creation script runs!
Step 2: Try logging in
Now you may attempt to login to mire.hcoop.net using your favorite SSH client or the new AJAX SSH service at [http://ssh.hcoop.net/]. The latter requires a modern browser that cooperates with AJAX.
SSH Public Key is Obsoleted
You can no longer use SSH public key authentication. ["Kerberos"] authentication ("ssh -K") is supported, for passwordless log-in. Some day, someone might implement the Kerberos support needed to make SSH public key auth work again. See MemberManual/DistributedSecurity for more information on all of this.
That being said, if you've always been typing a password to log in via SSH and don't care to do otherwise, then you don't need to bother reading this section!
DenyHosts
If you fail to log in correctly quite a few times, the DenyHosts scripts might lock you out. Currently any blocked IP's are purged after a week, so if you don't want to wait you'll need to submit a ticket, or if you can't access the portal to do this you'll need to send an email to MailTo(admins AT hcoop DOT net).
Step 3: Visit the new portal
[https://members2.hcoop.net/ The new portal] uses the same password you use to log in to mire. That is, if you haven't created a New account yet, then you can't access the new portal.
You should use the new portal for all administrative requests, except for the specialized request types (e.g., domains, firewall rules, etc.) when they relate to fyodor.
Step 4: Have your mail dual-delivered
We recommend that you tell fyodor to dual-deliver all of your mail so that one copy goes to deleuze (our new main server) and one copy goes to fyodor. That way you can start reading your email via deleuze, but if anything goes wrong you can just switch back to fyodor.
To do this, put the following lines in your ~/.forward file on fyodor. Note that the comment on the first line is mandatory -- it tells exim that this forward file uses special exim features. If your username was fred, you would put this in your ~/.forward:
# Exim filter deliver fred deliver fred@deleuze.hcoop.net
and you mail will be dual-delivered.
Step 5: Copy your existing email
You can also copy the contents of your mailboxes from fyodor to mire (actually to our shared AFS filesystem by way of mire). To do this, log in to fyodor and type the following.
rsync -are ssh --no-g --progress --verbose ~/Maildir/ mire.hcoop.net:Maildir/
Migration strategy
Making a subdomain on fyodor and pointing it at mire
It is possible to test out your setup on the new servers by making a new subdomin on the old machine that points to the new machine. This way you can hone your new setup until it's as good as the old, while still having access to the old.
First, make a directory in your /etc/domains/TLD/DOMAIN folder on the old machine. TLD is the Top-Level Domain of your domain. For example, it might be com, net, us, in etc. DOMAIN is your domain, and SUB is the new subdomain that you would like to use. SUB should not include any of the text in DOMAIN, and should have no periods.
mkdir /etc/domains/TLD/DOMAIN/SUB
In that directory, make a file called .dns with the following contents.
Primary ns ns Default 69.90.123.68
Then, run the domtool command to finalize your changes on Fyodor.
Now request control of the DOMAIN using the new portal (http://members2.hcoop.net). When you receive notification of control, you can then log into mire.hcoop.net and configure DomTool so that Apache knows it can serve your SUBdomain. Please take a look at [:MemberManual/UsingDomtool: using DomTool], the [:DomTool/UserGuide: DomTool user guide], and [:DomTool/Examples: DomTool examples] to learn how to do this. You'll probably want to take a look at the vhost directive.
Quickies
Be sure to read through the chapters of the MemberManual that interest you. The following are some very quick overviews of things that have changed.
DNS
We are purposely not sending any DNS data from Old to New, which means that you need to change domains at your registrar if you want New to be authoritative for them. The proper nameservers are ns1.hcoop.net and ns3.hcoop.net, in that order. Keeping ns.hcoop.net and ns2.hcoop.net will not work.
Domains
See the DomTool page for instructions on managing your domains with the new setup. The configuration files are in a vastly different format, but they have a better-defined syntax that should be relatively easy to understand.
Home
Your home directory is now managed by AFS. You will enter it by default when logging in to mire.hcoop.net via ssh. Type pwd to see what the path is. It will look like /afs/hcoop.net/user/u/us/username. Some directories have been created for you already, so that they have the correct permissions for things like serving web pages and delivering mail.
OpenAFS and permissions
First of all, UNIX permissions carry no weight with AFS -- therefore they are useless to you. Instead, use Access Control Lists (ACL), which are a far more powerful way of restricting access to parts of a file tree. Read MemberManual/GettingStarted for further information on AFS concepts.
See the [:../TransferringFiles/OpenAFS:OpenAFS] subpage to find installation directions for various operating systems.
Mailman
See the [:MemberManual/Email/MailingLists:Mailing Lists page] for details, including how to migrate existing lists to the new machines.
MoinMoin
See the [:MemberManual/ServingWebsites/MoinMoin:MoinMoin configuration page] for details on how to set up MoinMoin and how to migrate data to match the new version of MoinMoin that we have installed.
rsync
If you're using rsync to transfer data to the new servers, the "-a" option by itself won't work properly because rsync attempts to chgrp the transferred files. Use "-a --no-g" instead of "-a".
WebDAV
WebDAV is accessible at https://dav.hcoop.net/. WebDAV is useful when working on a website using systems that cannot mount an AFS share. For details on how to setup WebDAV, take a look at http://research.cs.berkeley.edu/doc/dav/
Note that you can only use WebDAV on directories that have system:anyuser rl as part of its ACL. You'll be able to write even if system:anyuser does not.
webmail
A Squirrelmail instance for reading your email on the new servers is available at [https://mail2.hcoop.net/].
Web sites
Your ~/public_html directory is available via HTTP through http://deleuze.hcoop.net/~USER/. Eventually this will change to http://hcoop.net/~USER/.
Due to consequences of AFS authentication, we don't plan to allow dynamic content (CGI, PHP, etc.) via hcoop.net/~you/... on New. If you don't have a domain hosted at HCoop, but want to serve dynamic content, then you can request an hcoop.net subdomain (example: USER.hcoop.net, where USER is your username) via [http://bugzilla.hcoop.net/]. See the chapter on [:MemberManual/ServingWebsites:Serving Websites] for more details.