This document explains how to add new hardware to the [[ phacility_cluster | Phacility Cluster ]].
Overview
======
To add hardware to the cluster:
- Log in to the AWS console using your IAM role.
- Launch a new instance into the VPC.
- Add a `phacility.net` DNS entry for the device in Route 53.
- Launch and attach any required EBS storage.
- Using the [[phacility_cluster/cli | CLI Tools]]: `deploy`, `install`, and `upgrade` the device.
- If the device receives traffic from load balancers, add the host to the load balancer pool.
- If the device hosts a service, create a new Almanac device entry and bind it to new or existing services.
This process is not as automated as it could be, but we an automate it as the need arises. The more complicated and error-prone parts //are// automated.
Launching Instances
======
Before launching instances, consider these cases:
| Device | Considerations |
|---|---|
| `admin` | Do not launch multiple `admin` devices without making software changes to support this first. |
| `bastion` | Do not launch these unless you're sure you know what you're doing. |
| `vault` | These are tricky to launch properly. |
Launch instances using these settings:
| Device | AMI | Type | Security Group | Key |
|---|---|---|---|---|
| `admin` | ami-5c120b19 (Ubuntu 14) | t2.micro | instance.admin | phacility-master |
| `bastion` | ami-5c120b19 (Ubuntu 14) | t2.micro | instance.bastion | phacility-master |
| `db` | ami-5c120b19 (Ubuntu 14) | t2.micro | instance.db | phacility-master |
| `repo` | ami-5c120b19 (Ubuntu 14) | t2.micro | instance.repo | phacility-master |
| `vault` | ami-5c120b19 (Ubuntu 14) | t2.micro | instance.vault | phacility-master |
| `web` | ami-5c120b19 (Ubuntu 14) | t2.micro | instance.web | phacility-master |
NOTE: We'll stop using micro instances before we launch, so double-check if you go through this process again.
Adding DNS
======
For all devices, add a `phacility.net` DNS entry in Route 53 with the internal (VPC) device IP address. This should be an "A" record, similar to the other device records. The UI defaults are generally correct.
Set the name of the device in the EC2 console to be the same as the DNS entry you selected.
For example, if you launch a new web instance, you might call it `web007.phacility.net` (you should use the next number which doesn't have a DNS entry yet, of course).
EBS Storage
======
These types of devices have persistent EBS storage:
| Device | Storage Types |
|---|---|
| `admin` | `adata`, `bak` |
| `db` | `data`, `bak` |
| `repo` | `store`, `bak` |
If you're launching a device which uses one or more kinds of persistent EBS storage, you need to create and attach EBS volumes to the device. Use these settings for each storage type:
| Storage | Size | Attach To |
|---|---|---|
| `adata` | 8GB | `/dev/sdh` |
| `bak` | 8GB | `/dev/sdf` |
| `data` | 8GB | `/dev/sdh` |
| `store` | 8GB | `/dev/sdg` |
NOTE: We'll increase the size of these volumes significantly at some point, so double check if you go through this process again.
For example, if you are brining up a `db` device, create an `adata` volume and attach it to `/dev/sdh`. Then create a `bak` volume and attach it to `/dev/sdf`.
Name any volumes you create with `phacility.net` names, for example `bak007.phacility.net`.
Deploy
======
Using the CLI tools in rCORE, deploy the device (for example, `web007`):
core/ $ ./bin/remote deploy web007
core/ $ ./bin/remote install web007
core/ $ ./bin/remote upgrade web007
Add Devices to Load Balancers
=======
If you've launched a device which is part of a load balancer pool, add it to the appropriate load balancer:
| Device | Add To | Notes |
|---|---|---|
| admin | alb | Should you really be launching these? |
| web | lb | Should also be added to `vault` but that doesn't really exist yet. |
Other devices do not need to be added to load balancer pools.
Update Almanac Services
======
If you've launched a device which provides a cluster service, create a device record for it in Almanac on `admin.phacility.com`, then attach it to an existing Almanac Service (to add or replace a device in a service pool) or create a new Almanac Service for it (to add a new service pool).
//All services have only one host in them today, so this is largely future work.//