Network Team: Difference between revisions

From Technologia Incognita
Jump to navigation Jump to search
← Older edit
Mattronix (talk | contribs)
459 edits
Removed part about fixed IP addresses since we can do that from Unifi now
 
(34 intermediate revisions by 6 users not shown)
Line 1: Line 1:
Below is the list of pages that are handy for the Network team and space members.  
The network team is an informal team that takes care of the [[Network Infrastructure]] in TechInc.


== Documentation ==
If you want to do something related to the network infrastructure (fix something, add a new service, want to help maintain...), either reach a member directly, or send an email to network@ (might not be up to date).


*[[Network Ranges,VLANS and Switches]]
Board infrastructure is handled separately, as it includes members PII and other sensitive information that should only be accessible to board and board-appointed board helpers.
*[[Space IP List]]
*[[TI Certificate Authority]]
*Services Page Template


== Services ==
== Members ==


This is an initial setup, by Mattronix on 19-11-2014
While there isn't a formal structure, those members have some access and knowledge about the infra:
{|class="wikitable"
|-
! Service !! Description !! Maintainer
|-|-
| [[monitoring.ti]] ||  Infra Monitoring system. || N/A
|-|-
| [[ampache.ti]] ||  Music streaming server. || N/A
|-|-
| [[backup.ti]] || Backup management and backup system. || N/A
|-|-
|[[cloud.ti]] || Dedicated Owncloud Server|| N/A
|-|-
| [[ldap.ti]] || User authentication and accounting server. || N/A
|-|-
| [[quessel.ti]] || Shared IRC Client Server for dedicated IRC Clients || N/A
|-|-
| [[srv1.ti]] || Shared Webserver running ISPConfig for members who want to run a website. || N/A
|-|-
| [[techinc.nl]] || Dedicated machine for wiki.techinc.nl and techinc.nl + mailing lists.|| N/A
|-|-
| [[router.ti]] || The spaces primary gateway to the internet. || N/A
|}


== Admin Portal Links ==
* Frogeye (inherited most of the access from pre-2024 network team)
* Grey
* Thijs
* xbr


This is an initial setup, by Mattronix on 19-11-2014
Those people have been designated as trusted by Frogeye and also have an access to the systems to increase the bus factor:
{|class="wikitable"
|-
! Link !! Function
|-
| LDAP Portal Fusion Directory || Use this portal to maintain LDAP Users,Groups and Attributes.
|-
| LDAP Portal Emergency/Advanced || Used for when something goes wrong ALWAYS USE FUSION DIRECTORY for day to day tasks.
|-
| monitoring.ti || Network Monitoring Server used to automatically detects and warn of critical events.
|-
| dfm.ti || NetApp Data Fabric Manager server used to optimize NetApp Backups
|}


== Space Infrastructure Maintainers ==
* mrCyborg
* tams


This is an initial setup, by Mattronix on 19-11-2014
== Inventory ==
{|class="wikitable"
 
|-
Keeping track of things here is hard because there are so many moving parts.
! Member !! Member Maintains
So it's best to always look at the source
|-
 
| [[User:Mattronix|Mattronix]] || Storage,Backups,Network,Hyper-Visors
* Introduction and generalities: [[Network Infrastructure]]
|-|-
* VMs: See descriptions on proxmox cluster (https://longhorn.ti:8006/)
| [[User:Piele|Piele]]  || Network,Hyper-Visors
* Managed others: Rudder might have some extra hardware: http://rudder.ti
|-|-
* Unmanaged others: Unifi should discover everything, but also a lot of user devices: http://unifi.ti
| [[User:Wizzup|Wizzup]] || N/A
 
|-|-
== Agent ==
| [[User:Tg|tg]] || N/A
 
|-|-
If you create a VM / physical machine that is for members to use, we ask you to make it available to the network team.
| [[User:Arda Xi|Arda Xi]] || boot.ti
That way, should you not be available, we can fix problems too.
|-|-
To ensure the current network team has access to the machine, (also check we have a minimum of security good practices, maybe more too) we use Rudder (http://rudder.ti).
| [[User:Webmind|Webmind]] || N/A
To connect your machine to it, please run:
|-|-
 
| [[User:Mattronix|Mattronix]] || N/A
    wget --quiet -O /etc/apt/trusted.gpg.d/rudder_apt_key.gpg "https://repository.rudder.io/apt/rudder_apt_key.gpg"
|-|-
    apt install lsb-release -y
| [[User:nathan7|nathan7]] || N/A
    echo "deb [arch=$(dpkg --print-architecture)] https://repository.rudder.io/apt/latest/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list
|-|-
    apt update
| [[User:Muse|Muse]] || LTSP
    apt install rudder-agent -y
|}
    rudder agent policy-server 10.209.60.232
    rudder agent inventory
 
And ping the network team so we can add it.
 
== Old documentation ==
 
Pre-2022 (if not 2014) documenation: https://wiki.techinc.nl/index.php?title=Network_Team&oldid=29772

Latest revision as of 16:36, 20 January 2025

The network team is an informal team that takes care of the Network Infrastructure in TechInc.

If you want to do something related to the network infrastructure (fix something, add a new service, want to help maintain...), either reach a member directly, or send an email to network@ (might not be up to date).

Board infrastructure is handled separately, as it includes members PII and other sensitive information that should only be accessible to board and board-appointed board helpers.

Members

While there isn't a formal structure, those members have some access and knowledge about the infra:

  • Frogeye (inherited most of the access from pre-2024 network team)
  • Grey
  • Thijs
  • xbr

Those people have been designated as trusted by Frogeye and also have an access to the systems to increase the bus factor:

  • mrCyborg
  • tams

Inventory

Keeping track of things here is hard because there are so many moving parts. So it's best to always look at the source

Agent

If you create a VM / physical machine that is for members to use, we ask you to make it available to the network team. That way, should you not be available, we can fix problems too. To ensure the current network team has access to the machine, (also check we have a minimum of security good practices, maybe more too) we use Rudder (http://rudder.ti). To connect your machine to it, please run: 

   wget --quiet -O /etc/apt/trusted.gpg.d/rudder_apt_key.gpg "https://repository.rudder.io/apt/rudder_apt_key.gpg"
   apt install lsb-release -y
   echo "deb [arch=$(dpkg --print-architecture)] https://repository.rudder.io/apt/latest/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list
   apt update
   apt install rudder-agent -y
   rudder agent policy-server 10.209.60.232
   rudder agent inventory

And ping the network team so we can add it.

Old documentation

Pre-2022 (if not 2014) documenation: https://wiki.techinc.nl/index.php?title=Network_Team&oldid=29772

Retrieved from "https://wiki.techinc.nl/index.php?title=Network_Team&oldid=29775"