| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
From now on, `morph deploy` will work to only accept a cluster
morphology as argument. A cluster morphology defines a list of
systems to built, and for each system a list of ways to deploy
them. We will not support the old syntax anymore.
- Update `morph deploy` docstring with the new syntax, including
an explanation of cluster morphologies (also document `tar`
deployments).
- Fix tests that used the old syntax.
- Add tests for cluster deployments.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a configuration extension or write extension fails, then it should
abort then, not continue to run other configuration extensions.
There was a period where this didn't happen, due to a missing feature
of cliapp that was assumed to be there, so failure to run these
extensions was not noticed.
This has since been fixed, but this would cause deploy to fail to
clean up its temporary directories.
Now it will cleanup the contents of the temporary directory after
any failures after it has been created.
A small amount of re-ordering was performed to make this easier.
|
| |
|
|
|
|
|
|
| |
It's a waste of time to unpack the rootfs, only to have to clean it up
again when you find out that you messed up the command line arguments.
This also has the benefit of reducing the amount of resources that have
to be considered for cleanup.
|
| |
|
|
| |
It is now a tested helper function in morphlib.util
|
| |
|
|
|
|
|
|
|
| |
We can't assume an extension cleans up after itself, as they can be
arbitrary shell scripts, and the best shell has to offer for cleanup is
`trap`, which is difficult to use.
So now, anything created with `mktemp` will get automatically cleaned
up by morph.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cross-bootstrap is a way to build baserock on an architecture that
does not currently have Baserock. It can be used by `morph
cross-bootstrap <ARCH> <REPO> <REF> <MORPH>`, and will build an artifact
that can be used as a root filesystem with a basic build environment
with a script named `native-bootstrap` which will build and install
every chunk in the system.
If done with a devel system, this will give you a suitable environment
for building a proper Baserock system.
This does not currently provide a kernel for the target architecture.
Apart from adding the cross-bootstrap plugin, it also makes the
following changes:
* Moves the lit of valid_archs into morphlib (instead of locally-scoped
in MorphologyFactory)
* BuildCommand takes an extra argument, build_env
* split BuildCommand's get_artifact_object into create_source_pool and
resolve_artifacts (plus changes things that use get_artifact_object to
use the new way)
* setup_mounts finds out whether to do so by whether build_mode is
'staging', instead of by whether the setting 'staging-chroot' is true.
* Makes ChunkBuilder's get_sources use the
morphlib.builder2.extract_sources() method, and moved
set_mtime_recursively into morphlib.builder2, since it's not currently
used anywhere else.
* moved ChunkBuilder's get_commands into the Morphology class (plus
changes to anything that used get_commands)
|
| | |
|
| |
|
|
|
| |
This was left over from experimentation, it works with sh, and is
faster.
|
| |
|
|
|
| |
This requires a patch to cliapp to actually print the output, as there
is a bug that causes it to always output to a pipe.
|
| |
|
|
|
| |
I find it easier to read without them, since there are less variables
to remember.
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
git://git.baserock.org/baserock/baserock/morph
I had fixed an conflict and change to use morph_tmp instead of
morph as default temp dir.
Reviewed by Lars Wirzenius
Conflicts:
morphlib/app.py
|
| | |
| |
| |
| |
| |
| | |
Now, inside the temporary directory we will have the following
subdirectories: chunks, staging, failed and deployments. The failed
directory will contain the staging areas of failed builds.
|
| |/
|
|
|
|
|
| |
The same check that cachedir and tempdir are large enough is used
for both build and build-morphology.
Deploy only checks for tempdir being large enough.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| | |
Terminal will let user know which extension (write or config) is
being run.
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
'remotes/origin/baserock/richardholland/expand-morph-deploy-help'
Reformatted the text a bit.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
When too few arguments are given to morph deploy it points you to the
help page, which contains no information about the number of arguments
needed. This patch adds some information from the morph reference manual
regarding the arguments needed for morph deploy.
|
| | |/
|/|
| |
| |
| |
| |
| | |
This adds TMPDIR to the environment of deployment extensions.
It uses the --tempdir setting from morph in the case that TMPDIR
is not already set.
|
| |/
|
|
|
|
| |
Previously we used the system branch top directory, when we need
the directory where the git repo for the system morphology is
checked out.
|
| | |
|
| |\ |
|
| | | |
|
| |\ \
| |/
|/|
| | |
'origin/baserock/richardholland/morph-deploy--tempdir'
|
| |/
|
|
| |
Allowed user to set the location of the temp directory using --tempdir
|
| |
|
|
|
| |
The artifact's build dependencies replace the build order graph
from previously.
|
| |
|
|
| |
Suggested-By: Sam Thursfield
|
| |
|
|
|
|
|
| |
This saves a check (and an indentation) in the deployment plugin,
making the code a tiny bit simpler.
Suggested-By: Sam Thursfield
|
| |
|
|
| |
Suggested-By: Sam Thursfield
|
| |
|
|
| |
Suggested-By: Sam Thursfield
|
| | |
|
|
|
This adds a new optional field to system morphologies:
"configuration-extensions".
The deployment plugin relies heavily on code from the branch and
merge plugin. This needs to be eventually fixed by refactoring
the codebase so that the shared code is in morphlib and not in
plugins. However, doing that is beyond the scope of adding a
deployment plugin.
|
