This document explains how to add new hardware to the Phacility Cluster.
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 CLI Tools, deploy 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.
Before launching instances, consider these cases:
|admin||Do not launch multiple admin devices without making software changes to support this first.|
|bastion||Requires master key. Use --master. Copy master key to /core/conf/keys/master.key after deployment.|
|notify||These need software changes to scale up.|
|secure||Requires software changes to scale up.|
|vault||These are tricky to launch properly.|
Launch instances using these settings:
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).
These types of devices have persistent EBS storage:
|repo||rdata, rbak, rlog|
|secure||sdata, srepo, sbak, slog|
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:
For example, if you are brining up a db device, create an adata volume and attach it to /dev/sdh. Then create an abak volume and attach it to /dev/sdf.
Name any volumes you create with phacility.net names, for example dbak007.phacility.net.
Storage devices should have the same number as the hosts they are attached to. For example, db007 should use ddata007 and dbak007.
Volumes which will have backups written to them need device entries in Almanac on admin.phacility.com. These entries are used to store backup logs.
Using the CLI tools in rCORE, deploy the device (for example, web007):
core/ $ ./bin/remote deploy web007
The deploy workflow automatically runs the upgrade and restart workflows.
If you've launched a device which is part of a load balancer pool, add it to the appropriate load balancer:
|admin||alb||Should you really be launching these?|
|web||lb||Should also be added to vault but that's muddy.|
|notify||nlb||No process for putting multiple nlb nodes into production yet.|
Other devices do not need to be added to load balancer pools.
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).
Create device records for any storage devices you created, too.
All services have only one host in them today, so this is largely future work.