AppDB

From EGIWiki
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Tools menu: Main page Instructions for developers Accounting Repository AppDB GGUS Message brokers ARGO Operations Portal GOCDB
AAI Proxy Metric Portal Licenses OTAGs Accounting Portal e-GRANT Perun Gstat LToS


Contents


The EGI Applications Database (AppDB) is a central service that stores and provides to the public, information about:

Reusing software products, registered in the AppDB, means that scientists and developers may find a solution that can be directly utilized on the European Grid Infrastructures without reinventing the wheel. …read more

Tool name Applications Database (AppDB)
Tool Category and description TBD

Offers SW & vAppliances for the EGI Grid & Cloud infrastructure.

Tool url https://appdb.egi.eu
Email appdb-support@iasa.gr
GGUS Support unit AppDB
GOC DB entry https://goc.egi.eu/portal/index.php?Page_Type=Site&id=430
Requirements tracking - EGI tracker https://rt.egi.eu/rt/Dashboards/1838/AppDB
Issue tracking - Developers tracker n/a
Release schedule AppDB Release Schedule
Release notes https://wiki.appdb.egi.eu/main:about:changelog
Roadmap TBD
Related OLA TBD
Test instance url https://appdb-dev.marie.hellasgrid.gr/
Documentation https://wiki.appdb.egi.eu/
License Apache2.0
Provider IASA
Source code provided on demand


Change, Release and Deployment

This sections are providing detailed agreement in terms of requirements gathering, release and deployment of APP DB which extend Instructions for Operations Tools teams


  1. All requirements are gathered in EGI Request Tracker
  2. Prioritization and testing is done by dedicated AppDB Advisory and Testing Board coordinated by EGI Operations team
  3. EGI RT statuses of requests are as follow
    • New - newly recorded in system
    • Accepted - accepted by OTAG team
    • Rejected - rejected by OTAG team
    • Open - (In progress) development team is implementing change
    • Resolved - released
  4. Priority of requests are as follow
    • None - 0
    • Low - 1
    • Normal - 2
    • High - 3
    • Immediate (i.e. emergency) - 4
  5. Standard changes (routine actions, no need for approval)
    • changes related to database information update
    • bug fixing - restoring service to expected functionality
  6. Emergency changes (implemented without approval but subject of post-review)
    • Security incidents
  7. Releases
    • Frequency: Minor every 3-4 months, Major 1 per year


Documentation


Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export