logo operations poral

logo egi


Operations Portal is an EGI service provided by CCIN2P3,
co-funded by EGI.eu and EGI-Engage



Release Version : 4.0 - July 11th

For any contact, use this section: Contact Us



The Operations Portal is a central portal for the EGI operations management that offers a different capabilities, such as the broadcast tool, VO management facilities and various of dashboards (Security, VO and Operations) to facilitate infrastructure oversight.

Latest news

Hello,

I would like to announce the DPM workshop 2016, which will
take place on the 23th and 24th of November 2016 at LPNHE(Paris),
with the kind support of the French DPM community.

https://indico.cern.ch/event/559673/

You are invited to participate to the workshop and to the discussions, where
we cover news and updates on the status of DPM: releases, distributions,
development directions, involvement of the DPM collaboration, new components, new setup, old components revisited, performance evaluations and experiences in general.

It will cover news and updates on experiences and best practices, user reports,
administration tools, federations, data access and community talks.

 We will soon set up the agenda, please get in touch if you
would like to contribute. If you have ideas or suggestions for
specific topics and contributions, then please let us know, we are
very interested in your opinions.

We hope to see you all there.

Cheers
Fabrizio
We would like to inform you of the decommissioning process of Production 
Services at IFISC-GRID:

Services:
nureddunase.uib-csic.es
nureddunace.uib-csic.es
nureddunaui.uib-csic.es
nureddunasb.uib-csic.es
nureddunamb.uib-csic.es

The timeline is as follows:
20.07.2016 : Decommissioning process begin, broadcast to VO managers
27.07.2016 : Downtime on the service.
31.08.2016 : HARD DEADLINE for VO Managers to retrieve all data from nureddunase.uib-csic.es
01.09.2016 : Removal of the service from GOCDB. 

Best regards,
  Antònia Tugores
Correction: in the previous broadcast regarding the decommissioning  of CEs grid-cr{2,3}.desy.de., not all active CEs at DESY-HH had been announced.

Please use for job submission either the ARC CEs
 - grid-arc0.desy.de.
 - grid-arc4.desy.de.
 - grid-arcce0.desy.de 
 - grid-arcce1.desy.de
or the remaining CREAM CEs
 - grid-cr0.desy.de
 - grid-cr1.desy.de

Cheers,
  the DESY-HH Grid team
The CREAM CEs
 - grid-cr2.desy.de
 - grid-cr3.desy.de
are being decommissioned at DESY-HH

Please use for job submission either the ARC CEs
 - grid-arcce0.desy.de 
 - grid-arcce1.desy.de
or the remaining CREAM CEs
 - grid-cr0.desy.de
 - grid-cr1.desy.de

Cheers,
  the DESY-HH Grid team
Dear Users

The current downtime notification system will be decommissioned on September 5th .
We invite you to use the new system : https://operations-portal.egi.eu/downtimes/subscription 

You have to select the targets of you subscription then a channel of communication (RSS, Ical or email) . Don't forget to fill your email address if you have selected the email channel !

We won't keep any subscription from the old system so if you want to be informed about downtimes you have to ask for a new subscription.

If you have questions, remarks please don't hesitate to contact us : cic-information@cc.in2p3.fr

Regards,
Operations Portal Team
Dear all,

this is to inform you that the following services will be decommissioned by 26/08/2016. 

HG-03-AUTH:
wms01.afroditi.hellasgrid.gr
wms03.afroditi.hellasgrid.gr

GR-01-AUTH:
lfc.grid.auth.gr - central LFC for vo.complex-systems.eu

The downtime will start on 15/07/2016.

Best regards,
Pavlos Daoglou

>>> More news <<<

Dear users,

The version 4.0 of the Operations Portal is now online .

Here are the major changes :

1) Frameworks & JS Libraries

- migration to Symfony 3.
- upgrade of bootstrap library
- use of Datatables Js libraries to optimize the presentation of the tables (Vo Management, Metrics)
- Use of Google Chart (Vo Management, Metrics)


3) Ergonomics

- Addition of links to ARGO and VAPOR applications
- Changes into global menu presentation (and optimization depending on screen size)

4) Module and project modifications

- Reorganisation of project infrastructure
- Removal of useless files and features
- Merge of Vo Management Tool and VO ID cards (all-in-one page )
- Removal of Availabilities/reliabilities module (replaced by ARGO)

5) New Downtime Module

Replacement of  the current downtime notification system:
- with a suscription page (emails , rss , ical)
- with timelines charts and tables
- with a search tool
- different formats (CSV, Json)

6) Continuous Integration

