powernap and Eucalyptus seem unable to reach an understanding

Bug #711587 reported by C de-Avillez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
High
Andres Rodriguez
Natty
Fix Released
High
Andres Rodriguez
powernap (Ubuntu)
Fix Released
Medium
Andres Rodriguez
Natty
Fix Released
Medium
Andres Rodriguez

Bug Description

installed the Cloud on cempedak, and two nodes (mabolo and marula). Due to other problems the nodes ended up idle, and powernap grabbed them.

Eucalyptus now has 'euca-describe-availability-zones' as:

AVAILABILITYZONE UEC-TEST1 10.55.55.2
AVAILABILITYZONE |- vm types free / max cpu ram disk
AVAILABILITYZONE |- m1.small 0000 / 0000 1 192 2
AVAILABILITYZONE |- c1.medium 0000 / 0000 1 256 5
AVAILABILITYZONE |- m1.large 0000 / 0000 2 512 10
AVAILABILITYZONE |- m1.xlarge 0000 / 0000 2 1024 20
AVAILABILITYZONE |- c1.xlarge 0000 / 0000 4 2048 20

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: eucalyptus-cloud 2.0+bzr1241-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-1.28-server 2.6.38-rc2
Uname: Linux 2.6.38-1-server x86_64
.etc.eucalyptus.eucalyptus.cc.conf: CC_NAME="UEC-TEST1"
Architecture: amd64
Date: Tue Feb 1 19:00:36 2011
ProcEnviron:
 LC_TIME=en_DK.utf8
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SourcePackage: eucalyptus

Revision history for this message
C de-Avillez (hggdh2) wrote :
Revision history for this message
C de-Avillez (hggdh2) wrote :

Marking High, this can really mess up with usage.

Changed in eucalyptus (Ubuntu):
importance: Undecided → High
C de-Avillez (hggdh2)
tags: added: iso-testing
Changed in eucalyptus (Ubuntu Natty):
assignee: nobody → Andres Rodriguez (andreserl)
Dave Walker (davewalker)
tags: added: server-nrs
Dave Walker (davewalker)
Changed in eucalyptus (Ubuntu Natty):
milestone: none → natty-alpha-3
Martin Pitt (pitti)
Changed in eucalyptus (Ubuntu Natty):
milestone: natty-alpha-3 → ubuntu-11.04-beta-1
Revision history for this message
Andres Rodriguez (andreserl) wrote :

After a bit of testing and researching I was unable to reproduce this bug and determined that this was apparently related to bug #724470, which caused the CC to be unable to communicate to the NC. After this bug was fixed, the issues presented in this bug report were no longer seen.

However, due to the recent changes in PowerNap we need to consider various things:

When running Eucalyptus with SCHEDPOLICY=ROUNDROBIN (default), PowerNap (in each of the NC's with default configuration) should not take any action if the NC's if activity is detected, to prevent PowerNap to entering in a powersave state (or if modified to suspend/poweroff). To prevent this we should either do:

 - Do not start PowerNap by default.
 - Add a ProcessMonitor for /sbin/init so that it never detects inactivity.

If we still want to be able to use PowerNap and save power while inactive it *should* be left configured for "PowerSave" mode and:
 - Add a ProcessMonitor for kvm.

NOTE: This will prevent PowerNap for performing any actions that will take the machine offline or leaving the server in a lower power state when it shouldn't be.

When running Eucalyptus with SCHEDPOLICY=POWERSAVE, we should take even more special considerations. If the action method is to suspend/poweroff, then PowerNap should:

 - Add a ProcessMonitor for /sbin/init

If the action method in this case is PowerSave, then the following should be considered:

 - Add ProcessMonitor for kvm
 - Set ABSENT_SECONDS (powernap) equal or higher to IDLESECONDS (eucalyptus)

NOTE: This considerations will ensure that Eucalyptus takes control of the process of taking machines online/offline rather than leaving PowerNap to do by itself when it probably shouldn't.

Before marking this bug invalid, I'd like someone to post opinions/comments or even better solutions/considerations.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Marking Triaged, we know what this is all about now.

Changed in eucalyptus (Ubuntu Natty):
status: New → Triaged
Changed in powernap (Ubuntu Natty):
status: New → In Progress
assignee: nobody → Andres Rodriguez (andreserl)
importance: Undecided → Low
importance: Low → Medium
Changed in powernap (Ubuntu Natty):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package powernap - 2.5-0ubuntu1

---------------
powernap (2.5-0ubuntu1) natty; urgency=low

  * Add support to load confs from /etc/powernap/config.d. Added to leverage
    compatibility with other applications, such as Eucalytpus. (LP: #711587)
 -- Andres Rodriguez <email address hidden> Mon, 14 Mar 2011 16:55:19 -0400

Changed in powernap (Ubuntu Natty):
status: Fix Committed → Fix Released
Martin Pitt (pitti)
Changed in eucalyptus (Ubuntu Natty):
milestone: ubuntu-11.04-beta-1 → ubuntu-11.04-beta-2
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Marking this as Fix released, as Eucalyptus is now shipping a config file for PowerNap which will ensure that they all work together correctly per recent PowerNap changes.

Changed in eucalyptus (Ubuntu Natty):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.