Jump to: navigation, search

Difference between revisions of "Glance-v2-v1-client-compatability"

m
m
Line 1: Line 1:
 
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, previously working, 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. Scripts relying on those fields being in the output will fail.
 
 
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
Line 69: Line 62:
 
| image-list ||  || <span style="color:green">Yes</span> || <span style="color:orange">No</span>  || v2 displays fewer fields
 
| image-list ||  || <span style="color:green">Yes</span> || <span style="color:orange">No</span>  || v2 displays fewer fields
 
|-
 
|-
| image-list || --verbose || <span style="color:green">Yes</span> || <span style="color:orange">No</span> || v2 displays fewer fields  
+
| image-list || --verbose || <span style="color:green">Yes</span> || || v2 displays fewer fields  
 
|-
 
|-
 
| image-list || --name || <span style="color:red">No</span> || <span style="color:red">No</span> || Does not exist in v2
 
| image-list || --name || <span style="color:red">No</span> || <span style="color:red">No</span> || Does not exist in v2

Revision as of 14:03, 28 August 2015

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