[Kimchi-devel] [RFC V2 1/3] Implement integrity verification: verify template integrity, update API.md

[Shu Ming]

In my opinion,  the 'invalid' is a return value with failure reason when 
the user tries to create a VM from an existing template.  Why should it 
be a parameter of POST method to '/vms'? Do you expect it is be used to 
as a return value of GET method of '/vms'?

2014/2/19 18:06, shaohef at linux.vnet.ibm.com:
> From: ShaoHe Feng <shaohef at linux.vnet.ibm.com>
>
> Sometimes, user create a template, but networks, cdrom, disks or
> storagepool will change later.
> So users can not create a vm from this template successfully.
> It is necessary to check some paramenters of template.
>
> This patch will check the follow paramenters of template.
> networks: check networks exists.
> cdrom: check cdrom is available.
> disks: check the volume is available.
>
> This patch does not check the storagepool exists. waiting for royce's
> disks patch.
>
> Signed-off-by: ShaoHe Feng <shaohef at linux.vnet.ibm.com>
> ---
>   docs/API.md | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/docs/API.md b/docs/API.md
> index fff740d..7940cf2 100644
> --- a/docs/API.md
> +++ b/docs/API.md
> @@ -249,6 +249,10 @@ A interface represents available network interface on VM.
>                        Independent Computing Environments
>               * null: Graphics is disabled or type not supported
>           * listen: The network which the vnc/spice server listens on.
> +    * invalid: A dict indicates which paramenters of this template are invalid.
> +        * networks *(optional)*: A list of invalid network names.
> +        * cdrom *(optional)*: A list of invalid cdrom names.
> +        * disks *(optional)*: A list of invalid volume names.
>
>   * **DELETE**: Remove the Template
>   * **POST**: *See Template Actions*