Composing Fedora: Difference between revisions

Latest revision as of 17:51, 3 November 2015

This page is deprecated
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository

Description

When Quality Engineering requests a TC or RC they do so by filing or reopening a ticket in Release Engineering trac. There is one trac ticket per milestone.

Action

create the full product tree.

Composing the Tree

1) Log into a compose system: compose-x86-01 or arm01-releng00.arm.fedoraproject.org

$ ssh -A compose-x86-01.phx2.fedoraproject.org

ssh agent forwarding is needed to enable sshing to boxes for composing the different arch trees.

2) update or checkout the git repo

$ cd releng/
$ git pull --rebase

or

$ git clone https://git.fedorahosted.org/git/releng

3) Sign rpms for bleed repo

ssh releng04.phx2.fedoraproject.org

repeat step 2 on signing box.

$ cd releng/scripts
$ NSS_HASH_ALG_SUPPORT=+MD5 ./sigulsign_unsigned.py fedora-22 -v --write-all <build nvrs>

4) update the bleed repo on compose-x86-01:

$ ~/releng/scripts/makebleed <build nvrs>

5) kick off compose on a compose system: compose-x86-01 or arm03-releng00.arm.fedoraproject.org

for a TC

$ cd ~/releng/scripts
$ ./run-pungi 22_Beta_TC9 "" 20150409

for a RC

$ cd ~/releng/scripts
$ ./run-pungi 22_Beta _RC2 20150413

6) check the compose

check the tree under /mnt/fedora_koji/compose/<Compose>/<Release>/ for completeness

7) open up the tree:

sg releng "chmod 755 /pub/alt/stage/<Compose>/"

8) Close the ticket: Copy the ooutput pasted at teh end of run-pungi and paste into the ticket and close it.

Update the ticket

The ticket should be closed when the compose has been opened up pasting in the output from run-pungi

Verification

Verification can be done as the task steps are being performed.

Image Creation

When pungi exits, you can verify that the development/<arch>/os/images/ directory exists and has content. That path is relative to the destination directory you provide pungi.

Updating the Ticket

One can click the link provided in the ticket update and ensure the path is correct. Verifying that the ticket is closed should be pretty self evident.

Consider Before Running

Many things can hinder a compose, broken deps in the chroot set, broken deps in the compose set, bugs in the compose software, etc... If any problem is ran into along the way, it is best to alert QA via a ticket update, and then work with the appropriate party to clear the obstruction.

Some of these tasks take a long time to finish, so it is highly recommended that you run these tasks in a screen session.

@@ Line 1: / Line 1: @@
+{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}}
 == Description ==
 When Quality Engineering requests a TC or RC they do so by filing or reopening a ticket in Release Engineering trac. There is one trac ticket per milestone.
@@ Line 6: / Line 8: @@
 === Composing the Tree ===
-) Log into compose system: <code>compose-x86-02</code>
+) Log into a compose system: <code>compose-x86-01</code> or <code>arm01-releng00.arm.fedoraproject.org</code>
 <pre>
-$ ssh -A compose-x86-02.phx2.fedoraproject.org
+$ ssh -A compose-x86-01.phx2.fedoraproject.org
 </pre>
 ssh agent forwarding is needed to enable sshing to boxes for composing the different arch trees.
@@ Line 19: / Line 21: @@
 or
 <pre>
-$ git clone git://git.fedorahosted.org/git/releng
+$ git clone https://git.fedorahosted.org/git/releng
 </pre>
@@ Line 29: / Line 31: @@
 <pre>
 $ cd releng/scripts
-$ NSS_HASH_ALG_SUPPORT=+MD5 ./sigulsign_unsigned.py fedora-20 -v --write-all <build nvrs>
+$ NSS_HASH_ALG_SUPPORT=+MD5 ./sigulsign_unsigned.py fedora-22 -v --write-all <build nvrs>
 </pre>
-) update the bleed repo on <code>compose-x86-02</code>
+) update the bleed repo on <code>compose-x86-01</code>:
 <pre>
-$ cd ~/bleed
 $ ~/releng/scripts/makebleed <build nvrs>
 </pre>
-) kick off image composition on <code>localhost</code>
+) kick off compose on a compose system: <code>compose-x86-01</code> or <code>arm03-releng00.arm.fedoraproject.org</code>
-locally checkout spin-kickstarts and cloud-kickstarts git repos
+for a TC
 <pre>
-$ git clone ssh://git.fedorahosted.org/git/spin-kickstarts.git
+$ cd ~/releng/scripts
-$ git clone ssh://git.fedorahosted.org/git/cloud-kickstarts.git
+$ ./run-pungi 22_Beta_TC9 "" 20150409
+</pre>
+for a RC
+<pre>
+$ cd ~/releng/scripts
+$ ./run-pungi 22_Beta _RC2 20150413
 </pre>
+) check the compose
+check the tree under /mnt/fedora_koji/compose/<Compose>/<Release>/ for completeness
+) open up the tree:
+<pre>
+sg releng "chmod 755 /pub/alt/stage/<Compose>/"
+</pre>
+) Close the ticket:
+Copy the ooutput pasted at teh end of run-pungi and paste into the ticket and close it.
 === Update the ticket ===
@@ Line 64: / Line 80: @@
 Some of these tasks take a long time to finish, so it is highly recommended that you run these tasks in a screen session.
-If you need to make use of freshly built packages since the last rawhide compose, you can create a local repository.  <code>/srv/pungi/bleed/<arch>/</code> on the compose system can be used as a temporary repo for new packages.  Don't forget to update the mock chroot with the new packages (if appropriate) and to add the temporary repo to the <code>spin-kickstarts/fedora-install-fedora.ks</code> file for use by pungi.
-Disk space on secondary1 is limited, so if you need to go through a number of composes before you get one that tests well, be sure to prune the failed composes.  This is true of disk space on the compose host too, be sure to trim /srv/pungi/ of composes that are no longer needed locally.
 [[Category:Release Engineering SOPs]]

Search