Skip to main content

CloudStack and Puppet

I was reading some CloudStack items on this guy's blog and came across this post ( ).  A lot of this resonates with what our company is trending towards.

As a software developer, the different build stages all require complete and dedicated environments.

  • Dev
  • QA/UAT
  • Prod
When it comes time to build a new product for a new customer, a new set of environments needs to be spooled up.  Traditionally, everything was scratch built (VM templating being the best automation in use today) meaning a dev environment rollout could take a week or two:
  • Lay out environment as per architecture's design
  • Figure out networking/auth structure
  • Deploy VM templates
  • Install/configure IIS/SQL
  • Deploy starter software packages
  • Create/test public (if required) accessibility
  • Hand over access to the dev team
  • Wait for them to sign off
  • Double-check that all relevant info documented
There is plenty of room for improvement in this process.  The next part of it (and most important) is the successful recreation of Prod for QA/UAT environment roll-outs.  Due to whatever wizardry the devs get up to, there are multiple streams under one customer, so this means you have one dev environment, but sometimes 3-4 QA/UAT environments, and they need to be torn down/built up as fast as possible.

A QA/UAT build today looks like this:
  • Deploy a dev environment
  • Deploy all current software packages in order (a manual process)
  • Get Dev/QA to sign off
Doesn't sound like much, but when I say manual process...I mean an MSI is the best we have for automation.  An MSI that really just copies files, maybe does some basic IIS config if you're lucky.  It's an inconsistent process due to some reason I am not sure of.

So all of that being said...what the heck does this have to do with CloudStack and Puppet?

Here what we're planning to do:
  1. Deploy an environment according to an env. template (VMs, storage, networking all at once)
  2. Automate package and config deployment via Puppet/agents
  3. Go get a coffee and plan retirement
Haha!  So simple, right?  Well, it kinda is.  CloudStack has made it quite easy with their VMware integration, and the Puppet side has some decent Windows plugins/functionality.

Expect more CS/Puppet posts.  It is REALLY cool stuff.  I'm also going to work on integrating NSClient++ into the VM builds and automating monitoring as well.  :D


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…