Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Perun

From EGIWiki
Revision as of 09:59, 27 February 2015 by Krakow (talk | contribs) (Created page with "{{Template:Op menubar}} {{Template:Tools menubar}} {{TOC_right}} Perun is {| class="wikitable" |- | '''Tool name''' | ''Perun'' |- | '''Tool description''' | |- | '''Tool...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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
Email
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

  1. All requirements are gathered in Ops portal Forge instance.
    • Development team is obliged to keep EGI RT up to date and consistence
  2. Prioritization and testing is done by dedicated Operations Portal Advisory and Testing Board (OPAnTG) coordinated by EGI Operations team
  3. Forge statuses of requests are as follow
    • New
    • In progress - work on it
    • Rejected - rejected by OPAnTG
    • Resolved - released
  4. Forge priority of requests are as follow
    • Low
    • Normal
    • High
    • Immediate (i.e. emergency)
  5. Standard changes (routine actions, no need for approval)
    • changes related to database information update
  6. Emergency changes (implemented without approval but subject of post-review)
    • Security incidents
  7. Releases
    • Frequency: every 2 months

Documentation