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

Safenode numbering does not lend itself to easy display and sorting #2036

Open
willief opened this issue Aug 10, 2024 · 1 comment
Open

Safenode numbering does not lend itself to easy display and sorting #2036

willief opened this issue Aug 10, 2024 · 1 comment

Comments

@willief
Copy link
Contributor

willief commented Aug 10, 2024

The existing convention of numbering nodes from safenode1 up does not lend itself to optimal display and sorting.
Consider using a three digit node identifier with leading zeroes from safenode001 up to allow more convenient display and sorting.

@willief
Copy link
Contributor Author

willief commented Aug 10, 2024

This will obviously limit us to <999 nodes per machine. As it stands, that is not an issue. A further digit could be added to future-proof this but current thinking is for relatively small numbers of nodes per machine so this is a far out edge case.

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

No branches or pull requests

1 participant