Hi Rayees,
Here are detailed steps to workaround your issues in your installed
setup:
1. Go to your tomcat client web app folder, in WEB-INF\classes, you should
find the following 3 files:
-environment.properties
-components.xml
-components_nonoss.xml
2. Check environment.properties, it should have the following line:
cloud-stack-components-specification=components-nonoss.xml
If it shows as "components.xml" here, then it is wrong, you need to change
to what shown above, and file a build bug for this since you are using
build.
Thanks
-min
On 1/23/13 4:07 PM, "Min Chen" <[email protected]> wrote:
>You cannot just change that one line, since it will depend on some new
>managers introduced in components-nonoss.xml. I think that you need to
>file a bug to track this build package issue. Can you check if you can
>find a components-nonoss.xml in your install folder (same directory as
>your components.xml)? If so, just rename that file as components.xml.
>Otherwise, you may have to copy components-nonoss.xml.in from
>client/tomcatconf/components-nonoss.xml.
>
>Thanks
>-min
>
>On 1/23/13 3:53 PM, "Rayees Namathponnan" <[email protected]>
>wrote:
>
>>Thanks Min,
>>
>>We modified the components.xml to include " <adapter
>>name="VShpereServer"
>>class="com.cloud.hypervisor.vmware.VmwareServerDiscoverer"/>" entry:
>>
>> <adapters key="com.cloud.resource.Discoverer">
>> <adapter name="XCP Agent"
>>class="com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer"/>
>> <adapter name="SecondaryStorage"
>>class="com.cloud.storage.secondary.SecondaryStorageDiscoverer"/>
>> <adapter name="KVM Agent"
>>class="com.cloud.hypervisor.kvm.discoverer.KvmServerDiscoverer"/>
>> <adapter name="Bare Metal Agent"
>>class="com.cloud.baremetal.BareMetalDiscoverer"/>
>> <adapter name="SCVMMServer"
>>class="com.cloud.hypervisor.hyperv.HypervServerDiscoverer"/>
>> <adapter name="Ovm Discover"
>>class="com.cloud.ovm.hypervisor.OvmDiscoverer" />
>> <adapter name="VShpereServer"
>>class="com.cloud.hypervisor.vmware.VmwareServerDiscoverer"/>
>>
>> </adapters>
>>
>>But management server fails to come up and following exception seen in
>>the logs:
>>
>>com.cloud.utils.exception.CloudRuntimeException: Unable to inject
>>VmwareManager in VmwareServerDiscoverer
>> at
>>com.cloud.utils.component.ComponentLocator.inject(ComponentLocator.java:5
>>3
>>7)
>> at
>>com.cloud.utils.component.ComponentLocator.configureAdapters(ComponentLoc
>>a
>>tor.java:623)
>> at
>>com.cloud.utils.component.ComponentLocator.parse(ComponentLocator.java:28
>>4
>>)
>> at
>>com.cloud.utils.component.ComponentLocator.getLocatorInternal(ComponentLo
>>c
>>ator.java:867)
>> at
>>com.cloud.utils.component.ComponentLocator.getLocator(ComponentLocator.ja
>>v
>>a:905)
>> at
>>com.cloud.servlet.CloudStartupServlet.init(CloudStartupServlet.java:48)
>> at javax.servlet.GenericServlet.init(GenericServlet.java:212)
>> at
>>org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java
>>:
>>1173)
>> at
>>org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
>> at
>>org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.ja
>>v
>>a:4187)
>> at
>>org.apache.catalina.core.StandardContext.start(StandardContext.java:4496)
>> at
>>org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.jav
>>a
>>:791)
>> at
>>org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
>> at
>>org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
>> at
>>org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:10
>>4
>>1)
>> at
>>org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:
>>9
>>64)
>> at
>>org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
>> at
>>org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
>> at
>>org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321
>>)
>> at
>>org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSup
>>p
>>ort.java:119)
>> at
>>org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
>> at
>>org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
>> at
>>org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
>> at
>>org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
>> at
>>org.apache.catalina.core.StandardService.start(StandardService.java:516)
>> at
>>org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
>> at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
>>:
>>57)
>> at
>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
>>m
>>pl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:616)
>> at
>>org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
>>
>>
>>vmware related jars seem to be already present and included in the
>>classpath:
>>
>>[root@s####-ms1 java]# ls -ltr vm*
>>-rw-r--r--. 1 root root 2645679 Jan 22 18:13 vmware-vim.jar
>>-rw-r--r--. 1 root root 5666804 Jan 22 18:13 vmware-vim25.jar
>>-rw-r--r--. 1 root root 5666804 Jan 22 18:13 vmware-vim25-1.0.jar
>>-rw-r--r--. 1 root root 2645679 Jan 22 18:13 vmware-vim-1.0.jar
>>-rw-r--r--. 1 root root 40057 Jan 22 18:13 vmware-apputils.jar
>>-rw-r--r--. 1 root root 40057 Jan 22 18:13 vmware-apputils-1.0.jar
>>[root@selenium-ms1 java]#
>>
>>
>>Is there any other changes required?
>>
>>Regards,
>>Rayees
>>
>>-----Original Message-----
>>From: Min Chen [mailto:[email protected]]
>>Sent: Wednesday, January 23, 2013 3:23 PM
>>To: [email protected]
>>Subject: Re: Unable to add vmwre cluster in non-oss build
>>
>>That is the problem. Non-oss build should deploy the non-oss version of
>>components.xml, the one you listed here is the one used for oss build.
>>
>>Thanks
>>-min
>>
>>On 1/23/13 3:19 PM, "Rayees Namathponnan"
>><[email protected]<mailto:[email protected]>>
>>wrote:
>>
>>>No, "VShpereServer" is missing in components.xml
>>>
>>>
>>>Please see the components.xml
>>>
>>> </adapters>
>>> <adapters key="com.cloud.resource.Discoverer">
>>> <adapter name="XCP Agent"
>>>class="com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer"/>
>>> <adapter name="SecondaryStorage"
>>>class="com.cloud.storage.secondary.SecondaryStorageDiscoverer"/>
>>> <adapter name="KVM Agent"
>>>class="com.cloud.hypervisor.kvm.discoverer.KvmServerDiscoverer"/>
>>> <adapter name="Bare Metal Agent"
>>>class="com.cloud.baremetal.BareMetalDiscoverer"/>
>>> <adapter name="SCVMMServer"
>>>class="com.cloud.hypervisor.hyperv.HypervServerDiscoverer"/>
>>> <adapter name="Ovm Discover"
>>>class="com.cloud.ovm.hypervisor.OvmDiscoverer" />
>>> </adapters>
>>>
>>>
>>>Regards,
>>>Rayees
>>>
>>>-----Original Message-----
>>>From: Min Chen [mailto:[email protected]]
>>>Sent: Wednesday, January 23, 2013 2:55 PM
>>>To:
>>>[email protected]<mailto:[email protected]
>>>h
>>>e.org>
>>>Subject: Re: Unable to add vmwre cluster in non-oss build
>>>
>>>Can you check your components.xml to see if it includes
>>>VmwareServerDiscoverer as one of its Discoverer adapters?
>>>
>>>Thanks
>>>-min
>>>
>>>
>>>On 1/23/13 2:17 PM, "Rayees Namathponnan"
>>><[email protected]<mailto:[email protected]>>
>>>wrote:
>>>
>>>>Hi all,
>>>>
>>>>I am using nono-oss build from "master" branch, and tying to add
>>>>vmware cluster; but unable to add cluster and getting error in UI
>>>>"Could not find corresponding resource manager for VMware"
>>>>
>>>>
>>>>I cannot see any other error in MS log or API log, apart from below
>>>>
>>>>2013-01-23 10:51:01,772 INFO [cloud.api.ApiServer]
>>>>(catalina-exec-10:null) (userId=2 accountId=2
>>>>sessionId=6D784E414A2A40005EB7E65F5BD13AA2) 10.216.133.42 -- GET
>>>>command=listConfigurations&response=json&sessionkey=NMs5tJDbcf5j%2B6cH
>>>>3
>>>>KEu
>>>>QVL8e2c%3D&name=vmware.use.nexus.vswitch&_=1358967096110 200 {
>>>>"listconfigurationsresponse" : { "count":1 ,"configuration" : [
>>>>{"category":"Network","name":"vmware.use.nexus.vswitch","value":"false"
>>>>,"d escription":"Enable/Disable Cisco Nexus 1000v vSwitch in VMware
>>>>environment"} ] } }
>>>>2013-01-23 10:51:01,917 INFO [cloud.api.ApiServer]
>>>>(catalina-exec-9:null) (userId=2 accountId=2
>>>>sessionId=6D784E414A2A40005EB7E65F5BD13AA2) 10.216.133.42 -- GET
>>>>command=listPods&zoneid=fa7c6c32-b677-4033-baeb-59cb328014ae&response=
>>>>j
>>>>son
>>>>&sessionkey=NMs5tJDbcf5j%2B6cH3KEuQVL8e2c%3D&_=1358967096256 200 {
>>>>"listpodsresponse" : { "count":1 ,"pod" : [
>>>>{"id":"142122a6-ac73-4059-935a-fef88e5eb4bf","name":"POD01","zoneid":"
>>>>f
>>>>a7c
>>>>6c32-b677-4033-baeb-59cb328014ae","zonename":"Adv-VMware-Zone1","gatewa
>>>>y
>>>>"
>>>>:
>>>>"10.223.250.129","netmask":"255.255.255.192","startip":"10.223.250.132"
>>>>,"e ndip":"10.223.250.189","allocationstate":"Enabled"} ] } }
>>>>2013-01-23 10:51:31,923 INFO [cloud.api.ApiServer]
>>>>(catalina-exec-3:null) (userId=2 accountId=2
>>>>sessionId=6D784E414A2A40005EB7E65F5BD13AA2) 10.216.133.42 -- GET
>>>>command=addCluster&zoneId=fa7c6c32-b677-4033-baeb-59cb328014ae&hypervi
>>>>s
>>>>or=
>>>>VMware&clustertype=ExternalManaged&podId=142122a6-ac73-4059-935a-fef88
>>>>e
>>>>5eb
>>>>4bf&username=#Admin#&password=#password#&url=http%3A%2F%2F#VCenterIP#%
>>>>2
>>>>FSC
>>>>-CLOUD-QA03%2Fesxcluster&clustername=###%2F#########%2Fesxcluster&resp
>>>>o
>>>>nse
>>>>=json&sessionkey=NMs5tJDbcf5j%2B6cH3KEuQVL8e2c%3D&_=1358967126269 431
>>>>Could not find corresponding resource manager for VMware
>>>>
>>>>Any idea ?
>>>>
>>>>
>>>>Regards,
>>>>Rayees
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>
