Perun
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 |
Perun is
Tool name | Perun |
Tool description | |
Tool url | |
GGUS Support unit | |
Requirements tracking - EGI tracker | |
Issue tracking - Developers tracker | |
Release schedule | |
Release notes | |
Roadmap | |
Related OLA | |
Test instance url |
Change, Release and Deployment
This sections are providing detailed agreement in terms of requirements gathering, release and deployment of Operations Portal which extend Instructions for Operations Tools teams
- All requirements are gathered in Ops portal Forge instance.
- Development team is obliged to keep EGI RT up to date and consistence
- Prioritization and testing is done by dedicated Operations Portal Advisory and Testing Board (OPAnTG) coordinated by EGI Operations team
- Forge statuses of requests are as follow
- New
- In progress - work on it
- Rejected - rejected by OPAnTG
- Resolved - released
- Forge priority of requests are as follow
- Low
- Normal
- High
- Immediate (i.e. emergency)
- Standard changes (routine actions, no need for approval)
- changes related to database information update
- Emergency changes (implemented without approval but subject of post-review)
- Security incidents
- Releases
- Frequency: every 2 months