This PR adds a SNS event callback for each Ray cluster setup event. Tested with ray up, ray exec.
To configure, the events field must be added to the cluster config YAML
events takes the following arguments:
notification_uri: Cloud specific resource identifier for dispatching events to. This may vary based on which cloud provider you use (e.g. GCP, AWS, Azure). For this implementation, SNS topic ARNs are taken as valid input.
parameters: Arbitrary key-value parameters that you want to include into the payload of each callback. This might be useful, if for example, you need to pass in additional metadata for a particular Ray job, such as the job ID.
Why are these changes needed?
This PR adds a SNS event callback for each Ray cluster setup event. Tested with
ray up,ray exec.To configure, the
eventsfield must be added to the cluster config YAMLeventstakes the following arguments:notification_uri: Cloud specific resource identifier for dispatching events to. This may vary based on which cloud provider you use (e.g. GCP, AWS, Azure). For this implementation, SNS topic ARNs are taken as valid input.parameters: Arbitrary key-value parameters that you want to include into the payload of each callback. This might be useful, if for example, you need to pass in additional metadata for a particular Ray job, such as the job ID.This PR is rebased off of the
experimentalbranch. Old PR: https://github.com/amzn/amazon-ray/pull/96Related issue number
Checks
scripts/format.shto lint the changes in this PR.License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.