CentOS 5.4 support on VMware Studio 2.0

Sun, 01 Nov 2009 04:22:02 GMT

In order to add CentOS 5.4 to be supported under VMware Studio 2.0 you must add it to the supported OS profiles.
I hope this helps someone.

#1 Copy the DVD ISO to /opt/vmware/www/ISV/ISO/

#2 Go to /opt/vmware/etc/build/templates/centos/5 and create directory “4” as the latest version can also add “4_x86_64”.

#3 Create build_profile.xml as sample below. The latest md5sum must exist in the line that reads:

<vadk:ISO vadk:path="file:///opt/vmware/www/ISV/ISO/CentOS-5.4-i386-bin-DVD.iso" vadk:md5sum="071e18754c2fb066c526672f9aea0515" vadk:containFiles=""/>

So md5sum="071e18754c2fb066c526672f9aea0515" is the latest CentOS 5.4 DVD ISO md5.

#4 Create build_profile.xml inside /opt/vmware/etc/build/templates/centos/5/4/

<ovf:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.dmtf.org/ovf/envelope/1 /opt/vmware/etc/build/schemas/vadk.xsd"
xmlns:vadk="http://www.vmware.com/schema/vadk"
xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1"
xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData"
xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData"
xmlns:vmw="http://www.vmware.com/schema/ovf"
ovf:version="0.7.0"
vadk:version="1.1">

<References></References>


<Section xsi:type="ovf:AnnotationSection_Type">
<Info></Info>
<Annotation></Annotation>
</Section>

<Section xsi:type="ovf:ProductSection_Type" ovf:required="false">
<Info>VM ISV branding information</Info>
<Product>CentOS Linux 5.4</Product>
<Vendor>Independent Software Vendor, Inc.</Vendor>

<Version>1.0.0.0</Version>
<FullVersion>1.0.0.0 alpha</FullVersion>
<ProductUrl></ProductUrl>
<VendorUrl></VendorUrl>
<AppUrl>http://${app.ip}/</AppUrl>
<Category>Application</Category>
</Section>

<Section xsi:type="vadk:ExtendedProductSection_Type">
<Info></Info>
<vadk:VendorUUID></vadk:VendorUUID>
<vadk:ProductRID></vadk:ProductRID>
<vadk:AppUrlName>Application Home</vadk:AppUrlName>
<vadk:Logo></vadk:Logo>
<vadk:LogoUrl></vadk:LogoUrl>
<vadk:WelcomeText>${app.name} - ${app.version}

To manage this VM browse to ${vami.url}
</vadk:WelcomeText>

</Section>

<Section xsi:type="vadk:SSLCertificateSection_Type">
<Info></Info>
<vadk:CommonName>Self-Signed by YourCompany, Inc.</vadk:CommonName>
<vadk:OrganizationName>YourCompany, Inc.</vadk:OrganizationName>
<vadk:OrganizationalUnitName>VM Division</vadk:OrganizationalUnitName>
<vadk:CountryName>US</vadk:CountryName>
</Section>

<Section xsi:type="vadk:VAMISection_Type">
<Info>VAMI Specific Information</Info>
<vadk:Services>
<vadk:Service vadk:name="core" vadk:version="2.0.0.0" vadk:tabOrder="0"/>
<vadk:Service vadk:name="update" vadk:version="2.0.0.0" vadk:tabOrder="0"/>
<vadk:Service vadk:name="system" vadk:version="2.0.0.0" vadk:tabOrder="1"/>
<vadk:Service vadk:name="network" vadk:version="2.0.0.0" vadk:tabOrder="2"/>
</vadk:Services>
<vadk:WebServer vadk:httpsPort="5480"/>
<vadk:ViewCustomization>
<vadk:FooterLeft></vadk:FooterLeft>
<vadk:FooterCopyright></vadk:FooterCopyright>
</vadk:ViewCustomization>
<vadk:ShowEULA>true</vadk:ShowEULA>
</Section>

<Section xsi:type="vadk:ApplicationSection_Type">
<Info></Info>

<vadk:VMXFilename>VM.vmx</vadk:VMXFilename>

<vadk:DistributionFormat vadk:format="ovf" vadk:filename="VM" vadk:directory="VM"/>

<vadk:ApplicationPackages>
<vadk:url>http://http://VADK.localIP/ISV/appliancePackages</vadk:url>
<vadk:url>http://http://VADK.localIP/vmware-open-vm-tools/centos/5/3</vadk:url>
</vadk:ApplicationPackages>

<vadk:OSPackages> 
<vadk:Package vadk:name="openssh-server"/>
<vadk:Package vadk:name="openssh-clients"/>
</vadk:OSPackages>

