< Cloud
(Created page with "= Runbooks and SOPs for Atomic = Let's keep docs on how Atomic images are generated, updated, etc. here for future Cloud WG members.") |
(Add some initial documentation based on answers from this week's #atomic meeting) |
||
| Line 1: | Line 1: | ||
= Runbooks and SOPs for Atomic = | = Runbooks and SOPs for Atomic = | ||
This page documents how Atomic images are generated, updated, etc. to provide a better understanding for Cloud WG members. This is a work in progress, as many changes discussed below are noted as not having been implemented yet. | |||
== Educate yourself == | |||
* Know what [http://www.projectatomic.io/ Project Atomic] is and [https://fedoraproject.org/wiki/Changes/Atomic_Cloud_Image what the Fedora Project is doing with it] | |||
* Know what a [http://en.wikipedia.org/wiki/Metalink metalink] is | |||
* Learn about [[MirrorManager]] and how the Fedora Project uses it | |||
== Compose script operations == | |||
Scripts that compose images need to be updated to generate the files required by Atomic. Releng scripts "buildbranched" and "buildrawhide" need to be updated with Atomic code, similar to "run-pungi". All of these scripts need to run `ostree summary -u` to generate ostree summary files for each compose. | |||
== MirrorManager operations == | |||
Normally, MirrorManager crawls directories looking for repositories. In that case, repositories are identified by their repomd.xml file. The info contained in that file is used to build the metalinks. However, for atomic images, we don't care about repomd.xml files. Future patches to MirrorManager will need to look for an ostree repo with a summary file instead. | |||
MirrorManager's "mirrorlist_server.py" file needs to be updated to generate a metalink to the summary file generated by the compose scripts. | |||
Revision as of 20:33, 2 October 2014
Runbooks and SOPs for Atomic
This page documents how Atomic images are generated, updated, etc. to provide a better understanding for Cloud WG members. This is a work in progress, as many changes discussed below are noted as not having been implemented yet.
Educate yourself
- Know what Project Atomic is and what the Fedora Project is doing with it
- Know what a metalink is
- Learn about MirrorManager and how the Fedora Project uses it
Compose script operations
Scripts that compose images need to be updated to generate the files required by Atomic. Releng scripts "buildbranched" and "buildrawhide" need to be updated with Atomic code, similar to "run-pungi". All of these scripts need to run ostree summary -u to generate ostree summary files for each compose.
MirrorManager operations
Normally, MirrorManager crawls directories looking for repositories. In that case, repositories are identified by their repomd.xml file. The info contained in that file is used to build the metalinks. However, for atomic images, we don't care about repomd.xml files. Future patches to MirrorManager will need to look for an ostree repo with a summary file instead.
MirrorManager's "mirrorlist_server.py" file needs to be updated to generate a metalink to the summary file generated by the compose scripts.