Difference between revisions of "Trove-Guest-Agent-Upgrades"
Dan Nguyen (talk | contribs) m (→Description) |
Dan Nguyen (talk | contribs) m |
||
| Line 7: | Line 7: | ||
=== Description === | === Description === | ||
| − | ==== Configuration | + | ==== Configuration ==== |
New properties will be add to the trove configs to allow: | New properties will be add to the trove configs to allow: | ||
Revision as of 22:44, 27 February 2014
TODO: draft up the design here DN 2014-02-27
Introduction
This article describes the design for the Guest Agent upgrades in Trove. Currently Guest Agent upgrades are implemented through external deployment tools that push new code to each guest instance. Usually the same deployment tools for upgrading the control plane handle guest agent upgrades. This can create a bottle neck on the deployment infrastructure.
Description
Configuration
New properties will be add to the trove configs to allow:
- Enabling/Disabling Guest Agent Upgrades
- Specify an upgrade strategy
Workflow
- An external process will create a upgrade package or artifact
- An Admin user will notify a Guest Agent through the Trove Management API
- The Guest Agent will process the RPC message created by the API call and handle the upgrade accordingly
