Goals
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.
Application |
Priority/Criticality |
CPU/Memory Requirements (average/peak) |
Resource abuse potential |
|---|---|---|---|
Pipeline (Production) |
5 |
2/4 |
3 |
Pipeline Mail client |
5 |
1/2 |
1 |
Pipeline Jobcontrol clients |
5 |
1/2 |
2 |
Datacatalog server (crawler) |
3 |
2/2 |
2 |
Astroserver (loader) |
2 |
2/5 |
3 |
Tomcat applications |
4 |
3/5 |
5 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Resource management
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.