search for: mgmthost

...t-awake failed [...] l 71 : it's a problem with the net redirection in bash my little fix : diff --git a/scripts/ovirt-awake b/scripts/ovirt-awake index c6a6902..8983ef1 100755 --- a/scripts/ovirt-awake +++ b/scripts/ovirt-awake @@ -68,7 +68,7 @@ ovirt_startup () { if [[ -n "${mgmthost}" ]] && [[ -n "${mgmtport}" ]]; then # log "Notifying oVirt management server: ${mgmthost}:${mgmtport}" - exec 3<> /dev/tcp/$mgmthost:$mgmtport + exec 3<>/dev/tcp/$mgmthost/$mgmtport connect-to-server receive_tex...

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

...ts/ovirt-awake +++ b/scripts/ovirt-awake @@ -33,7 +33,6 @@ . /etc/init.d/ovirt-functions prog=ovirt-early -NODE_CONFIG=/etc/sysconfig/node-config VAR_SUBSYS_NODECONFIG=/var/lock/subsys/node-config # load the configuration file @@ -57,8 +56,8 @@ error () { } ovirt_startup () { - local mgmthost=${OVIRT_MANAGEMENT_SERVER} - local mgmtport=${OVIRT_MANAGEMENT_PORT} + local mgmthost=${NODE_MANAGEMENT_SERVER} + local mgmtport=${NODE_MANAGEMENT_PORT} if [[ -z "${mgmthost}" ]] || [[ -z "${mgmtport}" ]]; then find_srv identify tcp @@ -109,7 +108,7 @@ s...