Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in
N
nrm
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 12
    • Issues 12
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • argo
  • nrm
  • Issues
  • #5

Closed
Open
Opened Dec 07, 2017 by Swann Perarnau@perarnau2 of 6 tasks completed2/6 tasks
  • Report abuse
  • New issue
Report abuse New issue

Implement basic topology awareness

We need to be able to recover the topology of the node, and connect it to our other components:

  • container manager, to know where the containers are.
  • power readings, to know what is consuming power
  • power control, to know what we can control
  • container scheduler, to know where to launch the next container

Hwloc is probably the right tool for that, although it might not be super easy to convert it into a structure that makes sense internally.

The TODO for this issue are:

  • merge back hwloc client into NRM code
  • connect topology awareness to other NRM components
    • use topology mapping in sensor readings
    • handle container resource requests using topo
    • connect power actuators to topology
  • handle resource availability from topology manager
Edited Dec 20, 2017 by Swann Perarnau
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: argo/nrm#5