keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fedostree/web: Add some usage stories, tweak installation

Browse Source
This commit is contained in:
Colin Walters 2014-01-20 10:13:11 -05:00
parent bab54b162e
commit f9a13b2fda
2 changed files with 42 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
fedostree/web/partials/home.html
View File

@ -119,6 +119,14 @@
<p>Anaconda should have an OSTree backend in addition to RPM. A basic UI
that provides a listview of shipped trees and allows picking them would
be quite sufficient initially.</p>
<h5>Dracut</h5>
<p>OSTree, when replicating content from a build server, effectively reverts
the <a href="https://fedoraproject.org/wiki/Features/DracutHostOnly">Dracut
host-only mode</a>. Furthermore, at the moment we hardcode
/etc/machine-id, which is a definite bug that needs to be fixed.
Possibly systemd should support reading the machine ID from the
kernel commandline, as it's the only host-writable area available
in early boot.</p>
<h3>Development area: OSTree Layering</h3>
<p>
This phase would be allowing "layering" of trees. For example,
@ -172,4 +180,37 @@
possible to engineer userspace so that many classes of upgrades
can be applied both live and safely, without race conditions.
</p>
<h3>OSTree example: Bisecting Mesa</h3>
<p>
OSTree allows not just dual booting - one can just as easily have
50 or more trees locally. Suppose that you're tracking Fedora
rawhide, and an upgrade breaks Mesa+GNOME (or sound, or something
else). You can not only easily revert to a last known good tree,
you can use OSTree to download intermediate builds from the build
server and <i>bisect</i> across them. Given the ability to do
local builds from git, automating bisection across source code is
entirely possible as well.
</p>
<h3>OSTree example: Parallel installing Red Hat Enterprise Linux and Fedora</h3>
<p>
Many contributors to Fedora are also Red Hat engineers working on
Red Hat Enterprise Linux. An example way to use OSTree is to have
EL7 installed in the physical /, and install Fedora in
/ostree/deploy/fedora. One can choose whether or not to share
/home.
</p>
<h3>OSTree example: Trying rawhide safely</h3>
<p>
This is an obvious use case - you can run a stable release, and
periodically try the development release on bare metal with a
great deal of safety, particularly if you choose not to share
/home. In this model, the only major risk is the newer kernel
containing filesystem corrupting bugs.
</p>
<h3>OSTree example: Reliable safe upgrades of a server cluster</h3>
<p>
OSTree allows taking a "cloud" like approach to a cluster of
traditional servers. Every upgrade is atomic and (relatively)
efficient, and can be served by any plain HTTP server.
</p>
</article>

1
fedostree/web/partials/installation.html
View File

@ -20,6 +20,7 @@
additional OSTree-generated boot entries. Otherwise, you will be
booting the (quite ordinary) Fedora install.
</p>
<p>Log in to the VM as root - there is no password.</p>
<p>Skip to <b>Booting the system</b> below.</p>
<h3>Installation instructions (inside an existing OS)</h3>
<p>First, you should understand what you'll be doing here. OSTree