A guide to moving your services to our new virtual infrastructure at digital ocean.

<<TableOfContents>>

== Changes Requiring Action ==

If you...

 * have a crontab
 * are running any daemons on `bog`
 * use postgresql
 * are using the low level `domain` domtool type instead of `dom` 

...you will need to take some manual actions during the migration or '''your services may break'''.

Migration should be otherwise transparent.

== Important Dates ==

TBD

 * all domains converted from suphp/cgi php to fastcgi based php
 * email migration
 * database migration (incurring downtime)
   * TODO: estimated max downtime window for migrating databases after doing test run
 * volumes migration

== Overview of New Machines ==

list new machines and their purposes (only user facing machines, interested users can check out [[Hardware]] for details on others.

shelob - webserver
marsh - shell server
minsky - mail server

=== Networking Change: IPv6 is Supported ===

Core HCoop services (ssh, email, dns, ...) are now IPv6 enabled. Members with native IPv6 are encouraged to test the new services and report any problems.

By default, domtool will not generate `AAAA` (IPv6) DNS records for your domains, but this will be enabled for the `dom` type after all sites are migrated. If you're feeling like living on the cutting edge, you can set an `AAAA` record to the web server manually using `dnsIPv6` and `dnsDefaultv6`, for example:

{{{
dom "yourdomain" where
  DefaultWebNode = "shelob";
  ...
with
  dnsDefaultv6 shelob_ipv6; (* sets AAAA for "yourdomain" *)
  dnsIPv6 "www.yourdomain" shelob_ipv6;
  ...
end
}}}


== Using the New Shell Server ==

The new shell server may be accessed using `ssh marsh.hcoop.net`. Thanks to [[AndrewFileSystem|openafs]], both the old and new infrastructure share the same volumes and you can access your data from either.

== Moving Web Sites ==

We are upgrading from apache 2.2 to 2.4, but have a configuration that should behave identically the one currently used on ServerNavajos. We are currently using `mod_access_compat` (Allow/Deny/Satisfy directives) instead of the newer `Require` access framework so that existing configurations do not need to be updated. At some point in the future we will update domtool and convert member configurations to the new access control directives.

If you are using the `dom` type, the move should be transparent; we will update `DefaultWebNode` to the new web server and reconfigure all domains on the date scheduled for transitioning to the new servers. If you would like to migrate your domains early, you may set the environment variable `DefaultWebNode = "shelob";` in your configuration to force the domain to be configured on the new webserver.

=== PHP ===

The new webserver is running php 5.6, with a configuration matching the existing production configuration.

We have supported a simple fastcgi based php for a while now, but have not widely deployed it. Our current method of supporting php-cgi based php (suphp) has been removed from debian stretch, and `shelob` only supports fastcgi based php.

All domains will be automatically upgraded to fastcgi based php, and plain cgi php will be disabled before migration.

After we migrate all domains, we will be able to enable php 7.2 with minimal effort (due to domtool limitations, it's not feasible to support it while ServerNavajos is in production).

(fastcgi php is mandatory now)

=== Low-level domain users ===

You're on your own, possibly ;-)

If you use `vhost` or `vhostDefault` to configure your websites, you will need to set the Web``Places environment variable to host them on `shelob`:

{{{
domain "yourdomain"
with
  vhostDefault where
    WebPlaces = [web_place_default "shelob"];
  with
    ...
  end;
end;
}}}

Any `dnsIP` or `dnsDefault` records pointing toward `navajos_ip` or "69.90.123.70" need to be changed to point to `shelob`:

{{{
domain "yourdomain"
with
  ...
  dnsDefault shelob_ip;
end;
}}}

=== Proxied Servers ===

Will need to be moved to `marsh`, but will still work when connecting from the new webserver to `bog`. Connections will be going unencrypted over the Internet however!

todo: example of proxied server config and update.

== Changes to Databases ==

== Postgresql ==

Postgres users '''must''' take action! Due to our usage of gssapi and ident for authentication, we cannot set up a simple stunnel for secure connections between the datacenters. To ensure the security of your data, connections from one datacenter to the other will require ssl be enabled in postgres. Applications based on `libpq` ought to negotiate ssl automatically, but php applications using the PDO library will not automatically negotiate, and require `sslmode=require` be added to the connection string. 

Postgresql is also being upgraded to 9.6 as 9.1 is not longer supported. There should be no major compatibility issues, and all databases will be automatically migrated. Postgres will still listen on port `5433`; some time after migration is complete we will enable postgresql 10 on port `5432`.

[[MemberManual/Databases#PostgreSQL|dbtool]] commands for postgres will now use version `postgres-9` instead of `postgres-9.1`.

=== MySQL ===

The MySQL migration should be transparent. We are staying on Percona MySQL 5.6, and are using an stunnel to transparently/securely proxy connections between the datacenters during migration.

== Changes to XMPP ==

We are now using ejabberd 18.06, which brings ...


== Features Coming After Migration ==

Once migration is completed, a few features will be implemented as soon as feasible:

 * PHP 7.2 support
 * Postgresql 10.x support
 * Automated integration with [[https://letsencrypt.org/|letsencrypt]] in DomTool.
----
CategoryMemberManual