Felix Edel 040c5c8032 Move parent provider determination to pipeline manager ... Moving the parent provider determination into the pipeline manager allows us to remove the buildset and job objects from the NodeRequest constructor. This way we can fully serialize the NodeRequest to ZooKeeper and restore it without missing important information. This has also an impact on the NodeRequest's priority property. As this is only needed to determine the znode path when the NodeRequest is submitted, we can provide it directly as parameter to the submitNodeRequest call (and the related update callbacks). To ensure that NodePool doesn't strip those additional information when it fulfills the NodeRequest, we use the new "requestor_data" field which is implemented in [1]. To make this work, we also have to look up the buildset by its UUID from the active tenants and pipelines when the NodesProvisioned event is handled in the scheduler. Something similar was already done for handling the other result events as well. [1]: https://review.opendev.org/c/zuul/nodepool/+/798746/ Depends-On: https://review.opendev.org/c/zuul/nodepool/+/798746/ Change-Id: Id794643dcf26b0565499d20adba99d3b0518fdf1		2021-07-08 13:27:08 -07:00
..
__init__.py	Add nodepool integration test	2017-01-24 13:37:21 -08:00
test_nodepool_integration.py	Move parent provider determination to pipeline manager	2021-07-08 13:27:08 -07:00