Difference between revisions of "RAL Tier1 weekly operations castor 18/05/2018"
(Created page with "== Draft agenda == 1. Problems encountered this week 2. Upgrades/improvements made this week 3. What are we planning to do next week? 4. Long-term project updates (if not ...") |
|||
| Line 31: | Line 31: | ||
== Operation problems == | == Operation problems == | ||
| − | * gdss700 and gdss771 (lhcbDst) had drive failures and removed from production; gdss700 is back in RO | + | * gdss700 and gdss771 (lhcbDst) had drive failures and removed from production; gdss700 is back in RO |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== Operation news == | == Operation news == | ||
| − | + | == Plans for next few weeks == | |
| − | + | * CASTOR patching Wed 23/05: | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
* RA to finish developing the new information system for tape | * RA to finish developing the new information system for tape | ||
| Line 59: | Line 49: | ||
Headnode migration to Aquilon - The former vcert headnodes have been configured as CASTOR macroheadnodes and they pass functional tests | Headnode migration to Aquilon - The former vcert headnodes have been configured as CASTOR macroheadnodes and they pass functional tests | ||
SL7 name severs installs ok and pass functional tests. The six VMware VMs for generic headnodes/nameservers requested [https://helpdesk.gridpp.rl.ac.uk/Ticket/Display.html?id=207796 RT ticket] and DNS/MagDB entries added by Kash. Floating IP was obtained for vcert-stager-haproxy.gridpp.rl.ac.uk to test HAproxy | SL7 name severs installs ok and pass functional tests. The six VMware VMs for generic headnodes/nameservers requested [https://helpdesk.gridpp.rl.ac.uk/Ticket/Display.html?id=207796 RT ticket] and DNS/MagDB entries added by Kash. Floating IP was obtained for vcert-stager-haproxy.gridpp.rl.ac.uk to test HAproxy | ||
| − | |||
| − | |||
| − | |||
| − | |||
RA writing a new accounting system to match WLCG archival requirements | RA writing a new accounting system to match WLCG archival requirements | ||
== Actions == | == Actions == | ||
| − | |||
| − | |||
JK to investigate why ralreplicas fails and submit a "bug" report | JK to investigate why ralreplicas fails and submit a "bug" report | ||
| Line 78: | Line 62: | ||
== Staffing == | == Staffing == | ||
| − | RA on call | + | RA on call for next week |
Latest revision as of 10:01, 18 May 2018
Contents
Draft agenda
1. Problems encountered this week
2. Upgrades/improvements made this week
3. What are we planning to do next week?
4. Long-term project updates (if not already covered)
1. SL5 elimination from CIP and tape verification server 2. CASTOR stress test improvement 3. Generic CASTOR headnode setup 4. Aquilonised headnodes
5. Special topics
6. Actions
7. Review Fabric tasks
1. Link
8. AoTechnicalB
9. Availability for next week
10. On-Call
11. AoOtherB
Operation problems
* gdss700 and gdss771 (lhcbDst) had drive failures and removed from production; gdss700 is back in RO
Operation news
Plans for next few weeks
* CASTOR patching Wed 23/05:
* RA to finish developing the new information system for tape
* Need to gracefully shut down the current information system
* Sort out status of the remaining SL5 tape verification server
Long-term projects
Headnode migration to Aquilon - The former vcert headnodes have been configured as CASTOR macroheadnodes and they pass functional tests SL7 name severs installs ok and pass functional tests. The six VMware VMs for generic headnodes/nameservers requested RT ticket and DNS/MagDB entries added by Kash. Floating IP was obtained for vcert-stager-haproxy.gridpp.rl.ac.uk to test HAproxy
RA writing a new accounting system to match WLCG archival requirements
Actions
JK to investigate why ralreplicas fails and submit a "bug" report
RA/BD: Run GFAL unit tests against CASTOR. Get them here: https://gitlab.cern.ch/dmc/gfal2/tree/develop/test/
GP/RA to write a Nagios test to check for large number of requests on the NewRequests DB table that remain for a long time - the check will run every xxx min (to be aggreed with Production) and issue an alarm if the number exceeds 1,000 for an extended period of time (15 min)
Staffing
RA on call for next week
