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: Ic2511fc486798edb60b8f4ef7f60886663f898bd
Story: #2002586
Task: #24284
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I6e873ea38b4483ea477afcb8925fb8e60d65b60f
Adding a validation util function to help with standardising
how we do action validation, so that validation doesn't continue
after one failure.
Change-Id: I4b46fbfa1382ca94b0821a76439675120be5af60
When Adjutant has sizes defined for a service
that isn't in all regions, we need to skip that
service when doing size comparisons if the current
usage doesn't contain that service.
Change-Id: Iea6a03d97e03501fff6e0635d079759faafbd18b
* Replaces large amounts of repeated code on the task view with a
_handle_task_error() function
* try and unify error handling to always return a list 'errors' or
a dict when specific field name errors are known.
Change-Id: I9d140db0af204524eadc4ba3a6d3eb7299b239b4
Lets set a default timestamp format for any datetime
strings we know we need to parse later. While we can always
parse the direct output of what we have now, lets control it
so we always have a valid format as expected.
Change-Id: I4af359ea30ace9361c9c5d21e91a0528076eb892
This setting has been missing for quite some time and
needs to be added. While it is mostly assumed Adjutant
is running on the same network as the email server itself
TLS should really always have been used. We now have the
setting to properly turn this on and use it.
Change-Id: Ib6d54829d58df87a4b606ca316052418f5a1cfa5
* If a token is submitted to a task and that task becomes invalid
then that task is not complete and the token should not be
deleted
Change-Id: Ieb7610fd0fa9b626f0223e09661d167f92cfcaff
As much as I agree that ERP systems tend to be "eternal", I think you
meant "external" here.
Change-Id: I1c2b8e9b984fef42b1dded444e165a907cd53f62
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Because of how vague the scope of Adjutant is (for a reason)
we need a way to define what actually fits in a sensible way.
The new guide lines are part of that, and we're also now
adding a section to our docs about the project history to
explain why the scope is so vague and how it got there.
Plus a section on project features, to help define what it
can do.
Change-Id: I7d05c1f43570843171a4144ece2228efc3227cce
Adjutant didn't have a way to control is usage was to be included
with the quota data, and this caused perfomance issues when
adjutant-ui would query for all regions but not need the
usage data.
Change-Id: I50b6c19792ccf1a264bd29174f7d3f95180e0564
Update the quota logic to ignore change history
if the current change in quota is downward.
Change-Id: Iacbab882c3031db3d126a15dfb42c3cc8baa713e
Fixes-Bug: 1746137
For these exceptions it is probably safer to actually
raise them and throw a 500. That way a notification
goes out, and we deal with it and potentially rerun the
actions.
The responsibility is on the deployer to correctly configure
the QUOTA_SERVICES setting, and eventually we will also add
checking against the catalog for service types in a given
region.
Change-Id: I3fa6013cb3dd02ae40109a10c79211e55cb73ef8
Fix another issues introduced by 'Update the QUOTA_SERVICES
config to be a region mapping' and not properly testing my own
bloody logic.
Correctly process the region as a dict.
Change-Id: I69226879faf992b54727bef476aaaab4d63c737f
Introduced in 'Update the QUOTA_SERVICES config to be a region mapping'
was a pop while processing a setting. This meant following calls
already popped the setting and incorrectly executed. This makes
a local copy of the settings dict and uses that instead.
Change-Id: I72d865d4456d5779c219cf3b48557dd699c45dbc
QUOTA_SERVICES is better setup as dict of region > services
so you can control which services are active in which region.
Change-Id: I84d547fa87f8e2281638c1c93c18fb34e1d3d430
* Makes it easier to add more services to the quota actions
* Fixes issues with endpoints that don't exist
* Allows deployers to override the services using the quotas
available
Change-Id: Iff64d33a7f3773d5c9b1674c3dccb4804804b0a0
Add tests to confirm this is the case, and fix and edge
case that when notifications engines are incorrectly configured
for a task, to skip them.
Change-Id: Ib715924b4e068e3d0c9a43b55183fe86eb27e38f
* Same api changes as for pagination for task list
* Also cleans up the code for task list pagnation a little bit.
Change-Id: I45885fd6fa583fe256b2dbbb87ed92f138b75428
* Adds a test to check this as well
* Also modifies the large_cinder_only quota size
to ensure that it is not matching the same amount
as the actual large amount
Change-Id: Idd66560d27b0867c2532b8ecbfe5268bee76da8c
Fixes-Bug: 1746137
Fixes an issue where a failure during pre_approve will
incorrectly setup a task that can be revalidated and approved,
but should not be since actions will be missing.
Change-Id: I733f947851ec1dc6492ed2055df95d838d381e67
Closes-bug: bug/1745053
4.19.0 introduced use of oslo.cache which made memcache
a requirement, this broke some things, version 4.20.0
makes that lazy loaded to stop unexpected import
requirements.
Change-Id: I7bdf02307be1ce559b92da1a43b8f02c122193ce