Skip to main content

TFS & Jenkins & Chef, oh my: Part 2 - POC detail

The goal is simplify the POC...I think my initial vision will be a bit much to pull off 'well' inside a month.  Some key points like packaging/dependency management, pipelining, etc, will have to be set aside.

POC Scenario: Build and deploy a webapp/svc project (it just needs to deploy with no human intervention)

  1. New code checked in; Orchestrator sees new code and kicks off build script
    1. Build command runs, creates zip file & moves it into Jenkins build# folder?
  2. Build successful? Orchestrator runs deploy script (otherwise notify failure)
    1. Hey Chef, please install the updated project (build) into QA
      1. Ok, let's check out the project definition:
        1. Get latest
        2. Stop services
        3. Copy/extract/overwrite files
        4. Copy new configuration files
        5. Start services
      2. Let's test! serverspec?
    2. Report success (pipeline?)

Bonus Scenario: Rollback

  1. Something is not caught by testing, we need to roll back ASAP.
  2. Authorized person chooses 'rollback to previous version' for this project
  3. Orchestrator deletes the latest build?
  4. Chef runs and installs LastSuccessful

Pain points - even with the simplest method

  • Consistency in projects varies - this means where ProjectA puts all files in this folder, ProjectB puts them elsewhere, ProjectA and BProject (naming conventions)
  • Dependencies - not defined anywhere for anything (i.e. IIS req's, server req's...etc)
  • Configuration files - consistency in naming (mostly pathing and connection strings)
  • Versioning - this is done very wrong/not at all today, also - how to version Chef/config files?

More info on Windows & CD
Did some reading/viewing, very interesting stuff...we aren't even doing CI at this point, so there isn't a huge rush to make it perfect.

I think it's going to be TeamCity or GO at this point.  After having used Jenkins now, it works, but has issues around living in Windows (building from TFS at this point requires it to live there), specifically around the Chef/ruby stuff (doesn't work in Windows Jenkins).  Plus a few other...inconsistencies (the plugin update/restart process occasionally working)...have lead me to investigate other options.  TeamCity comes highly recommended, and it's free - at least for the POC stage (up to 20 projects).  I would have had to use GO & Jenkins together anyways (for pipeline visualization) if TeamCity can do both, or if GO can do both...ya.

The quick and dirty is 'zip'.  Better is to have dependencies and whatnot laid out, so things like NuGet/Chocolatey can be used.  Really no clue about how to do this.

Chef, for's really now just taking our existing deployment documents and using the principle 'Chef does everything, until it can't...then PowerShell'.  How the whole Chef repo works, and how we do configuration files...not sure yet.


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…