sysadmin
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
sysadmin [2020-05-23 12:04] – [Network] tim | sysadmin [2020-06-06 10:48] – [More Pages] tim | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== System Administration ====== | ====== System Administration ====== | ||
- | This page will describe how we organise ourselves to operate | + | At the time of writing, most of Hacklab's network and server infrastructure |
- | ===== Categories | + | ===== What do we maintain? |
- | We separate administration into categories based on the level of security required. This is so that we can make a trade-off between including more interested members vs restricting | + | * Internet connection |
+ | * Core network router and switches | ||
+ | * WiFi access | ||
+ | * Rack space and network service for member colo servers | ||
+ | * Virtual machines for members | ||
+ | * DNS & DHCP | ||
+ | * Members registration and authentication | ||
+ | * Access management (doors, tools and lockers) | ||
+ | * Shared services: shell, file storage, nextcloud | ||
+ | * Mailing lists | ||
- | | Internet of Things | Lights, sound, automation | + | ===== What don't we maintain? ===== |
- | | General Systems | + | |
- | | Network | + | |
- | | Personal Data | Members database, home directories, | + | |
- | ===== Network ===== | + | * Hacklab email - this is currently hosted on fastmail.com |
+ | * Domain registration - this is closely guarded. | ||
+ | * Internet of Things at the lab - this is a free-for-all. | ||
+ | * Members' | ||
- | https:// | + | ===== Communications ===== |
- | There is a netadmin unix group which provides access to network-infrastructure VMs and webapps. | + | There is a // |
- | There is a network password for router and switch access. | + | Users can reach us at // |
- | ===== Sysadmin | + | ===== Access Privileges |
- | https://lists.ehlab.uk/ | + | Network: The //netadmin// LDAP group provides access to network-related servers. There is a network password for the router, switches, UniFi controller and anything else that doesn' |
- | ===== Restricted Access ===== | + | Servers: The // |
- | These are the currently restricted services: | + | Team members will be expected to agree to the code of conduct before getting any privileges and may not receive all privileges immediately. |
- | * ehl-vm-access: | + | ===== Code of Conduct ===== |
- | * Access control for doors, tools and lockers. | + | |
- | * Hosted on magnesium. | + | |
- | * Available to sysadmin unix group. | + | |
- | * ehl-vm-admin: | + | |
- | * Members database | + | |
- | * Hosted on magnesium. | + | |
- | * Available to sysadmin unix group. | + | |
- | * ehl-vm-audit: | + | |
- | * Netflow, syslog, mqtt logs. 30 day retention. | + | |
- | * Hosted on Tim's server. | + | |
- | * Available to Tim. | + | |
- | * magnesium: | + | |
- | * Bare-metal VM server. | + | |
- | * Contains VMs with personal data, and VM that belong to individual members. | + | |
- | * Available to sysadmin unix group. | + | |
- | * ganymede and shell server: | + | |
- | * Home directories. | + | |
- | * Hosted on magnesium. | + | |
- | * Available to sysadmin unix group. | + | |
- | Tim's commentary: I would like to restructure these services so that the sysadmin team can be more inclusive. The members database will be moved to an external VM. I would like to adjust the expectations | + | We adopt the [[https://www.usenix.org/ |
- | ===== Conduct ===== | + | Of particular interest: |
- | What behaviour do we expect from members with access privileges? | + | > "I will maintain professional conduct in the workplace and will not allow personal feelings or beliefs to cause me to treat people unfairly or unprofessionally." |
- | * Respect personal data by only accessing it when legally or technically necessary, or when requested by the owner. | + | This means use your powers |
- | * Act in good faith. | + | |
- | * Co-operate with other group members. Don't change the technology choices or methods without discussing first. | + | |
- | Should we adopt an existing code of conduct? https://www.usenix.org/ | + | > "I will access private information on computer systems only when it is necessary in the course |
+ | This is important because the sysadmin team has access to users' VM and stored data, and to personal data entrusted to the organisation. | ||
+ | > "I will strive to ensure the necessary integrity, reliability, | ||
+ | > "I will design and maintain each system in a manner to support the purpose of the system to the organization." | ||
+ | This means that we need to co-operate as a team. The services we create should be maintainable after the person who created them has moved on. Technology choices should be shared. | ||
+ | |||
+ | ===== Technical Policies ===== | ||
+ | |||
+ | Server naming: | ||
+ | |||
+ | * Bare-metal servers are named after chemical elements. | ||
+ | * VMs are named functionally, | ||
+ | |||
+ | Configuration management: | ||
+ | |||
+ | * There is an [[https:// | ||
+ | * Use Docker for applications unless they are complex and require a dedicated host. | ||
+ | |||
+ | ===== More Pages ===== | ||
+ | |||
+ | * [[servers|List of servers]] | ||
+ | * [[network|Network]] | ||
+ | * [[wifi|WiFi]] | ||
+ | * [[dnsdhcp|DNS and DHCP]] | ||
+ | * [[ehana|Numbering]] | ||
+ | * https:// | ||
+ | * {{ : | ||
+ | |||
+ | Pages under sysadmin:* (login required) | ||
+ | |||
+ | <nspages sysadmin -h1 -textPages="" | ||
+ | ~~NOCACHE~~ | ||
sysadmin.txt · Last modified: 2022-04-22 13:47 by tim