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

Revise flavor naming standard according to review criticism #332

Merged
merged 8 commits into from
Aug 17, 2023
Merged

Conversation

mbuechse
Copy link
Contributor

Resolves #327

Signed-off-by: Matthias Büchse <[email protected]>
…ndard, but of the certification (which standards have to be complied with)

Signed-off-by: Matthias Büchse <[email protected]>
@mbuechse mbuechse requested a review from garloff August 16, 2023 09:44
Signed-off-by: Matthias Büchse <[email protected]>
Signed-off-by: Matthias Büchse <[email protected]>

Alternatively, if this commitment is not opportune — i.e.,
microcode updates needed for mitigation are lacking for longer than a month, default kernel/hypervisor
mitigations are disabled, or hyperthreading is enabled despite the CPU being susceptible to L1TF —,
Copy link
Member

Choose a reason for hiding this comment

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

Here my suggestion:
If a provider does not want to commit to deploy available microcode fixes and upstream kernel/hypervisor updates within a month or if the provider wants to enable hyperthreading on compute hosts despite having CPUs susceptible to L1TF there (and no SCS-accepted core-scheduling mechanism is used for mitigation), the flavors must be declared insecure with the i suffix.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. I will implement the suggestion.

garloff and others added 2 commits August 16, 2023 18:21
Signed-off-by: Matthias Büchse <[email protected]>
Copy link
Member

@garloff garloff left a comment

Choose a reason for hiding this comment

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

/lgtm

@garloff garloff merged commit 26fb468 into main Aug 17, 2023
3 checks passed
@garloff garloff deleted the issue/327 branch August 17, 2023 13:14
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.

Revise flavor naming standard according to review criticism
2 participants