![Will Szumski](/assets/img/avatar_default.png)
This will wait for any resources that are created to become available before exiting the script. This allows you to avoid a race condition where a server could be created before the resource tracker had been updated with the new resources; server creation would fail. Change-Id: I57f8c93cb1ebbc284b96ef1ced2c4edd59b27795 Story: 2004274 Task: 27823 Depends-On: https://review.openstack.org/617642
29 lines
1.1 KiB
YAML
29 lines
1.1 KiB
YAML
---
|
|
|
|
# A list of dictionaries, each with the following keys:
|
|
# * resource_class - the name of the resource class that you want to be
|
|
# available
|
|
# * traits - a list of traits a provider requires before that provider is
|
|
# considered to provide that resource
|
|
# * amount - natural number representing the amount of the resource that
|
|
# should be available. This will be tested against the total resource count
|
|
# minus the amount that is reserved.
|
|
wait_for_resources_required_resources:
|
|
|
|
# Virtualenv containing OpenStack client
|
|
wait_for_resources_venv:
|
|
|
|
# The resources are polled this many times. The delay between each iteration
|
|
# is also configurable, but defaults to 10 seconds
|
|
wait_for_resources_retry_limit: 15
|
|
|
|
# The delay between each iteration.
|
|
wait_for_resources_delay:
|
|
|
|
# The URL of the upper constraints file to pass to pip when installing Python
|
|
# packages.
|
|
wait_for_resources_python_upper_constraints_url:
|
|
|
|
# Path on the remote machine to copy the python requirements file to
|
|
wait_for_resources_python_requirements_path: /tmp/wait-for-python-requirements.txt
|