[one-users] Any reasons why the VNM driver is treated differently than the other drivers?

[Simon Boulet]

Hi,

I'm working on a custom set of drivers for OpenNebula. From my research, I
understand that the OpenNebula VMM wrapper (one_vm_exec or one_vm_ssh) is
responsible for doing the appropriate calls to the VNM (and to the VMM)
when doing VM actions. Is there any particular reasons why the VNM isn't
spawned and called directly by the OpenNebula core, like the other drivers
are (VMM, IM, Datastore, etc).

Am I right to assume that my custom VMM would need to spawn the VNM driver
as per the VM template <NET_DRV> attribute?

Thanks

Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20121122/6978d72f/attachment.htm>