nodepool/releasenotes/notes/aws-statemachine-64fe9beeef9c24b1.yaml
James E. Blair 43678bf4c1 Update AWS driver to use statemachine framework
This updates the aws driver to use the statemachine framework which
should be able to scale to a much higher number of parallel operations
than the standard thread-per-node model.  It is also simpler and
easier to maintain.  Several new features are added to bring it to
parity with other drivers.

The unit tests are changed minimally so that they continue to serve
as regression tests for the new framework.  Following changes will
revise the tests and add new tests for the additional functionality.

Change-Id: I8968667f927c82641460debeccd04e0511eb86a9
2022-02-22 17:06:07 -08:00

39 lines
1.5 KiB
YAML

---
prelude: >
The AWS driver has been updated to achieve parity with other
Nodepool drivers.
features:
- |
The AWS driver now supports rate limiting. It utilizes a two-tier
rate limiting system to match AWS's request token buckets. The
rate specified in the config file is used as the rate for mutating
requests. Non-mutating requests will have their rate limited to
10 times that amount.
- |
The AWS driver now supports quota. AWS only provides a quota
value for the number of cores.
- |
The AWS driver now support diskimage uploads.
- |
The AWS driver uses a new state machine framework within Nodepool
with significant caching in order to improve performance at scale.
- |
The AWS driver now supports IPv6 addresses.
upgrade:
- |
The AWS driver will now ignore the "Name" tag if specified.
Instead, it matches the behavior of other Nodepool drivers and
sets the instance name to the Nodepool hostname (which is derived
from the node name; e.g, "np0000000001")
deprecations:
- |
In AWS providers, the ``public-ip-address`` setting is deprecated.
Use ``public-ipv4`` or ``public-ipv6`` instead.
- |
In AWS providers, specifying image filter values as non-string
values is deprecated. The current behavior is that Nodepool
coerces non-string values (such as ``true`` or integers) into
strings, but a later version of Nodepool will produce an error.
Please update config files to use literal (quoted if necessary)
YAML strings.