- a procedure of developments is in place : https://forge.in2p3.fr/projects/opsportaluser/wiki/Development_Procedure
- an integration plateform has been set-up with PHPUnit , GitlabCI , docker and SonarQBE : https://forge.in2p3.fr/projects/opsportaluser/wiki/Continuous_Integration

Don't hesitate to contact us for comments, feedback, bugs at cic-information@in2p3.fr

Regards,
1) New configuration for DTEAM VO

The HellasGrid Certification Authority changed its DN from "/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006" to "/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016"

Since it is also changed the certificate of the 2 voms servers hosting dteam VO, the settings of this VO need to be updated accordingly on *ALL THE (grid and cloud) SERVICES*

- New yaim settings (for the ../vo.d/dteam file):

VOMS_SERVERS='vomss://voms.hellasgrid.gr:8443/voms/dteam?/dteam/'
VOMSES="'dteam voms.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr dteam 24' 'dteam voms2.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr dteam 24'"
VOMS_CA_DN="'/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016' '/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016'"

- .lsc files:

# cat /etc/grid-security/vomsdir/dteam/voms.hellasgrid.gr.lsc
/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr
/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016

# cat /etc/grid-security/vomsdir/dteam/voms2.hellasgrid.gr.lsc
/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr
/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016

- configuration information:

https://voms.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action
https://voms2.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action


2) EGI central monitoring instance (ARGO)

Since July 1st, the EGI infrastructure is being monitored by two monitoring instances that can be found on these addresses:

https://argo-mon.egi.eu/nagios
https://argo-mon2.egi.eu/nagios

Both instances are running the same set of tests and results provided are equivalent.

