search for: ovirt_early

...-by: Alan Pevec <apevec at redhat.com> --- scripts/ovirt-early | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/ovirt-early b/scripts/ovirt-early index 4b85102..c17ea74 100755 --- a/scripts/ovirt-early +++ b/scripts/ovirt-early @@ -426,13 +426,13 @@ start_ovirt_early () { i=${i#collectd=} eval $(printf $i|awk -F: '{print "collectd_server="$1; print "collectd_port="$2;}') ;; - console=*) - bootparams="$bootparams $i" - ;; ovirt_early=*)...

Add a kernel parameter, vendor= which takes a path to a script embedded in the image. If this script is executable, we will then source it during ovirt-early start() after command line processing and before mounting of /config. We also call a post hook at the end of ovirt-early start(). Also include a sample vendor script. Signed-off-by: Ryan Harper <ryanh at us.ibm.com> ---

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