Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 65
    • Merge requests 65
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Merge requests
  • !1713

Open
Created Mar 28, 2022 by Larry Shen@atlineContributor
  • Report abuse
Report abuse

Persistent nfs affinities support for device.

  • Overview 0
  • Commits 2
  • Pipelines 1
  • Changes 6

We have site1, site2 deployed with 2 same rootfs. To make all devices be fully used, we wish the devices in 2 sites be treated as a global pool. Another word, one job could be either executed in site1 or site2 as soon as the device is idle.

For some reasons, our job is configured with persistent_nfs, but it can just specify either site1 nfs or site2 nfs. What we really need is: the dispatched device should find the nearest nfs server based on affinities.

This patch to binding a external nfs ip to device, so the device possible to find the nfs server with the same job define, won't care itself been dispatched to which site.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: persistent_nfs_affinities