Skip to content

Conversation

nemacysts
Copy link
Member

This requires a task_processing bump to allow for starting pods with Topology Spread Constraints (TSCs) as well as a PaaSTA one (that will be merged after this is fully deployed) to start configuring this.

NOTE: since this is adding new data that will be serialized, reverting this will not be as straightforward as reverting this commit: we would need to leave the config classes laying around so that we can still deserialize the pickles

abridged yaml of a pod launched with this: https://fluffy.yelpcorp.com/i/BV1gwjFrFGFn88cR8SPmpMwspTlmxGmj.html

This requires a task_processing bump to allow for starting pods with
Topology Spread Constraints (TSCs) as well as a PaaSTA one (that will be
merged after this is fully deployed) to start configuring this.

NOTE: since this is adding new data that will be serialized, reverting
this will not be as straightforward as reverting this commit: we would
need to leave the config classes laying around so that we can still
deserialize the pickles
@nemacysts
Copy link
Member Author

requires Yelp/task_processing#220

These should be discovered as part of the mesos_executor extra -- and
this is in fact happening on my devbox -- but for some reason GHA isn't
seeing these requirements are actually depended upon
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change really shouldn't be necessary (and check-requirements is fine internally without this) - but i couldn't figure out what's going on

(and in any case, hopefully we can de-pickle things in the near future and actually delete all the unused mesos code)

@nemacysts nemacysts requested a review from jfongatyelp October 28, 2024 20:47
@KaspariK KaspariK merged commit 01fc582 into master Oct 29, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants