Skip to content
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.

Allow random cluster selection when no override #117

Merged
merged 1 commit into from
Aug 25, 2020
Merged

Conversation

honnix
Copy link
Member

@honnix honnix commented Aug 24, 2020

TL;DR

In case there is no override in resource table, we should allow the code to go through and apply non-label based weighted random selection.

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added
  • Any pending items have an associated Issue

Complete description

As commented, it makes more sense to let the code go through and apply different selection.

BTW these unit tests relies on GOPATH and we should fix that.

Tracking Issue

Will create later
https://github.com/lyft/flyte/issues/

Follow-up issue

NA

In case there is no override in resource table, we should allow the code
to go through and apply non-label based weighted random selection.
@codecov-commenter
Copy link

Codecov Report

Merging #117 into master will increase coverage by 0.07%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #117      +/-   ##
==========================================
+ Coverage   62.32%   62.39%   +0.07%     
==========================================
  Files         104      104              
  Lines        7753     7752       -1     
==========================================
+ Hits         4832     4837       +5     
+ Misses       2351     2345       -6     
  Partials      570      570              
Flag Coverage Δ
#unittests 62.39% <ø> (+0.07%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...g/executioncluster/impl/random_cluster_selector.go 80.39% <ø> (+5.63%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d094408...b76ec5c. Read the comment docs.

@honnix honnix changed the title [WIP] Allow random cluster selection when no override Allow random cluster selection when no override Aug 25, 2020
@honnix honnix merged commit 6985f7a into master Aug 25, 2020
@honnix honnix deleted the allow-non-overridden branch August 25, 2020 07:49
schottra added a commit that referenced this pull request Sep 8, 2020
* master:
  Gcs remote data (#121)
  Do not depend on GOPATH to locate test data (#122)
  Add index to optimize for list task executions for node execution (#120)
  Grpc health checking (#118)
  Allow random cluster selection when no override (#117)
eapolinario pushed a commit that referenced this pull request Sep 6, 2023
In case there is no override in resource table, we should allow the code
to go through and apply non-label based weighted random selection.

Close flyteorg/flyte#481
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants