ESX Deployment Appliance (EDA) is a small and easy to use appliance
that makes deploying ESX servers a breeze. It has a very intuitive
web-interface that can configure and deploy dozens of ESX servers in
minutes. It has a script-builder that will allow any admin to create
%post-scripts that will do most anything one needs to get the ESX hosts
up and running! Even if deploying with RDP/Altiris or the UDA, this
script-builder can help setting those up very quickly.
I am still having issues getting part 4 of this downloaded. Ive done this both at home and work and I get the same issue where the page times out . Any assistance would be appreciated!
i originally posted the files on microsoft's spaces and that will only allow files of 50mb or less. and since it's 170mb i had to cut it into 4 pieces.
and it will very likely work on fusion since the virtual layer is supposed to be identical.
Try to test this in Vmware Workstation, Can some one give me some advises for that, or any link for manual.
did try put this Appliances and anothere windows XP in the Same LAN (Team), still can not ping it: 192.168.1.68
Even give the XP ip 192.168.1.1 still can not ping Appliance
Thanks you very much!
I use it in workstation. You just need to make sure it is mapped to the VMNET that hosts the 192.168.1.1 address. You may also need to shut of the winders firewall.
If 192.168.1.1 is the actual ip address associated with the workstation's physical NIC, then change the VM's network connection to "bridged". Is 192.168.1.1 the workstation's proper IP address?
Thanks for your quick reply.
Let me show what i did,
In VMware workstation V6.0. I did create a windows XP VM. Manual setup the IP Address to 192.168.1.1 (Bridge same as Appliance) Try to ping 192.168.1.68. can NOT. Then I created a Team in vmware workstation, setup a new LAN for Appliance and windows XP VM only. from windows XP VM still can not ping Appliance.
try setting your XP machine IP address 192.168.1.100. If that does not work try setting your NAT or HOSTONLY to 192.168.1.x and then use that network.
moving a VM to workstation can get the network wrong. edit the vmx file and remove the line where it says 'networkname'. else you can try to remove the network card and add it again.
So, is that ok? in Vmware Workstation, I setup a Windows XP VM Team with Appliance ("edit the vmx file and remove the line where it says 'networkname'.) and setup the IP Address to 192.168.1.1 /24, Default gateway to 192.168.1.1. Then IE to url http://192.168.1.68.
really want to try the appliance
you should never point the gateway of any host to itself. rather have no gateway at all than point to it's own ip address. but if you put both xp and the eda in the same network they should see eachother nonetheless.. so yeah, your setup should work if they both have working network adapters.
Hi I've download EDA I want to enlarge the system disk but I nothing about Ubuntu 7.10 can this be done and how, or can I attach a second disk and share this out via SAMBa if so how do I that?
the appliance is set up so it wouldn't need more diskspace than it has. but if you have to, you can add a new disk to it and then log into it as root. then you'll have to create a partition and filesystem on it and mount it somewhere. you'd do something like:
create new partition
mkfs -J -t ext3 /dev/sdb1
add '/dev/sdb1 /opt ext3 defaults 0 0'
and you're done. plenty of space in /opt.
>!http://communities.vmware.com/people/Pauile3576/avatar/32.png?a=-1!  1 posts since
>13-jun-2008 > >Does anyone have a guide on how to setup and use this thing? I am completely lost. I moved the appliance onto a LUN and tried to create a custom VM and my VC will not see the VMDK. What the hell am I doing wrong???
the diskformat in ESX isn't the same as on workstation or server. you have to convert it in ESX before you can assign it to a VM. use 'vmkfstools -i newdisk.vmdk olddisk.vmdk' to do so.
Hi thanks for replying. The reason I wanted a larger disk!!! I'm deploying ESX 3.5 on to HP Proliant DL585's the script includes installing the HP DataProtector 6.0 agent. The agent files are rapped in the DP_DEPOT file which is 600+ megs hence I added a new disk , shared it out via Samba and rapped my own script around the install process , which is then pushed out via EDA....
Sorry have a question?
When EDA deploys does it disable the SAN drivers , if so how I do I reable the drivers so the ESX server can see the SAN
i would first try to extract only the files you need from that huge archive. hp agents are typically some 25mb so it's a shame to go through all the trouble of adding disks for all the agentfiles for windows and whatnot when you only need the esx agents.
but you can use the method in the earlier post to add a disk of say 1GB under /var/www/dl. it will then automatically be shared and the scriptbutton to get a file to the host will work automatically as well.
as for the san drivers. the current version strips the san drivers from the boot image which makes it save for the installer to install to the first harddisk which will always be a local disk. the current version 0.6 has a small problem though where somewhere it will still look at san disks and find a filesystem it doesn't know. i'm currently working on a new version 0.7 that fixes that problem. i'll upload it hopefully coming weekend. i'll post a message here where to find it.
Hi thanks for the information
I think I have a different problem, I've used EDA to deploy an esx 3.5 box all worked fine ... But I cannot see the SAN,,, have a look at the attach images hence looking at the drivers and loaded modules etc
I've used vmkload_mod -l
Name R/O Addr Length R/W Addr Length ID Loaded
qla2300_707_vmw 0x8b2000 0x59000 0x28c8300 0xac000 4 Yes
looking at other ESX 3.02 boxes I see /proc/scsi/qla2300 which is correct,,,, But on the ESX 3.5 box ONLY /proc/scsi/ ,,,, Don't know what's happening
The VC for ESX 3.02 see image "With SAM.bmp" is fine.... but using the ESX 3.5 see image "NO SAN.bmp" there's no SAN
Do you have any advise , useful commands