From Fedora Project Wiki

Revision as of 17:13, 29 June 2010 by Smooge (talk | contribs) (Instructions on how to edit puppet for staging servers)

Infrastructure InfrastructureTeamN1.png

We have the ability to create a staging environment in Infrastructure. This attempts to duplicate a small section of our infrastructure for testing purposes. If there's a large scale change that you need to perform, it's a good idea to push the changes to the staging environment first and check that everything works properly and that you have puppetized all the necessary changes before pushing the changes live.

Contact Information

Owner: Fedora Infrastructure Team

Contact: #fedora-admin

Persons: mmcgrath

Location: Phoenix

Servers: (proxy1.stg, db1.stg, app1.stg, app2.stg fas1.stg)

Purpose: Staging environment to test changes to apps.


When you're on a stg server, you won't have much access to non-stg servers. For example, if you're on proxy1.stg and you ping app1... there's a hosts entry to direct it to app1.stg so it should behave exactly as production does.


Staging servers are managed through puppet so that you can test config changes in puppet before pushing live. You need to use a different branch to push to the staging servers. Basic steps:

git clone /git/puppet/
git checkout --track -b staging origin/staging # This only needs to be run once on the initial clone
# make changes, git commits
git push
git checkout master # switch back to the master branch
git checkout staging # switch back to the staging branch
On staging, for files not in modules (ie stuff in configs/*), puppet will use what's in the master branch for those files (TODO: confirm this statement more completely).

Troubleshooting and Resolution