summaryrefslogtreecommitdiff
path: root/morphlib
Commit message (Collapse)AuthorAgeFilesLines
* deploy: Set status prefix to show which deployment the status is forRichard Maw2014-03-141-53/+69
|
* deploy: Make extension output display which it isRichard Maw2014-03-141-1/+2
| | | | This also makes it obey status prefix
* Add sysroot write extensionRichard Maw2014-03-141-0/+29
| | | | | | | | | | | | This moves the deployed system to somewhere on the host. Any existing contents of the directory is deleted, so don't try to be clever and deploy a new system on top of / in place of a proper upgrade. It can be used to deploy a chroot, sysroot or container, but its current use is to allow for nested deployments to include another system in itself, since the parent deployment's "$1" is prepended to the sub-deployment's "$2".
* Add the ability to do nested deploymentsRichard Maw2014-03-141-6/+18
|
* Move deploy logic into multiple methodsRichard Maw2014-03-141-14/+28
| | | | | Check is now separate from setup, which is now separate from running the commands.
* Move tempdir creation out of the loopRichard Maw2014-03-141-21/+27
| | | | | | We don't need to remove the whole thing every time, and for nested deployments, we want to keep the directories around, since there will be multiple deploys happening in it concurrently.
* Patch buildcommand once, rather that once per systemRichard Maw2014-03-141-3/+5
|
* Remove ugly loading of old b&m pluginRichard Maw2014-03-141-10/+0
|
* Fix copyright date in stagingarea_testsRichard Maw2014-03-141-1/+1
|
* Merge branch 'liw/quieten-staging-area'Lars Wirzenius2014-03-133-6/+10
|\ | | | | | | | | Reviewed-by: Sam Thursfield Reviewed-by: Adam Coldrick
| * Reduce spam from setting up staging areaLars Wirzenius2014-03-103-6/+10
| | | | | | | | | | | | | | | | | | | | | | Make the message "Installing chunk..." be chatty, i.e., only displayed when the user turns verbosity higher. Most of the time the chunk is already unpacked in the cache, so installing it takes a fraction of a second. Add a new message, at default verbosity, when a chunk needs to be unpacked. This can take a while, so a message is appropriate, so the user knows what is happening.
* | Give a useful error when attempting to build a cluster morphSam Thursfield2014-03-121-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously this resulted in a confusing traceback. This is a quick fix. I'd rather insert the error in the buildcommand module instead, but that code assumes the source being built is a system in several places before it actually checks the kind. Those would all need to be changed, or the code would need to reworked to call _validate_root_kind() much earlier. The Application.traverse_morphs() method is rather ugly anyway, so I'm happy to add further ugliness to it for the time being.
* | Fix creating a Source() from a cluster morphologySam Thursfield2014-03-121-1/+1
| | | | | | | | | | | | | | | | | | The Source.__init__() function assumes that the artifact.split_rules attribute is not None. Rather than complicating that code with error checks, let's make it always be correct. Avoids traceback from Source.__init__() when passing a cluster morph to `morph build`.
* | Merge branch 'sam/branching-fixes'Sam Thursfield2014-03-113-5/+10
|\ \ | |/ |/| | | Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
| * Fix `morph petrify` in cases where root repo URL has a trailing /Sam Thursfield2014-03-072-3/+8
| | | | | | | | | | | | | | | | | | gitdir._list_work_tree_files() needs to use os.relpath() instead of direct string manipulation to avoid chopping off the first line of every filename in cases where the base gitdir path string includes the trailing /. Unit test updated to catch this.
| * Raise correct error on `morph checkout|branch` of repo with no morphsSam Thursfield2014-03-071-2/+2
| |
* | Fix system branch dirname generation to avoid colonsLars Wirzenius2014-03-062-4/+12
| |
* | Fix assert in unit testLars Wirzenius2014-03-061-2/+2
|/ | | | | | We're clearly comparing two values for equality rather than asserting that the type of an object is not False, since that would make no sense at all.
* Merge branch 'baserock/markdoffman/s10382/add-help-option-v3'Mark Doffman2014-03-041-16/+52
|\ | | | | | | | | Reviewed-By: Richard Maw <richard.maw@codethink.co.uk> Reviewed-By: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
| * Make '--help' and help subcommand the same.Mark Doffman2014-03-041-16/+52
| | | | | | | | | | '--help' when used with a subcommand will show the subcommand help. Do not reflow the help text by using a custom formatter.
* | deploy: Record deployment information in deployed systemSam Thursfield2014-03-043-2/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit introduces a new requirement: USERS MUST NOT HAVE SENSITIVE DATA IN THEIR ENVIRONMENT. Otherwise it will be leaked into the system. Note that configuration fields with 'PASSWORD' in their name are stripped before writing the /baserock/deployment.meta file, so the OpenStack OS_PASSWORD field is not leaked. We want this so that we can run hooks at upgrade-time in the future. These hooks might need to know how the system was configured and what releaseuu it was. I'm not quite sure how we will define 'release' yet, but by using `git tag` and `git describe` we are able to textually label a time period in the history of the system's source code. We already have the specific SHA1 of definitions.git stored in the system metadata, so this should give us enough to be able to implement specific hooks that work around any awkward upgrade complications we encounter in the future.
* | deploy: Fix double exception in rawdisk.writeSam Thursfield2014-03-041-1/+2
| | | | | | | | | | | | | | If the disk image was not yet created then the os.remove() call fails and the original exception gets lost, causing confusion and sadness. Also print status earlier on failure
* | deploy: Check the --upgrade flag has been used correctly.Sam Thursfield2014-03-046-0/+199
| | | | | | | | | | Most write extensions don't handle both initial deployments and upgrades of a system.
* | deploy: Add optional 'check' extensionsSam Thursfield2014-03-041-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A write extension will have various kinds of sanity checks to do before actually performing the write. The current architecture of 'morph deploy' means that several minutes pass between the user starting the command and the write extension actually executing. It would be rage-inducing watching `morph deploy` spend 3 minutes unpacking a system only to then abort due to a silly error such as forgetting the --upgrade switch. Therefore it's better for now to split the sanity checks out into separate extensions that can be run as soon as possible and abort if the write extension is not going to be able to operate. For now this will just be used to validate usage of the --upgrade flag but in future checking connectivity to remote servers and the like should be done here too.
* | deploy: Honour AUTOSTART in ssh-rsync extensionSam Thursfield2014-03-041-0/+5
| | | | | | | | | | Now you can deploy an upgrade, set it to be the default version and reboot into it all with one call to `morph deploy`.
* | Make parse_autostart() into more general get_environment_boolean()Sam Thursfield2014-03-044-11/+11
| | | | | | | | | | Also, be more flexible when parsing environment booleans -- convert to lower case and match 0/1 and true/false as well as yes/no.
* | deploy: Always set new system as defaultSam Thursfield2014-03-041-0/+5
| |
* | deploy: Depend on client OS version manager to deploy upgradesSam Thursfield2014-03-041-91/+41
| | | | | | | | | | | | We now have a OS version manager tool in Baserock (in tbdiff.git). The code to deploy a new base OS version should live there, to minimise duplication between write extensions.
* | Don't create a blank /etc/fstabSam Thursfield2014-03-042-26/+1
| | | | | | | | | | | | | | | | This messes up the baserock-system-config-sync tool. Systemd does not require /etc/fstab to exist in any case. I have bumped the 'system-compatibility-version' field in this commit to trigger rebuilding all system artifacts.
* | deploy: Finish off the Btrfs system layout implementationSam Thursfield2014-03-043-42/+145
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The shared state directories defined in writeexts.py (/var, /home etc.) are now separate Btrfs subvolumes that are mounted in place using fstab. There are some warnings on mounting /var and /srv about the mountpoint not being empty. Not yet investigated. If a configure extension has already added / to the fstab, use the device it chose rather than assuming /dev/sda. This is required for the vdaboot.configure extension that we use for OpenStack deployments. Similarly, if a configure extension has added an entry for a state directory in /etc/fstab already, we don't replace it with a /state/xxx directory. That's only done as a default behaviour.
* | deploy: Add new --upgrade optionSam Thursfield2014-03-041-0/+7
| |
* | Adding syslinux 'menu.c32' file during the deployment.Pedro Alvarez2014-03-041-1/+19
|/ | | | | We will need this file to enable a bootloader menu to choose between OS after an upgrade.
* Add missing year to copyright headerLars Wirzenius2014-03-031-1/+1
| | | | | | After this, "./check --full" works. Reviewed-by: Daniel Silverstone (on IRC)
* Revert "Make '--help' and help subcommand the same."Mark Doffman2014-02-211-53/+16
| | | | This reverts commit a72c8dca6965d1ac239e4f0102f08fbf7fe59ac7.
* Revert "Add utilities for listing and finding extensions."Mark Doffman2014-02-213-155/+40
| | | | This reverts commit ab0a83a09a93ca33aa402d9c4d3b916a48a1a882.
* Revert "Add write and configuration extensions to help."Mark Doffman2014-02-211-51/+38
| | | | This reverts commit 329b81419be20e7b1f2651a47030186216044eec.
* Add write and configuration extensions to help.baserock/markdoffman/s10382/add-help-option-v2Mark Doffman2014-02-211-38/+51
| | | | | | | Add a command 'help-extensions' to list all extensions. Add the ability to find help on an extension by calling 'morph help [extension name]'. This will then call the extension with the '--help' option to obtain help text.
* Add utilities for listing and finding extensions.Mark Doffman2014-02-213-40/+155
|
* Make '--help' and help subcommand the same.Mark Doffman2014-02-211-16/+53
| | | | | '--help' when used with a subcommand will show the subcommand help. Do not reflow the help text by using a custom formatter.
* Legacy morph code: Also dump in specified orderRichard Maw2014-02-174-125/+12
| | | | | This rips out any remaining order-preserving code and instead uses the yaml dumper from morphloader.
* morphloader: Dump dicts with a nicer key orderRichard Maw2014-02-172-5/+93
|
* Warn and default to null if repo or ref are givenRichard Maw2014-02-133-5/+142
| | | | | | | | | | | | | | | | | | This now means that the system morphology is not altered when chunks are altered, so some tests had to change. Since this uses the python warnings API, these warnings can be ignored by running python -W ignore:"stratum morphology" \ -W ignore:"system morphology" \ "$(which morph)" ...` or turned into errors with python -W error:"stratum morphology" \ -W error:"system morphology" \ "$(which morph)" ...`
* Don't use repo or ref in test suiteRichard Maw2014-02-132-7/+5
|
* Allow omitting repo and ref when referring to strataRichard Maw2014-02-136-34/+35
|
* Allow tagging branches with null refsRichard Maw2014-02-131-27/+13
| | | | | | | This includes various changes allowing the repo and ref fields to be missing; but also a change to the the component_key function, so that instead of generating a string, it returns a tuple, since it's only required to be a consistently hashable index.
* Update Copyright and wrap lines longer than 79 charsPedro Alvarez2014-02-041-2/+3
|
* Improve help for gc commandrichardipsum/gc_plugin_improve_helpRichard Ipsum2014-01-301-6/+9
|
* Fix copyright year in previous commitRichard Maw2014-01-281-1/+1
|
* virtualbox-ssh: Work around change in VBox optionsRichard Maw2014-01-281-1/+19
| | | | | | | | | | | | VirtualBox changed a command line option in 4.3 incompatibly, so we now have to check the version number and change an option from --sataportcount to --portcount if the version of VirtualBox running on the target is at least 4.3 This turns the version into a tuple and compares it against another, since it's more reliable than comparing strings, which will count '1.10' as earlier than '1.2', and more convenient than comparing the digits individually.
* Add validation for chunk refs in strata to be (non-empty) stringsBen Brown2014-01-222-0/+69
|
View Lorry Controller Status