Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #30273

Closed (moved)
Open
Opened Apr 23, 2019 by anarcat@anarcat💬

improve inventory of hardware resources

We currently have a few hosting providers and locations where we have "stuff":

  • virtual machines
  • colocated servers
  • raspberri pi under desk
  • routers
  • "cloud" things (like AWS)
  • test machines
  • etc

TPO machines are currently documented in LDAP. But they are also in Puppet. And there's a spreadsheet (which we want to replace with something else, probably a grafana dashboard, in #29816 (moved)). And there are many things (like AWS) which are not really tracked formally anywhere that I am aware of.

So this project is about establishing a clearer process to keep such an inventory. It should at least cover the following, TPO-managed infrastructure:

  • physical servers
  • virtual machines on those physical servers or on other cloud providers

Ideally, we would also have a unified view of this for all machines paid for by TPI, regardless of the team.

Each machine should have documentation on:

  • remote console access or control panel
  • cost
  • location
  • responsible team
  • purpose
  • age and lifecycle (see parent #29304 (moved))

The last bit is of course related to another problem, which is lifecycle management (see parent ticket #29304 (moved)).

A lot of that stuff is currently in LDAP and maybe it should just be added there. But I wonder if it would be useful to create another system (which might eventually supersede LDAP) that would be more flexible. If that process would happen at all, we would first need to thoroughly document how hosts are integrated into LDAP and so on, of course.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#30273