search for: 951d108

Ovirt-post wasn't dependent on libvirtd being started. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-post | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/scripts/ovirt-post b/scripts/ovirt-post index 951d108..326c0b8 100755 --- a/scripts/ovirt-post +++ b/scripts/ovirt-post @@ -4,7 +4,7 @@ # ### BEGIN INIT INFO # Provides: ovirt-post -# Required-Start: ovirt +# Required-Start: ovirt libvirtd # Default-Start: 2 3 4 5 # Description: Performs managed node post configuration setup. ### END INIT INFO -...

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.

...s @@ -8,6 +8,8 @@ _log_status=1 OVIRT_LABEL=OVIRT # configuration defaults OVIRT_DEFAULTS=/etc/default/ovirt +# global configuration file +NODE_CONFIG=/etc/sysconfig/node-config if [ -f $OVIRT_DEFAULTS ]; then . $OVIRT_DEFAULTS fi diff --git a/scripts/ovirt-post 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/ser...