Pike Series Release Notes¶
9.1.1¶
Bug Fixes¶
Fix an ability to boot server with multiple nics which was broken with microversion 2.42 (fix tag attribute disappearing).
9.1.0¶
Nouvelles fonctionnalités¶
Added support for microversion 2.47 which returns the flavor details directly embedded in the server details when listing or showing servers. With this change, CLI requests with microversion >= 2.47 will no longer need to do additional queries to get the flavor and flavor extra_specs information. Instead, the flavor information will be output as separate key/value pairs with the keys namespaced with the « flavor: » prefix. As one would expect, these keys can also be specified as output fields when listing servers, like this:
nova list --fields name,flavor:original_nameWhen displaying details of a single server, the
--minimaloption will display aflavorfield with a value of theoriginal_nameof the flavor. Prior to this microversion the value was theidof the flavor.
Added support for microversion 2.49 that enables users to attach tagged interfaces and volumes. A new
--tagoption is added tonova volume-attachandnova interface-attachcommands.
Microversion 2.52 is now supported which adds the
--tagsoption to thenova bootcommand and atagskwarg to thenovaclient.v2.servers.ServerManager.create()python API binding method.
Added support for microversion 2.53. The following changes were made for the
servicescommands and python API bindings:The
nova service-listcommand and API will have a UUID value for theidfield in the output and response, respectively.The
nova service-enablecommand and API will require a UUID service id value to uniquely identify the service rather than ahostandbinaryvalue. The UUIDidfield will also be in the command output.The
nova service-disablecommand and API will require a UUID service id value to uniquely identify the service rather than ahostandbinaryvalue. The UUIDidfield will also be in the command output.The
nova service-force-downcommand and API will require a UUID service id value to uniquely identify the service rather than ahostandbinaryvalue. The UUIDidfield will also be in the command output.The
nova service-deletecommand and API will require a UUID service id value to uniquely identify the service rather than an integer service id value.
The following changes were made for the
hypervisorscommands and python API bindings:The ID field in the various
nova hypervisor-*commands andHypervisor.idattribute in the API binding will now be a UUID value.If paging over hypervisors using
nova hypervisor-list, the--markermust be a UUID value.The
nova hypervisor-showandnova hypervisor-uptimecommands and APIs now take a UUID value for the hypervisor ID.
Notes de mises à jours¶
The
novaclient.v2.quota_classes.QuotaClassSetManager.updatemethod now defines specific kwargs starting with microversion2.50since updating network-related resource quota class values is not supported on the server with microversion2.50. The list of excluded resources is:fixed_ipsfloating_ipsnetworkssecurity_groupssecurity_group_rules
Notes dépréciées¶
The
binaryargument to thenova service-enable,nova service-disable, andnova service-force-downcommands has been deprecated. The only binary that it makes sense to use isnova-computesince disabling a service likenova-schedulerornova-conductordoes not actually do anything, and starting in the 16.0.0 Pike release the compute API will not be able to look up services other thannova-computefor these operations.
Bug Fixes¶
Adds support for the
2.50microversion which fixes thenova quota-class-showandnova quota-class-updatecommands in the following ways:The
server_groupsandserver_group_membersquota resources will now be shown in the output table fornova quota-class-show.The
floating_ips,fixed_ips,security_groupsandsecurity_group_rulesquota resources will no longer be able to be updated usingnova quota-class-updatenor will they be shown in the output ofnova quota-class-show. Use python-openstackclient or python-neutronclient to work with quotas for network resources.
In addition, the
nova quota-class-updateCLI was previously incorrectly limiting the ability to update quota class values forfloating_ips,fixed_ips,security_groupsandsecurity_group_rulesbased on the 2.36 microversion. That has been changed to limit based on the2.50microversion.
9.0.0¶
Nouvelles fonctionnalités¶
novaclient now adds information about itself to the keystoneauth user-agent. Adding information about wrapping libraries or consuming applications can be found at https://docs.openstack.org/developer/python-novaclient/api.html
A new
global_request_idparameter is accepted on the client constructor, which will then passX-OpenStack-Request-IDon all requests made.
A new
--instance-uuidoption is added tonova migration-listcommand. This is used to query the migration history of a specific server by the migration-list command. Please usenova server-migration-listcommand for querying in-progress migrations of a specific server.
Support was added for microversion 2.45. This changes how the
createImageandcreateBackupserver action APIs return the created snapshot image ID in the response. With microversion 2.45 and later, the image ID is return in a json dict response body with animage_idkey and uuid value. The oldLocationresponse header is no longer returned in microversion 2.45 or later.There are no changes to the
nova image-createCLI. However, thenova backupCLI will print out the backup snapshot image information with microversion 2.45 or greater now.
Notes de mises à jours¶
The following deprecated options have been removed:
--tenant(fromflavor access list)--cell_name(frommigration list)--volume-service-name(global option)
remove version 1.1 API support as we only support v2 and v2.1 API in nova side now.
Notes dépréciées¶
The
nova x509-create-certandnova x509-get-root-certcommands andnovaclient.v2.certsAPI binding are now deprecated and will be removed in the first major release after the Nova server 16.0.0 Pike release.
The os-cloudpipe API has been removed from Nova. As a result, the
nova cloudpipe-list,nova cloudpipe-create, andnova cloudpipe-configurecommands and thenovaclient.v2.cloudpipeAPI bindings are now deprecated, and will be removed in the first major release after the Nova server 16.0.0 Pike release.
The following CLIs and their backing API bindings are deprecated and capped at microversion 2.43:
nova host-describe- superseded bynova hypervisor-shownova host-list- superseded bynova hypervisor-listnova host-update- superseded bynova service-enableandnova service-disablenova host-action- no alternative by design
The CLIs and API bindings will be removed in the first major release after Nova 16.0.0 Pike is released.
The following CLIs and their backing API bindings are deprecated and capped at microversion 2.44:
nova add-fixed-ip: use python-neutronclient or openstacksdknova remove-fixed-ip: use python-neutronclient or openstacksdknova floating-ip-associate: use python-neutronclient or openstacksdknova floating-ip-disassociate: use python-neutronclient or openstacksdknova virtual-interface-list: there is no replacement as this is only implemented for nova-network which is deprecated
The CLIs and API bindings will be removed in the first major release after Nova 16.0.0 Pike is released.
Bug Fixes¶
Microversion 2.42 is related to the following bug.
The following options have been changed as of Microversion 2.42.
Remove
tagattribute in--block-deviceoption on the server boot (nova boot) between microversion 2.33 and 2.41.Remove
tagattribute in--nicoption on the server boot (nova boot) between microversion 2.37 and 2.41.
8.0.0¶
Prelude¶
Deprecated image commands and python API bindings have been removed.
Deprecated network-related resource commands and python API bindings have been removed. From this point on, python-novaclient will no longer work with nova-network except for the nova virtual-interface-list, nova add-fixed-ip and nova remove-fixed-ip commands.
Notes de mises à jours¶
The deprecated name and availability_zone positional arguments in the
nova aggregate-updatecommand have been removed. Use the--nameand--availability-zoneoptions instead.
The following deprecated image commands have been removed:
* nova image-list * nova image-show * nova image-meta * nova image-delete
Along with the related python API bindings in
novaclient.v2.images.
The following deprecated network-related resource commands have been removed:
* nova dns-create * nova dns-create-private-domain * nova dns-create-public-domain * nova dns-delete * nova dns-delete-domain * nova dns-domains * nova dns-list * nova fixed-ip-get * nova fixed-ip-reserve * nova fixed-ip-unreserve * nova floating-ip-create * nova floating-ip-delete * nova floating-ip-list * nova floating-ip-bulk-create * nova floating-ip-bulk-delete * nova floating-ip-bulk-list * nova floating-ip-pool-list * nova net * nova net-create * nova net-delete * nova net-list * nova network-create * nova network-delete * nova network-list * nova network-show * nova network-associate-host * nova-network-associate-project * nova network-disassociate * nova scrub * nova secgroup-create * nova secgroup-delete * nova secgroup-list * nova secgroup-update * nova secgroup-add-rule * nova secgroup-delete-rule * nova secgroup-list-rules * nova secgroup-add-default-rule * nova secgroup-delete-default-rule * nova secgroup-list-default-rules * nova secgroup-add-group-rule * nova secgroup-delete-group-rule * nova tenant-network-create * nova tenant-network-delete * nova tenant-network-list * nova tenant-network-show
Along with the following python API bindings:
* novaclient.v2.contrib.tenant_networks * novaclient.v2.fixed_ips * novaclient.v2.floating_ip_dns * novaclient.v2.floating_ip_pools * novaclient.v2.floating_ips * novaclient.v2.floating_ips_bulk * novaclient.v2.fping * novaclient.v2.networks * novaclient.v2.security_group_default_rules * novaclient.v2.security_group_rules * novaclient.v2.security_groups
The baremetal CLIs and python API bindings were deprecated in the Newton release and have been removed. Use python-openstackclient or python-ironicclient for CLIs. Use python-ironicclient or openstacksdk for python API bindings
Notes dépréciées¶
CLI argument
--cell_namefornova migration-listcommand is deprecated. Nova API does not have logic for handling cell_name parameter in os-migrations, and while the parameter is passed to Nova it has never been used.
The
only_contribparameter for thenovaclient.client.discover_extensionsmethod is deprecated and now results in an empty list returned since all contrib extensions are either required or have been removed.