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.
actually, eda should have picked that up. the pxe import reads the boot file from CD and redirects the files on it to the webserver in the eda. the vib builder generates that file and points to the openmanage.v00 which in turn gets redirected by the eda.
so building vibs into your image should work. HP and Dell images work fine and they do exactly the same. if it boots from CD, it should boot from eda as well. it's how eda works
how exactly did you build the image?
I'm probably skipping 1.10
The 1.05 version runs 5.5 perfectly so there's no need for it.
The two small patches on the ntp and syslog targets I built in my 1.10 aren't big enough to go through the whole process of applianicing a new version
the solution exchange links have been fixed. we moved sites and were promised the links would automatically be redirected. unfortunately that promise was only half kept. we're working on getting old links back up so references will work again but the https://solutionexchange.vmware.com/store/products/esx-deployment-appliance-eda and http://virtualappliances.eu/?download links are back up!
That's actually exactly what EDA is built for. It installs ESX servers and fully configures them so they're ready to be included into the cluster and go straight to work.
Thank you for your response. Can you please tell me how edit the ks file in EDA 1.05? i do not see the editor like in previous version 0.88. Problem i am having is --firstdisk is not set to remote by default and i am not sure how to edit the ks file.
you dont have to edit the ks file for that. you can simply put '=remote' in the installdisk option on the bottom left side of the eda interface. you need to have an esx5 cd mounted for the option to show.
be sure to disconnect any data luns (zone them out) or at least have their lun id set to something higher than the lun you want esx to install on.
I am having all kinds of trouble with the 1.05 version on Workstation 8, and on ESXi 5.0. The IP address doesn't persist through a reboot, and i get a lot of nasty error logging to the console while i'm trying to configure the management IP info. Is it possible the file that i'm downloading has an issue? Is it possible to get another version somewhere?
This is a common problem with EDA. Edit the On VM edit /etc/udev/rules.d/70-persistent-net.rules file and change eth1 to eth0 and make sure the mac address matches in if cfg-eth0 file and reboot the VM. It should work fine.
Thanks for the response yaseen_ka. Is there a way for me to access the console in the EDA directly, or do I need to map the vmdk in to another Linux VM to edit it? All is see when I'm booted in is the configuration menu.
actually, you can simply remove that file and reboot the machine. alt-f2 should work to access the console but you can use the 'patch' menu from the eda as well. simply type in the execute box: 'rm /etc/udev/rules.d/70-persistent-net.rules'. it's a known issue in linux vm's where underlying hardwarelevel changes.
i'm currently having some problems with my internet uplinks. things should be back up again soon. i don't have access at the moment but i'm awaiting a call to let me know things are working again.