Basically, my understanding is that we can generate two versions of
libvdsm from the schema file for both the node and the management
application. First, the transportation protocols(XMLRPC, REST-API) will
depend on libvdsm(node version) to export the APIs to remote management
application. S
I'm sorry, but I don't really understand the drawing
- Original Message -
> From: "Shu Ming"
> To: "Adam Litke"
> Cc: vdsm-devel@lists.fedorahosted.org
> Sent: Wednesday, July 11, 2012 10:24:49 AM
> Subject: Re: [vdsm] [RFC] An alternative way to provide a supported interface
> -- libvd
Adam,
Maybe, I don't fully understand your proposal. Here is my
understanding of libvdsm in the picture. Please check the following link
for the picture.
http://www.ovirt.org/wiki/File:Libvdsm.JPG
http://www.ovirt.org/wiki/File:Libvdsm.JPG
On 2012-7-9 21:56, Adam Litke wrote:
On Fri, Ju
On 07/11/2012 09:08 AM, Shu Ming wrote:
Hi,
I created a VM with from existing template and found that the image of
the new VM actually copied the image from the template instead of
sharing a base from the template. I am wondering why the new VM
doesn't use a new cow image as its image pointi
Hi,
I created a VM with from existing template and found that the image of
the new VM actually copied the image from the template instead of
sharing a base from the template. I am wondering why the new VM doesn't
use a new cow image as its image pointing to the base image in
template. By th