ArgusCampaign2014

Argus is a central banning framework that helps CSIRT's and grid infrastructures enforce security policies. EGI.eu is requesting all participating NGI's to deploy an NGI-level Argus service. #AAROCARGUS2014

Motivation

To support the EGI emergency central user suspension, on November 2013 the OMB agreed to deploy an Argus instance at NGI level. The NGI Argus instance will fetch from the central instance the list of suspended user DNs. Sites are supposed to query the NGI instance, in order to avoid to overload the central instance.

Description of work to be done

The ticket https://ggus.eu/index.php?mode=ticket_info&ticket_id=104874 describes the work to be done :

1. A central ARGUS instance has to be installed at Meraka.
2. Sites should either deploy their own Argus configured to listen to the one at Meraka, or perform manual synchronisation (see http://wiki.nikhef.nl/grid/Argus_Global_Banning_Setup_Overview#Site_runs_no_Argus)

Campaign pages

The campaign will be discussed at https://github.com/AAROC/DevOps/wiki/ArgusCampaign2014

Timeline

The campaign will run from 04/08/2014 to 15/08/2015

Campaign Results.

• A new service was added to GOCDB - https://goc.egi.eu/portal/index.php?Page_Type=Service&id=5988
• A new VM was provided by Uli - argus.c4.csir.co.za
• A new host certificate issued for argus.c4.csir.co.za.
• The installation guide was followed and an Argus role created in the DevOps repo.
• all Nagios tests are passing : https://nagios.c4.csir.co.za/nagios/cgi-bin/status.cgi?host=argus.c4.csir.co.za

The campaign can be considered ended in success !