diff options
| author | Sean Whitton <spwhitton@spwhitton.name> | 2021-02-27 09:44:52 -0700 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2021-02-27 13:39:57 -0700 |
| commit | cd76b500d6e513d94422d394f8ae2319739fab96 (patch) | |
| tree | 6a8a6766bf3744032a5da94ade6f332cf6c399c6 | |
| parent | 4f3672536a9c96476aa5576beeeb446086ef64e7 (diff) | |
| download | consfigurator-cd76b500d6e513d94422d394f8ae2319739fab96.tar.gz | |
notes about how we could use SAVE-LISP-AND-DIE
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
| -rw-r--r-- | doc/ideas.rst | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/ideas.rst b/doc/ideas.rst index 9430cb5..02e1d95 100644 --- a/doc/ideas.rst +++ b/doc/ideas.rst @@ -21,6 +21,15 @@ Connections Then DEPLOY* can call that and error out if establishing the next hop requires LISP- but we only have POSIX-. +- :DEBIAN-SBCL could SAVE-LISP-AND-DIE and then immediately reinvoke the saved + image. That way, we have something that a cronjob can call to re-run the + deployment to ensure that all properties remain applied. Need to + think about how the property which sets up the cronjob will be specified in + consfigs -- does it make sense to allow passing in arbitrary deployments, or + do we only allow re-running exactly the same thing? If the former, the + saved image will need to take some sort of command line input telling it + what arguments to pass to DEPLOY*. + Data sources ------------ |