Client
Size: 11664
Comment:
|
Size: 8832
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 38: | Line 38: |
The client will export a DBus API on the system bus which will allow for a u/i in the System Settings to query, begin, cancel, and apply a system update. This service starts via DBus activation and exits automatically after a configurable amount of time (i.e. it does not run forever). It maintains state such that the client can exit and get restarted to continue the update, even across reboots. The client uses the [[../Downloader|download service]] to manage all file downloads. Here is the DBus API specification: === Signals === '''!UpdateAvailableStatus(is_available, downloading, message, version, size, descriptions)'''<<BR>> Sent in response to '''!CheckUpdateStatus()''' async calls, this signal provides information about the state of the update. * ''is_available'' - boolean which indicates whether an update is available or not. This will be false if the device's build number is equal to or greater than any candidate build on the server (IOW, there is no candidate available). This flag will be true when there is an update available. * ''downloading'' - boolean indicating whether a download is in progress. This doesn't include any preliminary downloads needed to determine whether a candidate is available or not (e.g. keyrings, blacklists, {{{channels.json}}}, and {{{index.json}}} files). This flag will be false if a download is paused. * ''message'' - A UTF-8 English human readable string indicating why the download did not start. Only useful if the second argument ('''downloading''') is false, otherwise ignore this value. * ''version'' - integer specifying the candidate build number we plan to update to. * ''size'' - integer providing total size in bytes for the upgrade. This does not include any preliminary files needed to determine whether an update is available or not. * ''descriptions'' - array of mappings containing the descriptions for all updates that will be downloaded. Each element of the array is a mapping of language-specific description keys to the UTF-8 description for that language. See [[../Server|the server documentation]] for details. Depending on the state of the system, as described below, some of the arguments of this signal may be ignored. '''!UpdateProgress(percentage, eta)'''<<BR>> Sent periodically, while a download is in progress. This signal is not sent when an upgrade is paused. * ''percentage'' - integer between 0 and 100 indicating how much of the download (not including preliminary files) have been currently downloaded. * ''eta'' - estimated time remaining to complete the download, in integer seconds '''!UpdateDownloaded()'''<<BR>> Sent when the currently in progress update has been completely and successfully downloaded. When this signal is received, it means that the device is ready to have the update applied (typically by issuing a system reboot). '''!UpdateFailed(consecutive_failure_count, last_reason)'''<<BR>> Sent when the update failed for any reason (including cancellation). The client will remain in the failure state until a '''!CheckUpdateStatus(0)''' or '''!CheckUpdateStatus(2)''' call is made. * ''consecutive_failure_count'' - an integer specifying the number of times in a row that a '''!CheckUpdateStatus()''' has resulted in an update failure. This increments until an update completes successfully (i.e. until the next '''!UpdateDownloaded()''' signal is issued). * ''last_reason'' - a string containing the English reason for why this updated failed. === Methods === '''!CheckUpdateStatus(reset_level)'''<<BR>> Asynchronous call instructing the client to check for an available update. If the client is in ''auto-download'' mode (see below), then this call will both check the server for an available update, and initiate the download of that update. If the client is in ''manual-download'' mode, then any available update will ''not'' occur automatically. It is also possible for the download to only occur automatically if other criteria are met, e.g. we are not on a wifi, or the device has a low battery. * ''reset_level'' indicates how the client should check for updates: * 0 means ''Hard reset'' * If an update is in progress or paused, it will be canceled. In all cases, any previous state will be reset, and a new update check will be performed. * 1 means ''Keep current state'' * If the previous update succeeded, a new update check will be started. * If an update check or download is already in progress, it will continue. * If a download is currently paused, it will resume if possible. * If a previous update check or download failed, state will ''not'' be reset and no new update check will be initiated. * 2 means ''Restart if in failure state'' * If the previous update succeeded, a new update check will be started. * If an update check or download is already in progress, it will continue. * If a download is currently paused, it will resume if possible. * If a previous update check or download failed, reset state and begin a new update. In all cases, an '''!UpdateAvailableStatus''' signal will be issued once an update candidate is determined to be available. If the client is in ''auto-download'' mode, then the download will also be started, leading to an '''!UpdateDownloaded''' or '''!UpdateFailed''' signal, as described above. When the '''!UpdateAvailableStatus''' signal is issued, the arguments can have the following values: * '''!UpdateAvailableStatus(true, true, "", build_number, size, descriptions)''' - This means that an update is available and is currently downloading. The build number of the candidate update is given, as is its total size in bytes, and the descriptions of the updates in all available languages. * '''!UpdateAvailableStatus(true, false, 'Reason', build_number, size, descriptions)''' - This means that an update is available, but it is not yet downloading, possibly because the client is in manual-update mode, or because the download is currently paused. The reason is given in the third argument, and the build number, size, and descriptions are given as above. * '''!UpdateAvailableStatus(false, ?, ?, ?, ?, ?)''' - There is no update available, and the remaining arguments should be ignored. '''!ApplyUpdate()'''<<BR>> Synchronous method to apply the update and initiate the reboot. Because the success path leads almost immediately to a reboot, the return value of this method is not meaningful (but will in practice be the empty string). In the failure case, the return value is a UTF-8 English string indicating the cause of the failure. '''!CancelUpdate()'''<<BR>> Synchronous method to cancel any update check or download in progress. No value is returned. '''!PauseDownload()'''<<BR>> Synchronous method to pause the current download. Returns a flag indicating whether the download was successfully paused. '''!ResumeDownload()'''<<BR>> Synchronous method to resume the current download. Returns a flag indicating whether the download was successfully resumed. '''!SetSetting(key, value)'''<<BR>> Synchronous method to write or update a setting. {{{key}}} is always a UTF-8 string, {{{value}}} is any basic DBus type (e.g. string, integer, boolean). While any key/value pair may be set, only the following currently have useful semantics: * '''min_battery''' - The minimum battery strength which will allow downloads to proceed. If the batter level is less than this, an available download will not be automatically initiated, although an explicit '''!DownloadUpdate()''' call can force this. * '''auto_downloads''' - A tri-state (currently) value indicating whether downloads should normally proceed automatically if an update is available or not. * 0 - Never download automatically (i.e. an explicit '''!DownloadUpdate()''' call is required to start the download) * 1 - Only auto-download if the device is connected via wifi * 2 - Always download the update automatically (the default) * '''failures_before_warning''' - An integer value which is unused by the client, but stored here for use by the user interface. '''!GetSetting(key)'''<<BR>> Synchronous method to read a setting. An exception is raised if the key has not previously been set. === Notes === * I decided not to include the ''version'' argument for '''!ApplyUpdate()''' and '''!CancelUpdate()'''. I understand why these were requested, but I'm calling YAGNI on it, at least for now. It complicates the API and until we work out the semantics for updating to anything other than the highest build number available, I want to keep things simple. It's easier to add things to an API than remove them. Similarly on the '''!UpdateProgress''', '''UpdateDownloaded''', and '''UpdateFailed''' signals, although not on the '''!UpdateAvailableStatus''' signal since the version there would indicate what update candidate we're going to update to. However, the etherpad indicates that this value may allow for synchronization between the u/i and the client. For example, it might allow for ignoring some signals in the case where an update is canceled and later restarted. Using a version for this isn't sufficient though because no new update may be available between these two actions. Thus for the latter use case, we may need an "update id". Still, I'd rather not add this complexity unless we absolutely need it. * I changed the values for ''reset_level''. It made more sense to me that level 0 was a hard reset. * I changed the order of some of the arguments to methods and signals. |
The client will export a D-Bus API on the system bus which will allow for a [[SoftwareUpdates#Phone|u/i in the System Settings]] to query, begin, cancel, and apply a system update. This service starts via D-Bus activation and exits automatically after a configurable amount of time (i.e. it does not run forever). It maintains state such that the client can exit and get restarted to continue the update, even across reboots. The client uses the [[../Downloader|download service]] to manage all file downloads. See the [[http://manpages.ubuntu.com/manpages/utopic/man8/system-image-dbus.8.html|manpage]] for the up-to-date description of the D-Bus interface. |
Line 119: | Line 42: |
== Mock scenarios == === Normal update in auto mode === option: --testing=update-auto-success 1. !CheckForUpdate() is received 2. wait for 3 seconds 3. !UpdateAvailableStatus(is_available: true, downloading: true, available_version: 42, update_size: 1337*1024*1024, last_update_date: 1983-09-13T12:13:14, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "") is sent by the daemon 4. immediately the daemon sends !UpdateProgress(0, 50) 5. then every half a second, send !UpdateProgress(+1, -0.5) 6. daemon sends !UpdateDownloaded() 7. client sends !ApplyUpdate(), daemon gives back an empty string (success) Note that while download is in progress, calling: * !PauseDownload will pause the emission of !UpdateProgress(). It's a noop otherwise (even if called when not download). * !DownloadUpdate will resume the emission of this signal. It's a noop otherwise (even if called when not download). * !CancelUpdate will cancel the update. It's a noop otherwise (even if called when not download). Next !CheckForUpdate will restart from 1. * !CheckForUpdate will immediately resends !UpdateSignal and !UpdateProgress (if a download is in progress). Then, it will eventually send !UpdateDownload if the update was already done, as per spec. General: * !GetSetting("auto_download") returns "1" * !SetSetting("auto_download", ''int'') will set the value in memory and then !GetSetting() will return it * !GetSetting("foo") returns "" === Normal update in manual mode === --testing=update-manual-success 1. !CheckForUpdate() is received 2. wait for 3 seconds 3. !UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "") is sent by the daemon 4. clients sends !DownloadUpdate 5. immediately the daemon sends !UpdateProgress(0, 50) 6. then every half a second, send !UpdateProgress(+1, -0.5) 7. daemon sends !UpdateDownloaded() 8. client sends !ApplyUpdate, daemon gives back an empty string (success) === Failing update === --testing=update-failed The daemon is already in failure mode 1. the client will send !CheckForUpdate 2. the daemon answers with !UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "You need some network for downloading.") 3. the daemon then send !UpdateFailed(9, "You need some network for downloading.") 4. the client will then send !CancelUpdate 5. the client will send !CheckForUpdate 6. the daemon answers with !UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "") === Failing apply === option: --testing=fail-apply the daemon is in !UpdateDownloaded mode 1. the client will send !CheckForUpdate 2. the daemon answers with !UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "") 3. then the daemon sends the !UpdateDownloaded signal 4. client sends !ApplyUpdate and receive "Not enough battery, you need to plug your phone." string === Failing Resume / Manual download === --testing=fail-resume the daemon is paused, 42% of download is done 1. the client will send !CheckForUpdate 2. the daemon answers with !UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "") 3. the daemons sends the !UpdatePaused(42) signal 4. client tries to call !DownloadUpdate() and receive an !UpdateFailed(9, "You need some network for downloading.") === Failing pause === --testing=fail-pause the daemon is downloading, initially, 10% is downloaded, there is no known ETA. 1. the client will send !CheckForUpdate 2. the daemon answers with !UpdateAvailableStatus(is_available: true, downloading: true, available_version: 42, update_size: 1337*1024*1024, last_update_date: '1983-09-13T12:13:14', descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "") 3. immediately the daemon sends !UpdateProgress(10, 0) (note! 0 for no ETA) 4. the clients then sends !PauseDownload() and will receive "no no, not now" as a string from the daemon. === No Update === --testing=no-update Nothing is downloading and no check is in progress. 1. client sends !CheckForUpdate 2. daemon answers with !UpdateAvailableStatus(is_available: false, downlading: false, ? ?, last_update_date: '1983-09-13T12:13:14', ", ") |
Client side
Introduction
The client tool is used to calculate the update, download the files, validate them and then set the needed flags for the upgrader to pick them up and apply.
Requirements
- Secure download of the indexes (HTTPS + GPG)
Support for everything described in the GPG spec (revocation list, multiple keyrings, ...)
- Resolution of the best upgrade path based on different policies (total download size, least number of reboots, ...)
- Download and validation of the files
- Flexible implementation to allow different upgrader setups with minimal changes required
- Support for suspend/resume of downloads
Nice to have
- Bandwidth limiting is a nice to have and might be tricky to implement.
Implementation
The current implementation is a command line tool, however it's expected to be turned into a DBus service that the Touch UI can drive.
Step-by-step example for an update
Whenever called the client does the following:
Grab https://server/channels.json and lookup the index for the current channel. If present, also grab the device GPG keyring.
Grab https://server/<channel>/<model>/index.json
- Read the current version number of the device (ubuntu-build file)
- Look for the most recent version available
- Resolve an upgrade path to it, minimizing download size and number of reboots
- Download any file needed up until the next reboot
- Validate all the files
- Write them to the cache partition
- Write the list of updates for the upgrader to use
- Reboot into the upgrader
Those steps don't include all of the specific GPG validation bits required to ensure the authenticity of all files. Those are detailed in the separate GPG wiki page.
Security (e.g. what to download over https/http) is outlined in the server security section.
DBus API
The client will export a D-Bus API on the system bus which will allow for a u/i in the System Settings to query, begin, cancel, and apply a system update. This service starts via D-Bus activation and exits automatically after a configurable amount of time (i.e. it does not run forever). It maintains state such that the client can exit and get restarted to continue the update, even across reboots. The client uses the download service to manage all file downloads. See the manpage for the up-to-date description of the D-Bus interface.
Code
Mock scenarios
Normal update in auto mode
option: --testing=update-auto-success
CheckForUpdate() is received
- wait for 3 seconds
UpdateAvailableStatus(is_available: true, downloading: true, available_version: 42, update_size: 1337*1024*1024, last_update_date: 1983-09-13T12:13:14, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "") is sent by the daemon
immediately the daemon sends UpdateProgress(0, 50)
then every half a second, send UpdateProgress(+1, -0.5)
daemon sends UpdateDownloaded()
client sends ApplyUpdate(), daemon gives back an empty string (success)
Note that while download is in progress, calling:
PauseDownload will pause the emission of UpdateProgress(). It's a noop otherwise (even if called when not download).
DownloadUpdate will resume the emission of this signal. It's a noop otherwise (even if called when not download).
CancelUpdate will cancel the update. It's a noop otherwise (even if called when not download). Next CheckForUpdate will restart from 1.
CheckForUpdate will immediately resends UpdateSignal and UpdateProgress (if a download is in progress). Then, it will eventually send UpdateDownload if the update was already done, as per spec.
General:
GetSetting("auto_download") returns "1"
SetSetting("auto_download", int) will set the value in memory and then GetSetting() will return it
GetSetting("foo") returns ""
Normal update in manual mode
--testing=update-manual-success
CheckForUpdate() is received
- wait for 3 seconds
UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "") is sent by the daemon
clients sends DownloadUpdate
immediately the daemon sends UpdateProgress(0, 50)
then every half a second, send UpdateProgress(+1, -0.5)
daemon sends UpdateDownloaded()
client sends ApplyUpdate, daemon gives back an empty string (success)
Failing update
--testing=update-failed The daemon is already in failure mode
the client will send CheckForUpdate
the daemon answers with UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "You need some network for downloading.")
the daemon then send UpdateFailed(9, "You need some network for downloading.")
the client will then send CancelUpdate
the client will send CheckForUpdate
the daemon answers with UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "")
Failing apply
option: --testing=fail-apply the daemon is in UpdateDownloaded mode
the client will send CheckForUpdate
the daemon answers with UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "")
then the daemon sends the UpdateDownloaded signal
client sends ApplyUpdate and receive "Not enough battery, you need to plug your phone." string
Failing Resume / Manual download
--testing=fail-resume the daemon is paused, 42% of download is done
the client will send CheckForUpdate
the daemon answers with UpdateAvailableStatus(is_available: true, downloading: false, available_version: 42, update_size: 1337*1024*1024, last_update_date: 83-09-13, descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "")
the daemons sends the UpdatePaused(42) signal
client tries to call DownloadUpdate() and receive an UpdateFailed(9, "You need some network for downloading.")
Failing pause
--testing=fail-pause the daemon is downloading, initially, 10% is downloaded, there is no known ETA.
the client will send CheckForUpdate
the daemon answers with UpdateAvailableStatus(is_available: true, downloading: true, available_version: 42, update_size: 1337*1024*1024, last_update_date: '1983-09-13T12:13:14', descriptions: [{'description': "Ubuntu Edge support", 'description-en_GB': 'change the background colour', 'description-fr': "Support d'Ubuntu Edge"}, {'description': "Flipped container with 200% boot speed improvement"}], error_reason: "")
immediately the daemon sends UpdateProgress(10, 0) (note! 0 for no ETA)
the clients then sends PauseDownload() and will receive "no no, not now" as a string from the daemon.
No Update
--testing=no-update Nothing is downloading and no check is in progress.
client sends CheckForUpdate
daemon answers with UpdateAvailableStatus(is_available: false, downlading: false, ? ?, last_update_date: '1983-09-13T12:13:14', ", ")
ImageBasedUpgrades/Client (last edited 2016-10-31 14:09:03 by localhost)