EGI Application Database :: Wiki

The EGI Applications Database consists of a number of components, each of which follows different versioning, thus different release cycles, and therefore their release notes are provided separately. The following components are those which present significant activity within the reporting period:

• Switched to new EGI Operations portal RESTful API for VO information

• Internal security API for backend services

• Handle empty response when fetching virtual appliance availability info
• Avoid logo convert errors

• Migrate AppDB components to GLUE2.1 from GLUE2.0
• Migrate from TopBDII to AMS mechanism for infrastructure information source

• Endorsements dashboard to allow users to endorse existing VM images
• Security dashboard to allow security officers to tag VM images known for security issues

• Invalid user authentication when performing topology actions

• OIDC authentication flow for user actions

• Internal GLUE2.1 schema migration
• UI for site endpoints using only native APIs, instead of OCCI
• Hide empty location field from block storages created for running VMs

• OIDC authentication flow on user actions and monitoring tasks

• Include fields project name and project domain name in share, image and template schema and filters

• GLUE2.1 schema support
• New GraphQL schema to match GLUE2.1 schema
• New Restful API to match GLUE2.1 schema
• Swagger UI when accessing the rest API root endpoint from browser
• GraphQL playground UI when accessing the GraphQL endpoint from browser
• Documentation endpoint for inner modules to expose their documentation

• Swagger UI to render links to filter inputs for documentation regarding the filter valid search terms
• Enable by default the GLUE2.1 schema

• Entity shared fields optimization to reduce number of calls to the backend

• Server endpoint to serve CouchDB topology

• Configurable LDAP bind DN and credentials
• Configurable network interface for the service to listen to
• Updated package dependencies

• Handle more LDAP errors

• Include project name and project domain name in cloud endpoint share entities
• Include related project name and project domain names in explicitly generated image and template entries of cloud endpoints
• Logging of unhandled errors when processing cloud info provider information

• Manage more unhandled errors

• CouchDB compaction once every 24 hours

• Revised hashes of GLUE2.1 objects to be generated by their IDs instead of whole data
• Revised ARGO monitoring module
• Revised compaction tool to perform compaction in multiple collections
• Avoid unnecessary garbage collection of data entries

• No longer query site BDII health status of service providers with ARGO monitoring
• Certificate usage for requests that do not need any

• Manage unhandled errors
• Handle max number of HTTP connections