Skip to main content

TFS & GO & Chef, oh my: Part 6 - Just legwork now...

Here's a broad overview of the process.  We are surprisingly close...

  1. Code for the project (webapp/website/windows service) sits in TFS
  2. The GO build agent is on a Windows server w. Visual Studio - it builds the project
  3. Have the config files changed?  If so, this process is still manual - thankfully rare, should just be an onboarding task
  4. On the build agent, git commit the built files and config files
  5. After the commit, get your latest version number and apply a label into the TFS project noting the associated git hash (so when troubleshooting, we say 'it's this git hash version we're running', and they say, 'oh, what label in TFS?' - now we have an answer!  (co-worker came up with this idea)
  6. Git houses built project files and project config files
  7. Git also houses the Chef config files
  8. Chef will be run to re-configure IIS (if necessary), operate services/appPools, and...dun dun a git fetch! (or git clone, not sure yet)  Bam!  New code!
  9. External tests will confirm things are ok.  (internal tests will be part of the entire process, too)
  10. QA now needs to automate their tests
  11. Deploy to UAT
  12. UAT now needs to automate their tests
  13. Deploy to PROD
  14. UAT/ProdSupport now need to have automated smoke tests
We're choosing to handle the environment specifics like this: Pipeline steps for each environment deployment, so just customize the pipeline to say 'use MY config files', rather than all sorts of complicated logic.

Yay!  Getting there...

Other fun features we're going to bundle into this new process:
  • Re-organized config files - i.e. putting site-level stuff once at the site level, instead of once inside each confif file
  • configSource config files (as mentioned, will be used to deal with environment-specific settings)
  • IIS-level config, doing it right - every time!
  • GO pipeline - this is going to be the showpiece, so we'll have to make sure it works brilliantly


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…