XS Community Edition/Features/power management: Difference between revisions
(Created the page) |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{xsce}} |
|||
<noinclude> |
<noinclude> |
||
[[Category:Feature Page Incomplete]] |
[[Category:Feature Page Incomplete]] |
||
| Line 12: | Line 13: | ||
== Summary == |
== Summary == |
||
Optimize power management on the server to minimize power consumption. |
|||
Administration and Management GUI |
|||
== Owner == |
== Owner == |
||
* Name: Jon Nettleton |
|||
''This should link to your home wiki page so we know who you are'' |
|||
* Email: [mailto:jon.nettleton@gmail.com jon.nettleton@gmail.com] |
|||
* Name: Miguel González Álvarez |
|||
* Email: migonzalvar@activitycentral.com |
|||
== Current status == |
== Current status == |
||
* Targeted release: 0. |
* Targeted release: >= 0.6 |
||
* Last updated: October 21, 2013 |
* Last updated: October 21, 2013 |
||
* Percentage of completion: |
* Percentage of completion: 0% |
||
== Detailed Description == |
== Detailed Description == |
||
A UI for administering the school server has been a big requirement over the years. This feature implements the UI using a service called Ajenti. |
|||
First, data need to be collected to determine whether implementing power optimizations is worthwhile. |
|||
Next, these are some of the optimizations to investigate |
|||
* wake on lan |
|||
* spin down hard disk when not being used (with sd/ssd being used as a cache) |
|||
* schedule the server to go to sleep at certain times of day |
|||
These are ideas we have brainstormed and this list is not definitive. Feel free to add more. |
|||
== Benefit to XSCE == |
== Benefit to XSCE == |
||
Ajenti enables the control of various aspects of the school server through a user interface. It also enables the creation of a framework through which services can be added scalably (Ajenti is written in python and is quite actively developed and maintained) |
|||
== Scope == |
== Scope == |
||
The codebase needs to be moved from the dextrose server (https://github.com/activitycentral/dxs) to the XSCE. The playbooks already exist so it should just be a matter of porting and testing. |
|||
See the Ajenti folder: |
|||
https://github.com/activitycentral/dxs/tree/master/roles/ajenti |
|||
==UI Design== |
==UI Design== |
||
See screenshots here: |
|||
http://ajenti.org/ |
|||
== How To Test == |
== How To Test == |
||
Latest revision as of 15:07, 3 November 2013
This IIAB XSCE content does not reflect the opinion of OLPC. These pages were created by members of a volunteer community supporting OLPC and deployments.
Summary
Optimize power management on the server to minimize power consumption.
Owner
- Name: Jon Nettleton
- Email: jon.nettleton@gmail.com
Current status
- Targeted release: >= 0.6
- Last updated: October 21, 2013
- Percentage of completion: 0%
Detailed Description
First, data need to be collected to determine whether implementing power optimizations is worthwhile.
Next, these are some of the optimizations to investigate
- wake on lan
- spin down hard disk when not being used (with sd/ssd being used as a cache)
- schedule the server to go to sleep at certain times of day
These are ideas we have brainstormed and this list is not definitive. Feel free to add more.
Benefit to XSCE
Scope
UI Design
How To Test
Testing notes go here
User Experience
If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.
Dependencies
What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
Contingency Plan
If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.
Documentation
Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
Release Notes
The XSCE Release Notes inform end-users about what is new in the release. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.