|
|
---
|
|
|
title: TPA-RFC-40: Cymru migration budget
|
|
|
title: TPA-RFC-40: Cymru migration budget pre-approval
|
|
|
---
|
|
|
|
|
|
Summary: buy three large servers to migrate services from Cymru to a
|
|
|
trusted colocation facility. hardware: 40k$ ± 5k$ for 5-7 years,
|
|
|
colocation fees: 600$/mth.
|
|
|
Summary: broadly approve the idea of buying three large servers to
|
|
|
migrate services from Cymru to a trusted colocation
|
|
|
facility. hardware: 40k$ ± 5k$ for 5-7 years, colocation fees:
|
|
|
600$/mth.
|
|
|
|
|
|
Note: this is a huge document. The executive summary is above, to see
|
|
|
more details of the proposals, jump to the "Proposal" section
|
... | ... | @@ -105,8 +106,8 @@ infrastructure hosted at Cymru should be rebuilt in a new Ganeti |
|
|
cluster hosted in a trusted colocation facility which still needs to
|
|
|
be determined.
|
|
|
|
|
|
This will require a significant capital expenditure (~75,000$, still
|
|
|
to be clarified) that could be subsidized. Amortized over 7 to 8
|
|
|
This will require a significant capital expenditure (around 40,000$,
|
|
|
still to be clarified) that could be subsidized. Amortized over 7 to 8
|
|
|
years, it is actually cheaper, per month, than moving to the cloud.
|
|
|
|
|
|
Migration labor costs are also smaller; we could be up and running in
|
... | ... | @@ -120,7 +121,7 @@ colocation facility. |
|
|
|
|
|
The price breakdown is as follows:
|
|
|
|
|
|
* hardware: 42k$ ±5k$, 8k$/year over 5 years, 6k$/year over 7 years,
|
|
|
* hardware: 40k$ ±5k$, 8k$/year over 5 years, 6k$/year over 7 years,
|
|
|
or about 500-700$/mth, most likely 600$/mth (about 6 years
|
|
|
amortization)
|
|
|
* colo: 600$/mth (4U at 150$/mth)
|
... | ... | @@ -130,11 +131,11 @@ The price breakdown is as follows: |
|
|
## Scope
|
|
|
|
|
|
This proposal doesn't detail exactly how the migration will happen, or
|
|
|
exactly where. Those two are delegated to TPA's normal decision making
|
|
|
process and will probably be the subject of a new RFC detailing the
|
|
|
exact hardware, providers, and migration procedures going forward.
|
|
|
exactly where. This discussion happens in a subsequent RFC, TPA-RFC-43.
|
|
|
|
|
|
Only the budget is in question here.
|
|
|
This proposal was established to examine quickly various ideas and
|
|
|
validate with accounting and the executive director a general
|
|
|
direction to take.
|
|
|
|
|
|
## Goals
|
|
|
|
... | ... | @@ -182,8 +183,8 @@ already doing so. |
|
|
|
|
|
This section evaluates the cost of the three options, in broad
|
|
|
terms. More specific estimates will be established as we go along. For
|
|
|
now, the budget in the proposal is the actual proposal, and the costs
|
|
|
below should be considered details of the above proposal.
|
|
|
now, this broad budget in the proposal is the actual proposal, and the
|
|
|
costs below should be considered details of the above proposal.
|
|
|
|
|
|
## Self-hosting: ~12k$/year, 5-7 weeks
|
|
|
|
... | ... | @@ -548,7 +549,9 @@ This will need to be approved by those entities, in sequence: |
|
|
|
|
|
# Status
|
|
|
|
|
|
This proposal is currently in the `proposed` state.
|
|
|
This proposal is currently in the `obsolete` state. It has been
|
|
|
broadly accepted but the details of the budget were not accurate
|
|
|
enough and will be clarified in TPA-RFC-43.
|
|
|
|
|
|
# References
|
|
|
|
... | ... | |