Sorry for the 'spoke to soon' email. I got my VISDK to connect first and the OpenNebula worked fine. All set.
Thanks, Jon On Tue, Aug 31, 2010 at 1:56 PM, Jonathan Kelley <jkel...@vm-labs.com>wrote: > Hi Tino, > > Thanks that worked however now I hit the next layer of issues. I try adding > my ESXi host using onehost via the following command: > > bin/onehost create <fqdn_name> im_vmware vmm_vmware tm_vmware > > and I have set the im_vmwarerc as well as the vmm_vmwarerc files up as well > as the keystore imported the certificate which shows the fqdn name as well. > I also have setup oned.conf to include the vmware driver details. > > The only message I get in the log though is the following: > > r...@xxxxx:/srv/cloud/one# cat var/im_vmware.log > [31.08.2010 13:52:58] MONITOR FAILURE 6 Failed monitoring host > 12core.boston.vm-labs.com > > or > > Tue Aug 31 13:52:58 2010 [ReM][D]: HostPoolInfo method invoked > Tue Aug 31 13:52:58 2010 [InM][E]: Error monitoring host 6 : MONITOR > FAILURE 6 Failed monitoring host 12core.boston.vm-labs.com. > > How can I add more debugging to find out the details of the failure? > > Thanks, > Jon > > > On Fri, Aug 27, 2010 at 7:36 AM, Tino Vazquez <tin...@fdi.ucm.es> wrote: > >> Hi Jonathan, >> >> There are no differences setup-wise between OpenNebula v1.4 y v2.0 >> regarding the VMware drivers. >> >> In order to correctly configure the VI SDK 2.5, I recommend you follow >> the guide at [1], more precisely section "Setup Instructions for Java >> Development". You need to compile the jar files from the VI SDK 2.5, >> the errors you are experience comes from the lack of needed jar files >> in your CLASSPATH. Remember that java treats the jar files as >> directories, so you need to specify them explicitly in the CLASSPATH >> variable. Assuming your VI SDK and AXIS install resides at /opt/, a >> correct CLASSPATH looks like >> >> -- >> >> /opt/axis-1_4/lib/axis-ant.jar:/opt/axis-1_4/lib/axis-schema.jar:/opt/axis-1_4/lib/axis.jar:/opt/axis-1_4/lib/commons-discovery-0.2.jar:/opt/axis-1_4/lib/commons-logging-1.0.4.jar:/opt/axis-1_4/lib/jaxrpc.jar:/opt/axis-1_4/lib/log4j-1.2.8.jar:/opt/axis-1_4/lib/log4j.properties:/opt/axis-1_4/lib/saaj.jar:/opt/axis-1_4/lib/wsdl4j-1.5.1.jar:/System/Library/Frameworks/JavaVM.framework/Home/lib:/System/Library/Frameworks/JavaVM.framework/Home/lib/tools.jar:/opt/Vim25-SDK/samples/Axis/java/vim.jar:/opt/Vim25-SDK/samples/Axis/java/lib/activation.jar:/opt/Vim25-SDK/samples/Axis/java/lib/mailapi.jar:/opt/Vim25-SDK/samples/Axis/java/vim25.jar:/opt/Vim25-SDK/samples/Axis/java/vim25.jar:/opt/Vim25-SDK/samples/Axis/java/samples.jar:/opt/Vim25-SDK/samples/Axis/java/apputils.jar:/opt/Vim25-SDK/samples/Axis/java/vim25.jar:/opt/Vim25-SDK/samples/Axis/java/samples.jar:/opt/Vim25-SDK/samples/Axis/java/apputils.jar:/opt/Vim25-SDK/samples/Axis/java:/opt/axis-1_4/lib/axis-ant.jar:/opt/axis-1_4/lib/commons-logging-1.0.4.jar:/opt/axis-1_4/lib/saaj.jar:/opt/axis-1_4/lib/axis.jar:/opt/axis-1_4/lib/jaxrpc.jar:/opt/axis-1_4/lib/wsdl4j-1.5.1.jar:/opt/axis-1_4/lib/commons-discovery-0.2.jar:/opt/axis-1_4/lib/log4j-1.2.8.jar:/lib/wbem.jar:/opt/Vim25-SDK/samples/Axis/java/lib/activation.jar:/opt/Vim25-SDK/samples/Axis/java/lib/jaxen-core.jar:/opt/Vim25-SDK/samples/Axis/java/lib/jaxen-jdom.jar:/opt/Vim25-SDK/samples/Axis/java/lib/jdom.jar:/opt/Vim25-SDK/samples/Axis/java/lib/mailapi.jar:/opt/Vim25-SDK/samples/Axis/java/lib/saxpath.jar:/opt/Vim25-SDK/samples/Axis/java/lib/smtp.jar:/opt/Vim25-SDK/samples/Axis/java/lib/wbem.jar:/opt/Vim25-SDK/samples/Axis/java/lib/xalan.jar:/opt/Vim25-SDK/samples/Axis/java/lib/xerces.jar:/opt/Vim25-SDK/samples/Axis/java/lib/xml-apis.jar >> -- >> >> Best regards, >> >> -Tino >> >> [1] >> http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/visdk25setupguide.pdf >> -- >> Constantino Vázquez Blanco | dsa-research.org/tinova >> Virtualization Technology Engineer / Researcher >> OpenNebula Toolkit | opennebula.org >> >> >> >> On Thu, Aug 26, 2010 at 5:52 PM, Jonathan Kelley <jkel...@vm-labs.com> >> wrote: >> > Additional info on the errors I see when running ./install_vmware.sh: >> My >> > classpath is >> > >> CLASSPATH=:/opt/axis-1_4/lib/:/opt/vi-2.5.0/SDK/samples/Axis/java/:/opt/vi-2.5.0/SDK/samples/Axis/java/lib >> > Installing VMWare drivers.DeployVM.java:125: cannot access >> > org.apache.axis.AxisFault >> > class file for org.apache.axis.AxisFault not found >> > = cb.getConnection().getService().registerVM_Task( >> > ^ >> > DeployVM.java:235: unreported exception >> > com.vmware.vim.InsufficientResourcesFault; must be caught or declared to >> be >> > thrown >> > = cb.getConnection().getService().reconfigVM_Task( >> > ^ >> > >> /opt/vi-2.5.0/SDK/samples/Axis/java/com/vmware/apputils/vim/ServiceConnection.java:51: >> > cannot access org.apache.axis.client.Service >> > class file for org.apache.axis.client.Service not found >> > _locator = new VimServiceLocator(); >> > >> > Thanks, >> > Jon >> > >> > >> > On Thu, Aug 26, 2010 at 3:55 PM, Jonathan Kelley <jkel...@vm-labs.com> >> > wrote: >> >> >> >> Just curious if there are any differences to getting the VMware driver >> to >> >> work with OpenNebula 2.0. >> >> >> >> I am curious whether it is necessary to compile the VI SDK 2.5 or the >> >> packaged jar files are enough. >> >> >> >> If anyone has some exact steps on getting the VISDK up and running >> >> properly that would be great. >> >> >> >> I am setting this up on Ubuntu 10.04. >> >> >> >> Thanks in advance, >> >> Jon >> >> >> > >> > >> > _______________________________________________ >> > Users mailing list >> > Users@lists.opennebula.org >> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> > >> > >> > >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
