Two Week Atomic Host Release


Every two weeks there is a new release of the Fedora Atomic Host deliverable from Fedora. This item was originally lead by the Fedora Cloud SIG and proprosed as a Fedora Change. The goal is to deliver Fedora Atomic Host at a more rapid release cycle than that of the rest of Fedora, allowing for the Atomic Host to be iterated as a released artifact through out a stable Fedora Release life cycle.


There is a script in the Fedora Releng repo named under the scripts/ directory.

This script must be run from the bodhi backend host, at the time of this writing that host is


The user that runs this must also have permissions in sigul to sign using the specified key.

Running the script requires two arguements:

  • The Fedora Release number that you are going to release, example: -r 23
  • The Fedora key to sign the checksum metadata files with, example: -k fedora-23


Before running this script, make sure that the previous compose was successful by verifying that the Cloud-Images/x86_64/Images/ directory is populated under the compose directory:

This should not always be necessary, but while the compose work is being iterated on it’s recommended.

The below example shows how to perform the Two Week Atomic Release.

localhost$ ssh

# If you do not already have the releng repo cloned, do so
bodhi-backend01$ git clone ~/releng

# If you do have the releng repo already cloned, make sure to pull the
# latest
bodhi-backend01$ cd ~/releng
bodhi-backend01$ git pull

# Perform the two week release
bodhi-backend01$ cd ~/releng/scripts
bodhi-backend01$ ./ -r 23 -k fedora-23


In order to verify this change has taken place, you should see emails on the various mailing lists that are defined in the list ATOMIC_EMAIL_RECIPIENTS in the script. At the time of this writing, those are:


This can also be verified by checking that the appropriate fedmsg messages were sent and recently received by Datagrepper in this datagrepper query.

One final item to check is that the actual compose artifacts have made their way into the appropriate stable directories.