AFS status update: Q (Elena G.): When will the web pages be migrated? A: Not yet fully defined; webservices can already serve files from EOS; we have asked the owners to do the migration manually; there might be also old websites that might not need migration (to be confirmed by their owners) Comment (Joel): ACLs are different and some dynamic websites are a pain to migrate; no access to the webservices logs C (Andreas W): there should be logs available; sometimes it's not obvious if the errors are related to the websites C (Jan): We still need action on the users' side in order to manually point their websites to the new location C (Natalia R, CMS): Do we expect for the AFS area(s) to be available until CMS moves to Rucio (as we would like to converge to using only one system)? C (Jan): We want to be finished with the migration before Run3. Please contact the AFS migration coordinators for CMS (A Pfeiffer, S Malik Muzaffar) for more clarifications; If Rucio migration is fast (couple of months), then probably you do not need to worry; if it's going to take more (years), then please consider moving; please check your timelines and send an email/ticket for this Q (Giovanni, BE-ABP): How about AFS workspaces for newcomers? Will they still get workspaces, how is it going to be done? User tickets? C (Jan): Yes, ticket to AFS support for keeping track and understanding the use cases Q (Frank L, BE-CO): FUSEX is not similar to AFS; worried about compatibility; how about storing/manipulating many small files? A (Jan): They are different systems (different tools for ACLs, quotas), but standard operations like compiling should now work without issues (EOS might be slightly slower than AFS)