Add Scientific Linux 6.4 x64 boxes for virtual box

[treydock]

I do not know what the procedure is to get my vbox files into S3, so I've put them on a public web server I manage. They will be temporarily available at http://vagrant.tamu.edu.

The "nocm" box is currently being used and tested successfully using my puppet-zfsonlinux module.

Once I get a copy of Fusion I can build those also.

Basing the 'nocm' version off the CentOS 6.4 x64 nocm, I was unable to make "validate" pass the ruby and gem checks. I assume this is expected, and was unable to find documented methods for skipping those validations unless I use the 2nd example below.

$ veewee vbox validate scientific-64-x64-vb4210-nocm --tags=vagrant virtualbox
Checking user - OK
Checking sudo - OK
Checking ruby - FAILED
Command: . /etc/profile ;ruby --version 2> /dev/null 1> /dev/null;  echo $?
Expected string 0
Output:
Checking gem - FAILED
Command: . /etc/profile ;gem --version 2> /dev/null 1> /dev/null;  echo $?
Expected string 0
Output:
Checking shared folder - OK

$ veewee vbox validate scientific-64-x64-vb4210-nocm --tags=vagrant
Checking shared folder - OK

[kbarber]

+1 @treydock I'm going to go through a re-rolling marathon soon enough, will look at this patch at that point okay?

I'm def +1 on having scientific linux images. Thanks.

[treydock]

@kbarber Sounds good to me.

[puppetcla]

Waiting for CLA signature by @treydock

@treydock - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppetlabs.com/

Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppetlabs.com/community/trivial_patch_exemption.html

[treydock]

CLA has been signed.

[puppetcla]

CLA signed by all contributors.

[treydock]

Any update on getting this into the Puppetlabs S3 instance?