Profile

Cover photo
Martin Alfke
303 followers|69,728 views
AboutPostsPhotosReviews

Stream

Martin Alfke

Shared publicly  - 
2
Giacomo Vacca's profile photo
 
Good luck. I saw your talk at Puppet Camp in London in Nov 2014 and it was very interesting and informative.
Add a comment...

Martin Alfke

Shared publicly  - 
 
Puppet Enterprise 3.8 Installation - steps and fixes
The new Puppet Enterprise Version 3.8 is out since a couple of days. It now supports Puppet 4 officially. On mailinglist people were telling about installation issues. This is a summary with fixes for SLES 11 and 12, CentOS 6 and 7, Ubuntu 12.04 and 14.10, ...
2
Add a comment...

Martin Alfke

Shared publicly  - 
 
 
The Openstack DACH Day is the community event of the Openstack association in Germany, Austria and Switzerland.
For the last two years this has been a track of the Linuxtag Berlin. This year it will be an independent event for the first time.
 ·  Translate
OpenStack DACH Day 2015
Thu, June 11, 4:00 AM
Urania Berlin, An der Urania 17, 10787 Berlin

1 comment on original post
1
Add a comment...

Martin Alfke

Shared publicly  - 
 
 
Der Ticketverkauf hat begonnen!

Tickets für den OpenStack DACH Tag 2015 sind nun im freien Verkauf!

Wer mehr über OpenStack erfahren möchte, hat dazu am Donnerstag den 11. Juni in der Urania in Berlin die Möglichkeit.

Es wird viele Vorträge und Workshops geben, von der OpenStack Foundation, HP, SUSE, B1 Systems, TeutoNet und vielen anderen Unternehmen und Spezialisten, die im OpenStack-Umfeld aktiv sind!
 ·  Translate
View original post
1
1
Marcel Wolf's profile photo
Add a comment...

Martin Alfke

Shared publicly  - 
 
 
Call for Papers - Dritter Openstack DACH Tag 2015

Der Openstack DACH Tag ist das Comminity Event der Openstack Organisation. Er hat die letzten beiden Jahre als Track auf dem Linuxtag stattgefunden und wird dieses Jahr das erste Mal als eigenständiges Event stattfinden - in der Urania in Berlin, am Donnerstag, dem 11. Juni 2015.

Du hast Themen für einen Vortrag oder einen Workshop in Englischer oder Deutscher Sprache? Hier kannst Du einreichen!
 ·  Translate
2 comments on original post
1
Add a comment...

Martin Alfke

Shared publicly  - 
 
Rathaus Lichtenberg
7
Add a comment...
Have them in circles
303 people
Markus Reinhard (coxorange)'s profile photo
Suk-Hyon Paek's profile photo
Marijana Prusina's profile photo
Jürgen Dr. Gräbel's profile photo
Stephan Polster's profile photo
Passi B.'s profile photo
Elisa Schmücke's profile photo
Michael G. Thies's profile photo
Walter Heck's profile photo

Martin Alfke

Shared publicly  - 
 
 
Das Programm steht, spannende Themen warten, z.B. systemd, Kernel Live-Patching, Samba4, Docker, btrfs, iSCSI-Anbindung eines Ceph Object Store, MySQL, DANE, OpenLDAP, Check_MK, Puppet4, IPv6 in der Praxis, Loganalyse mit Centralstation ... u.v.a.m.
 ·  Translate
View original post
1
Add a comment...

Martin Alfke

Shared publicly  - 
 
Puppet Enterprise on SLES
SLES and OpenSuSE are supported operatingsystems by Puppet. But I always saw trouble when installing either the Puppet Master or the Agent on SLES. One needs to take care on locales, paranoid umask, required packages. 1. locale Standard SLES installation wi...
2
Add a comment...

Martin Alfke

Shared publicly  - 
 
 
Der Openstack DACH Day 2015 findet im Juni in der Berliner Urania statt. Weil es in diesem Jahr keinen Linux-Tag gibt, haben die Organisatoren dafür einen eigenen Verein gegründet.
View original post
2
Add a comment...

Martin Alfke

Shared publicly  - 
 
SLAC 2015 - call for papers läuft.
23.-25. Juni 2015
Golden Tulip Hotel
 ·  Translate
1
Add a comment...

Martin Alfke

Shared publicly  - 
 
 
Maslow's hierarchy of SRE needs

In the course of talking to other tech companies about what they consider the scope of their SRE/DevOps roles, I've realized that the scope of SRE organizations differs substantially across the industry. Many SRE organizations are limiting their potential by hiring teams to do only the work that keeps the service(s) they are responsible for running but not the work that substantially improves the service(s). It feels like their teams are stuck due to being too overwhelmed with the basics to get out of the rut and do more meaningful work.

What I'm dubbing 'Maslow's hierarchy of SRE needs' categorizes the state of a team into the following buckets:
+ physiological health - is the service functioning at all (e.g. not repeatedly hard-down/bleeding revenue)? is the pager quiet enough to get any other work done? are we learning from outages and resolving postmortem action items to avoid repeating the same outages?
+ maintain homeostasis - is it possible to carry out day to day operations (e.g. push code, tolerate machine failures) without excessive manual work? are people automating away manual work?
+ boundaries & objectives - do we have clear scopes for what we're responsible for (e.g. better to be responsible for one thing solidly than many things diffusely), and an agreed-upon SLA/standard that we aspire to achieve?
+ self-awareness - do we know when we deviate from the standards based on metrics so we can take corrective action? conversely, this also means we can ignore noise that isn't tied to these metrics because our monitoring about the things we care about is solid.
+ self-actualization - freedom in time, trust, and ability dimensions to make substantial design improvements to the service (and measure the improvements!)

You don't get to the later stages of the hierarchy of needs without hiring both systems engineers and software engineers - SRE only works at its best if you have people with both skillsets collaborating. If all you're doing is giving people from pure sysadmin backgrounds a shiny devops title and no other support, you're not going to see results that are meaningfully different from the pure operational model of sysadmin work. If you struggle to name the exceptionally strong coders on your team, you're going to have a lot of trouble with the last step of actually getting core service-level improvements delivered (e.g. improving the service components themselves, instead of just rearranging their relationships). If you don't have a solid product dev-SRE relationship with clear boundaries, it's far too easy to slip into the trap of having all the operational work pushed onto SRE without effort put into reducing the total operational burden.

It's fairly easy to spot a well-functioning organization -- if it's primarily doing work in the self-actualization category, everything less complex in the hierarchy is likely to be shipshape. If an organization is stuck earlier in the hierarchy, it requires a great deal of support in order to reach a fulfilled and functional state. The support required takes many forms - upper management support for principled "no"s and enforcing good boundaries with product dev, hiring to ensure the correct breadth and depth of skillsets is present on the team, and vision from the team itself to push towards more sophisticated work rather than becoming comfortable just doing operations.

What can you do as the leadership of an engineering organization if you're looking to make sure your SRE team grows to its full potential? First, hire people who are excited about the scaling/performance/reliability challenges that your product development generalists lack expertise in, not just people to do the grungy work you don't want to be doing. Second, make SRE's goal to change the service based on experience running it, rather than just keeping it running. Third, make sure a majority of your SRE team's time is actually developing projects and learning new things. Finally, empower your SRE team to take full ownership of the service, including backing their ability to say no to product development.

If you don't do these things, you'll have trouble attracting new talent[1], and your best site reliability engineers will eventually become bored and leave for where they can enjoy self-actualization.


[1] For a potential external hire that wants to be doing work towards the latter steps in the hierarchy, it's a rather risky proposition to join a team that is currently stuck. Visibility into the root causes of the stuckness is often opaque from outside the organization, and whether there will be organizational support for making the necessary changes is also hard to assess from the outside. There's always a great feeling of accomplishment from being empowered to fix a situation and doing so, but it's best to avoid the situations where one is set up to fail from the beginning.
7 comments on original post
1
Add a comment...

Martin Alfke

Shared publicly  - 
1
Add a comment...
People
Have them in circles
303 people
Markus Reinhard (coxorange)'s profile photo
Suk-Hyon Paek's profile photo
Marijana Prusina's profile photo
Jürgen Dr. Gräbel's profile photo
Stephan Polster's profile photo
Passi B.'s profile photo
Elisa Schmücke's profile photo
Michael G. Thies's profile photo
Walter Heck's profile photo
Links
Contributor to
Work
Skills
Linux, Puppet, HA
awesome! ask for the steak with blue chesse - it is no longer on the menu but fantastic. very friendly family owned restaurant.
Public - 4 months ago
reviewed 4 months ago
nice conference location.
Public - 4 months ago
reviewed 4 months ago
friendly staff, fine food. a little expensive
Public - 4 months ago
reviewed 4 months ago
Ruhig gelegen. Nettes Café.
Public - 7 months ago
reviewed 7 months ago
53 reviews
Map
Map
Map
awesome hotel. rooms have been reworked lately. very friendly and helpfull staff - they also prepare food which is not on the menu. great nearby area.
Public - 4 months ago
reviewed 4 months ago
Awesome place to learn OpenSource related stuff.
Public - 7 months ago
reviewed 7 months ago
Tasty food, friendly staff.
Public - 9 months ago
reviewed 9 months ago