More storage for CloudLab storage servers
After spending quite a lot of time scrambling to come up with 10TB on one of our blockstore servers, I came to the conclusion that we are "under-storaged" if we are serious about the blockstore mechanism and allocation of 10+TB datasets. The situation:
- Utah: 43.5TB in one server, 6.7TB free. We have a couple of options for more space here. One is the DriveScale chassis which have over 100TB between them but needs more work to integrate with the model. The other is to wire up the Apt half of the Dell storage box. This would add a second server with 36TB. Requires running a 40Gb link from the Apt side of the pod over to
- Clemson: 50TB on one server, but in two zpools of 43 and 7TB. 5.8TB and 1.3TB free. Again a couple of possibilities. The first would be to commandeer another one of the first-gen storage node, giving us another 50TB. A more intriguing possibility would be to take over one of the
dss7500nodes with 45 HDDs and 270TB. That would solve the space issue for some time to come but would take one of only two of those machines. I only suggest it because those machines are almost never used right now, which is a waste.
- Wisc: 32TB on one server. 10TB free. The only option for more space here would be to take over another one or two
c240g1nodes, the only ones with significant storage. That would get another 32TB per server.
- UMass: no storage servers, no current plan.
- OneLab: no storage servers, no current plan.
- Emulab: 92TB on two storage servers. Each server has 40TB for persistent and 6TB for ephemeral. There is about 9.7TB free on each.
- Apt: 36TB in one server, all available, have been using for testing. The intent was to move this storage server + disk to CloudLab Utah.