Difference between revisions of "SystemAdministration"

From SoylentNews
Jump to: navigation, search
(Resources)
(Who we are)
Line 7: Line 7:
 
==Who we are==
 
==Who we are==
  
* robinld -- systems
+
* xlefay - Lead
 
+
* mechanicjay - Co-lead
* mechanicjay -- systems
+
* robinld
 
+
* NCommander
* xlefay -- systems
+
* audioguy
  
 
==Index of Development Pages and Resources==
 
==Index of Development Pages and Resources==

Revision as of 02:07, 27 March 2014

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

  • xlefay - Lead
  • mechanicjay - Co-lead
  • robinld
  • NCommander
  • audioguy

Index of Development Pages and Resources

Servers

  • soylent-www - Primary Apache and slash server for main site.
  • soylent-db -- mysql server, holds the slash database
  • slashcott - Holds the slashcott site, development machine
  • soylent-services - mail, wiki, other services as needed

Known Problems

  • Need cron job to backup server
  • There are errors in the zone file in the spf TXT record -- Mechanicjay would be happy to fix this and clean up the zone file in general, but needs linode manager access from NCommander.
  • No init script for Apache.
  • Broken https configuration
    • Mostly fixed, Slash is the problem child now

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