vmware - cmdline operation

Question

trying to figure out how to use the cmdline to do the following:

-create a VM/Image on a centos system -install a centos/rhel os into the VM -install additional apps into the VM -add additional files into specific dirs within the VM

I then want to use the VM to play/run it on a separate server, via the vmplayer app.

I've probably gone through 20-30 different articles on trying to set this up with no luck.

So, if you've got chops on this, let me know! Beer's on me!

Comments/Thoughts/Pointers are all appreciated.

Complete docs/scripts are really appreciated as well!!

thanks

Answer 1

Well, given that the CentOS installer is both graphical and interactive, you definitely can't do this without creating a Kickstart script for unattended install first. And frankly, if you're going that route, you really might as well just create one VM and clone it. Once you have the VM created, you can use the vmware-mount command to mount the VMDK and copy whatever files you need into it, assuming you're doing this from a Linux host system.

Answer 2

This can be done. Here is how I approached it:

1. Create empty VMWare VM on a site like easyvmx You can template the VMX file at this point to change names/add versions etc. As far as I know you can't create the vmx files/structure on the command line, so you'll have to use a site like this or clone empty vm's. (This might be possible on the VMWare infrastructure paid for products or with the VIX api for VMWare.)

2. Create a custom kickstart file. Keep it dead simple just install 1 application in the post section, create 1 user, mkdir it's directory structure and so on.

3. Create a custom Centos DVD this one worked for me. Point this at your kickstart file or install your kickstart file on the DVD.

4. Now you are home and dry. Just point the empty VMX created first to boot (after trying the hard disk) from the custom ISO/kickstart you made. It will boot off DVD perform the install and presto you have your ISO.

Be warned. It's a lot of work to get this going on any kind of a sizeable project (mine has 5 products to install, setting up databases etc., I've run through literally thousands of build/boot cycles) Some of the scripts for the programs are very old and only run interactive, I've made heavy use of the wonderful expect program to drive these as if they were running on a terminal with a person typing answers). The other thing I'd recommend is that you use some kind of templating language (I used python's cheetah). This lets you do if/else for/while kind of stuff in the kickstart file and handles things like changing database sizes easily. Some of our dev's want a very small footprint VM and we chop out components for that and resize the DB with a template value.

We use it to deploy new releases of a messaging app to our developers, we can deploy a tested working VM to them when we get a new release within about 4 hours. That's for a normal release of our product. If one of the other packages changes then we have to retool the scripts.

A very basic version of what I built is on code.google.com if you search for kickstart-maker.