----- Original Message -----
> From: "Adam Litke" <a...@us.ibm.com>
> To: vdsm-devel@lists.fedorahosted.org
> Sent: Friday, December 23, 2011 2:52:06 AM
> Subject: VDSM Data Types
>
> This week I spent some time analyzing the parameters that must be
> passed to all
> of the different VDSM API calls. For those involving complex types
> (dictionaries with required keys, magic strings, etc) I have
> attempted to
> document the required format and meaning of the required data. The
> document is
> in the ovirt wiki: http://ovirt.org/wiki/Vdsm_datatypes . Please
> take a look
> and correct any inaccuracies. Next, I would like to document complex
> return
> values.
>
Have not looked on all types, but at least VM_Create_t will be changed in next
version (3.1), of course we'll keep backward compatibility.
We must do it to support in several new features in 3.1
Regards,
Igor Lvovsky
> One of the reasons I have done this work is in an attempt to drive
> some
> improvements into the API redesign I am working on. I think the
> structure of
> the parameters and return values should be codified somehow. I
> noticed in
> storage_connection.py that there is some validation being performed
> on the
> connection information. Do people agree that this could be way
> forward for
> field validation? Are there better methods? Thanks for your
> comments on this
> issue!
>
> --
> Adam Litke <a...@us.ibm.com>
> IBM Linux Technology Center
>
> _______________________________________________
> vdsm-devel mailing list
> vdsm-devel@lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/vdsm-devel
>
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel
