-
Notifications
You must be signed in to change notification settings - Fork 8
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
Supporting deployments on zos4 nodes #3497
base: development
Are you sure you want to change the base?
Conversation
…m and wireguard to filters in all solutions
…ethods to support zos4 deployments
…ork light primitive
…yment, removing unnecessary comments and adding descriptive ones
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.
partial review will continue tmw
packages/playground/src/components/node_selector/TfManualNodeSelector.vue
Outdated
Show resolved
Hide resolved
packages/playground/src/components/node_selector/TfManualNodeSelector.vue
Show resolved
Hide resolved
packages/playground/src/components/node_selector/TfManualNodeSelector.vue
Show resolved
Hide resolved
} | ||
|
||
class ZmachineLightNetwork { | ||
//what is ValidateNested |
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.
please remove this comment
@@ -142,6 +142,7 @@ class MachineModel { | |||
@Expose() @IsInt() @IsOptional() solutionProviderId?: number; | |||
@Expose() @IsString() @IsOptional() zlogsOutput?: string; | |||
@Expose() @IsString({ each: true }) @IsOptional() gpus?: string[]; | |||
@Expose() @IsString({ each: true }) @IsOptional() features?: 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.
do we need this ?
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.
yes we do as it might be used like this
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.
As I mentioned before, I think we should have an enum for the possible values inside the array
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.
can we use the feature type here instead of the string ?
…n AddMachine filters and moving getFeatures method to utils
observe what ? in the tested scenarios please specify expected result |
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.
partial review will continue reviewing the other files
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 that we are handling the case if the worker or master has unsupported features; we need to test this case
@@ -142,6 +142,7 @@ class MachineModel { | |||
@Expose() @IsInt() @IsOptional() solutionProviderId?: number; | |||
@Expose() @IsString() @IsOptional() zlogsOutput?: string; | |||
@Expose() @IsString({ each: true }) @IsOptional() gpus?: string[]; | |||
@Expose() @IsString({ each: true }) @IsOptional() features?: 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.
As I mentioned before, I think we should have an enum for the possible values inside the array
Adjusted test scenarios with expected result |
…zmachine light in one condition to get rid of redundant code
…hineData, some updates in networklight primitive
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.
Node 249 isn't a valid node as it has zero vcores, so the automated selection is right. After some debugging, I figured out that the manual selection doesn't validate cru, mru and sru. For some reason this switch isn't entered. As This's not related to my pr please open a new issue |
Description
Supporting deployments on zos4 nodes from grid client and dashboard
Changes
Related Issues
Tested Scenarios
Node 168 which is a zos3 node
Node 255 which is a zos4 node
Go to Dashboard
Go to Dashboard
Checklist