Service Desk Knowledgebase: Servers: Difference between revisions

From Computer Laboratory System Administration
Jump to navigationJump to search
Line 38: Line 38:




===HotCRP===
===Creating a HotCRP Server===


from laira
from laira

Revision as of 12:40, 23 January 2015


This is the Severs content page of the CL Wiki Service Desk Knowledgebase. Its purpose is to provide information to the Service Desk team on how to handle problems and requests about this CL service. If you are involved with the provision of this CL service please feel free to add to the knowledge about that it.

If CL staff need to tell the Service Desk team about problems with this service please email
sys-admin-aside@cl.cam.ac.uk.

Return to the Service Desk Knowledgebase SERVICE PORTFOLIO

Key Service Description & URLs

CL Customer Documentation

Further CL Sys-Admin Resources

Underpinning Services

  • ??? - Any supporting or underpinning services

Customer-base for this Service

  • All staff and students of the Computer Laboratory

Costs

  • Free to all current staff and students of the Computer Laboratory

SLA

  • N/A

Service Desk Call Handling Procedure

Escalation points and key contacts to be defined...

  • RT tickets can be escalated to the ??? team by leaving the Queue as sys-admin with the Owner set to Nobody and the Status set to new. Tell the requestor:
    I am passing this request over to the ??? team who, I'm sure, will be in contact shortly.
  • RT tickets can be escalated to the ??? by changing the Queue to ??? with the Owner set to Nobody and the Status set to new. Tell the requestor:
    I am passing this request over to the ??? team who, I'm sure, will be in contact shortly.
  • RT tickets can be escalated to Firstname Lastname by changing the Owner to ??? with the Status set to new. Tell the requestor:
    I am passing this request over to ??? who, I'm sure, will be in contact shortly.


Creating a HotCRP Server

from laira sudo ssh -K svr-hotcrp then cd /opt/hotcrp sh -x README.cl SHortName [with no spaces in the name]


output like:-


SenSys_2015

edit SenSys_2015/conf/options.php (was Code/options.inc) and check that it looks plausible. 'paperSite' should be set to http://svr-hotcrp.cl.cam.ac.uk/hotcrp/SenSys_2015 'downloadPrefix' should be set to 'SenSys_2015-" (note the trailing hyphen). set shortName', 'longName', 'contactName', 'contactEmail' and 'emailFrom' and 'emailSubmissions' from the user supplied info.

+ echo

+ echo Add SenSys_2015 to /etc/apache2/httpd.conf, then 'cl-asuser service apache2 graceful' Add SenSys_2015 to /etc/apache2/httpd.conf, then 'cl-asuser service apache2 graceful'


Edit enSys_2015/conf/options.php to set the options mentioned

$Opt["dbName"] = "SenSys_2015"; $Opt["dbUser"] = "SenSys_2015"; $Opt["dbPassword"] = "SenSys_2015_cm542"; $Opt["shortName"] = "SenSys 2015"; $Opt["LongName"] = "13th ACM Conference on Embedded Networked Sensor Systems"; $Opt["conferenceSite"] = "http://sensys.acm.org/2015/"; $Opt["paperSite"] = "http://svr-hotcrp.cl.cam.ac.uk/hotcrp/SenSys_2015"; $Opt["downloadPrefix"] = "SenSys_2015-"; $Opt["contactName"] = "Cecilia Mascolo"; $Opt["contactEmail"] = "cm54@cam.ac.uk"; $Opt["sendEmail"] = true; $Opt["emailFrom"] = "cm54@cam.ac.uk"; $Opt["emailSender"] = null; $Opt["emailSubmissions"] = "cm54@cam.ac.uk";


Then edit /etc/apache2/httpd.conf adding to the end copying most of the data from the previous conference in the file, then restart

Contacts

Primary

Other

Availability

  • Monday:
  • Tuesday:
  • Wednesday:
  • Thursday:
  • Friday:
  • Saturday: Closed
  • Sunday: Closed

Hints, Tips & Known Issues

Title Person (Date)

The info...

Categorising Keywords

  • A categorization or service type
Retrieved from "https://wiki.cam.ac.uk/wiki/cl-sys-admin/index.php?title=Service_Desk_Knowledgebase:_Servers&oldid=1081"