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
[RA2 Ch4] Is there a need for different node labels for the different Cloud Infrastructure Profiles? #1762
Comments
Yes good idea. Anyone know if a similar approach has been taken in RA1 and any standards for label names etc. e.g. or cntt_basic=true Just thinking through whether a basic workload would want to be scheduled onto any node, with only network intensive needing to be directed? |
@tomkivlin In RA-1 the nodes are not labeled as they are created based on a profile (basic, network-intensive) and can be searched based on the profile. I don't think there are OpenStack APIs for node labeling. Need OpenStack experts to help. |
Assuming there might be more profiles over time (e.g., compute intensive [AI/ML]), I'd go for the second approach, allowing profiles to be overlapping and nodes meeting the requirements of multiple profiles to be used flexibly with regards to the workload running on them. |
Adding a requirement to label the worker nodes according to their CNTT profile compliancy. Closes: anuket-project#1762 Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
* [RA2 Ch4]: Anuket node labels Adding a requirement to label the worker nodes according to their CNTT profile compliancy. Closes: #1762 Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com> * Replacing CNTT with Anuket Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com> Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com>
RA2 should describe if a Kubernetes cluster should have different node labels for the different hosts supporting different CNTT Cloud Infrastructure Profiles.
The text was updated successfully, but these errors were encountered: