deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mani <wirelessa...@gmail.com>
Subject Re: unable to get hardware profile from vcenter/vsphere provider
Date Mon, 05 Nov 2012 22:31:03 GMT
(update)
The /api/hardware_profiles api works fine if I set the API_PROVIDER to 
vcenter server 4.1 (Windows based server).
The api /api/hardware_profiles fails with the exception mentioned in the 
thread if I connect to "VMWare vCenter Server Appliance 5.0.0.3324".

Does deltacloud support vCenter Server appliance?

Thanks.
-Mani

On 11/2/12 2:50 PM, Mani wrote:
> Hi Michal,
> Yes. I do have hosts defined in vsphere.  How can I debug this?
> Somewhere on the web I saw your post for debugging:
> I set API_VERBOSE=1 and launched deltacloudd with -V. I do not see any 
> additional log messages. Does deltacloud spit out logs anywhere else?
>
> Thanks for responding.
> -Mani
>
>
>
> On 11/2/12 2:06 AM, Michal Fojtik wrote:
>> On 10/31/2012 12:32 AM, Mani wrote:
>>
>> Hi Mani,
>>
>> I tried to guess what could be the problem. From the exception you 
>> send it appears that DC failed to get first Host entity (?).
>>
>> 52: max_cpu_cores << dc.hostFolder.childEntity.first.summary.numCpuCores
>>
>> Do you have Host defined in VSphere and is it available?
>>
>>   -- Michal
>>
>>> Hi All,
>>> I have set up a vcenter/vsphere server as the provider behind 
>>> deltacloud
>>> (v1.0.3).
>>>
>>> When I hit this api: http://10.194.188.24:3001/api/hardware_profiles I
>>> always get a "Error loading page" UI warning and this exception 
>>> (pasting
>>> part of it):
>>>
>>> E, [2012-10-30T19:26:29.197658 #20808] ERROR -- : [500]
>>> Deltacloud::ExceptionHandler::BackendError:Unhandled exception or 
>>> status
>>> code (undefined method `summary' for nil:NilClass)
>>>
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:52:in

>>>
>>> `hardware_profiles'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:50:in

>>>
>>> `each'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:50:in

>>>
>>> `hardware_profiles'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/drivers/exceptions.rb:199:in

>>>
>>> `call'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/drivers/exceptions.rb:199:in

>>>
>>> `safely'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:43:in

>>>
>>> `hardware_profiles'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/helpers/deltacloud_helper.rb:37:in

>>>
>>> `send'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/helpers/deltacloud_helper.rb:37:in

>>>
>>> `filter_all'
>>> /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/helpers/deltacloud_helper.rb:37:in

>>>
>>> `filter_all'
>>> /usr/lib/ruby/gems/1.8/gems/deltacloud-core-1.0.4/lib/deltacloud/helpers/rabbit_helper.rb:22:in

>>>
>>> `standard_index_operation'
>>>
>>>
>>> Any ideas as to what is going on here? Is there some default "hardware
>>> profile" that I need to create on the vcenter server?
>>>
>>> I am launching deltacloud as:
>>>   deltacloudd -i vsphere -r <IP address>
>>>
>>> Thanks.
>>> -Mani
>>
>>
>


Mime
View raw message