Difference between revisions of "Operations Portal"
Line 44: | Line 44: | ||
|} | |} | ||
= Change, Release and Deployment = | |||
This sections are providing detailed agreement in terms of requirements gathering, release and deployment of Operations Portal which extend | |||
[[https://wiki.egi.eu/wiki/Instructions_for_Operations_Tools_teams|Instructions for Operations Tools teams]] | |||
# All requirements are gathered in Ops portal Forge instance | |||
# Prioritization and testing is done by dedicated [[OTAG#Operations_Portal_Advisory_and_Testing_Board|Operations Portal Advisory and Testing Board (OPAnTG)]] coordinated by EGI Operations team | |||
# Statuses of requests are as follow | |||
#* New | |||
* | #* In progress - work on it | ||
#* Rejected - rejected by OPAnTG | |||
#* Resolved - released | |||
# Priority of requests are as follow | |||
* | #* Low | ||
#* Normal | |||
#* High | |||
#* Immediate (emergency e.g. security) | |||
# 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 | |||
= Documentation = | = Documentation = | ||
Line 65: | Line 73: | ||
*[[Operations Portal VO ID card notifications|VO ID card notifications document]] | *[[Operations Portal VO ID card notifications|VO ID card notifications document]] | ||
[[Category:Operations_Portal]] | [[Category:Operations_Portal]] |
Revision as of 13:07, 17 December 2014
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 Operations Portal provides VO management functions and other capabilities which support the daily operations of EGI. It is a central portal for the operations community that offers a bundle of different capabilities, such as the broadcast tool, VO management facilities, a security dashboard and an operations dashboard that is used to display information about failing monitoring probes and to open tickets to the Resource Centres affected. The dashboard also supports the central grid oversight activities. It is fully interfaced with the EGI Helpdesk and the monitoring system through messaging. It is a critical component as it is used by all EGI Operations Centres to provide support to the respective Resource Centres. The Operations Portal provides tools supporting the daily running of operations of the entire infrastructure: grid oversight, security operations, VO management, broadcast, availability reporting.
The Operations Portal is one of EGI core services and part of EGI Federated Operations service.
Tool name | Operations Portal |
Tool description | Tool provides VO management functions and other capabilities which support the daily operations of EGI |
Tool url | https://http://operations-portal.egi.eu/ |
cic-information@in2p3.fr | |
GGUS Support unit | Operations Portal |
Requirements tracking - EGI tracker | https://rt.egi.eu/rt/Dashboards/5543/OpsPortal-Requirements |
Issue tracking - Developers tracker | https://forge.in2p3.fr/projects/opsportaluser |
Release schedule | n/a |
Release notes | http://operations-portal.egi.eu/home/tasksList |
Roadmap | n/a |
Related OLA | https://documents.egi.eu/public/ShowDocument?docid=2170 |
Test instance url | n/a |
Change, Release and Deployment
This sections are providing detailed agreement in terms of requirements gathering, release and deployment of Operations Portal which extend [for Operations Tools teams]
- All requirements are gathered in Ops portal Forge instance
- Prioritization and testing is done by dedicated Operations Portal Advisory and Testing Board (OPAnTG) coordinated by EGI Operations team
- Statuses of requests are as follow
- New
- In progress - work on it
- Rejected - rejected by OPAnTG
- Resolved - released
- Priority of requests are as follow
- Low
- Normal
- High
- Immediate (emergency e.g. security)
- 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