From cd76b500d6e513d94422d394f8ae2319739fab96 Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Sat, 27 Feb 2021 09:44:52 -0700 Subject: notes about how we could use SAVE-LISP-AND-DIE Signed-off-by: Sean Whitton --- doc/ideas.rst | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'doc/ideas.rst') 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 ------------ -- cgit v1.2.3