Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

doc: cover changes related to swupd image reorganization #100

Merged
merged 3 commits into from
Apr 13, 2016

Conversation

pohly
Copy link
Contributor

@pohly pohly commented Apr 12, 2016

@dkinder @gvancuts please help review. This completes the integration
of meta-swupd as far as normal developers go. Documenting the usage of
swupd and swupd-based images is intentionally left out for now. I don't
have plans to add anything further about that.

This also replaces PR #98.

[skip ci]

Integrating meta-swupd changed image names and some concepts, for
example there is now an ostro-image.bbclass and several example image
recipes.

The revised "Image Configuration" section is sorted by importance
again (somehow the sstate subsection got inserted between the two
related "Development Images" and "Production Images" subsections).

The need to choose between development and production mode is stressed
more prominently in the "Initial Steps", because in practice first
time users missed that part. The resulting error message will be
enhanced slightly in a separate commit.

Signed-off-by: Patrick Ohly <[email protected]>
turned off, because:

a) swupd support is still new and may have unexpected problems.
b) image and swupd bundle creation cause additional overhead

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a little more on the overhead so people can decide for themselves. For example, is it only overhead on the build systems (compile time and disk space) or is there more to it than that? In other words, what is this 'extra work' that's mentionned in the next line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this be better?

b) image and swupd bundle creation cause additional overhead (disk space, compile time)
due to the extra work that needs to be done (creating multiple rootfs directories to simulate
what needs to be in each bundle, preparing the data that the swupd client pulls via HTTP(S)
when checking for updates). This can increase the build time from several minutes to over
an hour or more (depending on the number of bundles and files).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved in separate commit 2100fc.

Explains that the overhead is both in disk usage and copmpile time,
how large it is and why that cannot be avoided.

Signed-off-by: Patrick Ohly <[email protected]>
@barbieri
Copy link

+1 lgtm

The first argument about stability might be misunderstood, so let's
take it out and focus exclusively on the performance argument.

Signed-off-by: Patrick Ohly <[email protected]>
@pohly
Copy link
Contributor Author

pohly commented Apr 12, 2016

Accidentally included the functional changes from PR #104 in this PR. Removed by force-pushing just the doc changes.

@pohly
Copy link
Contributor Author

pohly commented Apr 13, 2016

@mythi I think enough people have looked at it now, so we do not need to wait for review by dkinder. Please merge.

If there are language issues, those can still be fixed later one, and right now the PR blocks further work (PR #104, new PR for cleaning up the architecture documents).

@mythi
Copy link
Contributor

mythi commented Apr 13, 2016

@pohly yes, I was waiting for OK from David but lets proceed.

@mythi mythi merged commit e2156b0 into ostroproject:master Apr 13, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants