Storage Switch-off: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
= <span style="color:#00528c">Storage Switch-off</span> = | = <span style="color:#00528c">Storage Switch-off</span> = | ||
On the 1st of January, 2018, we will be '''switching off''' our legacy storage cluster, which replaced on the 17th of July 2017. | On the 1st of January, 2018, we will be '''switching off''' our legacy storage cluster, which was replaced with a significantly improved system on the 17th of July 2017. | ||
= <span style="color:#00528c">Why?</span> = | = <span style="color:#00528c">Why?</span> = | ||
Revision as of 15:53, 18 September 2017
Storage Switch-off
On the 1st of January, 2018, we will be switching off our legacy storage cluster, which was replaced with a significantly improved system on the 17th of July 2017.
Why?
The old storage cluster is unstable, and since we're still using it as a fallback data source, when it goes down it's still affecting our services.
What's the problem?
All of our services are already running on the new system, however, there is an edge case that requires your attention.
Any vendors which are sitting in your inventory and have not been / are not rezzed between 17th of July and 31st of December, 2017 will lose their configuration. This does not affect rezzed vendors in any way!
What do I need to do?
If you aren't using CasperVend, you don't need to do anything. This does NOT affect CasperLet.
- Please rez any configured vendors (such as affiliate vendors) from your inventory.
- Grant debit permissions
- Check that the vendors come online OK
That's all you need to do. Then to clean up the vendors:
- Delete the vendors
- Rez an UpgradeBee and use the "Check All" button