Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • N nrm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • argo
  • nrm
  • Issues
  • #5

Closed
Open
Created Dec 07, 2017 by Swann Perarnau@perarnauOwner2 of 6 tasks completed2/6 tasks

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
Time tracking