Starting from the same date, the central ARGO Web UI (http://argo.egi.eu/lavoisier ) provides information from these two instances and the Operations Portal was reconfigured to raise alarms based on information from ARGO central instances.

Results coming from NGI SAM instances are no longer consumed by the central ARGO or Operations Portal so NGIs can eventually decommission them following the standard decommissioning procedures (https://wiki.egi.eu/wiki/PROC12 ).

3) New set of CREAM probes

A new set of probes is being used for monitoring the CREAM CEs and the A/R computation: https://wiki.italiangrid.it/twiki/bin/view/CREAM/DjsCreamProbeNew
This set of probe doesn't make use of the BDII, WMS and the messaging infrastructure like instead did the old WN monitoring framework.
Dear INFNGRID users,

this e-mail is for informing you that the Acknowledgment Statement of the VO was changed.

Please remember to use it in all scientific publications regarding INFNGRID work.

Best regards
Diego INFNGRID VO Manager
Dear GRIDIT users,

this e-mail is for informing you that the Acknowledgment Statement of the VO was changed.

Please remember to use it in all scientific publications regarding GRIDIT work.

Best regards
Diego GRIDIT VO Manager
Dear vo.mure.in2p3.fr members,

An Acknowledgement Statement has been added to the vo.mure.in2p3.fr VO. Don't forget to use it in your scientific publications.

Following is the acknowledgement statement to use:

"This work benefited from services provided by the vo.mure.in2p3.fr Virtual Organisation, supported by the national resource providers of the EGI Federation."

This statement can be found at http://operations-portal.egi.eu/vo/search .

The motivation of this request in explained in the message below.

Best regards,

Christophe.

-------- Forwarded Message --------
Subject: 	[VO ID card] - Acknowledgement Statement
Date: 	Mon, 20 Jun 2016 12:36:21 +0200
From: 	Giuseppe La Rocca <giuseppe.larocca@egi.eu>
To: 	Christophe Diarra <christophe.diarra@ipno.in2p3.fr>


Dear Virtual Organisation Manager,
 

We are working to improve the overall visibility and recognition of VOs in the context of EGI. This will help EGI as a whole (the federation)
to justify its scientific impact and secure funding on the long-term.

One of the key elements of the strategy is to make sure that VOs are properly acknowledged in the scientific publications they enable.

 To make sure this happens, we need your help! Specifically, we would like to see that:

        (1)   every EGI VO has a well defined acknowledgement text that users can include in their scientific publications to acknowledge the support, and

        (2)   the users are aware that VO acknowledgment texts exists and that they are encouraged to use them.

After these two things are completed, the visibility of EGI and its VOs will increase in publication tracing websites, such as OpenAire, ResearchGate,
Google Scholar, by text mining in acknowledgment parts. We can compile a list of publications that would not have existed without your work and there
is no stronger statement of our collective impact. This will also allow VOs  to use these statistics to demonstrate relevance and scientific impact,
when applying to funding in future work programmes.
 

How can you help?

 (1): 

In the EGI Operations Portal please define an acknowledgment text for your VO.
This is the text that members of the VO can use to make the VO use recognised.

You can register an acknowledgement text on the VO Id Card: http://operations-portal.egi.eu/vo/search
(Find your VO, Click Update VO Id Card). 

You can, for example, use this text for acknowledgement (Don't forget to replace XX with the name of your VO):

"This work benefited from services provided by the XX Virtual Organisation, supported by the national resource
providers of the EGI Federation".

Should you choose some alternative text, please consider including the EGI acknowledgement statement: http://go.egi.eu/acknowledge 

 (2):

Inform VO members about the acknowledgement text that they should use.

You can do that by:

-          Sending them an e-mail (if there is an email list for them)

-          Sending a broadcast email message to your VO users through the EGI Operations Portal (https://operations-portal.egi.eu/broadcast)

-          Adding the acknowledgement text to a visible place on science gateways or VREs that your users interact with
(such as here: http://milou.science.uu.nl/cgi/servicesdevel/DISVIS/disvis/). 

Should you need further help from us, or clarification on any of these points, please don't hesitate to ask at support@egi.eu.

Regards,

Giuseppe from EGI User Community Support Team

-- 
Technical Outreach Expert, EGI.eu
e-mail: giuseppe.larocca@egi.eu
skype: giuseppelarocca

EGI supports and promotes the Open Science Commons:
https://opensciencecommons.org/ | http://go.egi.eu/osc

----------------------------------------------------------------------------------------------------------------
link to this broadcast : https://operations-portal.egi.eu/broadcast/archive/id/1409
----------------------------------------------------------------------------------------------------------------

_______________________________________________
Grid.users mailing list
Grid.users@ipno.in2p3.fr
https://ipnlists.in2p3.fr/cgi-bin/mailman/listinfo/grid.users
Dear Fusion VO users,
 
Please remember the importance that any publication, research or project that uses FUSION VO resources, should use this or a similar text in acknowledgements.

"This work benefited from services provided by the Fusion Virtual Organisation, supported by the national resource providers of the EGI Federation"

Best Regards,
Dear dteam users,

for the following VOMS servers:

voms.hellasgrid.gr
voms2.hellasgrid.gr

a new certificate from a *new CA* has been installed, so all the services based on VOMS authentication need to be reconfigured with the new parameters available here:

https://voms.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action
https://voms2.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action

We have sent a broadcast to sites and NGIs asking for quick reconfiguration. At the moment, it is possible that some services will not work properly until the configuration is updated everywhere. We really apologise in advance for that and we are doing our best to coordinate the update all over the EGI infrastructure.

Feel free to ask for further information to EGI Operations through GGUS if needed.

EGI Operations
Dear site managers,

you get this message because your site supports the dteam VO.

For the following VOMS servers:

voms.hellasgrid.gr
voms2.hellasgrid.gr

a new certificate from a *new CA* has been installed, so all the services based on VOMS authentication need to be reconfigured with the new parameters available here:

https://voms.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action
https://voms2.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action

For the services with the old configuration in production, it should be enough to change the corresponding .lsc like this:

# cat /etc/grid-security/vomsdir/dteam/voms.hellasgrid.gr.lsc 
/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr
/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016

# cat /etc/grid-security/vomsdir/dteam/voms2.hellasgrid.gr.lsc 
/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr
/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016

which means to replace "2006" to "2016". 

If using yaim, the new configuration should look like this: 

# cat /root/siteinfo/vo.d/dteam

SW_DIR=$VO_SW_DIR/dteam
DEFAULT_SE=$SE_HOST
STORAGE_DIR=$CLASSIC_STORAGE_DIR/dteam
VOMS_SERVERS='vomss://voms.hellasgrid.gr:8443/voms/dteam?/dteam/'
VOMSES="'dteam voms.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr dteam 24' 'dteam voms2.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr dteam 24'"
VOMS_CA_DN="'/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016' '/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016'"

Please update your configuration as soon as possible. Feel free to ask for help to EGI Operations through GGUS if needed.

EGI Operations
Dear all,

we would like to inform you that due to the update of the HellasGrid CA certificate the certificates of the voms.hellasgrid.gr and voms2.hellasgrid.gr servers have been also updated. Therefore please make sure that you have updated LSC files on all of "VOMS-aware" services according to the following configuration details for each VO:

DTEAM:
https://voms.hellasgrid.gr:8443/voms/dteam/configuration/configuration.action

SEE:
https://voms.hellasgrid.gr:8443/voms/see/configuration/configuration.action

vo.complex-systems.eu:
https://voms.hellasgrid.gr:8443/voms/vo.complex-systems.eu/configuration/configuration.action

long-tail.egi.eu:
https://voms.hellasgrid.gr:8443/voms/long-tail.egi.eu/configuration/configuration.action

On behalf of the VOMS administration team,
Pavlos Daoglou