For a long time we are supporting both tenant_id and project_id for most
of the networking resources. tenant_id is deprecated since long time
already and we should stop sending it ourselves to Neutron, while
leaving it as attribute where it was present.
Change-Id: I19c4b76258eb22897b3ae5d9573b01ea4ce8022b
We need to complete rework of our cloud layer to rely on proxy layer
instead of reimplementing direct API calls. This time networking
functions are touched.
Change-Id: I23dc30abc8977c8ff14f5e7b9c9940af0d0894c7
In order to keep backward compatibility while we are switching more and
more things to the proxy layer add possibility to get attribute (in dict
style only) by server-side attribute name. While we do this inform user
not to use this anymore.
Change-Id: I981892aaba8d3f476a5d1ad71d22ab82b8798975
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as feature/r1 branch, tests will
continue to use the upper-constraints list on master.
Change-Id: I9c01131c4415ad4d0ed5c6cdc6830728734cc261
There are 2 jobs failing for a very long time and nobody taking care of
fixing them. Disable them for now while still keeping job definitions.
Change-Id: I99abe18e3d91d52fc580a3d75146d04ec3de775a
It is optional for resources to send in request's body attributes
which aren't included in mapping.
This is needed for Neutron to allow sending extra arguments in
POST/PUT requests to Neutron.
If that will be possible in SDK and OSC, Neutron team should be finally
able to deprecate (and drop) support for neutronclient CLI.
Change-Id: Ia3fd1052f438aedc6bc89bcca71834bcbafec9b9
There is currently no way to separate out statsd settings per cloud.
While you can set a prefix other than 'openstack.api', this applies to
all clouds and groups all the stats together.
While this may be what you want, it may also be not what you want :)
For example in nodepool, we have multiple cloud providers who each
have their own grafana page, so we'd like them all to log themselves
to different stats buckets (i.e. set individual prefixes).
This allows setting a "metrics" field in each individual cloud entry
that overrides the global settings. TBH I don't know if this is
important for InfluxDB as well, but I've implemented it for that too
for consistency.
Test cases are added for the global and merged settings.
I've also updated the documentation page a bit. I've separated it
into subsections for the three types of stats available. I removed
some of the in-depth stuff about logging types which wasn't that clear
(I think we can just present what we support and let people decide).
Change-Id: I9c3342161a257603f3cfd26bd03f6b71ffbfdd0d
Introduct the resource_filters resource, its attributes,
and API Calls for interacting with resource_filters.
Task: 41813 Story: 2008619
Change-Id: I03f618648da1f11583fb0dae990e0163ddc0624e
Signed-off-by: James Palmer <jpalmer7698@gmail.com>
We facing errors related to the new pip resolver, this
topic was discussed on the ML and QA team proposed to
to test lower-constraints [1].
I propose to drop this job because the complexity and recurring pain needed
to maintain that now exceeds the benefits provided by this mechanismes, and
We need to drop the lower-constraints.txt file as well as the corresponding
tox target
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html
Change-Id: Ib0ef1fadf4fe44f1d6af2f7d542b8af919652501
We are seeing an error raised by older Neutron's
400: Client Error for url: <cloud>/v2.0/security-group-rules,
Unrecognized attribute(s) 'remote_address_group_id'
This field was added unconditionally with
I50374c339ab7685a6e74f25f9521b8810c532e13 but, per above, appears to
cause problems for older Neutron instances.
To work around this, remove the argument from the body when blank by
overriding the _prepare_request function of SecurityGroupRule.
Two tests where this are used are updated; one checks the body is not
sent when None and the other is modified to send a
remote_address_group_id value to validate the other path.
Story: #2008577
Task: #41729
Change-Id: I25dabfde27b843df1c91c7fc37a1fe8d207b8010
Openstacksdk reports metrics for prometheus and adds an endpoint-label
containing the full url of every request. In case the endpoints
contain query strings this can easily cause metric explosion. To fix
this we can parse the url and strip the query string.
Change-Id: Ief3c3981a039b3ae38eeaeccd1fb70e974c94082
Compute 2.57 [1] removed the personality parameter and added the
user_data parameter to the server rebuild API. Also removed
maxPersonality and maxPersonalitySize from the limits API response.
https: //docs.openstack.org/nova/latest/reference/api-microversion-history.html#id53
Change-Id: Id098e7b9eddb2c94e93864211ab1bc6cfc068972
Neutron has got CRUD API for L3 conntrack helper since some time.
This patch adds support for it in the SDK.
Related-Bug: #1823633
Change-Id: I7614e3f4e5e3a77c7797fc5793febdcb3ad694fb
We want some functionality in osc-placement. Add it here rather than
there.
Initially only the resource providers resource type is supported.
Additional resources will be added in future patches.
We're skipping the tests for the broken placement API versions, pending
discussions with keystone folks on how to resolve this long-term.
Change-Id: Ibf5f01b842e6fc79eb95c2c21bd69732de849597
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Add the '-j auto' flag to all 'sphinx-build' invocations. While we're
here remove the unnecessary '-d DIR' argument: Sphinx will configure a
sane doctree directory for us without any special configuration. This
results in a tidy little speed boost. Before:
real 1m23.772s
user 1m9.665s
sys 0m6.299s
After:
real 0m54.613s
user 1m26.129s
sys 0m7.810s
Change-Id: Id9240456f8bb289620a64792b433dbde4fa09586
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
