sf3 issueshttps://gitlab.in2p3.fr/opsportal/sf3/-/issues2020-04-15T17:05:51+02:00https://gitlab.in2p3.fr/opsportal/sf3/-/issues/81[VO] Vo validity and VO security2020-04-15T17:05:51+02:00Cyril L'Orphelin[VO] Vo validity and VO securitySome improvements should be done on these pages .
> Hi Cyril,
>
> Following the recent discussions it would be handy to have the
> possibility to:
> - filter VO in the Secuirty and VOValidity pages (like every VO having
> at least...Some improvements should be done on these pages .
> Hi Cyril,
>
> Following the recent discussions it would be handy to have the
> possibility to:
> - filter VO in the Secuirty and VOValidity pages (like every VO having
> at least a problem, or only VO lacking AUP,...)
> - it would be good if all the required bits could be checked on the VO
> VOValidity page
> - Having a way to ease/automate contacting and recontacting all the
> "broken" VO could be great
>
> More generally it would be good to have links everywhere between the
> various entries, to easily switch from one view to another while also
> having to click as less as possible (you are welcome for such a generic
> and unclear request, will see if I can come with something more
> concrete...)
>
> Cheers,
> Baptistev5.4Paul BouchillouPaul Bouchillouhttps://gitlab.in2p3.fr/opsportal/sf3/-/issues/80[ROD] Indicators of load2020-04-15T17:05:01+02:00Cyril L'Orphelin[ROD] Indicators of loadIn case of creation of tickets the browser could load during a long time .
The different actions should be blocked during this time and some indicators should be visible .
Ticket : https://ggus.eu/index.php?mode=ticket_info&ticket_id=14...In case of creation of tickets the browser could load during a long time .
The different actions should be blocked during this time and some indicators should be visible .
Ticket : https://ggus.eu/index.php?mode=ticket_info&ticket_id=146395v5.4DE BARBANSON ArthurDE BARBANSON Arthurhttps://gitlab.in2p3.fr/opsportal/sf3/-/issues/79[ROD] clean up of alarms2020-04-15T17:07:49+02:00Cyril L'Orphelin[ROD] clean up of alarms A daily script should be put in place to :
* [x] remove alarms non assigned in OK status after 3 days
* [x] remove all alarms non assigned after 10 days
* [x] remove the corresponding history in the 2 previous cases
* [x] add the c... A daily script should be put in place to :
* [x] remove alarms non assigned in OK status after 3 days
* [x] remove all alarms non assigned after 10 days
* [x] remove the corresponding history in the 2 previous cases
* [x] add the call to this script into Lavoisierv5.4https://gitlab.in2p3.fr/opsportal/sf3/-/issues/64[ROD] CSI reports2020-04-10T16:25:18+02:00Cyril L'Orphelin[ROD] CSI reportsReplace the current CSI reports
[Capture_d_écran_de_2019-08-27_10-14-14](/uploads/c594c95a90c734aa24514322263a36a8/Capture_d_écran_de_2019-08-27_10-14-14.png)
* generates an email with the template used for downtimes
* wich displays ...Replace the current CSI reports
[Capture_d_écran_de_2019-08-27_10-14-14](/uploads/c594c95a90c734aa24514322263a36a8/Capture_d_écran_de_2019-08-27_10-14-14.png)
* generates an email with the template used for downtimes
* wich displays information from Lavoisier : reportcsiIssues?status=critical
* a view into the controller which could be called with a status (critical or warning)v5.4DE BARBANSON ArthurDE BARBANSON Arthurhttps://gitlab.in2p3.fr/opsportal/sf3/-/issues/35Manage the case when a VO does not use any user backend systems2020-03-02T14:07:27+01:00Cyril L'OrphelinManage the case when a VO does not use any user backend systems* When a vo is not using VOMS servers the record is missing from the vo_voms_server table
* The joined requested are not working properly in that case and the list of VO is not complete (* When a vo is not using VOMS servers the record is missing from the vo_voms_server table
* The joined requested are not working properly in that case and the list of VO is not complete (v5.4Cyril L'OrphelinCyril L'Orphelin