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

Moc protobuf change for checking TVM capabilities #179

Merged
merged 8 commits into from
Jun 22, 2023

Conversation

danmamsft
Copy link
Contributor

This is the first change for exposing TVM capabilities.
New properties are added to MOC rpc based on this design:
https://github.com/microsoft/wssdagent/blob/master/doc/features/AzureStackHCI/tvm.md

There will be followup PRs to in moc-pkg and node agent after this is checked in
I have coded up in moc-pkg to fill in these properties and tested node agent can get the properties properly.

SethBe
SethBe previously approved these changes Jun 13, 2023
Copy link
Contributor

@SethBe SethBe left a comment

Choose a reason for hiding this comment

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

:shipit:

@@ -33,6 +33,7 @@ message GPU {
message OperatingSystem {
uint64 operatingsystemsku = 1;
OperatingSystemType ostype = 2;
string operatingsystembuildnumber = 3;
Copy link
Contributor

Choose a reason for hiding this comment

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

This is looking different from the design doc. Is there a reason for the difference?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The OS version is what we want to check which is the OS build number. I named it build number to be consistent with wmi property name (the wmi property name is called build number)
Since the type is simply string, there is no need to create another type and define the type as string.

Copy link
Contributor

Choose a reason for hiding this comment

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

Makes sense. We usually align closely to azure-sdk. This makes the code extensisble when azure adds new feature.

SethBe
SethBe previously approved these changes Jun 19, 2023
Copy link
Contributor

@SethBe SethBe left a comment

Choose a reason for hiding this comment

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

:shipit:

@danmamsft danmamsft merged commit 1bf2b48 into main Jun 22, 2023
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.

3 participants