Tencent Cloud Lighthouse Application Server can quickly and easily adjust instance configurations by upgrading existing packages, which shows its flexibility. This article introduces the operation method and precautions for upgrading the package.
Notes
Lighthouse Application Server instance is only supported in upgrading packages, not in downgrading, which means the selected package's CPU, MEM, SSD system disk, bandwidth/peak bandwidth and monthly traffic should all be larger than the current package.
When upgrading an instance package, if there are changes in CPU or memory in the target package compared with the original package, the underlying layer will randomly assign a CPU model for the target package instance. It does not support specifying the CPU model of the underlying physical server and does not guarantee that the CPU model is the same as that of the original package instance.
After a successful package upgrade, the instance's existing IP address, firewall policy, password/key, and snapshots remain unaffected, and the instance expiration time remains unchanged.
Upgrading package across availability zones are not supported.
Entry-level, universal type, and storage packages can perform package upgrade operations. After a successful upgrade, the instance will occupy the quota of the target package type. For details, refer to Use Limits.
After upgrading the package for the "Cloud + Campus" event instance, you no longer enjoy the event renewal price.
When upgrading the Razor Speed Bundle for an instance, you can only select another Razor Speed Bundle with higher specifications.
We support fixed bandwidth package (which has been taken offline, configured with 1 core, 1GB MEM, 20GB SSD system disk, 1Mbps bandwidth) to upgrade to traffic package.
Only when the selected package’s CPU, MEM, SSD system disk, bandwidth/peak bandwidth and monthly traffic are all larger than the current package should cross-type upgrade package be available. That is, there is no package type restriction when the instance is upgraded to a package. For example, general package could be upgraded to storage package.
2. In the server list or table view, find and enter the details page of the instance whose package is to be upgraded.
3. Select Upgrade bundle in “Billing”. As shown below:
4. In the "Upgrade bundle" pop-up window, choose the selected package.
5. Read and tick “Fees for instance bundle upgrade” and click on Next step: Shutdown instance. As shown below:
6. In the "Shutdowninstance" step, tick "Agree to forced shutdown" and then click on Upgrade now.
Note:
Operating instance in shutdown status is supported. If you need to operate the instance in the power-on status, you need to confirm a forced shutdown, and it will take effect after restarting.
After upgrading, the current IP address, firewall policy, password/key settings will not be affected.
If the upgrade operation involves the expansion of the system disk of the instance, there is no need to manually expand the partition and file system operation after the package is successfully upgraded, and the original data will not be affected.
The current used traffic of the instance will not change, and the monthly traffic pack limit will be adjusted to the traffic pack limit of the upgraded package.
If the instance is upgraded from a fixed bandwidth to a traffic package, it will obtain a full traffic package limit and start calculating used traffic immediately after successful operation.
It usually takes 1-5 minutes for instance to finish upgrade. When it is done successfully, you can check the information about the package in the instance details page.
