Difference between revisions of "Automated Workspace Setup"

From CitconWiki
Jump to: navigation, search
 
Line 9: Line 9:
  
 
Other wins:
 
Other wins:
* spinning up VMs automatically based on base images.
+
* spinning up entire stack of VMs automatically using jira,  amazing stuff. harass [http://twitter.com/noeticpenguin Kevin] until he documents it.
 
* createing env through jira to enforce naming scheme and other conventions that make it all go.
 
* createing env through jira to enforce naming scheme and other conventions that make it all go.
 
+
* source control for database, using liquibase - migrations forwar and back, scripts are under source control.
 
Open problems:
 
Open problems:
  
Line 17: Line 17:
  
 
Tools:
 
Tools:
 +
* [http://www.liquibase.org liquibase] DB migrations
 
* [http://www.cfengine.org/ cfengine]
 
* [http://www.cfengine.org/ cfengine]
 
* [http://www.puppetlabs.com/ puppet]
 
* [http://www.puppetlabs.com/ puppet]
 
* [http://wiki.opscode.com/display/chef/Home chef] **Endorsed by [http://bestfriendchris.com Chris]
 
* [http://wiki.opscode.com/display/chef/Home chef] **Endorsed by [http://bestfriendchris.com Chris]

Latest revision as of 10:43, 17 April 2010

What's worked for Jay and his tribe:

  • homogenous workstation - all windows.
  • self extracting zip, with bat files that install ancillary tools (IDE, JDK, etc)
  • check registry for latest service packs, if not present get them and install.
  • install scripts can also update workspace

What doesn't work for Jay and his tribe: Some cool tools don't work on windows

Other wins:

  • spinning up entire stack of VMs automatically using jira, amazing stuff. harass Kevin until he documents it.
  • createing env through jira to enforce naming scheme and other conventions that make it all go.
  • source control for database, using liquibase - migrations forwar and back, scripts are under source control.

Open problems:

Ideas to pursue:

Tools: