ATLAS Update Room: 600/R-001 * Migration debrief after Eric/Giuseppe back from holiday * 170 TB still accounted to ATLAS in CASTOR * 20 July [write test 1 PB](https://docs.google.com/document/d/11t9q89NVVHpZ6rnJAiQ2s-kYq0Vxapcu0I6_KeBBqng/edit#heading=h.hhevn0icya3z) * Steps to get everyone involved in CTA operations (documentation, monitoring, rota, ...)

Monitoring Update Room: 600/R-001 ### Data Volume dashboard: solution for "Group by Month" issue * ElasticSearch is better for the "data accounting" use case. Data can be preserved indefinitely. * The Python script that combines both datasets should write the data to the monit-metrics JSON endpoint * On top if you also want to keep writing the data into IDB it's fine (at the same time you send it to monit) * That way we can store this new dataset, which I believe will come with the type: "daily_datavolume_castor_cta" in ES for long-term storage, and import the historical data from IDB. ### Documentation * David has produced some initial documentation * Give feedback to iteratively improve it

ALICE Room: 600/R-001 * Schedule to get ALICE into production: main agenda item for next week * What is the next step?

Schedule for migrating other LHC Experiments Room: 600/R-001 ### CMS * [Stress Test EOSCMS to EOSCTA](https://docs.google.com/document/d/1L5Ax9GoGcqqSZMPvghnoFQAOJmlRf_sQnEtafKoZ8Ac/edit?pli=1#heading=h.k7c6yk8d274t), writing 1PB. Maria is waiting for our green light. * FTS m-bit check? * Schedule for Phedex to Rucio migration? ### LHCb * Dataflow test "beginning of next year" * Would like to have CTA migration done before this test. * Suggestion: now until Sept.: integration with Dirac, functional tests. Oct/Nov: commissioning tests. Jan: migration

Non-LHC Experiments Room: 600/R-001 * NA62: We are eager to test the NA62 DAQ system with a CTA endpoint as soon as possible. (They use FTS). * Vova starts 1 August.

External Sites Room: 600/R-001 * We were getting an increasing number of e-mail requests from external sites including RAL and AARNET. * Julien created CTA Community site so we don't get individually e-mailed and don't have to keep re-answering the same questions. 12 people signed up, 6 non-CERN from RAL, AARNet and Tao Lin. Low traffic (so far!). * How can people submit documentation? * How can people submit issues? * How can people submit code/bug fixes?

RAO for LTO Room: 600/R-001 * Integrating Paul's work * Get something simple into CTA that is better than linear ordering. Then we can iteratively improve it as needed. * The idea is to have a configurable runtime option to allow us to select different RAO approaches ("linear order" as default) so we can test them during commissioning tests. * Only solutions proven to work will be deployed in production.

AOB Room: 600/R-001 ### Cleaning up * Documentation * e-groups * Log formats