| 2009-10-22 13:48:18 |
Dustin Kirkland |
bug |
|
|
added bug |
| 2009-10-22 13:48:27 |
Dustin Kirkland |
eucalyptus (Ubuntu): status |
New |
In Progress |
|
| 2009-10-22 13:48:31 |
Dustin Kirkland |
eucalyptus (Ubuntu): assignee |
|
Dustin Kirkland (kirkland) |
|
| 2009-10-22 13:48:34 |
Dustin Kirkland |
eucalyptus (Ubuntu): milestone |
|
ubuntu-9.10 |
|
| 2009-10-22 13:48:37 |
Dustin Kirkland |
eucalyptus (Ubuntu): importance |
Undecided |
High |
|
| 2009-10-22 13:48:44 |
Dustin Kirkland |
nominated for series |
|
Ubuntu Karmic |
|
| 2009-10-22 13:48:44 |
Dustin Kirkland |
bug task added |
|
eucalyptus (Ubuntu Karmic) |
|
| 2009-10-22 13:50:21 |
Dustin Kirkland |
tags |
|
regression-potential |
|
| 2009-10-22 14:49:27 |
Launchpad Janitor |
branch linked |
|
lp:powernap |
|
| 2009-10-22 14:53:42 |
Dustin Kirkland |
bug task added |
|
powernap (Ubuntu) |
|
| 2009-10-22 14:53:51 |
Dustin Kirkland |
powernap (Ubuntu Karmic): status |
New |
In Progress |
|
| 2009-10-22 14:53:57 |
Dustin Kirkland |
powernap (Ubuntu Karmic): importance |
Undecided |
High |
|
| 2009-10-22 14:54:03 |
Dustin Kirkland |
powernap (Ubuntu Karmic): assignee |
|
Dustin Kirkland (kirkland) |
|
| 2009-10-22 14:54:08 |
Dustin Kirkland |
powernap (Ubuntu Karmic): milestone |
|
ubuntu-9.10 |
|
| 2009-10-22 15:32:05 |
Matt Zimmerman |
tags |
regression-potential |
|
|
| 2009-10-22 15:32:47 |
Matt Zimmerman |
eucalyptus (Ubuntu Karmic): milestone |
ubuntu-9.10 |
karmic-updates |
|
| 2009-10-22 15:32:51 |
Matt Zimmerman |
powernap (Ubuntu Karmic): milestone |
ubuntu-9.10 |
karmic-updates |
|
| 2009-10-22 15:35:06 |
Matt Zimmerman |
bug task added |
|
ubuntu-release-notes |
|
| 2009-10-22 15:43:09 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/eucalyptus/ubuntu |
|
| 2009-10-22 17:03:52 |
Dustin Kirkland |
eucalyptus (Ubuntu Karmic): importance |
High |
Medium |
|
| 2009-10-22 17:03:57 |
Dustin Kirkland |
powernap (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2009-10-22 17:18:06 |
Dustin Kirkland |
eucalyptus (Ubuntu Karmic): importance |
Medium |
Wishlist |
|
| 2009-10-22 17:20:28 |
Dustin Kirkland |
summary |
[regression] euca_rootwrap fixes broke eucalyptus power management (powerwake) |
[regression] euca_rootwrap fixes affected eucalyptus power management (powerwake) |
|
| 2009-10-22 19:28:45 |
Launchpad Janitor |
powernap (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-10-26 09:53:27 |
Thierry Carrez |
eucalyptus (Ubuntu Karmic): status |
In Progress |
Triaged |
|
| 2009-10-26 14:22:41 |
Dustin Kirkland |
ubuntu-release-notes: status |
New |
Invalid |
|
| 2009-10-29 15:49:58 |
Matt Zimmerman |
eucalyptus (Ubuntu Karmic): status |
Triaged |
Fix Committed |
|
| 2009-11-03 21:56:04 |
Dustin Kirkland |
description |
cluster/handlers.c: euca_rootwrap rework did not whitelist powerwake; however, powerwake does *not* need root privs, drop euca_rootwrap wrapper. |
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
===========
|
|
| 2009-11-03 22:06:58 |
Dustin Kirkland |
description |
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
===========
|
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 potential should be minimal, and restricted to Eucalyptus SCHEDPOLICY=POWERSAVE users, which is not the default scheduling policy.
===========
|
|
| 2009-11-03 22:10:44 |
Dustin Kirkland |
description |
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 potential should be minimal, and restricted to Eucalyptus SCHEDPOLICY=POWERSAVE users, which is not the default scheduling policy.
===========
|
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
...
[Tue Nov 3 16:09:57 2009][017368][EUCADEBUG ] sending powerdown to node: 192.168.1.126, http://192.168.1.126:8775/axis2/services/EucalyptusNC
...
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 potential should be minimal, and restricted to Eucalyptus SCHEDPOLICY=POWERSAVE users, which is not the default scheduling policy.
===========
|
|
| 2009-11-05 00:01:11 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/powernap |
|
| 2009-11-05 17:52:52 |
Mathias Gug |
tags |
|
uec |
|
| 2009-11-06 10:06:47 |
Martin Pitt |
tags |
uec |
uec verification-needed |
|
| 2009-11-06 11:00:25 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/eucalyptus |
|
| 2009-11-23 09:46:08 |
Launchpad Janitor |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-11-23 09:48:38 |
Martin Pitt |
eucalyptus (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2009-11-23 09:51:59 |
Martin Pitt |
eucalyptus (Ubuntu Karmic): status |
Fix Released |
Fix Committed |
|
| 2009-11-30 18:08:08 |
Martin Pitt |
tags |
uec verification-needed |
uec verification-done |
|
| 2009-11-30 20:16:09 |
Launchpad Janitor |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
