Works for Kevin Harris (Configuration Management Director), who reports to Ed Wallen (VP in their PTO, Product Technology Organization) -- have known Ed for years. Frank Policastro re-connected us to him as Frank and Ed's kids run in the same circles and they belong to the same club, etc. Meeting with Kevin in Fairfax this PM to get better insight about the project, budgets, etc., but the existing description should be ample to post to get started for today. Two developers @ 6 months each with option to extend:
Required Skills for Puppet developers:
• Hands-on experience with each of:
o Open Source Puppet 3 and 5, know how they differ;
o authoring new Puppet modules for proprietary products; and
o Hiera data in YAML files, knowing how the three configuration tiers interact during lookups, and when to change the hiera.yaml file.
• Demonstrable experience with each of these technical aspects of Puppet:
o Custom Types;
o Custom Facts;
o Exported Resources; and
o Coding for heterogeneous environments (Windows and Linux).
• Know when to use Puppet Forge modules instead of rewriting them.
• Some experience or familiarity with strictly standards-compliant RPM and MSI building.
Git workflow, Jenkins and Nexus experience
Strong RPM development and package building background
Strong MSI development and package building background
Strong Linux OS system and admin level related background
Strong background with Windows Server OS admin functions including Windows registry
Strong PowerShell and Bash shell scripting
Nice to Haves:
JBoss and MSSQL Server background
OpenStack knowledge and HOT/Heat template design