OpsPortal issueshttps://gitlab.in2p3.fr/groups/opsportal/-/issues2024-01-16T10:27:47+01:00https://gitlab.in2p3.fr/opsportal/sf3/-/issues/164Improve CSI API2024-01-16T10:27:47+01:00Cyril L'OrphelinImprove CSI API
- [ ] is it possible that you could create API when I would be able to download that pakiti history for x days back?
- [ ] is it possible that in daily reports you will not take only last status, but you would take history for example ...
- [ ] is it possible that you could create API when I would be able to download that pakiti history for x days back?
- [ ] is it possible that in daily reports you will not take only last status, but you would take history for example 7 days back and if there will be CRITICAL then it will be in morning report?... I know that it can be confusing for us if last status is already OK, but it is still better for us to check if the site fixed that vulnerability then not getting it at all. Because as you said that you are taking only the last report then it is possible that one CE(CRITICAL) is vulnerable but we won't see it because other CE(with status OK) for that site will report before 7am and we will think everything is ok.
- [ ] The CVE is not always properly exposedv6.10https://gitlab.in2p3.fr/opsportal/sf3/-/issues/163Aligning the Operation Portal with EGI Brand Guidelines2024-01-16T10:24:08+01:00Cyril L'OrphelinAligning the Operation Portal with EGI Brand GuidelinesI am writing to inform you about our recently published brand guidelines, which outline the visual identity and design principles for the EGI brand, materials, website, and platforms. Since you are responsible for the Operation Portal (h...I am writing to inform you about our recently published brand guidelines, which outline the visual identity and design principles for the EGI brand, materials, website, and platforms. Since you are responsible for the Operation Portal (http://operations-portal.egi.eu/) development and maintenance, we kindly request your cooperation in aligning your platform's visual elements with the EGI brand.
Our new brand guidelines provide clear instructions for website developers to ensure a cohesive and unified visual identity across all EGI platforms. It is essential for us to maintain consistency in our digital presence to enhance our brand recognition and user experience.
We understand that each platform has its unique identity, and we are not seeking a complete revamp. Instead, we request specific adjustments that will visually align your platform with our brand. These adjustments might include incorporating our colour schemes, typography, imagery usage, and other design elements in subtle ways that resonate with the EGI brand.
You can access the brand guidelines document through the following link: https://cdn.egi.eu/app/uploads/2023/03/egi-brandguide-2023.pdfv6.10https://gitlab.in2p3.fr/opsportal/sf3/-/issues/162Improve API : new methods2023-12-18T14:29:07+01:00Cyril L'OrphelinImprove API : new methods- add a new method to provide information about sla reports
- add a new methods for the users accounting history- add a new method to provide information about sla reports
- add a new methods for the users accounting historyv6.9https://gitlab.in2p3.fr/opsportal/sf3/-/issues/161Align the Operation Portal with EGI Brand Guidelines2023-12-18T14:28:38+01:00Cyril L'OrphelinAlign the Operation Portal with EGI Brand Guidelines- Guideline : https://cdn.egi.eu/app/uploads/2023/03/egi-brandguide-2023.pdf- Guideline : https://cdn.egi.eu/app/uploads/2023/03/egi-brandguide-2023.pdfv6.9https://gitlab.in2p3.fr/opsportal/sf3/-/issues/160[EGI REPORTS] Improve the metrics for VO creation metrics2023-08-24T11:14:53+02:00Cyril L'Orphelin[EGI REPORTS] Improve the metrics for VO creation metrics- Harmonize the behaviour in the first page
- Remove the national/ international references (not used anymore)- Harmonize the behaviour in the first page
- Remove the national/ international references (not used anymore)v6.8https://gitlab.in2p3.fr/opsportal/sf3/-/issues/159Extend API with EGI reports2023-08-24T11:11:18+02:00Cyril L'OrphelinExtend API with EGI reportsI was wondering whether there are any plans to extend the current API in order to query the EGI reports [1] section and extract the number of users per VO.
Thank you.
> Cheers, GiuseppeI was wondering whether there are any plans to extend the current API in order to query the EGI reports [1] section and extract the number of users per VO.
Thank you.
> Cheers, Giuseppev6.8Cyril L'OrphelinCyril L'Orphelinhttps://gitlab.in2p3.fr/opsportal/eosc-opsportal/-/issues/25Jira authentication to be changed2023-06-30T08:51:12+02:00Cyril L'OrphelinJira authentication to be changedIt seems that the operation portal is making REST call on jira.egi.eu
using Basic Authentication. This is no longer going to work and should
be replaced by a Bearer access token as soon as possible. I'd really
appreciate if you could com...It seems that the operation portal is making REST call on jira.egi.eu
using Basic Authentication. This is no longer going to work and should
be replaced by a Bearer access token as soon as possible. I'd really
appreciate if you could come back to me and tell me if you can change
that, or give me a plan or a time frame. I believe that such
modification should be quite trivial to do.
One can issue a token by logging using the "opsportal" user, then
visiting the profile page and clicking on "Personal Access Tokens" on
the left side, or by visiting the following URL
https://jira.egi.eu/secure/ViewProfile.jspa?selectedTab=com.atlassian.pats.pats-plugin:jira-user-personal-access-tokens
I'd strongly recommend to un-click the "Automatic expiry" box, so that
the token stay forever valid. If not, Jira will send a email to
cic-information@cc.in2p3.fr shortly before the expiration, and the
token will cease to work upon expiration.
You can find more information on the usage of a Bearer token for doing
Jira REST calls at the following page, under the section "Using PATs":
https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html#UsingPersonalAccessTokens-UsingPATs
Also, if, for some very unlikely reason, you would like to
programmatically generate tokens, please do not use the Basic Auth
method as well. And please bear in mind that the number of live tokens
allowed per user is limited.
I stay at your disposition to provide any further information, help,
or discuss your concerns. I'd like to thank you in advance for your
feedback.Cyril L'OrphelinCyril L'Orphelinhttps://gitlab.in2p3.fr/opsportal/sf3/-/issues/158Upgrade symfony and php in components2023-08-24T11:15:41+02:00Cyril L'OrphelinUpgrade symfony and php in components- [x] [GGUS Workflow] Resolve dependency injection case issue
- [x] Upgrade lavoisier client- [x] [GGUS Workflow] Resolve dependency injection case issue
- [x] Upgrade lavoisier clientv6.8https://gitlab.in2p3.fr/opsportal/sf3/-/issues/157improve the cloud badge system including also the accounting data2023-08-24T11:11:50+02:00Cyril L'Orphelinimprove the cloud badge system including also the accounting data- [x] Add the accounting data verification into the system
- [x] Propose icons close to the initial pages
Initial request : https://jira.egi.eu/browse/EGITCB-398?filter=-8- [x] Add the accounting data verification into the system
- [x] Propose icons close to the initial pages
Initial request : https://jira.egi.eu/browse/EGITCB-398?filter=-8v6.8Cyril L'OrphelinCyril L'Orphelinhttps://gitlab.in2p3.fr/opsportal/sf3/-/issues/156[BROADCAST] filter the NGIs and Sites by scope in the broadcast tool2023-08-24T11:15:08+02:00Cyril L'Orphelin[BROADCAST] filter the NGIs and Sites by scope in the broadcast toolOn GOCDB there are also NGIs and Sites with different scope than EGI so quite often it happens that when sending a broadcast to NGI Managers and Site-Administrators this non-EGI entities are included among the recipients because people d...On GOCDB there are also NGIs and Sites with different scope than EGI so quite often it happens that when sending a broadcast to NGI Managers and Site-Administrators this non-EGI entities are included among the recipients because people don't notice them. We would like to avoid this situation.
- [x] 1) in the branches NGI Managers, Site-Administrators, and Site Security Contacts, list only the NGIs and Sites with the "EGI" scope tag
- [x] 2) create a new branch named for example "non-EGI recipients" where you can put NGIs, Site Admins, and Site Security Contacts tagged with other scopes.
Original request : https://jira.egi.eu/browse/EGITCB-494?filter=-1v6.8Cyril L'OrphelinCyril L'Orphelinhttps://gitlab.in2p3.fr/opsportal/sf3/-/issues/155Improve fedcloud badges2023-04-06T09:03:34+02:00Cyril L'OrphelinImprove fedcloud badges- Add the accounting verification
- Shift the time window of one month- Add the accounting verification
- Shift the time window of one monthv6.7https://gitlab.in2p3.fr/opsportal/sf3/-/issues/154Upgrade symfony2023-04-06T09:03:53+02:00Cyril L'OrphelinUpgrade symfony- upgrade composer
- upgrade symfony to version 6.2- upgrade composer
- upgrade symfony to version 6.2v6.7https://gitlab.in2p3.fr/opsportal/sf3/-/issues/153Upgrade the portal to php 8.02023-04-06T09:03:39+02:00Cyril L'OrphelinUpgrade the portal to php 8.0- Remove deprecated methods
- Upgrade libraries
- Upgrade composer- Remove deprecated methods
- Upgrade libraries
- Upgrade composerv6.7https://gitlab.in2p3.fr/opsportal/sf3/-/issues/152[METRICS] Improvements of the ergonomics2023-03-13T12:35:45+01:00Cyril L'Orphelin[METRICS] Improvements of the ergonomics- Remove the notion of national / International VOs
- Add a start and end date for all cases- Remove the notion of national / International VOs
- Add a start and end date for all casesv6.6https://gitlab.in2p3.fr/opsportal/sf3/-/issues/151[DOWNTIMES] add the cloud vo and the related topology in the downtime subscri...2023-03-13T12:36:05+01:00Cyril L'Orphelin[DOWNTIMES] add the cloud vo and the related topology in the downtime subscriptionAdd in the downtime subscription page the possibility to use the topology related to cloud / Vos by using the app db API .
More details here : https://jira.egi.eu/browse/EGIREQ-135Add in the downtime subscription page the possibility to use the topology related to cloud / Vos by using the app db API .
More details here : https://jira.egi.eu/browse/EGIREQ-135v6.6https://gitlab.in2p3.fr/opsportal/sf3/-/issues/150[VO ID CARD] Bug with multiple email address es2023-03-13T12:34:37+01:00Cyril L'Orphelin[VO ID CARD] Bug with multiple email address es> Dear Cyril,
> We found a problem when updating VO ID Cards. When setting up multiple addresses, we always get an error, as depicted below [1].
> Could you please verify if this is a bug?
> To reproduce the issue, edit any VO ID Car...> Dear Cyril,
> We found a problem when updating VO ID Cards. When setting up multiple addresses, we always get an error, as depicted below [1].
> Could you please verify if this is a bug?
> To reproduce the issue, edit any VO ID Card General information (e.g. https://operations-portal.egi.eu/vo/update/serial/...) and try to use multiple email addresses for the Security field.
> Thanks,
> Nacho.
![image](/uploads/279b7070d43b0a449854b0387909e07f/image.png)ZZZ[GONE] PERRIER GuillaumeZZZ[GONE] PERRIER Guillaumehttps://gitlab.in2p3.fr/opsportal/sf3/-/issues/149[AAI] Upgrade client and OIDC Endpoints2022-10-05T10:33:37+02:00Cyril L'Orphelin[AAI] Upgrade client and OIDC EndpointsFrom AAI team :
> We are writing to remind you that the legacy EGI Check-in OpenID Provider (based on MITREid Connect) will be decommissioned on Friday 16th of September 2022.
> Please make sure to reconfigure your Service before that da...From AAI team :
> We are writing to remind you that the legacy EGI Check-in OpenID Provider (based on MITREid Connect) will be decommissioned on Friday 16th of September 2022.
> Please make sure to reconfigure your Service before that date as described in the previous email.
> In case you miss the decommission date, the users of your service will not be able to login, but you will be able to update your configuration with the new OIDC Endpoints anytime.
>
> Warm regards,
> EGI Check-in teamv6.5Cyril L'OrphelinCyril L'Orphelinhttps://gitlab.in2p3.fr/opsportal/sf3/-/issues/148[MAILING] Layout uniformization of email skeleton2022-09-08T10:19:15+02:00ZZZ[GONE] PERRIER Guillaume[MAILING] Layout uniformization of email skeletonZZZ[GONE] PERRIER GuillaumeZZZ[GONE] PERRIER Guillaume2022-09-01https://gitlab.in2p3.fr/opsportal/sf3/-/issues/147[SLA] Make "Reliability" and "Availability" configurable2022-10-05T10:34:06+02:00ZZZ[GONE] PERRIER Guillaume[SLA] Make "Reliability" and "Availability" configurablev6.52022-09-01https://gitlab.in2p3.fr/opsportal/sf3/-/issues/146[ROD / DASHBOARD] Add new CVE vulnerabilities section2022-09-08T09:10:11+02:00ZZZ[GONE] PERRIER Guillaume[ROD / DASHBOARD] Add new CVE vulnerabilities sectionCron procees to integrate new daily CVEs
Add graph of vulnerabilities with date search featureCron procees to integrate new daily CVEs
Add graph of vulnerabilities with date search featurev6.5ZZZ[GONE] PERRIER GuillaumeZZZ[GONE] PERRIER Guillaume2022-09-01