Skip to content
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

Uperf scale variables #250

Merged
merged 21 commits into from
Feb 12, 2021
Merged

Uperf scale variables #250

merged 21 commits into from
Feb 12, 2021

Conversation

mrbojangles3
Copy link
Contributor

These changes add the new variables from the uperf-scale enhancements to benchmark-operator. Since there are defaults provided in the python calls, I assume this change is not dependent on the forthcoming pr to benchmark operator. I am also planning on squash merging, as the intermediate commit messages are not always descriptive.

snafu/uperf_wrapper/trigger_uperf.py Show resolved Hide resolved
snafu/uperf_wrapper/uperf_wrapper.py Outdated Show resolved Hide resolved
snafu/uperf_wrapper/uperf_wrapper.py Outdated Show resolved Hide resolved
snafu/uperf_wrapper/uperf_wrapper.py Outdated Show resolved Hide resolved
@jtaleric
Copy link
Member

jtaleric commented Feb 8, 2021

Also, can we squash?

@mrbojangles3
Copy link
Contributor Author

Usually you can squash merge, its a dropdown arrow inside the green commit button.

@jtaleric
Copy link
Member

jtaleric commented Feb 8, 2021

Usually you can squash merge, its a dropdown arrow inside the green commit button.

yes! I have seen that glorious button! I actually have used it in the past too! for a simple change that doesn't seem to add a considerable amount of code, I thought a squash was simple...

@mrbojangles3
Copy link
Contributor Author

@jtaleric maybe I should rebase after making changes suggested here, hopefully the magic button will appear.

Copy link
Collaborator

@smalleni smalleni left a comment

Choose a reason for hiding this comment

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

Replied on the comment about why I would like to see the ranges as lists/arrays.

@jtaleric jtaleric requested review from dustinblack and removed request for jtaleric February 11, 2021 18:59
Copy link
Collaborator

@smalleni smalleni left a comment

Choose a reason for hiding this comment

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

Thank you for making the requested changes, LGTM

@smalleni smalleni merged commit 491034d into cloud-bulldozer:master Feb 12, 2021
"networkpolicy": self.networkpolicy
"networkpolicy": self.networkpolicy,
"density": int(self.pod_density),
"nodes_in_iter":int(self.nodes_in_iter),

Choose a reason for hiding this comment

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

this gives error as pod_density default value is ""

@@ -54,6 +54,18 @@ def __init__(self, parent_parser):
self.args.num_pairs = os.getenv("num_pairs", "")
self.args.multus_client = os.getenv("multus_client", "")
self.args.networkpolicy = os.getenv("networkpolicy", "")
self.args.nodes_in_iter = os.getenv("node_count", "")
self.args.pod_density = os.getenv("pod_count", "")

Choose a reason for hiding this comment

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

initialize pod_count to default value 0 to avoid above type conversion error

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