HTTP-TPC push StoRM - GOOGLE

• discussed in GGUS:158487, related StoRM ticket STOR-1563
• GOOGLE site should be promoted to ATLAS T2 soon
• we need this issue to be fixed

FTS update

• improved logging - passive party address from RemoteConnections PerfMarker logged even without noisy debug level
• more readable log output
• deployed on fts3-devel.cern.ch
• production instances in ~ a month

Improving HTTP-TPC monitoring with active party address

• updated proposal for including both addresses (source and destination) in the PerfMarkers

Rucio DOMA testbed

• not running for a while, Monit people asked if we still need inactive message brokers topics for this testbed 
• destroy everything and start from scratch in future? to be asked in Rucio meeting tomorrow...