AppDB
Jump to navigation
Jump to 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 | • AAI Proxy | • Accounting Portal | • Accounting Repository | • AppDB | • ARGO | • GGUS | • GOCDB |
• Message brokers | • Licenses | • OTAGs | • Operations Portal | • Perun | • EGI Collaboration tools | • LToS | • EGI Workload Manager |
The EGI Applications Database (AppDB) is a central service that stores and provides to the public, information about:
- software solutions in the form of native software products and/or virtual appliances,
- the programmers and the scientists who are involved, and
- publications derived from the registered solutions
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 |
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
- All requirements are gathered in EGI Request Tracker
- Prioritization and testing is done by dedicated AppDB Advisory and Testing Board coordinated by EGI Operations team
- 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
- Priority of requests are as follow
- None - 0
- Low - 1
- Normal - 2
- High - 3
- Immediate (i.e. emergency) - 4
- Standard changes (routine actions, no need for approval)
- changes related to database information update
- bug fixing - restoring service to expected functionality
- Emergency changes (implemented without approval but subject of post-review)
- Security incidents
- Releases
- Frequency: Minor every 3-4 months, Major 1 per year
Documentation