Glance-v2-v1-client-compatability

This is an overview of the effects of the non-backwards compatibility of the prospective 1.0.0 glance client (which defaults to v2) on existing glance cli scripts.

Note: "Input compatible: No" means that any existing glance cli script with the specified arguments will fail with the new client.

Note: "Output compatible: No" means that the output to stdout is missing some fields, or ordering is reversed. Scripts relying on those fields/order being the same in the output will fail.

command	sub-command	Input Compatible	Output Compatible	Notes
image-create		Yes	No	Slightly different output
image-create		Yes	No	Slightly different output
image-create	--id	Yes	No	Slightly different output
image-create	--name	Yes	No	Slightly different output
image-create	--owner	No	No	Slightly different output
image-create	--size	No		Not implemented in v2 client
image-create	--store	No		Not implemented in v2 client
image-create	--min-disk	Yes	No	Slightly different output
image-create	--min-ram	Yes	No	Slightly different output
image-create	--location	No		Not implemented in v2 client
image-create	--owner	Yes	No	Slightly different output
image-create	--file	Yes	No	Slightly different output
image-create	--checksum	No		Not implemented in v2 client
image-create	--copy-from	No		Not implemented in v2 server
image-create	--is-public	No		Replaced with --visibility in v2 client
image-create	--is-protected	No		Not implemented in v2 client
image-create	--property	Yes	No	Slightly different output
image-create	--progress	Yes	No	Slightly different output
command	sub-command	Input Compatible	Output Compatible	Notes
image-delete	<IMAGE_UUID>	No	Yes	v2 client cannot accept more than one image to delete
image-delete	<IMAGE_NAME>	No		v2 client does not accept a name
command	sub-command	Input Compatible	Output Compatible	Notes
image-download	<IMAGE_UUID>	Yes	Yes	Note: bug 1488914
image-download	<IMAGE_NAME>	No		v2 client does not accept an image name.
image-download	--file	Yes	Yes
image-download	--progress	Yes	Yes
command	sub-command	Input Compatible	Output Compatible	Notes
image-list		Yes	No	v2 client displays fewer fields
image-list	--verbose	Yes	No	v2 client displays fewer fields
image-list	--name	No		Not implemented in v2 client
image-list	--status	No		Not implemented in v2 client
image-list	--container-format	No		Not implemented in v2 client
image-list	--disk-format	No		Not implemented in v2 client
image-list	--size-min	No		Not implemented in v2 client
image-list	--size-max	No		Not implemented in v2 client
image-list	--property-filter	Yes	No	v2 client displays fewer fields
image-list	--page-fize	Yes	No	v2 client displays fewer fields
image-list	--human-readable	No		Not implemented in v2 client
image-list	--sort-key	Yes	No	v2 client sorts in the opposite direction
image-list	--sort-dir	Yes	No	v2 client displays fewer fields
image-list	--is-public	No		Not implemented in v2 client (ignored/broken in v1?)
image-list	--owner	Yes	No	v2 client displays fewer fields
image-list	--all-tenants	No		Not implemented in v2 client
command	sub-command	Input Compatible	Output Compatible	Notes
image-show	<IMAGE_UUID>	Yes	No	Slightly different output
image-show	<IMAGE_NAME>	No		v2 client does not accept a name
image-show	--human-readable	Yes	No	Slightly different output
image-show	--max-column-width	Yes	No	Slightly different output
command	sub-command	Input Compatible	Output Compatible	Notes
image-update	<IMAGE_UUID>	Yes	No	Slightly different output
image-update	<IMAGE_NAME>	No		v2 client does not accept a name.
image-update	<data on stdin>	No	No	v2 client ignores data on stdin
image-update	--name	Yes	No	Slightly different output
image-update	--disk-format	Yes	No	Slightly different output
image-update	--container-format	Yes	No	Slightly different output
image-update	--owner	Yes	No	Slightly different output . (v1 returns 0 indicating success -- bug?)
image-update	--container-format	Yes	No	Slightly different output
image-update	--size	No		Not implemented in v2 client
image-update	--min-disk	Yes	No	Slightly different output
image-update	--min-ram	Yes	No	Slightly different output
image-update	--location	No		Not implemented in v2 client
image-update	--file	No		Not implemented in v2 client
image-update	--checksum	No		Not implemented in v2 client
image-update	--copy-from	No		Not implemented in v2 client
image-update	--is-public	No		Not implemented in v2 client (Replaced with visibility)
image-update	--is-protected	No		Not implemented in v2 client
image-update	--property	Yes	No	Slightly different output
image-update	--purge-props	No		Not implemented in v2 server
image-update	--human-readable	No		Not implemented in v2 client
image-update	--progress	No		Not implemented in v2 client
command	sub-command	Input Compatible	Output Compatible	Notes
member-create	<IMAGE_UUID>	Yes	Yes	displays additional output
member-create	<IMAGE_NAME>	No		v2 client does not support a name
member-create	--can-share	No		Not implemented in v2 client (server?)
command	sub-command	Input Compatible	Output Compatible	Notes
member-delete	<IMAGE_UUID>	Yes	Yes
member-delete	<IMAGE_NAME>	No		v2 client does not support a name
command	sub-command	Input Compatible	Output Compatible	Notes
member-list	--image-id	Yes	No	v2 client displays different output
member-list	--tenant-id	No		Not implemented in v2 client