Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • I infrastructure-maintenence
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Custom issue tracker
    • Custom issue tracker
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OSTC
  • infrastructure
  • infrastructure-maintenence
  • Issues
  • #43

Closed
Open
Created Feb 15, 2022 by Adam Szpilko@adam.szpilkoDeveloper

Diverge from `Puszka` and stick to RPi4 as worker for Nitrogen

2x Nitrogens (N0, N1) are connected via Puszka to our LAVA instance. Let's diverge from it and connect only one from the Nitrogens to wrc-pi4-1. I can see the scenarios below:

  1. Make Nitrogen 2 already connected to wrc-pi4-1 active (it is in a maintainance mode).
  2. Disconnect N0 and N1 from Puszka, connect one of them to wrc-pi-4-1 (via one free slot in Ykush) and make it active as well.

@stevan.radakovic , please try to be on it once you are back from holiday. We need to have it before rearrangement in the lab (moving to the rack cabinet)

CC @pastanki, @ @chase-qi

Assignee
Assign to
Time tracking

| Privacy policy | Cookies policy | Intellectual Property Compliance Policy |