Skip to content

Synchronise master with upstream - #120

Closed
github-actions[bot] wants to merge 14 commits into
stackhpc/masterfrom
upstream/master-2026-06-03
Closed

Synchronise master with upstream#120
github-actions[bot] wants to merge 14 commits into
stackhpc/masterfrom
upstream/master-2026-06-03

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown

This PR contains a snapshot of master from upstream master.

JohnGarbutt and others added 13 commits September 26, 2024 15:49
With the flavor reservation plugin, it has made some calcuation
on what the flavor chosen means in terms of resources.
This is exactly the sort of information that is needed by an
external enfrocement service, to track how many resource hours
are being comsumted by each reservation. As such, we find a way
to send this extra information to the external enforcement service.

Change-Id: I168a2e90735226676cd573fc1a3c316efde1f6d1
This change allows for users to configure blazar to call out to
an external enforcement API with a bearer token.
This is very handy when you create an enforcement API using
the Django Rest Framework.

Change-Id: I772db7c85620d7a9f0fc1b7aa10f73a96bc86a5f
To keep track of resource usage in an external enforcement service,
its really important for the lease_id to be passed to the external
service.

Change-Id: I953cf73891f27bd649ba27db9769f11f8fe98d59
The follow on change was cusing problems with the tox
complexity checker. This gives that change some head room.

Change-Id: Ic2378b6b7e856f99b31fcb2c8eb1dd1e0742b05d
If we use check_create to keep state about reserverations
we need an on_end callback to be attempted when the lease
is deleted early due to a failure, such as reserve_resource
failing due to some race with another reservation request.

In other error cases, we would expect a lease db object
to still be created at the end of the create lease call,
such that delete will be called that triggers on_end.

One alternative is to move check_create after operations
such as reserve_resource, but in that case we need to
make all of the plugins capable of cleaning up the resources
they have just created, which seems a bad idea when it is
not uncommon that a request is rejected due to the
enforcement logic.

Change-Id: If4ff1c8da32c3be47bf1523058f83effd7340f02
Option to just do the enforcement check and resource allocations check,
but not actually create the resources.

Change-Id: I150e3f0caad1ab5196d54e75d0ff366ec66797a7
C901 Function is too complex is catching ManagerService.create_lease()
because the function has more than 5 potential branches.

Because the function is in WIP in master branch, ignore C901 at least
until the function is in stable state.
Add C901 to ignore list of pep8
feat: automatic update of workflows stackhpc/master
feat: automatic update of community files stackhpc/master
@github-actions
github-actions Bot requested a review from a team as a code owner June 3, 2026 13:52
@github-actions github-actions Bot added automated Automated action performed by GitHub Actions synchronisation labels Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated action performed by GitHub Actions synchronisation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants