XS Community Edition/Features/port-to-ansible: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Created page with '<noinclude> Category:Feature Page Incomplete . <!-- You can add categories to tie features back to real deployments/schools requesting them, for example …')
 
Line 19: Line 19:


== Current status ==
== Current status ==
* Targeted release: 0.4.5
* Targeted release: 0.5
* Last updated: 5 October 2013
* Last updated: 5 October 2013
* Percentage of completion: 60%
* Percentage of completion: 60%

Revision as of 20:49, 21 October 2013



Summary

Porting XSCE services and modules to ansible

Owner

  • Name: Anish, Miguel, Santi Your Name
  • Email: anish@activitycentral.com

Current status

  • Targeted release: 0.5
  • Last updated: 5 October 2013
  • Percentage of completion: 60%

Detailed Description

Add detailed description and justification for porting to ansible.

Benefit to XSCE

Add detailed description and justification for porting to ansible.

Scope

Description of the effort involved.

UI Design

N.A.

How To Test

Testing notes go here

User Experience

N.A.

Dependencies

PyYAML
python-paramiko
python-jinja2

Contingency Plan

Stick to the old setup

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.

Comments and Discussion