Jump to: navigation, search

Difference between revisions of "Openstackclient-glance-imagecreate-v1-v2"

m
 
Line 36: Line 36:
 
| osc image create || --force || 2 || This relates to volume.
 
| osc image create || --force || 2 || This relates to volume.
 
|-
 
|-
| osc image create || --checksum <checksum> || 1 || This could be implemented client side, as the server no longer supports it.
+
| osc image create || --checksum <checksum> || 1 || This could be implemented client side, as the server no longer supports it. Needs investigation. If this was left out of v2 on purpose?
 
|-
 
|-
 
| osc image create ||--owner <tenant>  || 1 || Possibly should be a 2 as this could be due to the fact that the v2 server should support this else it can be done by linking a create and then an update the owner field.
 
| osc image create ||--owner <tenant>  || 1 || Possibly should be a 2 as this could be due to the fact that the v2 server should support this else it can be done by linking a create and then an update the owner field.

Latest revision as of 14:42, 16 September 2015

This page shows the changes that will need to be made to implement changes to the osc (openstack client), when moving from glance image create version one, to version two. As the sever has made some backwards incompatible changes. This could lead to a detrimental effect when updating the glance client to use version two, as it could break people scripts ect.

This page uses the following rating system.

  • 2 - The Good - v2 functionality that can be mapped onto v1 without problems.
  • 1 - The Bad - Partial functionality in version 2 compared to version 1.
  • 0 - The Ugly - No functionality similarities between v1 and v2.
Command Sub-Command Rating Notes
osc image create 'name' 2 This a positional argument.
osc image create *stdin* 2 Takes standard input.
osc image create --id <id> 2
osc image create --container-format <format> 2
osc image create --disk-format <format> 2
osc image create --min-disk <disk-gb> 2
osc image create --min-ram <ram-mg> 2
osc image create --file <local-filename> 2
osc image create --protected / --unprotected 2 Mapped to new format from is-protected to protected
osc image create --public / --private 2 These would have to be mapped onto the new format of visibility public/private.
osc image create --property <key=value> 2 Different properties available/restricted.
osc image create --volume <volume> 2 Not glance related? Since taking out of cinder? Therefore should just work.
osc image create --force 2 This relates to volume.
osc image create --checksum <checksum> 1 This could be implemented client side, as the server no longer supports it. Needs investigation. If this was left out of v2 on purpose?
osc image create --owner <tenant> 1 Possibly should be a 2 as this could be due to the fact that the v2 server should support this else it can be done by linking a create and then an update the owner field.
osc image create --location <image-url> 1 It may be possible with the location-add command, however unsure about that.
osc image create --store <store> 0? Needs investigation. If this was left out of v2 on purpose?
osc image create --size <size-bytes>  ? Needs investigation. If this was left out of v2 on purpose?
osc image create --copy-from <image-url> 0 The v2 server no longer supports this.