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
    • Locked Files
  • Issues 148
    • Issues 148
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Issues
  • #486

Closed
Open
Created May 05, 2021 by Anibal Limón@alimonDeveloper

LAVA support remote labs with shared boards

We currently have a remote lab (QCOM) that has boards attached and we would like to share the board resources between developers and LAVA because are MTP's and few available.

We already implement a set of commands to get console, power on/off the device, when LAVA request connect_device will lock the board until the LAVA jobs ends, allowing to power on/off the board when needed. With current implementation if a user are using the board the connect_device timeout will trigger and LAVA mark it as InfraestructureError that's fine for jobs but not for health-checks because will set the board in bad status.

An idea to handle this is to allow health-checks retries specified by the user and time between retries. If the board is in bad status will be responsibility of the remote worker admin, in this case us.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking