Skip to main content

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this?

  1. DevOps Demystified with Ben Rockwood:
  2. DevOps at
Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible on Windows. (nevermind the fundamental error - I watched this one before 'Devops Demystified')

So here I am a year later and while we have made good progress, we are still working on communicating/teaching the ideals behind 'improve the flow' and 'continuous improvement', and all the areas in between that may need rethinking.

It came up that while it's great that I have spent all this time and learned a lot - how have I communicated it to the rest of the team?  Since hallway conversations (while profitable) have a pretty narrowly focused audience, it makes for spotty coverage of these new ideas.

Thus...the watching/listening list (I didn't include reading because so many can't be bothered, but watching/listening is pretty hard to say 'no can do').  (see the symptom in that last sentence?).

Currently my personal goal is to make the entirety of IT a normal 9-5 job (at least here at my current employer).  Gene Kim's vision at a local scale, if you will.

Excuse the wiki markup.

This page is a summary of the media I've consumed over the last year.  By putting it up here in some organized fashion, I am hoping that others will check some of it out and try something new.

=DevOps philosophy & culture=
* Keynote: Why We Need DevOps - Gene Kim:
* DevOps Demystified with Ben Rockwood:
* Continuous Delivery with Jez Humble:
* Continuous Delivery with Jez Humble:
* The DevOps Transformation (Ben Rockwood, 2011):
* Simon Sinek - People don't buy what you do, they buy why you do it:
* DevOps... it's the "why?" not the "what".:

* Stop Hiring DevOps Experts and Start Growing Them by Jez Humble:
* Transforming to a Culture of Continuous Improvement:
* Theories of managing organizations for competitive advantage:
* Examining Failure Without Blame:

=Technical Debt=
* SATURN 2014 Panel Discussion on Technical Debt:
* Technical Debt in Large Systems: Understanding the Cost of Software Complexity:

=Examples from the wild=
* 10+ Deploys Per Day: Dev and Ops Cooperation at Flickr:
* Salesforce & DevOps, org design, toolchain choices:

=Agile & organizing=

* Continuous Integration - CI Told You So!:
* Developer productivity, eliminiating waste in the dev environment setup:

* Dima Kovalenko: Selenium and Cucumber:
* Scaling and managing Selenium Grid by Dima Kovalenko @ Selenium Conf 14:
* Better Late Than Never: Integrating Selenium After The Fact:
* Francois Reynaud + Kevin Menard: Selenium 2 Grid:
* Hackathon 2014 - Removing Dependency from SauceLabs - Christopher Grandoit:

* I Am SysAdmin (And So Can You!):
* History/future of systems admin, operations as craft/culture:
* "You Code Like a Sysadmin"—Software Development for the Non-Developer:

* Complexity and Failure. Like Peanut Butter and Jelly.:
* Resilient systems, culture, microservices, containers, the cloud, and how they are all intertwined:


=Automation & Powershell DSC=
* A Practical Overview of Desired State Configuration:
* Seattle Chef Meetup 7/15/14: Chef and Microsoft's Desired State Configuration (DSC):
* PowerShell Desired State Configuration DSC and Windows DevOps:
* DevOps, Desired State, and Microsoft Windows:
* Automating a Windows .NET 4.0 Stack with Opscode Chef and Microsoft Azure:

=DevOps & Windows=
If you are curious, the reason why this has a separate topic is because traditionally Windows has lagged far behind the Linux communities, so any developments are big news.
* Rachel Laycock - "Continuous Delivery: Tales from Windowsland":
* DEVOPS + Chef + Windows at
* #ChefConf 2014: Daniel Gilmer, "Ancestry's Use Of Chef For Windows: Phase 2":
* Webinar: Transforming to Continuous Delivery at with Opscode Private Chef:
* Tips and Tricks for Automating Windows with Chef - Doug Ireton:
* How to Achieve Continuous Delivery with TFS - Peter Gfader:
* DevOps in a Microsoft World:

* CollabNet webinar Real Time Metrics to Power DevOps Pipelines:
* Metrics Gauges, Counters, and Ratios, Oh My!:

=Databases & Data=
* Building an Automated Database Deployment Pipeline - Alex Yates:
* SQL Server Central Webinar #25 - Best Practices in Database Deployment (Part 1):
* The Database: The Elephant in the Room:

=Monitoring & logging=
* A New Age in Alerting with Bosun: The First Alerting IDE:
* OSMC 2013 | Andreas Ericsson: The future of Nagios (ENG):
* R2-D2 projector server monitoring system:
* logging: logstash and other things - Jordan Sissel of DreamHost - PuppetConf '12:
* More Logstash Awesome - Jordan Sissel - PuppetConf 2013:
* OSDC 2014: Gergely Nagy - Monitoring with syslog ng, Riemann and Kibana:
* DevOps Days Tel Aviv 2013: Ignite: Monitoring Patterns with Riemann - Itai Frenkel & Eli Polonsky:
* Monitoring in an Infrastructure as Code Age - PuppetConf 2013:

=Security & Networking=
* Software defined networks & future of network administration:
* Challenging the conventional thinking that hardware/software must come bundled together:

=New ideas in computing=
* (this one was kinda mind blowing) Modern Cloud-based platform:
* Postcode Anywhere: Optimize eCommerce with Machine Learning — Cassandra, Elasticsearch and Spark:


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…