[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-API] RE: Questions about the api
On 20/10/10 19:42, Ian Pratt wrote: Actually, if Nexenta exposes the underlying ZFS snapshot and clone primitives, then you're probably better off just accessing the raw files directly over NFS and then using the ZFS snap API for vdi_snapshot and vdi_clone. Is there any performance benefit to using iSCSI instead of NFS for the data path layer with Nexenta?I am writing a SR for Nexenta since I haven't found one and zfs seems pretty good until now.A Nexenta SR would be a very nice thing to have. I'd recommend exposing raw files over iSCSI, and then using ZFS's native snapshot capabilities to implement the snapshot and clone APIs. Is this your plan? - Julian Thanks, IanMy questions are more related to missing(?) api calls. I need to know if I can set the following fields in a VDI for example: Is-a-snapshot - there is a get_is_a_snapshot call but not a set_is_a_snapshot. Same for snapshot-of. Think it's usefull just in case I vdi-forget the snapshot and re introduce it with a scan or in other situations. parent - there is a get_parent but not a set_parent call, this would be nice. Of course I can use sm-config for example, to set a parent but still, since the field is there I would like to set it myself. Thank you! Tomoiaga Cristian _______________________________________________ xen-api mailing list xen-api@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/mailman/listinfo/xen-api_______________________________________________ xen-api mailing list xen-api@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/mailman/listinfo/xen-api _______________________________________________ xen-api mailing list xen-api@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/mailman/listinfo/xen-api
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |