| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Iea1d529fee535fc734bf0a305686a47698aa3964
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I74feabee7cf3d9e1e87dc1dfc6fcd01935bf85ef
Story: #2002586
Task: #24315
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This patch fixes a typo in the deprecation message for
floating-ip-associate and floating-ip-disassociate.
Change-Id: I3ed2f0962949d5c755b3f1f383dbfb879a4405a0
Closes-Bug: #1765192
|
| |/
|
|
|
|
|
|
| |
Zuul v2 uses 'jenkins' as user, but Zuul v3 uses 'zuul'.
Using $USER solves it for both cases.
Change-Id: Ia3f2646bd3b5fa87c90c8dac57117fd29d73706b
(cherry picked from commit 4707422377214829126f1d6352119ea08a7ec104)
|
| |
|
|
|
|
|
| |
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I87aa9c1fb703ff14c1eb9f4a4c1810bb7a9eb1fd
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We do not need tox_install.sh, pip can handle constraints itself
and install the project correctly. Thus update tox.ini and remove
the now obsolete tools/tox_install.sh file.
This follows https://review.openstack.org/#/c/508061 to remove
tools/tox_install.sh.
Change-Id: I7f06c0be47f57a9c1ee3cadc7328b1b1b138b3cd
(cherry picked from commit aede01a0a8d21d49fc4a811650b5ae5bdcb17adc)
|
| |
|
|
|
|
|
|
|
| |
This patch moves the zuulv3 jobs for python novaclient.
Needed-By: I1508933ef77669754adf8032fc3d835960f78cb7
Needed-By: I37b02be0aeffc3a0f0516616b5294444012b8dea
Change-Id: I43a8435485751748ca6228f67d401945cb32652e
|
| |
|
|
| |
Change-Id: Id4ec07a04dc196852f59bf068281ed2ac0237511
|
| |
|
|
|
|
|
|
|
|
|
| |
Trying to boot a server while specifying multiple
--nic parameters leads to an error: Invalid nic
argument.
This patch fixes it.
Change-Id: I662fd366df8e79db1966d45a9e090087dbace4b0
Closes-Bug: #1706597
(cherry picked from commit 0a3cf89c67a3fb78876137506fe57e645f4fabe4)
|
| |
|
|
| |
Change-Id: Ie1100d8c08ff6beb90e82798e7afe6c447123778
|
| |
|
|
| |
Change-Id: I238b86e0e4932ab89e4d2ac2987c5727db1144e1
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The help text for "hypervisor-list --matching" reads,
"List hypervisors matching the given <hostname>."
This is a bit confusing, since it does talk about
hypervisors as plural, but it still talks about a
singular hostname as opposed to a pattern being matched.
Amended help text to make it clear.
Change-Id: I56fd449001289732254ea99d9b75030834491703
Closes-Bug: #1706525
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The following CLIs are doing a pattern match on the hypervisor
hostname when getting servers:
1. nova host-evacuate
2. nova host-evacuate-live (terrible name)
3. nova host-servers-migrate
4. nova host-meta (terrible name)
The fact that the hypervisor host(s) are looked up using
a pattern match is not clear in the help string for the host
argument.
This makes the help more clear and adds a warning about being
specific if you only want to target a specific host for these
operations.
In a later change we may modify the behavior in these CLIs which
allow you to find hypervisors via pattern matching, but for now
we should at least update the help text so we can backport it.
Change-Id: Icec03326bb4d9f898c04e10199038167ce5e3cce
Partial-Bug: #1667794
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Starting from microversion 2.11,
the 'force_down' parameter is returned in the response of
the "List Compute Services" API (GET /os-services).
But the service-list command does not show the 'forced_down' parameter
in the result table.
So add the 'Forced down' column in the table.
Change-Id: I79e3ba37bdf054604eab40452628dbf30014f6f1
Closes-Bug: #1706486
|
| |\ \ \
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Removed extra 'method' word from the file
api_versions.py
Change-Id: Ie0f89bdab5e3a0bd66f3cd992e03c45bda01ef1d
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Before this change, the Service object repr was
the binary for microversion < 2.53. With microversion
>= 2.53, the Service repr became the id, which is a UUID.
Using the binary never really made sense since if you have
multiple nova-compute services, the binary is going to be
the same for all of them in the repr and nothing is
distinguishable.
This changes the Service repr to just use the id, which is
going to be the integer id value if microversion < 2.53 and
the UUID id value if microversion >= 2.53.
There is no release note for this change since the repr should
not be treated as a contractual API.
Change-Id: I3a7de2683e339295022efb279828ab1a91b3b62e
|
| |\ \ \ \
| |/ / /
| | | /
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adds support for the 2.53 microversion which changes the
os-services and os-hypervisors APIs to use a UUID for the ID
value on the resource.
Also, the PUT and GET API methods have changed a bit for
both resources in this microversion, so the pythong API
bindings and command lines have been adjusted accordingly.
Part of blueprint service-hyper-uuid-in-api
Change-Id: Ic721143cc154d91e74a8a9dd2c1e991045c94305
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since we no longer have v2 extensions, the GET /os-services
response is going to have an id and disabled_reason field,
so we don't need to have conditional checks around those.
Change-Id: I5d11ffb48febb53f70bf1193b2cba5ec839a3f0d
|
| | | |
| | |
| | |
| | | |
Change-Id: I431f85c07465a184af16a9956f40396c63b05985
|
| | | |
| | |
| | |
| | | |
Change-Id: Id6714ca11b033b715004f4899b59dd6951320882
|
| |/ /
| |
| |
| | |
Change-Id: I6c7062c45fbc66512e7683552cd5fe477196c42c
|
| | |
| |
| |
| | |
Change-Id: Ia28ac9c04a663a2ce36950dae9cb9b348af01bc4
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Change I9269ffa2b80e48db96c622d0dc0817738854f602 in the Nova
server removes the need for reservations, which means that
once the server is resized in nova-compute and the vcpus and
memory_mb are changed on the instances record, the usage count
will also change, before the resize is confirmed. This means
we need to adjust the usage assertions in the resize down test.
Usage changes once the server is in VERIFY_RESIZE state, and
the usage will change again if the resize is reverted.
Note that if we were getting usage without the 'reserved'
query paramter to the 'limits' API, the behavior would have
been the same regardless of the change to Nova for counting
quotas.
Depends-On: I9269ffa2b80e48db96c622d0dc0817738854f602
Related to blueprint cells-count-resources-to-check-quota-in-api
Change-Id: I91ca0d204454987dcce1c68d9bf0f532b469df6d
|
| | | |
| | |
| | |
| | | |
Change-Id: Ia734b9f1dac610693a75df70ec1ffe0fe45dfcab
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Change-Id: Ib65894f0e128c599db8d3440fe5a8427e62d5782
Depends-On: Ifcaaf285c8f98a1d0e8bbbc87b2f57fbce057346
Implements: blueprint support-tag-instance-when-boot
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I4c242007dedf74821acae926329f4a59cedae6d5
|
| |\ \ \ \ \
| |/ / / / |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The spec [1] recommends the following sections:
- install
- contributor
- configuration
- cli
- admin
- user
- reference
Only a few of these are useful here:
- contributor
- cli
- user
- reference
Add these and populate them.
[1] specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration
Change-Id: I8a9ddcc915f25ebfaa1e994dba6c15883bd2715d
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The argument to the function should be the volume ID,
not the attachment ID.So the argument name of the
function here is easy to misunderstand.
Change-Id: Ie093b6acebe8b9e8dbdfed89856666db25bcf756
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This adds a functional test which creates a server at a larger
flavor and then resizes it down to a smaller flavor, and then
reverts the resize. It checks quota before, during and after
the resize. This is an important wrinkle with the counting
quotas changes happening in the server in Pike.
Change-Id: If1bb59e513b91a99fae2b6825248a40d8e7ac7b9
|
| |\ \ \ \ \ \
| |/ / / / /
| | | | / /
| |_|_|/ /
|/| | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With the upcoming counting quotas changes in Nova, and the
fact the novaclient functional tests are run in serial with
the same tenant, it would be useful to validate that
"nova resize-confirm" works as expected and that the quota usage
before, during and after the resize is confirmed is as expected,
that is, when resizing we expect the quota usage to change.
Change-Id: Id5be8edfde446b9e714460a606b446a2daf64007
|
| | | | |
| | | |
| | | |
| | | | |
Change-Id: I7ec074495426c43bb20f7d3c00ee1a122c351e87
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The 2.51 microversion adds the 'volume-extended' server
external event to the os-server-external-events API.
This is an admin-only API by default and this event is
currently only used by Cinder as part of extending the
size of an attached volume, and therefore does not
have any CLI or python API binding impacts in the client.
Part of blueprint nova-support-attached-volume-extend
Change-Id: I8293704dbb4f75306fe32d3a0118d5bf42c8457e
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds support for the 2.50 microversion which does the following:
* Adds the server_groups and server_groups_members resources to the output
for the 'nova quota-class-show' and 'nova quota-class-update' CLIs.
* Removes the ability to show or update network-related resource quota class
values, specifically floating_ips, fixed_ips, security_groups and
security_group_members.
* Defines explicit kwargs for the update() method in the python API binding.
This also fixes a problem where the 'nova quota-class-update' CLI was
incorrectly capped at the 2.35 microversion for updating network-related
resources. That was true for the os-quota-sets API which is tenant-specific,
but not for the os-quota-class-sets API which is global.
Functional tests are added for the 2.1 and 2.50 microversion behavior for
both commands.
Part of blueprint fix-quota-classes-api
Change-Id: I2531f9094d92e1b9ed36ab03bc43ae1be5290790
|
| | | |
| | |
| | |
| | | |
Change-Id: I4d947576ce0e8bfe1fda9d662faac7d32c1f32f3
|
