[one-users] OpenNebula 2.0 RC1 breaks vmware IM
Shi Jin
jinzishuai at gmail.com
Tue Oct 5 10:46:50 PDT 2010
I am seeing the same problem.
Hope this can be fixed soon.
Shi
On Tue, Sep 28, 2010 at 4:47 AM, Tino Vazquez <tinova at fdi.ucm.es> wrote:
> Hi Chris,
>
> This is indeed a compatiblity issue between the new driver structure and
> the VMware drivers. I've opened a ticket [1] so you can keep track of the
> fixing process.
>
> Thanks a lot for the feedback.
>
> Best regards,
>
> -Tino
>
> [1] http://dev.opennebula.org/issues/355
>
> --
> Constantino Vázquez Blanco | dsa-research.org/tinova
> Virtualization Technology Engineer / Researcher
> OpenNebula Toolkit | opennebula.org
>
>
>
> On Mon, Sep 27, 2010 at 8:13 PM, Chris Johnston <chjohnston at rim.com>wrote:
>
>> Looks like a change in RC1 has broken the vmware IM. The "MONITOR" command
>> is sending more data than the IM is expecting. With beta1 it was 3
>> arguments, with rc1 its 4 arguments, and only 3 are expected by the vmware
>> IM.
>>
>> one-2.0-beta1/src/im/InformationManagerDriver.cc - line 32
>> os << "MONITOR " << oid << " " << host << endl;
>>
>> opennebula-1.9.90/src/im/InformationManagerDriver.cc - line 32
>> os << "MONITOR " << oid << " " << host << " " << update << endl;
>>
>> opennebula-1.9.90/src/im_mad/vmware/OneImVmware.java - lines 118-121
>> } else if (str_split.length != 3)
>> {
>> send_message("FAILURE Unknown command");
>> }
>>
>> I'm guessing since 'update' is associated with the 'SCRIPTS_REMOTE_DIR' in
>> oned.conf and the im_ssh driver it can be ignored for the vmware IM.
>>
>> Chris
>>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
--
Shi Jin, Ph.D.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20101005/20d16699/attachment-0002.htm>
More information about the Users
mailing list