aboutsummaryrefslogtreecommitdiff
path: root/doc/ideas.rst
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2021-02-26 12:59:59 -0700
committerSean Whitton <spwhitton@spwhitton.name>2021-02-26 12:59:59 -0700
commit3c04fc76a24b75760c39504f40e8653c5b657ecc (patch)
tree6373882d17e11576aaf7401c119fb921472ca664 /doc/ideas.rst
parentf325935af59b47d8425b6a4acbb772940b8a5723 (diff)
downloadconsfigurator-3c04fc76a24b75760c39504f40e8653c5b657ecc.tar.gz
rough requirements for chroot connection types
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'doc/ideas.rst')
-rw-r--r--doc/ideas.rst9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/ideas.rst b/doc/ideas.rst
index 3ac4bc9..9430cb5 100644
--- a/doc/ideas.rst
+++ b/doc/ideas.rst
@@ -12,6 +12,15 @@ Properties
Connections
-----------
+- POSIX-CONNECTION which runs commands in a chroot, and a corresponding
+ LISP-CONNECTION which forks into the chroot. The latter will make a system
+ call so it will be an implementation of ESTABLISH-CONNECTION which does not
+ behave like a :POSIX property. So I think we actually want a generic for
+ each connection type keyword symbol, which returns whether establishing a
+ connection of that type requires the most recent hop to be POSIX- or LISP-.
+ Then DEPLOY* can call that and error out if establishing the next hop
+ requires LISP- but we only have POSIX-.
+
Data sources
------------