QA/Automation/Projects/Infrastructure/Puppet: Difference between revisions

QA/Automation/Projects/Infrastructure/Puppet (view source)

1,089 bytes added , 12 May 2014

canmove, Confirmed users, Bureaucrats and Sysops emeriti

4,747

edits

@@ Line 98: / Line 98: @@
 == Documentation ==
-* How [[ReleaseEngineering|Release Engineering]] at Mozilla is using Puppet: https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain
+As a general overview in how Release Engineering at Mozilla is handling Puppet, we suggest to read https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain.
+For our own Puppet instance we want to make sure to be able to setup the system, and install all necessary tools. The primary platforms we put focus on are Linux (Ubuntu) and OS X. Windows will follow later. So what we need is to setup networking including the proxy settings, VNC and SSH access, and other system preferences. Also the installation and configuration of Flash and Java has to be covered.
+Later with also Windows enabled via Puppet, we will have to take a look in how to setup a new node completely automated via Puppet. Most likely OS X will be the first platform, which will be covered for that.
+For any kind of modifications to Puppet modules, manifest, and files, the changes will land on the default branch of the https://hg.mozilla.org/qa/puppet repository. Once the changes have been tested and been approved they will land on the production branch, where puppet will pick those up and apply to existing machines during the next reboot. In case of testing for staging we will have to use an user environment with Puppet (see 'puppet -env').
 == References ==