Skip to main content

TFS & GO & Chef, oh my: Part 11 - The deploy process

Trying to work out a few things right now:
  1. Where do I draw the line between 'do this in Chef' and 'do this from Go'?
  2. How do you 'template' Chef recipes?
  3. Where do I draw the line between 'do this using Chef' and 'do this using Chef but via PowerShell'?
Regarding #1, I can do pretty much everything in Chef...but then you lack the visibility and variables from Go.  

This should be cleared up by figuring out exactly what we want the Go deploy pipeline to look like - where do we need the milemarkers to sit?  Or maybe we just need one stage with really detailed error handling?

Regarding #2, right now I have a cookbook for 'WebApp1', and it will only work for WebApp1, not WebApp2, or 10, etc.  I imagine there is a simple method here.  (might have found it: #{cookbook_name})

Regarding #3, it really comes down to 'I know this can be done (and how to do it) in PS, but figuring it out in Chef will take time'.  For the POC, we'll probably end up just using PS to speed us along.  For the pilot I'll want to clean the messier stuff up.

<this post went unedited for several days...>

We've now figured it out...

  1. Chef will handle infrastructure in a single Go stage (two once we figure out how to separate project and infra Chef code)
  2. Solved via calling either %GO% env vars or Chef env vars i.e. #{cookbook_name}
  3. Just had to hunker down and figure out the powershell_script stuff

So our actual sequence for deploy (as of today):
  1. SQL changes (manual)
  2. Chef infra bump (manual? move this?)
  3. Git clone the files
  4. Git clone the configs (pulls a GO environment
  5. Chef run (right now updates all layers, not 'just' the project-specific infra)
  6. Operations test suite
  7. QA test suite (manual, nothing here yet)

The demo is on Friday...


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…