Fedora Websites Release SOP

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Update with F13 instructions.)
(redirect page to new infra-docs)
 
(22 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{header|websites}}
 
{{header|websites}}
 +
This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: http://infrastructure.fedoraproject.org/infra/docs/fedorawebsites.txt
  
== Preparing the website for a release ==
+
For changes, questions or comments, please contact anyone in the Fedora Infrastructure team.
  
=== Update gpg key ===
 
  
As the release approaches, watch the <code>fedora-release</code> package for a
 
new key to be added.  Use the <code>update-gpg-keys</code> script in the
 
fedora-web git repository to add it to <code>static/</code>.  Manually add it
 
to <code>/keys</code> and <code>/verify</code>.
 
 
=== Branch master for stable release in fedora-web git repository ===
 
 
{{admon/note |  Perhaps this should be done right after release?}}
 
 
<pre>git branch f12 master && git push origin f12</pre>
 
 
=== Unfreeze website ===
 
 
Comment out the git checkout line in
 
<code>modules/fedora-web/files/syncStatic.sh</code> on <code>puppet1</code>.
 
 
=== Prepare puppet commits ===
 
 
Prior to release day, prepare puppet commits to move the fedora-web branch to
 
the release (alpha, beta, final, whatever) and, edit
 
<code>redirects.conf</code> (in <code>modules/fedora-web/files</code> on
 
<code>puppet1</code>) to do the right thing with <code>/get-prerelease</code>
 
requests.
 
 
=== Fire in the hole ===
 
 
After 9:15 AM EDT release day, push the puppet changes (e.g.: <code>cd ~/puppet
 
&& git push</code>).  This timing ensures that the cron jobs will not
 
automatically push the new website before 10:00 AM.  Then, on
 
<code>puppet1</code> run:
 
 
<pre>
 
# Ensure you have the puppet repo checked out to ~/puppet and up to date
 
cd ~/puppet && make HOSTS="bapp1 proxy1 proxy2 proxy3 proxy4 proxy5 proxy6 proxy7" push
 
</pre>
 
 
On bapp1, run:
 
<pre>
 
# Once /usr/local/bin/syncStatic on bapp1 is updated with your changes, run
 
sudo -u apache /usr/local/bin/syncStatic
 
</pre>
 
 
This takes about 15 minutes, so try to do this well before you need to push the
 
final site out.
 
 
Finally, when releng gives the OK, run the following on the proxies to make the
 
site live:
 
 
<pre>
 
# To sync the changes out, you can use func from puppet1 if you have sudo on puppet1.
 
# Otherwise, SSH to the proxies and call the below command.
 
sudo /usr/bin/rsync -a --no-owner --no-group bapp01::fedoraproject.org/* /srv/web/fedoraproject.org/
 
</pre>
 
 
== Fedora 12 Notes ==
 
(Still needs to be wikified)
 
 
 
<pre>
 
 
The times below are based on the timing of the website build and sync cronjobs.
 
It'd be a good idea to double check those in advance.
 
 
Unfreeze website (modules/fedora-web/files/syncStatic.sh), push after 9:05 AM EDT.
 
 
Run sudo /usr/local/bin/syncStatic on bapp1 after 9:45 AM EDT, make sure this
 
succeeds by checking /srv/web/fedoraproject.org.
 
 
Release:
 
 
Push commit to redirect get-prerelease to get-fedora.  If you have sudo on puppet1, run:
 
 
$ sudo func proxy\* call command run "/usr/bin/rsync -a --no-owner --no-group bapp1.vpn.fedoraproject.org::fedoraproject.org/* /srv/web/fedoraproject.org/"
 
 
Otherwise, manually run this on each proxy server:
 
 
$ sudo /usr/bin/rsync -a --no-owner --no-group bapp1.vpn.fedoraproject.org::fedoraproject.org/* /srv/web/fedoraproject.org/
 
 
If necessary, clear proxy caches using
 
 
$ rm -rf /srv/cache/mod_cache/*
 
 
After the site is out, do link checking and push any last-minute fixes/changes
 
by committing to the git repo, running syncStatic, and syncing to the proxies
 
as above.
 
 
Update the static banner on start.fedoraproject.org.  The procedure is the
 
same as with fedoraproject.org, except that the command to run on the
 
proxies is
 
 
$ sudo /usr/bin/rsync -a --no-owner --no-group bapp1.vpn.fedoraproject.org::start.fedoraproject.org/* /srv/web/start.fedoraproject.org/
 
 
Unfinished notes
 
 
* add release banner countdown
 
* add new release checksum files
 
* add gpg keys
 
 
Watch the webmaster@ moderator queue for reports of website issues.
 
 
update start.fp.o banner image
 
</pre>
 
 
[[Category:Websites]]
 
 
[[Category:Infrastructure SOPs]]
 
[[Category:Infrastructure SOPs]]

Latest revision as of 18:08, 19 December 2011

Artwork DesignService fedorawebsitesbanner 3.png

This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: http://infrastructure.fedoraproject.org/infra/docs/fedorawebsites.txt

For changes, questions or comments, please contact anyone in the Fedora Infrastructure team.