<vadk:BootActions>
<vadk:FirstBoot>
#!/bin/bash
#Un comment to send the output of this script to a logfile
#exec > /opt/vmware/var/log/firstboot 2>&1

echo This script is executed on first boot only.

#Un comment to run subsequent boot script after first boot
#/opt/vmware/etc/isv/subsequentboot
</vadk:FirstBoot>
<vadk:SubsequentBoot>
#!/bin/bash
#Un comment to send the output of this script to a logfile
#exec > /opt/vmware/var/log/subsequentboot 2>&1

echo This script is executed on all boots, except the first one.
</vadk:SubsequentBoot>
</vadk:BootActions>

<vadk:Users>
<vadk:User vadk:username="root" vadk:password="" vadk:passwordFormat="plaintext"/>
</vadk:Users>
</Section>

<Section xsi:type="vadk:IpAssignmentSection_Type">
<Info>Supported IP assignment schemes</Info>
<vmw:IpAssignmentSection
ovf:required="false" vmw:protocols="IPv4" vmw:schemes="ovfenv,dhcp">
<Info>Supported IP assignment schemes</Info>
</vmw:IpAssignmentSection>
</Section>

<Section xsi:type="vadk:PropertySection_Type">
<Info/>
</Section>

<Section xsi:type="vadk:AnyOVFSection_Type">
<Info>
Unknown OVF elements in this element will be passed directly
to the OVF output descriptor without interpretation
</Info>
</Section>

<Section xsi:type="vadk:UpdateSection_Type">
<Info></Info>

<vadk:Repository vadk:url="" vadk:username=""
vadk:password="" vadk:passwordFormat="plaintext"/>



<vadk:Info></vadk:Info>



<vadk:PreInstallShellScript>#!/bin/sh
#Sample pre install update script
#This script will be executed with the following arguments:

$1 - version of VM before update
$2 - version of VM trying to be installed

echo "Installing update from version $1 to version $2"

#exit with value of 0 to allow update to continue
exit 0
</vadk:PreInstallShellScript>
<vadk:PostInstallShellScript>#!/bin/sh
#Sample post install update script
#This script will be executed with the following arguments:

$1 - version of VM before update
$2 - version of VM trying to be installed
$3 - status of update process

#
#The Status in $3 will indicate to success of failure of the update:

0 - all update steps are successful
1 - pre install script failed, package test and installation skipped
2 - pre install success, package test failed, installation skipped
4 - pre install and package test success, package installation failed

#
#A Status of 2 is likely caused by a package dependency conflict. A Status of 4
#is likely caused by a failed package install script.

if $3 -eq 0 ; then
echo "Finished installing version $2"
else
echo "Failed with status of $3 while installing version $2"
echo "VM version is still $1"
fi

#Exit with a value of 0 to allow the VM version to be changed and set the final
#update status to success.
exit 0
</vadk:PostInstallShellScript>

</Section>


<Section ovf:id="88" ovf:version="5" xsi:type="ovf:OperatingSystemSection_Type">
<Info>Guest Operating System</Info>
<Description>CentOS Linux 5.4</Description>
</Section>

<Section xsi:type="ovf:VirtualHardwareSection_Type">
<Info>Virtual Hardware Requirements</Info>
<System>
<vssd:VirtualSystemType>vmx-04</vssd:VirtualSystemType>
</System>
<Item>
<rasd:Caption>1 virtual CPU</rasd:Caption>
<rasd:Description>Number of virtual CPUs</rasd:Description>
<rasd:InstanceId>1</rasd:InstanceId>
<rasd:ResourceType>3</rasd:ResourceType>
<rasd:VirtualQuantity>1</rasd:VirtualQuantity>
</Item>
<Item>
<rasd:AllocationUnits>MegaBytes</rasd:AllocationUnits>
<rasd:Caption>512 MB of memory</rasd:Caption>
<rasd:Description>Memory Size</rasd:Description>
<rasd:InstanceId>2</rasd:InstanceId>
<rasd:ResourceType>4</rasd:ResourceType>
<rasd:VirtualQuantity>512</rasd:VirtualQuantity>
</Item>
<Item>
<rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
<rasd:Caption>Ethernet adapter on vmnet</rasd:Caption>
<rasd:Connection>Network 1</rasd:Connection>
<rasd:InstanceId>3</rasd:InstanceId>
<rasd:ResourceSubType>PCNet32</rasd:ResourceSubType>
<rasd:ResourceType>10</rasd:ResourceType>
</Item>
<Item>
<rasd:BusNumber>0</rasd:BusNumber>
<rasd:Caption>SCSI Controller 0 - LSI Logic</rasd:Caption>
<rasd:InstanceId>4</rasd:InstanceId>
<rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
<rasd:ResourceType>6</rasd:ResourceType>
</Item>
<Item>
<rasd:AddressOnParent>0</rasd:AddressOnParent>
<rasd:Caption>Harddisk 0</rasd:Caption>
<rasd:HostResource>/disk/system</rasd:HostResource>
<rasd:InstanceId>5</rasd:InstanceId>
<rasd:Parent>4</rasd:Parent>
<rasd:ResourceType>17</rasd:ResourceType>
</Item>
</Section>

