search for: var_subsys_ovirt_post

...s/ovirt-firstboot + stop_ovirt_firstboot ;; *) echo "Usage: ovirt-firstboot {start}" exit 2 esac - diff --git a/scripts/ovirt-post b/scripts/ovirt-post index f53157a..d0d1d20 100755 --- a/scripts/ovirt-post +++ b/scripts/ovirt-post @@ -19,7 +19,7 @@ VAR_SUBSYS_OVIRT_POST=/var/lock/subsys/$prog # load the configuration file [ -f "$NODE_CONFIG" ] && . "$NODE_CONFIG" -start() { +start_ovirt_post() { # wait for libvirt to finish initializing local count=0 while true; do @@ -80,11 +80,16 @@ start() { rm -f $VAR_SUBSYS_...

I'm looking for feedback on this first patch. The node has been pushed towards a more generic boot process. With this patch the node can now boot up and execute a few specifically-named scripts that reside in /etc/node.d/ at key points during the startup. After this goes upstream, the next step will be to define in more detail the remote interfaces for the "managed" runtime

This patch supercedes the previous one by moving the functionality for relocating files into the make system.

...ost b/scripts/ovirt-post index 951d108..da8557c 100755 --- a/scripts/ovirt-post +++ b/scripts/ovirt-post @@ -74,7 +74,7 @@ start() { /etc/ssh/ssh_host*_key* # perform any post startup operations - case $OVIRT_RUNTIME_MODE in + case $NODE_RUNTIME_MODE in esac rm -f $VAR_SUBSYS_OVIRT_POST diff --git a/server/.gitignore b/server/.gitignore deleted file mode 100644 index 41bf6ae..0000000 --- a/server/.gitignore +++ /dev/null @@ -1,4 +0,0 @@ -build/ -data/ -dist/ -devdata.db diff --git a/server/MANIFEST.in b/server/MANIFEST.in deleted file mode 100644 index e9c47eb..0000000 --- a/serve...