First tests for VifsRequestParam scheduler... still red so far
Use a string instead of a symbol for the vifs parameter key
Define a mac range in the network scheduler unit tests
Added a dhcp range to the network so that our instance can get ips
Changed be to eq. Even when we get the same record from the database, the sequel object still has a different reference
Use a block when testing for raised errors. Otherwise the error is raised before we expect it, causing the test to fail when it shouldn't. As documented here: http://stackoverflow.com/questions/6837663/rspec-implicit-subject-and-exceptions
Extracted helper method for setting dhcp ranges for fabricated networks
Wrote another unit test where we schedule an instance with two network interfaces
Split up the specs into one assertion per example
Use a before block instead of let.  It's the same thing but easier to distinguish from the lazy let. Also corrected a grammatical error in a context name
Removed some debug output that was accidentally comitted
Added a test for adding interfaces with no networks set
Added a test for scheduling instances without network interfaces
Separated NetworkVifsRequestParam contexts in different files to make the whole thing easier to read
Use the constant instead of a string when describing our scheduler
Added another example to the VifsRequestParam unit tests
Define the sad paths and happy paths in different describe blocks so we don't have to define the subject each time
Merge pull request #420 from axsh/more-scheduler-unit-tests

More network scheduler (VifsRequestParam) unit tests