egi-federation / ansible-role-bdii Goto Github PK

The final state of the service needs to have processes running:

• openldap server
• periodic updates of information providers.

These tests are failing, and tasks to start them for various scenarios should be added.

If the site-bdii is properly configured properly, the nagios probe ( any idea where the nagios probe for glue2 / bdii is ?) should pass. We can run it against the test instances and assert that it completes properly.

The next release is for the site-bdii. This should include tests for

• Configuration files and variables
• Processes started and running
• Log files
• information provider plugin
• information
  • static information
  • dynamic information

The provisioned machines should be compliant with the security profile required by EGI operations. This should be attained by including the pakiti client and asserting that there are no unpatched packages.

There is no programmatic link between the configuration passed for the static site-bdii variables, and those registered in GOCDB. This can lead to drift between the stated and effective deployment. For a real deployment, we could implement infrastructure test that gets the site details (using requests and xml, as well as the relevant GOCDBI API endpoint).

This would help keep sites aware of drift between these two sources of informations.