Skip to main content

Development workstation build: Packer/Vagrant/Virtualbox for an IIS/MSSQL environment

There are lot of other blog posts out there detailing this (see end of post for links), but I wanted to share my experience.

I started this project with the mandate as follows:
Find a way to make onboarding new developers simple and easy, plus we'd like a way to ensure that development environments are kept up to date.
Seems like a good first task to get familiar with the systems!  The old process involved a lot of guesswork & fiddling, and generally took a few days at minimum.  There's an obvious business case to be made - especially when they plan on hiring ~15 developers this year (minimum 30 man-days of productivity lost, not counting the waste associated w. inconsistent environments).

I started with a few misconceptions, but eventually we had conversations around what should we be doing, rather than what do you want me to do.  One of the senior developers mentioned how a VM would go a long way to bringing stability, and after a chat everyone agreed.  Further, a VM would be easy to distribute amongst the team (separate locations).  It was a dramatic departure from tradition, but there was a good case to be made.  Further, the work I'd already done could be mostly repurposed into this new venture.

The environment was a standard .NET stack - IIS & SQL Server and a few supporting pieces.  I found some great templates to get me started, plus some great articles that held my hand through the first run.  We had tried boxstarter for the original attempt, but met with some difficulties around domain security policies.

So here we are.  There are two pieces to this:  

  1. The new developer has a bare workstation that needs some pieces installed/configured & code repo cloned.
  2. We need a VM that runs our IIS/MSSQL in a Server OS and links to our local code repo (builds dump into the local repo), plus we have some way to redirect DNS calls to *.domain.local.

I'll outline the two parts and post more detail/actual scripts later...


I would note that the whole process is somewhat flawed because we are not utilizing the same tooling to deploy this into production, but it's better than nothing.

Part1: Populating the bare workstation

  • PowerShell script that creates directories, downloads config files/scripts from S3 (prompts dev for their S3 key/secret)
  • PowerShell script that installs applications (Visual Studio, supporting apps e.g. Resharper & 7zip), plus sets up DNSagent (for *.domain.local resolution to our VM)
  • PowerShell script that automatically sets up a local SSH key & uploads it to Bitbucket (and prompts the dev for their Bitbucket user/pass), then pulls down a clone of the repo
  • PowerShell script that does the 'initial build' of the codebase, calls the VM to restart services

Part2: Create the VM

  • Packer script that builds the VM from an ISO (incl. autounattend.xml), install some apps, runs some initial setup scripts
  • Packer script that takes the ISO-build output and runs some further configuration scripts (IIS, SQL, dev database import), then re-arms the trial period and exports the VM
  • Vagrant template that sets up VirtualBox shared folders & networking
  • (not done yet) Some sort of script the developer runs on their end to get VirtualBox configured and ready for 'vagrant up'

Helpful links


  • http://www.developer.com/net/virtualize-your-windows-development-environments-with-vagrant-packer-and-chocolatey-part-1.html
  • http://www.developer.com/net/virtualize-your-windows-development-environments-with-vagrant-packer-and-chocolatey-part-2.html
  • https://www.packer.io/
  • https://github.com/packer-community/packer-windows-plugins
  • https://github.com/dylanmei/packer-windows-templates
  • https://gallery.technet.microsoft.com/scriptcenter/Reset-SQL-SA-Password-15fb488d
  • https://chocolatey.org/packages/MsSqlServer2014Express

Comments

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$\user.name\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):
MSSQLSVC/tor-sql-01.domain.local:1433

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

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/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
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 going...so here's a config and brain dump...

Why?
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)

How?
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
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…