Perl Ops Track

Perl Ops

The Perl Ops track contains topics relevant to System Administrators. Perl has been used for systems administration since the 1980s, bringing the light of automation to the sometimes-dark corners of computing infrastructure environments. Perl is the language of choice for many systems administration tasks. And, with all the new challenges of running modern software services, it’s time to revisit how Perl makes Ops better.

Examples of Perl Ops topics might include:

  • Automated OS Deployment/Provisioning
  • Automated Application Deployment
  • Reproducibility of systems/services
  • Configuration Management, including any of: staged release, version control, bug tracking & unit testing of configurations
  • Scalability, High Availability and recovery/coping with failure
  • Event Monitoring
  • Usage Monitoring
  • Log processing/analysis
  • Correctness checking/Service validation
  • Security from the beginning, Authentication/Authorization
  • Programming to the specific OS
  • Virtualization and/or Issues in Cloud Environments
  • Backup and Disaster Recovery
  • Basics of network service/server security from a systems or apps perspective

Perl Ops talks seek to provide a mixture of 'Why?' talks that promote/provide reasons why the recommendations are useful (and in what circumstances they are/aren't applicable) and 'What/How?' talks that show participants things that might be new to them.

Featured Speaker: Tom Limoncelli

Tom is an internationally recognized author, speaker, and system administrator. His best known books include Time Management for System Administrators (O'Reilly) and The Practice of System and Network Administration (Addison-Wesley). In 2005 he received the SAGE Outstanding Achievement Award. He works at Google in NYC on the Ganeti project. is his blog.

This year, Tom will be providing one of our keynote talks:

What Perl sysadmins wish Perl developers knew, and vice-versa ($a,$b) = ($b,$a)

Sysadmin teams and a software development teams have been known to work closely together, not at all, or somewhere in between. What happens when the barrier between such groups disappears and the two teams become one? The recent trend has been to incorporate "shared responsibility" for operational matters such as deployment, scalability and performance. As a result projects are more successful in ways one wouldn't have expected.

Copyright © 2006-2011 Pittsburgh Perl Mongers. Mast photo by whobee@flickr.