Would you like to help test Confluence and Jira updates? Please fill out the form here: https://forms.gle/5TbSqvYYCnTyyxSN7
We have decided to set up virtual machines on the Fermilnx boxes. This will enable us to map existing glastlnx boxes onto virtual machines, to first approximation keeping the existing break down of applications/ (virtual) servers.
Oct 14: Tomcat Migration Complete
Oct 14: Tomcat Migration Complete.
This node runs job control daemons for several accounts, at least glast, glastraw,glastmc
Oct 14: Migration Complete
This machine requires user login. This machine is used as a Fermi CVS server, and a subversion server for a variety of user groups. svn functionality should move elsewhere.
Oct 9: This is where the Elog runs. We have to be careful when moving it. The elog entries are currently on /nfs/farm/g/glast/u25/tomcat/glast/writable/glastlnx08/webapps.
This is used as a test SRS web server -- this should move somewhere else. Decorator -- could move elsewhere? Xroot proxy?
This is now used by EXO as a database server. A replacement machine is (about to be) ordered.
Merged Prod Pipeline (08/29/13)
Migrated Dev Pipeline (07/19/13)
Oct 14: Web Migration complete. Crontabs updated. Turned off tomcat server on glastlnx17.
Oct 14: Migration Complete.
There is also a SRS tomcat server in this machine -- it should migrate somewhere else
Oct 14: Migration Complete.
There is also an EXO tomcat server on this machine -- it should migrate somewhere else
Xrootd test redirector
Migrated Datacatalog Crawler (07/19/13)
Production datacatalog crawler
Xroot proxy server
We should identify a set relatively standalone services to move to fermilnx-v* machines. Some suggestions:
As we move services we should also check which version of Java they are using, and where possible switch to Java 7.
We will need to move aliases to point to new machines, in a phased way. It would probably also be good to introduce new aliases for some services which do not currently have them.
We need to identify critical applications and estimate resource usage for these applications and spread them across the servers accordingly. Since we are using fewer servers, we are increasing the number of services per machine so we want to limit effects incurred from possibly misbehaving applications. I'm going to try to rate the applications on a scale of 1-5 in these 3 metrics. The first metric is the priority of the application during a normal power scenario, assuming SLAC is not in a power outage scenario. The second metric is the estimated CPU usage and memory usage of the application. The third metric is the possibility an application will misbehave and abuse resources for an extended amount of time.
CPU/Memory Requirements (average/peak)
Resource abuse potential
Pipeline Mail client
Pipeline Jobcontrol clients
Datacatalog server (crawler)
Ideally we could put all applications on a few machines without worrying about interference from other applications. In practice this isn't practical. It's been suggested to use virtual machines and split up services among the machines.