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

[RA2 Ch4] Is there a need for different node labels for the different Cloud Infrastructure Profiles? #1762

Closed
CsatariGergely opened this issue Jul 8, 2020 · 3 comments · Fixed by #2181
Assignees
Projects

Comments

@CsatariGergely
Copy link
Collaborator

RA2 should describe if a Kubernetes cluster should have different node labels for the different hosts supporting different CNTT Cloud Infrastructure Profiles.

@CsatariGergely CsatariGergely added this to To do in old-RA2 via automation Jul 8, 2020
@tomkivlin
Copy link
Collaborator

Yes good idea. Anyone know if a similar approach has been taken in RA1 and any standards for label names etc.

e.g.
cntt_profile=basic
cntt_profile=network_intensive

or

cntt_basic=true
cntt_network_intensive=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 tomkivlin added this to the M3 (Freeze Contributions) milestone Aug 21, 2020
@pgoyal01
Copy link
Collaborator

@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.

@tomkivlin tomkivlin added the question Further information is requested label Aug 21, 2020
@gkunz
Copy link
Collaborator

gkunz commented Aug 24, 2020

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.

@tomkivlin tomkivlin moved this from To do to Backlog in old-RA2 Sep 14, 2020
@tomkivlin tomkivlin removed this from the M3 (Freeze Contributions) milestone Sep 14, 2020
@tomkivlin tomkivlin added Elbrus and removed New question Further information is requested labels Oct 1, 2020
@tomkivlin tomkivlin moved this from Backlog to To do in old-RA2 Oct 1, 2020
CsatariGergely added a commit to nokia/CNTT that referenced this issue Jan 12, 2021
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>
@tomkivlin tomkivlin moved this from To do to In Progress in old-RA2 Jan 12, 2021
old-RA2 automation moved this from In Progress to Done Jan 13, 2021
tomkivlin pushed a commit that referenced this issue Jan 13, 2021
* [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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
old-RA2
  
Done
Development

Successfully merging a pull request may close this issue.

4 participants