| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Replace 'Assert than' with 'Assert that'.
TrivialFix
Change-Id: I426895467dfa693214f78b495d82e730f4307b9d
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's weird that the flavor-delete CLI would print out the
details of the flavor the user just deleted, rather than give
some confirmation message, or simply not print anything out
at all, which is arguably more expected behavior when deleting
a resource. This change simply removes the output on successful
deletion which brings "nova flavor-delete" more inline with other
delete CLIs, including "openstack flavor delete" behavior.
While in here, the variable and docstring code is updated to
reflect reality and a release note is added in case anyone was
ever relying on this odd behavior.
Change-Id: Ie3e07b45cc70213cde4e6077c604c9f2835c75ad
Closes-Bug: #1764420
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In documents and comments, 'GB' (gigabyte) is used.
Strictly 'GiB' (gibibyte) should be used.
So replace 'GB' with 'GiB'.
Change-Id: Ic03f202d4fe357bc6400275abdccd4b37521f4a3
Closes-Bug: #1521791
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the 'wait_for_resource_delete' method of the 'ClientTestBase' class,
the following statement is executed when timeout.
self.fail("The resource '%s' still exists." % resource.id)
The 'resource' variable is passed in the argument of
the 'wait_for_resource_delete' method.
It is sometimes a string which is a resource ID.
When it is a string (a resource ID), AttributeError is raised
at the statement.
This patch fixes the issue.
Change-Id: I558026de54a5cc75359225b50054934a220f3e5c
Closes-Bug: #1704132
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the "Update Aggregate" API,
if both an availability zone and a name are not specified,
a 400 error is returned.
It should be checked in the novaclient side (nova command).
So add the validation for it at the 'nova aggregate-update' command.
Change-Id: If50579ef3572a10b67e6da32e3258917901e9d9d
Closes-Bug: #1696891
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I5c23fc5f4e31b461255865fb8973cc05c448e364
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
|
| |/ /
| |
| |
| | |
Change-Id: I2bbc33f1b8047c28ee257f588f5b33ba0e11dbbd
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
tox: ERROR: pypy: InterpreterNotFound: pypy
Maybe we need to remove pypy-constraints from envlist in tox.ini
because there is no effect to review.
Change-Id: I1ff1cb103dcaad1396bc2bda487165feae6b0931
Closes-Bug: #1756108
|
| |/ /
| |
| |
| | |
Change-Id: Iee40a8c0d7c6732cddac59e99ee39ebe3baf68fe
|
| | |
| |
| |
| | |
Change-Id: Ic73c18e76a4200a82d88d5eb63c24eab6b15cac4
|
| | |
| |
| |
| | |
Change-Id: I34e1019d1a78344bc4d4bec72d7a8639a214933d
|
| | |
| |
| |
| | |
Change-Id: I3329b703944b9f39df1f6b70878abc0c58c2fc12
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The py27 and py35 jobs fail because the subunit-trace command
is not found. The command is utilized in tools/pretty_tox.sh.
But os-testr is not included in test-requirements.txt.
So add it to fix the gate job failures.
Change-Id: I5ea7269d75413ebcc1311e4d9e6e1d1f60092cc9
Closes-Bug: #1753898
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'cliutils.arg' has been replaced with 'utils.arg'
in the following patches.
Iaec234fbcf4d0f8c7e8f2175eae11d3083a62090
I12b03aa0a13c95ae949adf7e876c675ce309bae5
I405044af3912d86da66df05413edfc724bc102d0
I8103adafde7d8b3a101181366639314740f9a25a
So replace 'cliutils.arg' with 'utils.arg'
in a comment.
TrivialFix
Change-Id: Id26b941979dd1a94c20c05d4debcd0ed2f1470e0
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In some part in the code we import objects. In the Openstack style guidelines
they recommend to import only modules. [1]: "Do not import objects, only modules".
[1] https://docs.openstack.org/hacking/0.10.3/
Change-Id: Id4b47eeae1d3e86a3cb259c32fcb376ffbd3f8c7
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is impossible to provide a description to update method
in versions 2.0-2.18. But the docstring of the method says
that it can update a description.
Change-Id: I832e8a752779277a045bd127e2e6c6a3ae88f840
|
| | | |
| | |
| | |
| | | |
Change-Id: I7288c55f19aec77faf8d1a16ec1b625f2cc15ce1
|
| |/ /
| |
| |
| | |
Change-Id: Idab1627d1b4d6fecc02d482f931a9ae072b46f09
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I suppose that methods get_resource_manager_extra_kwargs and
add_resource_manager_extra_kwargs_hook were designed in those days when
Nova API had extensions.
Nowdays, Nova API has strict schema validation of requests, so no
additional arguments are allowed and these methods look redundant.
The fact that get_resource_manager_extra_kwargs lists of the objects
added by add_resource_manager_extra_kwargs_hook whereas
add_resource_manager_extra_kwargs_hook is not called anywhere
doesn't add chances for leaving these methods in our code.
Compatibility: both methods are designed for CLI and the CLI behaviour
will not change after removing them, so we can do a cleanup without
following standard deprecation cycle.
Change-Id: Id61457c3db8a17e2294dc579b2519873927fec48
|
| |\ \ \
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Because of encoding issue, the "nova console-log" is prone to a stack
dump, as explained in the bug report.
This patch sets the encoding output of stdout to utf8 before attempting
to print in it.
Change-Id: I63bc3dc8807021f5a97f58b0fe13a10d93688c7e
Closes-Bug: 1746534
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Output of `nova list` command contained only `max_limit` entries even
when there were more. The list needs to be obtained in multiple
requests and the paging loop was terminated prematurely.
Change-Id: I4194e6d5e34ecc0ac704851c08bb895e223aa850
Closes-Bug: 1743532
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently we can get instance usage audit logs via Nova API,
and the docs also update for it. It is necessary to add that
to our client and CLI.
This patch adds the following command.
nova instance-usage-audit-log [--before <before>]
Co-Authored-by: Takashi Natsume <natsume.takashi@lab.ntt.co.jp>
Change-Id: I4ef8e40c322f1768ee1b5e01e9681cab0e2804bd
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When starting cold migration with nova command "nova host-
servers-migrate compute-1", the migration started from all
compute hosts starting with name "compute-1", not only from
compute-1 host. The same thing happens to "nova host-meta",
"nova host-evacuate", "nova host-evacuate-live" as well.
With the "--strict" option added to these nova commands, the
action will be applied to a single compute with the exact
hostname string match, but not to the computes with hostname
substring match. Error handling is also added to these nova
commands such that when specified hostname name does not exist,
"NotFound" will be returned.
Closes-Bug: #1667794
Change-Id: I5610efa160864b0d91cd67961883a6bec5bb8dd0
|
| |\ \ \ |
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Running `nova absolute-limits` or `nova limits` can fail
when unaccounted for limits are returned
This works OK for a standard Vanilla OpenStack deployment
today, but it is quite fragile if new limit types are
introduced, or if a deployer sends back
other custom limits.
For instance, my limits include `maxTotalPrivateNetworks`
and `totalPrivateNetworksUsed` limits, which do not map
accordingly, and thus result in an error.
This happens when 'Others' field(custom limit type) is
occuring more than once which is not handled in code
causing multiple columns having same name.
Which throws exception and does not pretty prints
absolute limit.
This fix should also fix any future custom limits.
Closes-bug: #1546767
Change-Id: I1d3cf707722fc71c20cf4ec517b3f4f4875480e0
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I9f67465dc14d90d2a79bd3e3964bb4aa14a59c06
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | | |
Change-Id: I0aa83fc265f2c274d703fa402c09887b32204aa1
|
| |/ /
| |
| |
| | |
Change-Id: I241ad34451a8e1e26dd4bc679b80cc02da176d53
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are no client-side changes for this, we're just
registering the microversion support. Someone would have
to use this microversion when trying to attach a multiattach
capable volume to a server.
Related nova API change: I02120ef8767c3f9c9497bff67101e57e204ed6f4
Part of blueprint multi-attach-volume
Change-Id: Iff590954e7e12ee630140024f70c98d3cfa14a31
|
| |\ \ \
| |/ /
| | /
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add optional parameters 'limit', 'marker' and 'changes-since' to the
os-migrations endpoints for pagination.
/os-migrations?limit={limit}&marker={migrations_uuid}
/os-migrations?changes-since={changes-since}
Change-Id: I7437a61ee07c339b43d008204d1416044a407b68
Implement: blueprint add-pagination-and-change-since-for-migration-list
Depends-on: I7e01f95d7173d9217f76e838b3ea71555151ef56
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Add optional parameters 'limit', 'marker' and 'changes-since' to the
os-instance-actions endpoints for pagination.
Implement: blueprint pagination-add-changes-since-for-instance-action-list
Change-Id: Ie66d9b00c90236fdcc01aed7649dc7f163aa323e
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the 2.57 microversion, we:
* Deprecate the --file option from the nova boot and
nova rebuild CLIs and API bindings.
* Add --user-data and --user-data-unset to the nova rebuild
CLI and API bindings.
* Deprecate the maxPersonality and maxPersonalitySize fields
from the nova limits and nova absolute-limits CLIs and API
bindings.
* Deprecate injected_files, injected_file_content_bytes, and
injected_file_path_bytes from the nova quota-show,
nova quota-update, nova quota-defaults, nova quota-class-show,
and nova quota-class-update CLIs and API bindings.
Part of blueprint deprecate-file-injection
Change-Id: Id13e3eac3ef87d429454042ac7046e865774ff8e
|
| |\ \ |
|
