13fd202b6b
Use the newer :puppet livery, and default to an m1.large for testing
2012-08-12 15:48:54 -07:00
0fe437a69d
Add a simple default profile for cucumber
2012-08-12 15:48:42 -07:00
cea1668ffb
Upgrade blimpy
2012-08-12 15:29:27 -07:00
bc27f8dadb
Up puppetlabs-firewall to the latest master
2012-08-12 15:28:31 -07:00
431f556546
Add a simple rakefile for running tests
2012-08-12 15:27:52 -07:00
b2d0fd8eaf
Add the parallel_tests gem
2012-08-12 15:26:42 -07:00
8eeed7226d
Properly tear down the AWS VM at the end of each scenario
2012-06-18 23:35:23 -07:00
0de91d693a
Implement the last step definition to make the first scenario pass
...
At this point I think it's safe to say that the idea is fleshed out enough, but
also that the pentagram-web Puppet module has been thoroughly test driven :)
2012-06-18 22:26:01 -07:00
5f07a8dfb7
Verify that the host is in fact running the web server
...
Using a little Blimpy internals trickery to SSH into the
host.
Implementing this step actually found an issue with the
resource graph generated between the 'apache' module and
the 'passenger' module. Huzzah!
2012-06-18 22:16:38 -07:00
6131f867e2
Fix up the package name for zlib-devel (which is really supposed to be libz-dev)
2012-06-18 21:50:54 -07:00
deedc8f11f
Add the zlib-devel package required by passenger
2012-06-18 21:30:09 -07:00
5367271c14
Add the 'build-essential' package to the pentagram-web module
...
After jumping *out* from rspec-puppet back to Cucumber, when I
provisioned the host, the passenger installation failed because
the system lacked:
* a compiler
* zlib development headers
Let's disregard the absurdity of requiring a compiler on a web host
and just play along.
With the indication from cucumber that we need more resources,
we can jump back down into rspec-puppet
2012-06-18 21:26:24 -07:00
5f02821ee8
Add the passenger module into the pentagram-web module
...
This was a little trickier since the puppetlabs-passenger module
does some checks on `$osfamily` when it loads. To mitigate this
we define (let) some facts for the rspec-puppet run
2012-06-18 21:15:16 -07:00
f0b4aef58d
Add puppetlabs-passenger as a dependency
2012-06-18 21:11:28 -07:00
a2f35833ad
Ensure that the ruby module is pulled in for pentagram-web hosts
2012-06-18 21:10:46 -07:00
bc87132a24
Add the puppetlabs-ruby module as a dependency
2012-06-18 21:09:39 -07:00
47386fdd82
First step of pentagram-web module, pull in apache
...
This also requires some stupid symlinking set up for rspec-puppet
to properly find other modules to load in
2012-06-18 21:07:56 -07:00
d863f7d425
Add the puppetlabs-apache module as a dependency
2012-06-18 21:06:31 -07:00
bafed7ecbd
Add the puppetlabs firewall module as a dependency
2012-06-18 20:58:12 -07:00
34f4e47bcd
Update to the latest released Blimpy
...
Adding the Gemfile.lock to make sure others are using the same gems as I
2012-06-18 12:48:15 -07:00
ed167d865a
Add the basic rspec-puppet skeleton necessary to drive pentagram-web
2012-06-17 14:27:35 -07:00
c065a192ae
Adding rspec-puppet to the Gemfile to dig deeper
2012-06-17 14:21:30 -07:00
2a323e5534
Add support to actually spinning up a VM on AWS inside of a Scenario
...
Things are now at a point where I need to "go in" and implement
the "pentagram-web" module and everything that it entails.
Time to whip out rspec-puppet and puppet-module
2012-06-17 14:09:10 -07:00
3a0ceb07c3
Reference my own local Blimpy which will copy symlinks properly on rsync
2012-06-17 14:04:16 -07:00
b28679e729
Further set up the temp directory to contain a modules symlink and bootstrap.sh
2012-06-17 13:42:37 -07:00
02257896a3
Pull in a bootstrap script to bootstrap Puppet on a test VM
2012-06-17 13:37:52 -07:00
375c4fbcda
Implement "Given the host is to become ..."
...
For now I'm just going to "manually" write the Puppet
manifest that I want to use on the VM host straight
into a file in the temp directory
2012-06-17 13:36:07 -07:00
555a1b6fed
Set up a temporary directory and a temporary Blimpfile to be used later on
...
The Blimpfile means we can delegate off to AWS instead of needing to run all this mess locally with Vagrant
2012-06-17 13:30:15 -07:00
765f355e65
Add tempdir to the Gemfile, it'll be useful for separating scenarios
2012-06-17 13:20:51 -07:00
940541c01d
Create the first scenario: Provision a fresh app host
...
Letting cucumber guide the way here, just taking the automatically generated
steps and throwing them directly into a step file
2012-06-17 13:17:31 -07:00
c307db4cfb
Add my first operations-focused feature, no scenarios yet
...
This is just "setting the stage" so to speak for what I want
to accomplish here
2012-06-17 13:15:00 -07:00
43354e8c44
Add a simple Sinatra app with a single root-route
...
This is a mock-standin for a real web service, I don't
really feel like building a photo-sharing site just for a blog
post
2012-06-17 13:12:50 -07:00
b875858a78
Add a simple readme
2012-06-17 13:09:52 -07:00
b772887830
Initial commit
2012-06-17 13:09:03 -07:00
R. Tyler Croy