[one-users] Incomplete information from hosts polling (VMWare ESXi 4.1 an OpenNebula 2.0.1)

[Luigi Fortunati]

On Fri, Feb 4, 2011 at 10:35 AM, Luigi Fortunati
<luigi.fortunati at gmail.com>wrote:

> To Siva:
> As far as I know you can connect to the ESXi Server in three ways:
>
> libvirt and virsh (the way of OpenNebula-VMWare Driver):
> The VMWare Driver of OpenNebula uses virsh commands (which relies on
> libvirt) to access some hypervisor functionalities. You can use directly
> virsh commands to test what libvirt is capable of by using this command:
> virsh -c esx://[<user>@]<hostname of hypervisor>/?no_verify=1
> Then you'll get a password prompt.
> you can use "root" as user. no_verify=1 disables check on certificates.
> You can find other useful infos here: http://libvirt.org/drvesx.html
>
> If OpenNebula can't connect you'll probably notice some error messages on
> the logs.
> Take a look in var/oned.log and var/<vm id>/vm.log and post the errors,
> otherwise check the installation steps in the VMWare Driver section of the
> documentation.
> I remember that you have to configure a username and password in a file in
> order to let OpenNebula connect to hypervisors through virsh.
>
> VMWare API (vSphere Client):
> ESXi hosts come with a public API developed by VMWare for accessing
> hypervisor functionalities:
> http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/
> I think that libvirt actually uses ver. 2.5 of those APIs.
> vSphere Client most probably connects to the hypervisor using those API
> (probably the latest version of the latter).
>
> Shell:
> You have to enable access to the shell through VSphere Client.
> As far as I know it is only possible to make ssh access with the root
> credentials, even if you created other users and modified /etc/passwd file
> to set a shell for the user.
>
> On Fri, Feb 4, 2011 at 7:33 AM, Siva Prasad <myknowinmail at gmail.com>wrote:
>
>> Hi
>>
>> Can you please let me know how are you able to connect to ESXI Server.I
>> tried the same but got the error "connection refused".
>>
>> Please let me know the detail steps.
>>
>> Thanks,
>> Siva
>>
>> On Thu, Feb 3, 2011 at 9:40 PM, Luigi Fortunati <
>> luigi.fortunati at gmail.com> wrote:
>>
>>> Hi,
>>> I noticed a serious problem about the usage of VMWare ESXi 4.1 and
>>> OpenNebula 2.0.1.
>>> I'm actually using the VMWare driver addon which can be found on the
>>> opennebula website (ver. 1.0) and libvirt (ver. 0.8.7).
>>> It happens that OpenNebula can't get information about the usage of
>>> resources on the cluster nodes.
>>> By running 2 VM (each one requires 2 VCPU and 1 GB of memory) and
>>> executing some commands I get this output.
>>>
>>>  oneadmin at custom2:~/src$ onehost list
>>>   ID NAME              CLUSTER  RVM   TCPU   FCPU   ACPU    TMEM    FMEM
>>> STAT
>>>    2 custom7.sns.it    default    0    200    200    200      2G      0K
>>>  off
>>>    1 custom6.sns.it    default    2    200    200    200      2G      0K
>>>   on
>>> oneadmin at custom2:~/src$ onehost show 1
>>> HOST 1 INFORMATION
>>>
>>> ID                    : 1
>>> NAME                  : custom6.sns.it
>>> CLUSTER               : default
>>> STATE                 : MONITORED
>>> IM_MAD                : im_vmware
>>> VM_MAD                : vmm_vmware
>>> TM_MAD                : tm_vmware
>>>
>>> HOST SHARES
>>>
>>> MAX MEM               : 2096460
>>> USED MEM (REAL)       : 0
>>> USED MEM (ALLOCATED)  : 0
>>> MAX CPU               : 200
>>> USED CPU (REAL)       : 0
>>> USED CPU (ALLOCATED)  : 0
>>> RUNNING VMS           : 2
>>>
>>> MONITORING INFORMATION
>>>
>>> CPUSPEED=1992
>>> HYPERVISOR=vmware
>>> TOTALCPU=200
>>> TOTALMEMORY=2096460
>>>
>>> As you can see OpenNebula is unable to get correct information about the
>>> usage of resources on the cluster nodes.
>>> As these informations are used by the VM scheduler, OpenNebula is unable
>>> to schedule the VM correctly.
>>> I tried to create several VM and all of them were placed on the same host
>>> even if the latter was unable to satisfy the resource requirements of all
>>> the VMs.
>>> I think that this problem is strongly related to libvirt as OpenNebula
>>> use it to recover information about hosts and vm.
>>>
>>> Do you get the same behavior? Do you know if there is a way to solve this
>>> big issue?
>>>
>>> --
>>> Luigi Fortunati
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>
>
> --
> Luigi Fortunati
>



-- 
Luigi Fortunati
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20110204/a6a40dee/attachment-0003.htm>