<Section xsi:type="vadk:JEOSSection_Type">
<Info></Info>

<vadk:BootArgs>
append ks=http://VADK.unattendedCfgURL ksdevice=eth0
method=http://http://VADK.localIP/build/http://VADK.buildID/
initrd=initrd.img
ip=http://VADK.ip netmask=http://VADK.nm gateway=http://VADK.gw dns=http://VADK.ns1
lang=en_US keymap=us ramdisk_size=100000
divider=10 clocksource=acpi_pm
</vadk:BootArgs>

<vadk:BootArgsDHCP>
append ks=http://VADK.unattendedCfgURL
ksdevice=eth0 ip=dhcp
method=http://http://VADK.localIP/build/http://VADK.buildID/
initrd=initrd.img
lang=en_US keymap=us ramdisk_size=100000
divider=10 clocksource=acpi_pm
</vadk:BootArgsDHCP>

<vadk:BootFiles vadk:relPath="images/pxeboot" vadk:kernel="vmlinuz"/>

<vadk:UnattendedInstallTemplate>
http://VADK.vadkRoot/etc/build/templates/redhat/5/redhat5.xsl
</vadk:UnattendedInstallTemplate>

<vadk:PreInstallScript
vadk:template="http://VADK.vadkRoot/etc/build/templates/centos/5/preinstall.xsl"
vadk:output="http://VADK.stageDir/preinstall.sh"/>

<vadk:EVMInstallScript vadk:template="http://VADK.vadkRoot/etc/build/templates/redhat/5/evm_install.xsl"/>
<vadk:EVMConfigScript vadk:template="http://VADK.vadkRoot/etc/build/templates/redhat/5/evm_config.xsl"/>
<vadk:EVMCleanScript vadk:template="http://VADK.vadkRoot/etc/build/templates/redhat/5/evm_clean.xsl"/>

<vadk:PostScriptRepoList>RepositoryList</vadk:PostScriptRepoList>

<vadk:PostScriptPackageList>PackageList</vadk:PostScriptPackageList>

<vadk:VADKPackages vadk:path="http://http://VADK.localIP/build/http://VADK.buildID/repo/vadkPackages/"
vadk:sourceDir="http://VADK.vadkRoot/lib/build/include/centos/5/3/"
vadk:targetDir="http://VADK.stageDir/repo/vadkPackages/"/>

<vadk:ISO vadk:path="file:///opt/vmware/www/ISV/ISO/CentOS-5.4-i386-bin-DVD.iso"
vadk:md5sum="071e18754c2fb066c526672f9aea0515" vadk:containFiles=""/>

<vadk:Distribution vadk:vendor="CentOS" vadk:OSverMajor="5" vadk:OSverMinor="3"
vadk:arch="i386" vadk:smp="1" vadk:packageFormat="rpm"
vadk:packageManager="yum" vadk:packageRepoDir="packageRepoDir"/>

<vadk:OSPackages>
<vadk:Package vadk:name="bash"/>
<vadk:Package vadk:name="bind-utils"/>
<vadk:Package vadk:name="boost"/>
<vadk:Package vadk:name="chkconfig"/>
<vadk:Package vadk:name="coreutils"/>
<vadk:Package vadk:name="curl"/>
<vadk:Package vadk:name="dhclient"/>
<vadk:Package vadk:name="gawk"/>
<vadk:Package vadk:name="grep"/>
<vadk:Package vadk:name="initscripts"/>
<vadk:Package vadk:name="iptables"/>
<vadk:Package vadk:name="libicu"/>
<vadk:Package vadk:name="libxml2-python"/>
<vadk:Package vadk:name="module-init-tools"/>
<vadk:Package vadk:name="ncurses"/>
<vadk:Package vadk:name="net-tools"/>
<vadk:Package vadk:name="openssl"/>
<vadk:Package vadk:name="passwd"/>
<vadk:Package vadk:name="rpm"/>
<vadk:Package vadk:name="procps"/>
<vadk:Package vadk:name="sed"/>
<vadk:Package vadk:name="sudo"/>
<vadk:Package vadk:name="sysklogd"/>
<vadk:Package vadk:name="SysVinit"/>
<vadk:Package vadk:name="util-linux"/>
<vadk:Package vadk:name="wget"/>
<vadk:Package vadk:name="which"/>
<vadk:Package vadk:name="yum"/>
<vadk:Package vadk:name="yum-metadata-parser"/>
</vadk:OSPackages>
</Section>

