Difference between revisions of "GGUS:ROCCI FAQ"
Jump to navigation
Jump to search
m (Updated names of supported components) |
|||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
'''rOCCI''' | |||
<!-- * decommission: https://its.cern.ch/jira/browse/GGUS-1636 --> | |||
[[Category:FAQ Former support units (GGUS)]] | |||
<!-- | |||
{{GGUS-FAQ | {{GGUS-FAQ | ||
|Unit= rOCCI | |Unit= rOCCI | ||
|Interface= H | |Interface= H | ||
|purpose=The purpose of the rOCCI SU is to handle tickets assigned to it through the GGUS system. These tickets can originate from users or from operations. | |purpose=The purpose of the rOCCI SU is to handle tickets assigned to it through the GGUS system. These tickets can originate from users or from operations. | ||
|responsible= The persons responsible for rOCCI are members of the team producing the rOCCI family of products. | |responsible= The persons responsible for rOCCI are members of the team producing the rOCCI and jOCCI family of products, and smaller accompanying tools within the ONe Integration suite. | ||
|service quality= Medium ([[FAQ_GGUS-QoS-Levels]]) | |service quality= Medium ([[FAQ_GGUS-QoS-Levels]]) | ||
|solved by= Unless the root of a problem is tracked elsewhere, tickets will be typically solved within the rOCCI SU. | |solved by= Unless the root of a problem is tracked elsewhere, tickets will be typically solved within the rOCCI SU. | ||
|components= The rOCCI SU provides support for the following subsystems: <code>rOCCI-server</code>, <code>rOCCI-core</code>, <code>rOCCI-api</code>, | |components= The rOCCI SU provides support for the following subsystems: <code>rOCCI-server</code>, <code>rOCCI-core</code>, <code>rOCCI-api</code>, <code>rOCCI-cli</code>, <code>jocci-core</code>, <code>jocci-api</code>, <code>oneacct-export</code>, <code>keystorm</code>, <code>cloudkeeper(-one)</code>, and <code>nagios-promoo</code>. | ||
|assigned by= A ticket is usually assigned to the rOCCI Support Unit by EGI 2nd level user support or directly by informed users or site admins. Tickets may also be re-assigned by other Support Units in case a cause for a perceived trouble is tracked down to rOCCI. | |assigned by= A ticket is usually assigned to the rOCCI Support Unit by EGI 2nd level user support or directly by informed users or site admins. Tickets may also be re-assigned by other Support Units in case a cause for a perceived trouble is tracked down to a product relevant to rOCCI SU. | ||
|documentation= The rOCCI SU consists of rOCCI developers with first-hand experience of the | |documentation= The rOCCI SU consists of rOCCI, jOCCI and ONe Integration developers with first-hand experience of the products. No specific support documentation is available, however it is recommended that supporters consult general product documentation to help them distinguish between bugs and erroneous usage: [https://github.com/the-rocci-project/rOCCI-server], [https://github.com/EGI-FCTF/jOCCI-api/wiki] | ||
|sortname=rocci | |sortname=rocci | ||
}} | }} | ||
--> |
Latest revision as of 15:46, 19 February 2019
rOCCI