reno doesn't currently handle missing branches so we need
to use the liberty-eol tag to fix the release note job in
the gate now that origin/stable/liberty is gone.
reno will eventually check for the -eol tag when a stable
branch isn't found in:
I41ab682f081e7fd39ea534b7e2180c2109ca34ef
Change-Id: Ie54f69f5c1f91a3781c876f035fe9ed838e11c08
Change ff6b9998bb977421a5cbc94878ced8542d910c9e enforces in
a database migration that you've run the simple_cell_setup
command for cells v2 but the instructions in the error and
in the release note said to use 'nova-manage db' when it should
be 'nova-manage cell_v2'.
Change-Id: I8e71d1c7022d1000f26b7c16ed1c56f6e87ab8ac
Closes-Bug: #1649341
compute_manager config options were deprecated in
13.0.0, we can remove it now.
Depends-On: I93b62372e357db4f7c39992c244b2ec9e594ad9c
Implements: bp centralize-config-options-ocata
Change-Id: I84503655bd9675ff441073e51059202142db22ab
Almost all proxy APIs were deprecated in microversion 2.36.
But the sub-resource image-metadata of image was forgotten to deprecate.
This patch deprecates the image-metdata API from 2.39.
Implements blueprint deprecate-image-meta-proxy-api
Closes-bug: #1614578
Change-Id: I5507337ab6fe4a377f66dec3fe275d75618cd7b4
The release note added in I4052186bffa3bddb4d28e378e6a135694a71e05b
was not entirely clear on what needs to be done to enable the feature
in existing deployments. This change attempts to make things more
clear.
Change-Id: Iaa18c70b8536f01fb543cb2cf3d2e4144893b9cd
We have code going into Ocata that needs to be sure that cell and
host mappings are in place. Since this was required homework in
Newton, we can land a migration to intentionally fail if this was
not completed.
This is, however, a little difficult to require because a first-time
deployment will be initialized schema-wise with none of these records,
which is also sane. So, we look to see if any flavors are defined as
a sentinel to indicate that this is an upgrade of an existing
deployment instead of a first-time event. Not perfect, but since this
is really just a helper for the user, it seems like a reasonable
risk.
Depends-On: If1af9c478e8ea2420f2523a9bb8b70fafddc86b7
Change-Id: I72fb724dc13e1a5f4e97c58915b538ba761c582d
This patch adds support for a REST API for CRUD operations on custom
resource classes:
GET /resource_classes: return all resource classes
POST /resource_classes: create a new custom resource class
PUT /resource_classes/{name}: update name of custom resource class
DELETE /resource_classes/{name}: deletes a custom resource class
GET /resource_classes/{name}: get a single resource class
Change-Id: I99e7bcfe27938e5e4d50ac3005690ac1255d4c5e
blueprint: custom-resource-classes
The following service manager config options were deprecated in
13.0.0 and remove them now:
- metadata_manager
- console_manager
- consoleauth_manager
- cert_manager
- scheduler_manager
- conductor.manager
Implements: bp centralize-config-options-ocata
Co-Authored-By: Stephen Finucane <sfinucan@redhat.com>
Change-Id: Ia50d18c350dbc4ca88da9543e1236e3398ea28ee
This patch exposes the root (version) resource to CORS-enabled
browser clients that wish to perform API version discovery.
This feature is required for js-openstack-lib, and its devstack
tests. https://review.openstack.org/#/c/370389/
Change-Id: I4052186bffa3bddb4d28e378e6a135694a71e05b
Needed-By: Ia19afa530ae8c2df60db740cec9267fe240978c0
The code relating to this patch can be seen in:
I7096463c5eba951dd6322ee6965435e877ca0371
Partial-bug: #1633518
Change-Id: I297e138aca52ae10fbfaa50c79cf001fadaf557e
In the case that the ceph storage backing volumes is different
from the one backing ephemeral storage in nova, the auth values
in the rbd connection_info could be different and not work if
we are using the nova.conf values for ephemeral storage.
This change makes the volume connection config code for rbd
prefer the cinder connection_info values if they exist, and
only falls back to nova config values if cinder doesn't have
anything set.
Depends-On: I4655cae3212d589177d2570403b563a83aad529a
Change-Id: Idcbada705c1d38ac5fd7c600141c2de7020eae25
Closes-Bug: #1635008
These are not tested and the feature either needs test coverage or
should be deprecated. Take the latter option, deprecating the feature
for a cycle to see if anyone actually cares about the feature.
Change-Id: I90206e6554bcbf5cd9105aa975c447c69640c923
Implements: bp centralize-config-options-ocata
This is required for a decrepit version of Ubuntu. Just remove it.
Change-Id: Ica2c08fc00abb70d6ff7955bfe2b9a66e725f437
Implements: bp centralize-config-options-ocata
This extends the work done in libvirt-virtio-net-multiqueue bp to
allow for enabling multiqueue mode for vrouter VIFs (OpenContrail).
In case of vrouter mechanism is slightly different and a tap device
created by nova-compute must already be in the multiqueue mode,
when it's passed to vrouter.
Implements blueprint vif-vrouter-multiqueue
Co-Authored-By: Michal Dubiel <md@semihalf.com>
Change-Id: I7b20650c8a772fdaa05707e0dfe27ad32481a2d3
In virtuozzo 7 we have changed disk bus from sata to scsi.
Sata is not supported in virtuozzo 7.
We don't need to support sata bus for virtuozzo in nova.
Virtuozzo 6 may work with python 2.6 only and
it's not possible to run upstream nova on virtuozzo 6.
We always use this patch in our internal infrastructure
to run openstack on virtuozzo 7.
Also in this patch we have changed tests for hypervisor version.
We don't need to check libvirt version in case of Virtuozzo hypervisor.
Because Virtuozzo 7 always has libvirt with
support of 'parallels' virt type.
Docs have already been updated:
If3d2f402bb1b21bec360693a6c1e9d73e998d167
Change-Id: If3d5e39bd745c0df74316a90159fffb3221864cc
The same policy rule (os_compute_api:os-server-groups) is being used
for all actions (show, index, delete, create) for server_groups REST
APIs. It is thus impossible to provide different RBAC for specific
actions based on roles. To address this changes are made to have
separate policy rules for each of action.
It has been argued that index and show may not need separate policy
rules, but most other places in nova (and OpenStack in general) do
have separate policy rules for each action. This affords the ultimate
flexibility to deployers, who can obviously use the same rule if
that is what they want. One example where show and index may be
different is that if show is restricted based on some criteria, such
that a user is able to see some resources within the tenant but not
others, then list would need to be disallowed to prevent the user
from using list to see resources they cannot show.
Change-Id: Ica9e07f6e80257902b4a0cc44b65fd6bad008bba
Closes-Bug: #1636157
This reverts commit c07046edeee562142c90aa3cadd4bdc47b0a15da.
Trove's CI jobs don't currently work with Neutron due to
bug 1629133 so this is a temporary revert until the Trove CI/infra
networking situation gets sorted out. We have agreement from
the Trove PTL to revert this revert after the o-2 milestone on
2016/12/15.
Change-Id: Ia4fc545a10c7c16532aefd73818dd7d90c9c271b
Related-Bug: #1629133
This patch refactors volumeops.py to use os-brick for volume
related operations.
The immediate benefits are:
* FC support
* improved iSCSI MPIO support
* simplified volume connect/disconnect workflow
Change-Id: Ib21947141aadca1fa6cb99afc07a175ce14d192e
Depends-On: I19dfc8dd2e9e8a1b17675b55c63de903804480e4
Implements: blueprint hyperv-use-os-brick
