Storage Switch-off: Difference between revisions
(Created page with "THIS ONLY AFFECTS CASPERVEND - '''NOT''' CASPERLET On the 1st of January, 2018, we will be '''switching off''' our legacy storage cluster. All of our services are already ru...") |
No edit summary |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= <span style="color:#00528c">Storage Switch-off</span> = | |||
On the 1st of January, 2018, we will be '''switching off''' our | On the 1st of January, 2018, we will be '''switching off''' our old storage system, which was replaced with a significantly improved system on the 17th of July 2017. | ||
= <span style="color:#00528c">Does this affect me?</span> = | |||
If you have given out affiliate vendors, or you otherwise have pre-configured vendors sitting in your inventory, you are affected by this notice and you need to read below. | |||
'''A pre-configured vendor is a vendor which you have rezzed, configured, and taken back into your inventory.''' | |||
:#. Please '''rez''' any configured vendors ( | If you aren't using CasperVend, you don't need to do anything. This does '''NOT''' affect CasperLet. | ||
:# | |||
:# | = <span style="color:#00528c">Why?</span> = | ||
We switched to a new, much faster, much more stable storage system in July. Due to the insane quantity of data involved, we're only migrating '''active data''' and we're getting rid of the billions of old vendor configurations belonging to vendors which don't exist any more. To facilitate this, we're still using the old system as a "fallback" - if a vendor attempts to load, and it doesn't exist on the new system, we'll check the old system to see if it exists there, and migrate it over. | |||
However, the old system is unreliable, and this "fallback" means that it still impacts our services when it goes down. For this reason, we need to set a cut-off date to get rid of it entirely. | |||
= <span style="color:#00528c">What's the problem?</span> = | |||
All of our services are already running on the new system, ''however'', '''there is a special case that you need to be aware of'''. | |||
<span style="color:red">Any vendors which are sitting in your inventory and '''are not/have not been rezzed between 17th of July and 31st of December, 2017''' will lose their configuration.</span> | |||
= <span style="color:#00528c">What do I need to do?</span> = | |||
:# Please '''rez''' any pre-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: | 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 | ||
Latest revision as of 16:12, 18 September 2017
Storage Switch-off
On the 1st of January, 2018, we will be switching off our old storage system, which was replaced with a significantly improved system on the 17th of July 2017.
Does this affect me?
If you have given out affiliate vendors, or you otherwise have pre-configured vendors sitting in your inventory, you are affected by this notice and you need to read below.
A pre-configured vendor is a vendor which you have rezzed, configured, and taken back into your inventory.
If you aren't using CasperVend, you don't need to do anything. This does NOT affect CasperLet.
Why?
We switched to a new, much faster, much more stable storage system in July. Due to the insane quantity of data involved, we're only migrating active data and we're getting rid of the billions of old vendor configurations belonging to vendors which don't exist any more. To facilitate this, we're still using the old system as a "fallback" - if a vendor attempts to load, and it doesn't exist on the new system, we'll check the old system to see if it exists there, and migrate it over.
However, the old system is unreliable, and this "fallback" means that it still impacts our services when it goes down. For this reason, we need to set a cut-off date to get rid of it entirely.
What's the problem?
All of our services are already running on the new system, however, there is a special case that you need to be aware of.
Any vendors which are sitting in your inventory and are not/have not been rezzed between 17th of July and 31st of December, 2017 will lose their configuration.
What do I need to do?
- Please rez any pre-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