[patch iwhd] Add RHEV-M template import

Jim Meyering jim at meyering.net
Wed Jun 15 14:48:27 UTC 2011


Pete Zaitcev wrote:
> Most clouds structure the procedure to start a VM into 2 general steps:
> 1. Upload and "register" the bundle, so that it is known to the cloud.
> This typically returns some kind of ID, such as Amazon's ami-xxxxxxxx.
> 2. Instantiate the "registered" image so that a running VM is created.
>
> Unlike other clouds, RHEV-M requires a 3-step process to start a VM:
> 1. Upload the bundle into so-called "export domain". This makes a
> "template" known to the cloud, but it cannot be launched yet.
> 2. Import the template. At its core it means copying the template
> from "export domain" to "master domain".
> 3. Instantiate the imported template to produce VMs.
>
> One way or the other, someone has to do this: either iwhd itself,
> or iwhd's user (Aeolus Conductor). This patch implements the middle
> step in iwhd.
>
> See the update to registration.md for the new parameter "cluster".
>
> ---
>  NEWS                 |    3
>  backend.c            |   15
>  dc-rhev-image.c      | 1245 ++++++++++++++++++++++++++++++++++-------
>  doc/registrations.md |   13
>  4 files changed, 1070 insertions(+), 206 deletions(-)

Hi Pete,
This looks fine, now.
Thanks for adding a NEWS entry.

> diff -urp -X dontdiff.iw iwhd-test/doc/registrations.md iwhd-tip/doc/registrations.md
...
> +The parameter "cluster" is optional. If it is omitted, it defaults to
> +"_none_". In that case, iwhd only uploads the object into the export
> +domain, but does not import the template. Do not use "Default" here.
> +It is a dummy cluster that RHEV-M comes with, just like the template
> +called "Blank".
> +
> +The name of the resulting template is going to be the object's name
> +("dummy_img" in the above example). Note that if you let iwhd to

s/ to//

> +import (by specifying "-d cluster=xxxxx"), template names have to
> +be unique in the datacenter, so you cannot register the same object
> +twice.


More information about the iwhd-devel mailing list