<Section xsi:type="vadk:BuildSection_Type">
<Info></Info>
<vadk:ProvisioningSettings> 
<vadk:NetworkConnection></vadk:NetworkConnection>
<vadk:NetworkType>dhcp</vadk:NetworkType>
<vadk:IP></vadk:IP>
<vadk:Netmask></vadk:Netmask>
<vadk:Gateway></vadk:Gateway>
<vadk:DNS1></vadk:DNS1>
<vadk:DNS2></vadk:DNS2>
</vadk:ProvisioningSettings>


<vadk:ProvisioningEngine>
<vadk:VmhostLan vadk:hostname="" vadk:port="" vadk:hostOS=""
vadk:login="root" vadk:password="" vadk:passwordFormat="plaintext"
vadk:path="/tmp" vadk:datastore=""
vadk:datacenter="" vadk:managedESX=""
vadk:resourcePool=""
vadk:fileLogin="root" vadk:filePassword="" vadk:filePasswordFormat="plaintext"
vadk:fileProto="scp" vadk:filePath="/tmp"
vadk:vmrunPath="" vadk:wsXDisplay=".0"/>
<vadk:VmhostProduct vadk:name="" vadk:majorVersion=""/>
</vadk:ProvisioningEngine>


<vadk:ProvisioningTimeouts vadk:boot="600" vadk:poweroff="25" vadk:hang="7200" vadk:sshWaitTime="120" vadk:scpOperationTime="300" vadk:scpAutoYesWaitTime="2" vadk:systemCmdWaitTime="30" vadk:systemCmdMaxTime="7200"/>

<vadk:PreInstallShellScript>
#!/bin/bash
echo pre-install shell code
</vadk:PreInstallShellScript>

<vadk:PostInstallShellScript>
#!/bin/bash
echo post-install shell code
</vadk:PostInstallShellScript>



</Section>


<Section xsi:type="ovf:NetworkSection_Type">
<Info>List of logical networks used in the package</Info>
<Network ovf:name="Network 1" ovf:id="vmnet">
<Description>Network 1</Description>
</Network>
</Section>

<Section xsi:type="ovf:DiskSection_Type">
<Info>List of the virtual disks and partitions needed</Info>
<Disk ovf:diskId="system" ovf:capacity="2048"
ovf:capacityAllocationUnits="MegaBytes"
ovf:fileRef="system.vmdk"
ovf:format="http://www.vmware.com/specifications/vmdk.html#sparse"
/>
</Section>

<Section xsi:type="vadk:DiskPartitionSection_Type">
<Info></Info>
<vadk:Partition vadk:diskId="system" vadk:bootable="1" vadk:fs="ext3" vadk:mount="/boot" vadk:size="128"/>
<vadk:Partition vadk:diskId="system" vadk:bootable="0" vadk:fs="ext3" vadk:mount="/" vadk:size="grow"/>
<vadk:Partition vadk:diskId="system" vadk:bootable="0" vadk:fs="swap" vadk:mount="" vadk:size="128"/>
</Section>

</ovf:Envelope>

VMware Studio Readme

cromero@vmware.com — Tue, 25 Aug 2009 22:12:13 GMT

VMware Studio Readme

Read Before Posting

Sat, 13 Sep 2008 01:52:45 GMT

Welcome to the VMware Studio Communities Forum

Sat, 13 Sep 2008 01:29:10 GMT

Welcome to the VMware Studio 1.0 Communities Forum. This interactive portal is designed to serve as a resource to VMware Studio customers, software developers and hardware appliance vendors. Your comments, suggestions and input are very important to the continued success of VMware Studio!

To begin, familiarize yourself with our Read Before Posting page, then browse our list of participant entries below. Select the subject heading to read the posting and click Reply to post a comment. To add content, select one of the action items on the left of this page. Feel free to browse, post and discuss issues relevant to VMware Studio. Product support documentation will be uploaded to this site periodically.

VMware Studio is available as a free download. Additional information about VMware Studio 1.0 can be obtained on the VMware Studio product web page, the Virtual Appliance Solutions White Paper, the User’s Guide, the Admin Guide, and the Release Notes.

Thank you for your participation in the VMware Studio 1.0 Communities Forum!

VMware Communities : Document List - VMware Studio

CentOS 5.4 support on VMware Studio 2.0

VMware Studio Readme

Read Before Posting

Welcome to the VMware Studio Communities Forum