-
Notifications
You must be signed in to change notification settings - Fork 3
Blueprint documentation #23
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
base: main
Are you sure you want to change the base?
Conversation
ajbalogh
left a comment
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.
this mr needs to reflect the new xpu choice, also i had originally pushed for a flat directory structure but we should start nesting blueprints under company like Winston has suggested
I have done changes for xpu in PR 24: #24 |
|
|
||
| Device blueprints enable you to instantiate specific device types using the Infragraph schema format. Each blueprint encapsulates attributes, component definitions, and configuration logic that represent actual hardware or node types within a network topology. | ||
|
|
||
| All device blueprints are organized under: |
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.
Winston would like to see device blueprints organized under an additional level, by vendor - so dgx and cx5 would go under nvidia
ajbalogh
left a comment
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.
code shouldn't be included in a doc, it should come from src
No description provided.