GCP BYOL Upgrade
Upgrading BYOL - GCP
Last updated
Upgrading BYOL - GCP
Last updated
# | Step | Executed by | Comments | Estimated duration |
1. | Console creation | Reblaze | Configuration will be migrated | 1 day |
2. | Create new deployment | Customer | Creating a new instance group | 30 minutes |
3. | Setup canary instance | Reblaze & Customer | Adding a new template | 15 minutes |
4. | Verify traffic monitoring | Reblaze & Customer | Verifying that there are no issues with site performance, and making changes to security profiles if necessary. | 1 hour |
5. | Rеmove old template | Customer | Replace all instances | 15 minutes |
The Reblaze team will set up a new 2.x console for you. Once this is done, proceed to Step 2.
Go to the Marketplace and create a new Reblaze Deployment in version 2.x.
For the Deployment type, make sure to select “New region”.
For the Template resource zone, select the same region as the one in the previous installation. (Otherwise, the upgrade will not work.)
Scroll further down the page to the following:
For the Networking region, select the same region as the one in the previous installation. (Otherwise, the upgrade will not work.)
Auto-scaling settings - Minimum number of instances: At least as many instances as in the previous installation. In any case, it should never be less than 2 instances.
Redis settings: If you already have a Redis server installed (which is usually true for Reblaze installations of v2.14 and later), you do not need to create a new one, so you can uncheck the Redis deployment checkbox.
After choosing these settings, click the Deploy button at the bottom of the page.
Once your setup is complete, notify Reblaze support. Reblaze personnel will ensure the console is seeing the new instance group, and will connect the Redis server to it.
Within your GCP console, go to Instance groups and select your current (i.e., the older version) instance group.
Here’s an example where the current group is 6887:
Select it by clicking on its name. The following screen will appear:
Now click on Update VMs. You’ll see this:
Click on Add a Second Template. Add the new template you created. (In this example, the new template is 2354.) Now click on Update VMs.
Go to your Reblaze dashboard, and make sure that you see traffic in the new instances, and that your sites are working as expected.
In your GCP console, delete the template for the old version.
