Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
FFS Gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
firmware
FFS Gluon
Commits
cd0d7715
Commit
cd0d7715
authored
10 years ago
by
Matthias Schiffer
Browse files
Options
Downloads
Patches
Plain Diff
docs: add some information about the new autoupdater
parent
c4109b34
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/features/autoupdater.rst
+13
-5
13 additions, 5 deletions
docs/features/autoupdater.rst
docs/user/site.rst
+4
-0
4 additions, 0 deletions
docs/user/site.rst
with
17 additions
and
5 deletions
docs/features/autoupdater.rst
+
13
−
5
View file @
cd0d7715
...
...
@@ -11,7 +11,15 @@ during development), but it can be enabled by setting the variable GLUON_BRANCH
to override the default branch set in the set in the site configuration.
A manifest file for the updater can be generated with `make manifest`. A signing script (using
ecdsautils) can by found in the `contrib` directory.
ecdsautils) can by found in the `contrib` directory. When creating the manifest, ``GLUON_PRIORITY`` can
be set on the command line, or it can be taken from the ``site.mk``.
The priority defines the maximum number of days that may pass between releasing an update and installation
of the images. The update probability with start at 0 after the release time mentioned in the manifest
and then slowly rise to 1 after the number of days given by the priority has passed. (Note: The priority
doesn't have an effect as the moment, this is yet to be implemented)
The priority may be an integer or a decimal fraction.
A fully automated nightly build could use the following commands:
...
...
@@ -25,7 +33,7 @@ A fully automated nightly build could use the following commands:
make manifest GLUON_BRANCH=experimental
contrib/sign.sh $SECRETKEY images/sysupgrade/experimental.manifest
cp -r images /where/to/put/this/experimental
mv /where/to/put/this/experimental/
experimental.manifest /where/to/put/this/experimental/manifest
ln -s
experimental.manifest /where/to/put/this/experimental/manifest
Infrastructure
...
...
@@ -47,8 +55,8 @@ We suggest to have following directory tree accessible via http:
factory/
The last level is generated by the Gluon build process. Do not forget
to re
name the ``<branch>.
manifest``
in
to ``manifest`` in
side of
the
sysupgrade directories.
to
c
re
ate symlinks from ``
manifest`` to ``
<branch>.
manifest`` in the
sysupgrade directories
to allow upgrades from Gluon versions before 2014.3
.
The server should be available via IPv6.
...
...
@@ -64,7 +72,7 @@ These commands can be used on a node.
::
# Force
U
pdate
C
heck
# Force
u
pdate
c
heck
, even when the updater is disabled
autoupdater -f
This diff is collapsed.
Click to expand it.
docs/user/site.rst
+
4
−
0
View file @
cd0d7715
...
...
@@ -168,6 +168,10 @@ GLUON_SITE_PACKAGES
GLUON_RELEASE
The current release version Gluon should use.
GLUON_PRIORITY
The default priority for the generated manifests (see the autoupdater documentation
for more information).
Examples
--------
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment