CloudStack and Puppet

I was reading some CloudStack items on this guy's blog and came across this post ( http://kirkjantzer.blogspot.ca/2013/06/next-generation-storage-wherefore-art.html ).  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

Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many...
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible...
Read more

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 configured You see the DFSR folders get created on the other end, but nothing stages Finally 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...
Read more