Feature roadmap/Image customization: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
|Name=Image customization |
|Name=Image customization |
||
|Feature subcategory=Security, activation and deployability |
|Feature subcategory=Security, activation and deployability |
||
|Requesters=Uruguay, Ethiopia, Colombia,Peru, Mexico |
|Requesters=Uruguay, Ethiopia, Colombia,Peru, Mexico |
||
|Requirements= |
|Requirements= |
||
For Colombia details, see: http://lists.laptop.org/pipermail/devel/2008-July/017299.html |
|||
When imaging a new laptop or upgrading a laptop we must allow the deployment to create a custom image. This special image will allow XOs to be re-imaged via USB or over a network (via olpc-update to internet, via olpc-update to XS, via Quicker Imaging feature above). The customized image must allow configuration of the following items. These should be settable when creating a new image or when upgrading unless otherwise noted. |
When imaging a new laptop or upgrading a laptop we must allow the deployment to create a custom image. This special image will allow XOs to be re-imaged via USB or over a network (via olpc-update to internet, via olpc-update to XS, via Quicker Imaging feature above). The customized image must allow configuration of the following items. These should be settable when creating a new image or when upgrading unless otherwise noted. |
||
The ideal solution would allow a deployments to load a source XO with the OS, add anything they want to it (e.g. RPMs, activities, other content, language packs, scripts, changed configuration files, etc.) then the "click a button" and output a signed image which is a full copy of that XO (need to document anything which does not get copied exactly, e.g. factory data, user name, other?). This signed image can then be installed via any of the available mechanisms. |
|||
Cuando haciendo un imagen nuevo para el XO o haciendo una actualizacion del Software debe permitir que el despliegue cree una imagen de encargo. Esta imagen especial permitiráue XOs sea puesto víel USB o sobre una red (víla olpc-update del Internet, víla olpc-update de un XS, o via Quicker Imaging definido arriba). La imagen modificada para requisitos particulares debe permitir la configuracióe los puntos siguientes. Étos deben ser configurable al crear una nueva imagen o al aumentar a menos que se indicare en forma diferente. |
Cuando haciendo un imagen nuevo para el XO o haciendo una actualizacion del Software debe permitir que el despliegue cree una imagen de encargo. Esta imagen especial permitiráue XOs sea puesto víel USB o sobre una red (víla olpc-update del Internet, víla olpc-update de un XS, o via Quicker Imaging definido arriba). La imagen modificada para requisitos particulares debe permitir la configuracióe los puntos siguientes. Étos deben ser configurable al crear una nueva imagen o al aumentar a menos que se indicare en forma diferente. |
Revision as of 19:22, 15 December 2008
Feature subcategory | Is part of::Category:Security, activation and deployability | |
Requesters | {{#arraymap:Uruguay, Ethiopia, Colombia,Peru, Mexico|,|x|Requested by::x}} | |
Requirements | For Colombia details, see: http://lists.laptop.org/pipermail/devel/2008-July/017299.html
When imaging a new laptop or upgrading a laptop we must allow the deployment to create a custom image. This special image will allow XOs to be re-imaged via USB or over a network (via olpc-update to internet, via olpc-update to XS, via Quicker Imaging feature above). The customized image must allow configuration of the following items. These should be settable when creating a new image or when upgrading unless otherwise noted. The ideal solution would allow a deployments to load a source XO with the OS, add anything they want to it (e.g. RPMs, activities, other content, language packs, scripts, changed configuration files, etc.) then the "click a button" and output a signed image which is a full copy of that XO (need to document anything which does not get copied exactly, e.g. factory data, user name, other?). This signed image can then be installed via any of the available mechanisms. Cuando haciendo un imagen nuevo para el XO o haciendo una actualizacion del Software debe permitir que el despliegue cree una imagen de encargo. Esta imagen especial permitiráue XOs sea puesto víel USB o sobre una red (víla olpc-update del Internet, víla olpc-update de un XS, o via Quicker Imaging definido arriba). La imagen modificada para requisitos particulares debe permitir la configuracióe los puntos siguientes. Étos deben ser configurable al crear una nueva imagen o al aumentar a menos que se indicare en forma diferente.
See also:
The following two points need redefinition and clarification:
| |
Specification | * http://lists.laptop.org/pipermail/devel/2008-March/011553.html | |
Owners | {{#arraymap:|,|x|Contact person::User:x}} Please indicate developers or champions supporting this request | |
Priority | Priority::1 | |
Helps deployability? | Helps deployability::yes | |
Target for 9.1? | Target for 9.1::yes |