| 2019-11-18 13:05:26 |
Rafael David Tinoco |
description |
[ Package Description ]
PowerNap is meant to run on the system(s) hosting virtual machines.
When one of those systems goes un-utilized (ie, no virtual machines running), PowerNap notices this and moves the physical machine to a lower power state (like S3 suspend).
When the Cloud Controller receives some new requests that demand new virtual machines, it would first look for a running host that has sufficient capacity to service the request, thereby keeping the overall cloud in a "compressed" state.
However, if demand requires, the Cloud Controller would PowerWake one of the sleeping hosts, bringing it online and increasing the current capacity of the cloud, such that it could service the new request.
PowerNap operates sort of like a screen saver for servers. Besides watching the console and terminals for keyboard activity, it also watches the system's process table for activity.
An administrator defines a list of regular expressions describing some critical MONITORED_PROCESSES that should be running. When powernapd notices that all of the MONITORED_PROCESSES have been absent from the process table for some configurable ABSENT_SECONDS, powernapd emits a warning to all users of the system that it will run powernap, unless canceled within the next GRACE_SECONDS.
[ Reason ]
This package seems to have been done for a specific need in the past and, nowadays, could be replaced by different types of scripts depending of one sysadmin need. It seems that it is currently unmaintained as well (https://launchpad.net/powernap).
Reading how it works:
http://blog.dustinkirkland.com/2009/07/introducing-powernap.html
And seeing that it hasn't changed for quite some time, and was demoted from main to universe quite sometime ago, I really don't see a need for this package not to be dropped from Ubuntu at all, reducing our management efforts. |
Based on the following documentation:
https://wiki.ubuntu.com/ArchiveAdministration#Removals
As I don't have proper rights for archive administration, I'm opening a bug to document the need for dropping powernap from the archive. I hope this format is good enough and subscribing archive admins do the trick.
[ Package Description ]
PowerNap is meant to run on the system(s) hosting virtual machines.
When one of those systems goes un-utilized (ie, no virtual machines running), PowerNap notices this and moves the physical machine to a lower power state (like S3 suspend).
When the Cloud Controller receives some new requests that demand new virtual machines, it would first look for a running host that has sufficient capacity to service the request, thereby keeping the overall cloud in a "compressed" state.
However, if demand requires, the Cloud Controller would PowerWake one of the sleeping hosts, bringing it online and increasing the current capacity of the cloud, such that it could service the new request.
PowerNap operates sort of like a screen saver for servers. Besides watching the console and terminals for keyboard activity, it also watches the system's process table for activity.
An administrator defines a list of regular expressions describing some critical MONITORED_PROCESSES that should be running. When powernapd notices that all of the MONITORED_PROCESSES have been absent from the process table for some configurable ABSENT_SECONDS, powernapd emits a warning to all users of the system that it will run powernap, unless canceled within the next GRACE_SECONDS.
[ Reason ]
This package seems to have been done for a specific need in the past and, nowadays, could be replaced by different types of scripts depending of one sysadmin need. It seems that it is currently unmaintained as well (https://launchpad.net/powernap).
Reading how it works:
http://blog.dustinkirkland.com/2009/07/introducing-powernap.html
And seeing that it hasn't changed for quite some time, and was demoted from main to universe quite sometime ago, I really don't see a need for this package not to be dropped from Ubuntu at all, reducing our management efforts. |
|
