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

Clarify management and cpu interface type descriptions #1156

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

dplore
Copy link
Member

@dplore dplore commented Jul 25, 2024

Change Scope

  • Add more detail to the descriptions for cpu and management interface types.
  • Since the component tree for management and cpu interfaces both should trace up to a CPU component, more description and examples are helpful to ensure the intended types are used.

@OpenConfigBot
Copy link

OpenConfigBot commented Jul 25, 2024

No major YANG version changes in commit 780c1d4

@dplore
Copy link
Member Author

dplore commented Oct 22, 2024

Setting last call to Nov 5, 2024

@dplore dplore added the last-call PR that is in final review before merging. label Oct 22, 2024
Copy link

@s19nal s19nal left a comment

Choose a reason for hiding this comment

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

one very minor NIT and one 'simon doesn't really understand something' question :)

a system. This is sometimes also called an internal control plane
interface. On systems that represent the CPU interface(s)
as Ethernet this leaf should be used to distinguish these internal
interface from dataplane and management interfaces.";
Copy link

Choose a reason for hiding this comment

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

nit: these internal interfaces

Comment on lines +731 to +732
This interface is not connected to an INTEGRATED_CIRCUIT and
therefore not typically used for dataplane traffic. It may be
Copy link

Choose a reason for hiding this comment

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

this is the only part of the description that seems slightly off to me. I'm not sure I can come up with a better description, but why the use of capitalised 'INTEGRATED_CIRCUIT'? I think I'm likely missing the significance of this term - it makes sense that a dedicated management only interface is not designed to make use of the devices dataplane, but what is the relevance of not connecting to an IC? Surely there could be a separate IC specifically designed to handle management plane traffic?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
last-call PR that is in final review before merging. non-breaking
Projects
Status: last-call
Development

Successfully merging this pull request may close these issues.

5 participants