Changed Vagrantfile's Multi-VM Configuration

Issue #2

Found right now puppet has been commented out. Could puppet be the
problem?
Fix unmatched do

Issue #2
Added Lucid32 Puppet Manifest

Threw back Lucid32's UbuntuManifest.pp

Will test to see if everything runs successfully.

Issue #2
Shut down VM's

Non issue

Issue #6
Adding other neccessary files

Issue #2
Force Prompts on RVM Requirements

Issue #2
Edited Force Yes

Issue #2
Removed Backslash

Issue #2
Successful

Issue #2

Overall success, with some error.

Error Message:

/opt/vagrant_ruby/lib/ruby/site_ruby/1.8/rubygems.rb:900:in
`report_activate_err
or'
:
Could not find RubyGem puppet (>= 0)
(
Gem::LoadError
)
from /opt/vagrant_ruby/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activa
te'
from /opt/vagrant_ruby/lib/ruby/site_ruby/1.8/rubygems.rb:1276:in `gem'
from /opt/vagrant_ruby/bin/puppet:18

but Lucid32 system still has ruby 2.0.0 installed (checked using $ruby
-v)
Successful

Issue #2

CentOS successfully provisioned wtih MySQL 5.5.30
Lucid32 successfully provisioned with Ruby 2.0.0 and PHP 5.4
No Ruby

Ruby be gone. Moving ahead without Ruby interpreter.

Issue #2
Lucid32 and CentOS fully automated and repeatable

Issue #2

CentOS sends back 1 instead of 0 on return values after reloading
machine, so I went in and change the manifest to account for that change
using an array of values.