SystemAdministration

From SoylentNews
Revision as of 10:02, 28 July 2016 by The Mighty Buzzard (talk | contribs) (Stuff That Needs To Be Addressed)

Jump to: navigation, search

TeamPages - parent, Development

Welcome

This is a comphensive index dealing with aspects of system administration and management of our clusters, as well as some of the more archine bits of setup required to make it work.

Who we are

Sysop Team Main Page

nick

position

timezone

paulej72 Co-leader UTC-4 (EDT)
mechanicjay Co-leader UTC-4 (EST/EDT)
NCommander Member UTC-9 (AKDT)
Audioguy Member UTC-7 (PST/PDT)
The Mighty Buzzard Emergency Reserve Member UTC-5 (CST/CDT)
martyb/bytram Catastrophe Reserve Member UTC-4 (EST/EDT)


Index of Development Pages and Resources

Servers

List of servers on linode: Category:SystemAdministration/Servers

  • soylent-www - Primary Apache, mysqld, and varnish servers for main site. Fluorine hosts slashd and ipnd as well.
Hydrogen, Fluorine
  • soylent-db -- ndb-cluster servers for mysql, hold the rehash database.
Helium, Neon
  • dev -- Development server.
Lithium
  • staff-slash -- Staff server, ssh entry point, staff-only rehash.
Boron
  • irc -- IRC server and related services.
Beryllium
  • backups -- Backup services. (NOT on linode)
Oxygen
  • directory services -- Hesoid and Kerberos.
Helium, Boron
Beryllium
Sodium, Magnesium

Stuff That Needs To Be Addressed

  • https is not default everywhere
  • icinga/monitoring project needs killed revamped into usefulness
  • Landscape - I appreciate NCommanders ability to obtain a product normally sold for free, but if this is not being used it should not be running and using resources. (helium (killed here), perhaps others)
  • Should have some sort of SN password safe
  • Privilege Duplication - making sure that all services have multiple admins
  • Systems Documentation needs to revised and brought up to date.
  • Work Coordination, not always good communication when fundamental things change.
  • There is no firewall coding at all. Something I normally set up before even one network cable is plugged in. I understand the desire to have an open system on public interfaces, but I see no reason that systems not publicly accessible such as database backends should not be firewalled off from Chinese and other such hackers. Such as the attempts being made on Helium from 120.192.20.162 120.192.0.0/11 China Mobile communications corporation at the moment I am writing this.

Work Notes

DNS is completely run and managed by Linode's DNS Manager service. This was an expedient decision when trying to get off bluehost. We may want to investigate putting the master zone file on helium or boron and having external services handle serving out our dns.

Resources