Archiv:Devops Meetup

aus Metalab Wiki, dem offenen Zentrum für meta-disziplinäre Magier und technisch-kreative Enthusiasten.
(Weitergeleitet von Devops Meetup)
Zur Navigation springenZur Suche springen

Devops Meetup
Status: active
Thema: closing the gap between software development and operations
Gestartet: 2010
Organisator: Michael Renner japhy Hannes Schaller
Zuletzt aktualisiert: 2016-10-19


A regular meetup of people interested in DevOps.

DevOps is kind of a new sysadmin buzzword for ways to close the gap between software development and operations; it's what happens when agile development spreads to the server room. We meet to discuss culture, processes, tools and trends that contribute to this field.

DevOps — slides from introductory lightning talk at Metaday #36

There is a mailing list for announcements and discussions, and an experimental page.

Next meetup

Tue., 2013-03-18, 19:00, Metalab Library


  • Chef for Puppeteers - japhy
  • DevopsDays London Recap - japhy

Presentation/topic propositions for future

If you have something to present, discuss, show, or ask around about, but don't want to commit to a date yet – here's the place to do it. If you want to hear about something specific, add it here too - maybe there's someone here who can tell about it.

  1. A comparative analysis of Linux HA Solutions by Bernhard Miklautz
  2. Monitoring with Icinga (or other Stuff That Is Not Nagios)


A list of all users for quick reference

  • ... you? :>



  • Automated installation & configuration
    • Opscode Chef Ruby-based automated system configuration
    • Puppet Another Ruby-based automated system configuration
    • Fai Fully Automated Installer
    • Cobbler Rapid deployment system, script/pluggable infrastructure, python-based
    • The Foreman Provisioning and external Node classification for Puppet
  • Cloud
  • Deployment and control
    • Capistrano Remote multi-server automation tool (deployment)
    • MCollective Framework to build server orchestration or parallel job execution systems
    • Vertebra [1] Another job execution system, XMPP-based
    • ControlTier cross-platform build and deployment automation framework (job automation / infrastructure orchestration)
  • Continuous Integration & Testing
    • Hudson Continuous Integration server
    • Buildbot Another Continuous Integration server
    • Selenium Web application testing system
    • Cucumber Behaviour Driven Development testing tool
  • Documenting infrastructure
    • OCS-ng Inventory system + GLPI Asset Management
    • Ohai Detecting information (facts) about system
    • Facter Detecting information (facts) about system
    • puppet + facter + puppet-dashboard
    • SICE Kit A set of tools and templates designed for MediaWiki to aid people who maintain systems and infrastructure
  • Interpreter "sandboxes"
  • Misc
    • Grml Debian-based live CD
    • Mongrel2, a language-agnostic Web server
    • Augeas, a parsing config file editor
    • IT Cockpit, a user-friendly UI for configuring Nagios
    • fail2ban, banning malicious hosts based on log-file entries



  • A bit about Foreman
  • A bit about Postgres 9.2


  • Odin Authenticator - a cookie-based single sign-on system for Apache - japhy
  • A short potpourri of tools which proved useful when working in a large & rather homogenous infrastructure. Will include war-stories. pssh, graylog2, puppet & facter, lldpd, pt-query-diag, etc. - Robe


  • From OpenVZ to LXC - Michael Renner and Stefan Schlesinger



  • Continuous Integration Packaging with FPM -- japhy

FPM is a command-line tool that converts between different package formats (from: local directory, ruby gem, php pear, python module, node.js npm package, deb, rpm; to: local directory, deb, rpm, solaris, tar). The "local directory" pseudo-format allows for easy creation of quick-and-dirty packages that Just Work, short-circuiting all the layers from the Debian Policy Manual all the way up to dh_make with one quick script call. FPM doesn't care about actually building your stuff (as in: unpacking, configuring, compiling, etc). It just takes directory you put it into, and turns it into a package. To prepare the compiled files and put them in the right place first is your job. So is specifying the dependencies - there are no automatic dependencies on dynamically linked libraries.

Workflow for the continuous integration using bits & pieces from the gist:

    • On developer's workstation, "vagrant up" command brings up new VirtualBox VM with clean Debian and sets up a clone of the "packages" repository with a local branch
    • "vagrant ssh" to the VM, go to the packages repo, prepare or modify new package, test it
    • "git push" from the VM to the "develop" branch on the host server
    • "git pull . develop" on the host server's master branch to merge
    • "git push" to central git repo
    • buildbot (continuous integration server) picks up the commit
    • buildbot builds changed package and adds it to the apt repo
    • new package is available to clients via apt-get within minutes from the push.



  • ?


  1. Velocity EU recap by Michael


  1. Tier1 Hardware (Dell, HP, IBM) show & tell Michael
    • We're going to look at a Dell R200, HP DL380G5 as well as a IBM x3650 M3 and see how they fare in regards of hardware maintenance, configuration, out of band management and general pain points.
  2. What hardware should I get anyways? General thoughts on performance evaluation, capacity planning, daily operations and other pitfalls.


  1. git-flow, a successful branching model – japhy
  2. Bullshit Bingo: Cloud strategies (how to make cloud work for you) - japhy
  3. Monitoring systems, capacity planning, trending, etc. discussion


  1. NexentaCore 3 ZFS Presentation & Workshop - David Gabriel

clickme: Presentation


  1. What's new in Perl 5.14? (Daxim)
  2. Opscode-hosted Chef stuff demo: cookbook repository, platform, … (japhy)


  1. Kanban in operations by Tony (Datei:Kanban and Devops.pdf)
  2. 5 Years Metalab discussion


  1. Cloud - is it good for anything? (japhy) slides


  1. Time management - basic ideas – japhy (based on the Time Management for System Administrators book)
  2. The Foreman - cyberkov, Provisioning and external Node classification for Puppet (Presentation from FOSDEM)


  1. Mongrel2 introduction by Lukas Fittl
  2. Grml fly-by by Christian Hofstädtler (slides)
  3. Plat_forms - The web development platform comparison


  • A 10 minute PostgreSQL crash course including Q&A for operations-relevant Stuff - Michael
  • A hopefully short and functional live presentation of my company's infrastructure User:b2c
    • Overview: puppet+dashboard, vmware, storage
    • live server deployment
    • automated tests
  • Free talk, show&tell, …

2010-11-23 Bootstrap meeting