[Bug 458163] Re: [regression] euca_rootwrap fixes affected eucalyptus power management (powerwake)

[Dustin Kirkland]

** Description changed:

  cluster/handlers.c: euca_rootwrap rework did not whitelist powerwake;
  however,  powerwake does *not* need root privs, drop euca_rootwrap
  wrapper.
+ 
+ ===========
+ SRU Verification
+ 
+ This fix is bundled with a set of unrelated SRU fixes for Eucalyptus.
+ 
+ To test this:
+  1) From a working UEC cluster, ensure that you have availability on your nodes:
+   $ euca-describe-availability-zones verbose
+  2) Ensure that your nodes support:
+   a) one of [ pm-suspend | pm-hibernate | poweroff ]
+   b) and wake-on-lan (might need to check bios, sudo ethtool eth0)
+  3) Adjust your eucalyptus scheduling algorithm to POWERSAVE on the front end
+   $ sudo sed -i "s/^SCHEDPOLICY=.*/SCHEDPOLICY=POWERSAVE/" /etc/eucalyptus/eucalyptus.conf
+  4) Restart eucalyptus
+   $ sudo restart eucalyptus
+  5) Make sure there are no running instances in your cloud
+  6) Watch the output of the CC, which will note the status of each node, waiting for 300 seconds of inactivity before putting the node to sleep
+   $ tail -f /var/log/eucalyptus/cc.log
+   ...
+   [Tue Nov  3 14:39:09 2009][023511][EUCADEBUG ] node 192.168.1.126 idle since 1257280677: (72/300) seconds
+   ...
+  7) After 300 seconds, you should see the node either suspend, hibernate, or poweroff, based on its capability
+  8) Once the node(s) are sleeping, run an instance.  Eucalyptus should dynamically resume (powerwake) the node and deploy the new instance there.
+   $ euca-run-instances $EMI -k mykey -t c1.medium
+ ===========

-- 
[regression] euca_rootwrap fixes affected eucalyptus power management (powerwake)
https://bugs.launchpad.net/bugs/458163
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.