-
Notifications
You must be signed in to change notification settings - Fork 511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[refactor][plugin] RayClusterSpecObject #3238
Conversation
type RayClusterYamlObject struct { | ||
ClusterName string | ||
Namespace string | ||
Labels map[string]string | ||
Annotations map[string]string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I folded this struct into RayClusterSpecObject
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#3225's very similar RayClusterConfig and rayClusterSpecObjectFromConfig() motivated this PR.
56968e6
to
cfaabee
Compare
rebased to fix conflicts |
WorkerMemory string | ||
WorkerEphemeralStorage string | ||
WorkerReplicas int32 | ||
Context *string `yaml:"context,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why YAML tags in both RayClusterSpecObject and RayClusterConfig?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think RayClusterConfig is introduced yet? I will rename this struct to RayClusterConfig in #3225.
so we can use it for [this proposed cluster config schema][1]. We change in a backwards-compatible way to support multiple worker groups and other fields in the schema. [1]: https://docs.google.com/document/d/18V5_7SGUzS0LGlaJB7xus04omyr3drKkK4vV6Kz14jY/edit?tab=t.0#heading=h.tuqyq1b6b2x7 Signed-off-by: David Xia <[email protected]>
so we can use it for this proposed cluster config schema. We change in a backwards-compatible way to support multiple worker groups and other fields in the schema.
Checks