Add instruction for upgrading trove guest agent
Change-Id: I574f93d2023d35b2ede0e6e532a06ea1bdddad5f
This commit is contained in:
parent
cf3e9a6e74
commit
6b1c31e2ed
@ -9,4 +9,5 @@
|
||||
datastore
|
||||
building_guest_images
|
||||
secure_oslo_messaging
|
||||
upgrade-trove-guest-agent
|
||||
troubleshooting
|
||||
|
20
doc/source/admin/upgrade-trove-guest-agent.rst
Normal file
20
doc/source/admin/upgrade-trove-guest-agent.rst
Normal file
@ -0,0 +1,20 @@
|
||||
=========================
|
||||
Trove guest agent upgrade
|
||||
=========================
|
||||
|
||||
Normally, during Trove service upgrade, a new guest image needs to be rebuilt and used to rebuild the guest instance when the interfaces between Trove controller and guest agent change. Otherwise, the newer version Trove controller can't talk to the older version guest agent.
|
||||
|
||||
Prior to Victoria release, the process to upgrade guest agent is:
|
||||
|
||||
#. The cloud administrator builds a new guest image based on the target Trove code version.
|
||||
#. The cloud user creates backup for their instance.
|
||||
#. The cloud administrator upgrades Trove controller service.
|
||||
#. The cloud administrator updates the existing datastore version using the new image.
|
||||
#. The cloud user creates a new instance using the backup created above.
|
||||
#. The cloud user deletes the old instance.
|
||||
|
||||
From Victoria release, the upgrade process is much simpler:
|
||||
|
||||
#. The cloud administrator builds a new guest image based on the target Trove code version.
|
||||
#. The cloud administrator updates the existing datastore version using the new image.
|
||||
#. The cloud administrator triggers rebuild for the existing instances using the new image.
|
Loading…
x
Reference in New Issue
Block a user