| Summary: | Updater: Investigate OSTree updater to add in the developer workflow | ||
|---|---|---|---|
| Product: | [Runtime] General Runtime | Reporter: | Mariano Lopez <mariano.lopez> |
| Component: | General Runtime | Assignee: | Mariano Lopez <mariano.lopez> |
| Status: | VERIFIED WONTFIX | QA Contact: | Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | benjamin.esquivel, bogdanx.a.voiculescu |
| Version: | unspecified | ||
| Target Milestone: | 1.9 M1 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Mariano Lopez
2015-04-29 21:54:37 UTC
We really need to put a bit more information into this bug about the kind of investigation that will be done and what the deliverable would be. YP is evaluating different software updater to integrate into the project. YP updater must be an atomic image based update that provides essential patches/features to embedded systems. It must have high reliability characteristics and tolerance to failures. The updaters investigation has given some data and a discussion is happening to decide whether this updater will be enabled for YP. This updater was discarded because the resource consumption that OSTree has. A new bug will be opened in the future if is considered again. won't fix |