https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Psolagna&feedformat=atomEGIWiki - User contributions [en]2024-03-28T19:41:42ZUser contributionsMediaWiki 1.37.1https://wiki.egi.eu/w/index.php?title=PROC25&diff=97910PROC252017-11-15T15:37:06Z<p>Psolagna: /* Step for the release of a UMD/CMD update */</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} <br />
<br />
{{Ops_procedures<br />
|Doc_title = Middleware release procedure<br />
|Doc_link = https://wiki.egi.eu/wiki/PROC25<br />
|Version = 0.1<br />
|Policy_acronym = OMB<br />
|Policy_name = Operations Management Board<br />
|Contact_group = operations at egi.eu <br />
|Doc_status = DRAFT<br />
|Approval_date = <br />
|Procedure_statement = The procedure describes the process of adding a new product release to the software provisioning process and releasing it in UMD/CMD. <br />
}}<br />
<br />
= Overview =<br />
<br />
The procedure describes the process to add a new product, or a new release of an existing product to the UMD/CMD repositories. <br />
<br />
= Definitions =<br />
<br />
Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure. <br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.<br />
<br />
= Entities involved in the procedure =<br />
* ''Product team'': The developer, or the team of developers, who is responsible for maintaining a software and producing the new releases.<br />
<br />
= Requirements =<br />
<br />
The prerequisites are: <br />
<br />
*The product team releasing the software has already provided the information to fill the product ID Card as described in the links below:<br />
** [[UMD_products_ID_cards | UMD ID card]]<br />
** [[EGI_Cloud_Middleware_Distribution_products#Product_ID_card_description | CMD ID card]]<br />
*Development team should follow [[Instructions_for_Production_Tools_teams#Release_and_deployment_management | Instructions for Production Tools teams: Release and deployment management]]<br />
<br />
= Steps for the validation of individual product releases =<br />
<br />
{| width="906" height="305" class="wikitable"<br />
|-<br />
! <br> <br />
! Responsible <br />
! Action <br />
! Notes<br />
|- valign="top"<br />
|1.1<br />
|Product team<br />
|[https://ggus.eu/?mode=ticket_submit Submits a GGUS ticket] for the "'''EGI Software provisioning support'''" support unit with the following information<br />
* Product release and version number<br />
* Link to the release notes<br />
* Full list of packages that compose the release and that need to be released in UMD/CMD<br />
|<br />
|-<br />
|1.2<br />
|Stage rollout manager<br />
| Product release is injected in the EGI SW provisioning infrastructure.<br />
* One or more RT tickets are created to track the progresses of the software provisioning of the new product release.<br />
* Reply to the GGUS ticket with the link to the RT and close as 'solved' the GGUS ticket.<br />
* The RT ticket is then used to track the progress of the software in the release process.<br />
* The RT ticket status is now "unverified".<br />
|This action must be completed within ''5 working days'' after step 1.<br />
|-<br />
|1.3<br />
| Software provisioning team, quality assurance<br />
|Begin of verification<br />
*Move the RT ticket created in step 2 in the "Verification" status. This means that the software provisioning team is verifying the product in the testbed. <br />
* Perform the verification in the testbed.<br />
* Attach verification report to the RT ticket.<br />
|This action must start within ''one month'' after step 2 is completed.<br />
* If the verification does not start in one month the RT ticket must be updated with information about the delay.<br />
This action must be completed in ''one week''.<br />
* If the verification is not completed after one week the RT ticket should be updated with information about the delay and moved to the "Delayed" status. PT to be informed as well. <br />
|-<br />
|1.4<br />
|Staged Rollout manager<br />
|Begin staged rollout<br />
* Move the ticket from "Verification" or "Delayed" to the "Staged rollout" status<br />
* The product is announced to the early adopters testing in staged rollout the product.<br />
* The reports provided by the early adopters are attached to the RT ticket.<br />
|This action must be completed in ''one month''.<br />
* Tickets more than one month in the "Staged rollout" status must be moved to the "Delayed" status with an explanation for the delay.<br />
|-<br />
|1.5<br />
|Staged rollout manager<br />
|Complete staged rollout.<br />
* Evaluate the reports and take a decision about the release.<br />
** If the product release qualifies for production the RT is moved to "UMDStore"<br />
** If the product release does not qualify for production the RT ticket is moved to "Rejected" and an explanation is provided to the developers.<br />
|<br />
|}<br />
<br />
== Notes == <br />
# The whole process should not last longer than 2 months without providing any information to the product team about delays through the RT ticket.<br />
<br />
= Step for the release of a UMD/CMD update =<br />
<br />
{| width="906" height="305" class="wikitable"<br />
|-<br />
! <br> <br />
! Responsible <br />
! Action <br />
! Notes<br />
|-<br />
|2.1<br />
|EGI Operations<br />
|Freeze UMD/CMD release contents<br />
|Using the UMD Composer add all products that are queued in the UMDStore to a new UMD/CMD release bundle.<br />
|-<br />
|2.2<br />
|Staged rollout manager<br />
|Prepare wiki page for the release with known issues and installation notes<br />
|Create a Wiki entry for the release at:<br />
* UMD-x:UMD-x.y.z using the major (x), minor (y) and revision (z) numbers for UMD release,<br />
* CMD-OS-x:CMD-OS-x.y.z using the major (x), minor (y) and revision (z) numbers for CMD-OS release, or,<br />
* CMD-ONE-x:CMD-ONE-x.y.z using the major (x), minor (y) and revision (z) numbers for CMD-ONE release.<br />
Create sections for each product that is included in the release. Add all findings (bugs, workarounds, etc.) collected in the QC Verification and Staged Rollout reports to the "Known Issues & Installation notes" wiki entry. <br />
|-<br />
|2.3<br />
|Staged rollout manager<br />
|Check for security vulnerabilities affecting existing products<br />
|Use the Vulnerabilities Dashboard, and contact Linda Cornwall about any advisories on any pending security vulnerabilities that require cross-linking<br />
*SVG RAT drafts advisory for a vulnerability, and notifies the Technology Provider.<br />
*Technology Provider confirms product version that fixes the vulnerability (e.g. BDII core 1.2.3), and the planned release (e.g. EMI-1 Update 13) in the vulnerabilities dashboard.<br />
*Release manager cross checks this dashboard with any planned releases.<br />
*The resulting list is circulated to release documentation team (TSA2.3 and TSA1.3), and the RAT manager<br />
*Releases CSIRT Advisories are published cross-referencing each other <br />
|-<br />
|2.4<br />
|EGI Operations<br />
|Compile release documentation in the release web site<br />
|UMD/CMD release metadata will be published in the UMD/CMD Repository and must cover the following sections:<br />
*Description<br />
*Contact Info<br />
*Technical Contact Info<br />
*Release Notes<br />
*Installation Notes<br />
*Known Issues<br />
*Change Log <br />
* RT tickets containing requirements associated to this release if available (''Added on 15 Nov 2017'')<br />
|-<br />
|2.5<br />
|EGI Operations<br />
|Produce release candidate<br />
|From the list of included products in (1) generate a Release Candidate. Notify quality UMD assurance team.<br />
|-<br />
|2.6<br />
|UMD quality assurance team<br />
|Test release candidate<br />
|The release candidate is automatically tested for installability and dependencies problems.<br />
* If the test goes well the procedure goes to next step<br />
* If there are problems with the release candidate the procedure goes back to step #6 or step #1 depending on the nature of the problem<br />
|-<br />
|2.7<br />
|EGI Operations<br />
|Publish UMD/CMD release<br />
|Only when all previous actions are signed off, publish the UMD/CMD release. <br />
|-<br />
|2.8<br />
|EGI Operations<br />
|Post-release cleanup <br />
|Post-release actions perform some housekeeping in the UMD/CMD release management area, including:<br />
* Add the UMD/CMD release announcement to UMD/CMD release schedule overview<br />
* Add text "EGI has released UMD 1.4.0 on 19 December 2011. (Announcement)" in the list of the topics for the next EGI monthly broadcast<br />
|}<br />
<br />
= Emergency release = <br />
== Definition of emergency release ==<br />
An emergency release is the process of releasing one product, or a set of product, with the targeted goal of solve a specific problem that affects the EGI infrastructure. To qualify the problem for an emergency release the problem should be classified in at least one of the following categories:<br />
* Major incident<br />
* Critical security vulnerability<br />
<br />
== Steps for emergency release ==<br />
<br />
{| width="906" height="305" class="wikitable"<br />
|-<br />
! <br> <br />
! Responsible <br />
! Action <br />
! Notes<br />
|-<br />
|3.1<br />
|Product team<br />
|[https://ggus.eu/?mode=ticket_submit Submits a GGUS ticket] for the "EGI Software provisioning support" support unit with the following information:<br />
* Product release and version number<br />
* Link to the release notes<br />
** Information about the problem that is patched by the release (e.g. link to GGUS ticket)<br />
* Full list of packages that compose the release, and that need to be released in UMD/CMD<br />
|<br />
|-<br />
|3.2<br />
|<br><br />
|Follow the steps of the ''Steps for the validation of individual product releases'' from step ''1.2''<br />
* For emergency releases the step 1.4 is optional. UMD team, together with the security team if relevant, will decide if the staged rollout should be skipped or not, based on the urgency of the release.<br />
|<br />
|-<br />
|3.3<br />
|<br><br />
|Follow the ''Steps for the release of a UMD/CMD update''<br />
|All the steps should be properly executed<br />
|-<br />
|3.4<br />
|EGI Operations<br />
|Communicate to the relevant stakeholders the availability of the new product(s) release<br />
|Depending on the nature of the problem solved, and on the urgency, the release manager will contact the EGI Security Vulnerability Group, or produce a broadcast to invite service managers to upgrade to the new version.<br />
|}</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=PROC23&diff=97904PROC232017-11-15T13:42:34Z<p>Psolagna: /* Steps */</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} <br />
<br />
{{Ops_procedures<br />
|Doc_title = Production tools release and deployment process<br />
|Doc_link = https://wiki.egi.eu/wiki/PROC23<br />
|Version = <br />
|Policy_acronym = OMB<br />
|Policy_name = Operations Management Board<br />
|Contact_group = operations at egi.eu <br />
|Doc_status = FINAL<br />
|Approval_date = <br />
|Procedure_statement = The procedure describes the process of release and deployment in EGI production infrastructure for Production tools <br />
}} <br />
<br />
= Overview =<br />
<br />
The procedure describes the process of release and deployment in EGI production infrastructure for Production tools.It is applicable to all production instances of the tools mentioned in the following list:<br />
<br />
* Operations portal<br />
* Service Availability Monitoring<br />
* GOCDB<br />
* GGUS<br />
* Accounting portal<br />
* Metrics portal<br />
* Gstat<br />
* Availability Calculation Engine<br />
* AppDB<br />
* e-GRANT<br />
* Network monitoring<br />
* Security monitoring<br />
* Catch-all services<br />
* Software provisioning infrastructure<br />
* Collaboration tools<br />
* Authentication and Authorization Infrastructure (AAI)<br />
<br />
Adding and removing tools from this list can be done by EGI central operations office, upon request, and every change is communicated to the OMB ML before being implemented. Please, open a ggus ticket to the Operations SU to request any change.<br />
<br />
= Definitions =<br />
<br />
Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure. <br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.<br />
<br />
= Entities involved in the procedure =<br />
<br />
*'''Service Provider team''': Team responsible for development, release and deployment of the tool <br><br />
*'''Operations team''': Oversees all the process and may provide further people for testing the tool<br />
*'''Noc-Managers''': they are informed regarding the release of the new tool and may provide further people for testing it<br />
<br />
= Requirements =<br />
<br />
The prerequesites are: <br />
<br />
*Tool is used by EGI production Infrastructure<br> <br />
*Development team should follow [https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management]<br />
* In case of deployment of a major update of a tool, a contingency plan must be agreed with the team who operates the tool, to handle major disruptions caused to production activities by problems in the new version of the tool.<br />
<br />
= Acceptance criteria = <br />
<br />
A new release of a Tool can be deployed in production if:<br />
* All the prerequisites are satisfied<br />
* The results of the testing in step ''3b'' do not show any major problem:<br />
** The tool is usable in all its features<br />
** The interoperability with the other tools is not broken<br />
<br />
= Steps =<br />
<br />
{| width="906" height="305" class="wikitable"<br />
|-<br />
! <br> <br />
! Responsible <br />
! Action <br />
! Notes<br />
|- valign="top"<br />
| 1<br><br />
| Service Provider team<br><br />
| <br />
Once release is ready the team opens a GGUS ticket to Operations with the following information:<br />
<br />
*Name of the tool<br />
*Date of release<br />
*Release notes<br />
*Suggested deployment date<br />
*Testing instance url and testing instructions <br />
*Names of testers if testing is manual (if not defined Development team may ask to appoint testers)<br />
<br />
| <br><br />
|-<br />
| 2<br />
| Operations Team<br />
|<br />
*Inform the Noc-Managers about the upcoming release, asking if there is anyone else interested in performing the tests<br />
*can add further people for performing the tests<br />
*The suggested duration of the test phase is two weeks<br />
*Update the ticket<br />
|-<br />
| 3a<br />
| Operations Team / Noc-Managers<br />
| Update the ticket with the information on the performed tests and their result<br />
|<br />
|-<br />
| 3b<br />
| Service Provider team<br />
| Update the ticket with information about results of the overall testing phase<br><br />
| <br><br />
|-<br />
| 4<br><br />
| Service Provider team<br />
| Provide in the ticket the link to updated documentation<br><br />
| <br><br />
|-<br />
| 5<br />
| Service Provider team and Operations team<br><br />
| Agree on deployment date and update the ticket<br />
| <br><br />
|-<br />
| 6<br />
| Operations team<br />
| 10 days before the upcoming deployment, inform the Noc-Managers.<br />
Update the ticket<br />
| <br><br />
|-<br />
| 7<br />
| Service Provider team<br />
| Schedule a downtime of the service in case it is needed<br />
|-<br />
| 8<br />
| Service Provider team<br />
| Deploy release and update the ticket<br />
| <br><br />
|-<br />
|9<br />
|Product team or Operations team<br />
|Check that the GGUs tickets contains links to the changes (RT tickets) that are implemented in this release. ''Added on Nov 15th 2017''<br />
|<br><br />
|-<br />
| 10<br />
| Operations team<br />
| Close the GGUS ticket after a week of the deployment only if the release was successful<br />
|<br> <br />
|}<br />
<br />
= Revision History =<br />
<br />
{| class="wikitable"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| <br><br />
| Alessandro Paolini<br />
| 2016-07-25<br />
| added the new AAI in the tools list<br />
|-<br />
|<br />
| Alessandro Paolini<br />
| 2016-03-22<br />
| procedure revised and made some changes<br />
|}<br />
<br />
[[Category:Operations_Procedures]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=PROC23&diff=97903PROC232017-11-15T13:42:02Z<p>Psolagna: /* Steps */</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} <br />
<br />
{{Ops_procedures<br />
|Doc_title = Production tools release and deployment process<br />
|Doc_link = https://wiki.egi.eu/wiki/PROC23<br />
|Version = <br />
|Policy_acronym = OMB<br />
|Policy_name = Operations Management Board<br />
|Contact_group = operations at egi.eu <br />
|Doc_status = FINAL<br />
|Approval_date = <br />
|Procedure_statement = The procedure describes the process of release and deployment in EGI production infrastructure for Production tools <br />
}} <br />
<br />
= Overview =<br />
<br />
The procedure describes the process of release and deployment in EGI production infrastructure for Production tools.It is applicable to all production instances of the tools mentioned in the following list:<br />
<br />
* Operations portal<br />
* Service Availability Monitoring<br />
* GOCDB<br />
* GGUS<br />
* Accounting portal<br />
* Metrics portal<br />
* Gstat<br />
* Availability Calculation Engine<br />
* AppDB<br />
* e-GRANT<br />
* Network monitoring<br />
* Security monitoring<br />
* Catch-all services<br />
* Software provisioning infrastructure<br />
* Collaboration tools<br />
* Authentication and Authorization Infrastructure (AAI)<br />
<br />
Adding and removing tools from this list can be done by EGI central operations office, upon request, and every change is communicated to the OMB ML before being implemented. Please, open a ggus ticket to the Operations SU to request any change.<br />
<br />
= Definitions =<br />
<br />
Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure. <br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.<br />
<br />
= Entities involved in the procedure =<br />
<br />
*'''Service Provider team''': Team responsible for development, release and deployment of the tool <br><br />
*'''Operations team''': Oversees all the process and may provide further people for testing the tool<br />
*'''Noc-Managers''': they are informed regarding the release of the new tool and may provide further people for testing it<br />
<br />
= Requirements =<br />
<br />
The prerequesites are: <br />
<br />
*Tool is used by EGI production Infrastructure<br> <br />
*Development team should follow [https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management]<br />
* In case of deployment of a major update of a tool, a contingency plan must be agreed with the team who operates the tool, to handle major disruptions caused to production activities by problems in the new version of the tool.<br />
<br />
= Acceptance criteria = <br />
<br />
A new release of a Tool can be deployed in production if:<br />
* All the prerequisites are satisfied<br />
* The results of the testing in step ''3b'' do not show any major problem:<br />
** The tool is usable in all its features<br />
** The interoperability with the other tools is not broken<br />
<br />
= Steps =<br />
<br />
{| width="906" height="305" class="wikitable"<br />
|-<br />
! <br> <br />
! Responsible <br />
! Action <br />
! Notes<br />
|- valign="top"<br />
| 1<br><br />
| Service Provider team<br><br />
| <br />
Once release is ready the team opens a GGUS ticket to Operations with the following information:<br />
<br />
*Name of the tool<br />
*Date of release<br />
*Release notes<br />
*Suggested deployment date<br />
*Testing instance url and testing instructions <br />
*Names of testers if testing is manual (if not defined Development team may ask to appoint testers)<br />
<br />
| <br><br />
|-<br />
| 2<br />
| Operations Team<br />
|<br />
*Inform the Noc-Managers about the upcoming release, asking if there is anyone else interested in performing the tests<br />
*can add further people for performing the tests<br />
*The suggested duration of the test phase is two weeks<br />
*Update the ticket<br />
|-<br />
| 3a<br />
| Operations Team / Noc-Managers<br />
| Update the ticket with the information on the performed tests and their result<br />
|<br />
|-<br />
| 3b<br />
| Service Provider team<br />
| Update the ticket with information about results of the overall testing phase<br><br />
| <br><br />
|-<br />
| 4<br><br />
| Service Provider team<br />
| Provide in the ticket the link to updated documentation<br><br />
| <br><br />
|-<br />
| 5<br />
| Service Provider team and Operations team<br><br />
| Agree on deployment date and update the ticket<br />
| <br><br />
|-<br />
| 6<br />
| Operations team<br />
| 10 days before the upcoming deployment, inform the Noc-Managers.<br />
Update the ticket<br />
| <br><br />
|-<br />
| 7<br />
| Service Provider team<br />
| Schedule a downtime of the service in case it is needed<br />
|-<br />
| 8<br />
| Service Provider team<br />
| Deploy release and update the ticket<br />
| <br><br />
|-<br />
|9<br />
|Product team or Operations team<br />
|Link the changes (RT tickets) that are implemented to this release in the GGUS ticket. ''Added on Nov 15th 2017''<br />
|<br><br />
|-<br />
| 10<br />
| Operations team<br />
| Close the GGUS ticket after a week of the deployment only if the release was successful<br />
|<br> <br />
|}<br />
<br />
= Revision History =<br />
<br />
{| class="wikitable"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| <br><br />
| Alessandro Paolini<br />
| 2016-07-25<br />
| added the new AAI in the tools list<br />
|-<br />
|<br />
| Alessandro Paolini<br />
| 2016-03-22<br />
| procedure revised and made some changes<br />
|}<br />
<br />
[[Category:Operations_Procedures]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=PROC23&diff=97902PROC232017-11-15T13:41:38Z<p>Psolagna: /* Steps */</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} <br />
<br />
{{Ops_procedures<br />
|Doc_title = Production tools release and deployment process<br />
|Doc_link = https://wiki.egi.eu/wiki/PROC23<br />
|Version = <br />
|Policy_acronym = OMB<br />
|Policy_name = Operations Management Board<br />
|Contact_group = operations at egi.eu <br />
|Doc_status = FINAL<br />
|Approval_date = <br />
|Procedure_statement = The procedure describes the process of release and deployment in EGI production infrastructure for Production tools <br />
}} <br />
<br />
= Overview =<br />
<br />
The procedure describes the process of release and deployment in EGI production infrastructure for Production tools.It is applicable to all production instances of the tools mentioned in the following list:<br />
<br />
* Operations portal<br />
* Service Availability Monitoring<br />
* GOCDB<br />
* GGUS<br />
* Accounting portal<br />
* Metrics portal<br />
* Gstat<br />
* Availability Calculation Engine<br />
* AppDB<br />
* e-GRANT<br />
* Network monitoring<br />
* Security monitoring<br />
* Catch-all services<br />
* Software provisioning infrastructure<br />
* Collaboration tools<br />
* Authentication and Authorization Infrastructure (AAI)<br />
<br />
Adding and removing tools from this list can be done by EGI central operations office, upon request, and every change is communicated to the OMB ML before being implemented. Please, open a ggus ticket to the Operations SU to request any change.<br />
<br />
= Definitions =<br />
<br />
Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure. <br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.<br />
<br />
= Entities involved in the procedure =<br />
<br />
*'''Service Provider team''': Team responsible for development, release and deployment of the tool <br><br />
*'''Operations team''': Oversees all the process and may provide further people for testing the tool<br />
*'''Noc-Managers''': they are informed regarding the release of the new tool and may provide further people for testing it<br />
<br />
= Requirements =<br />
<br />
The prerequesites are: <br />
<br />
*Tool is used by EGI production Infrastructure<br> <br />
*Development team should follow [https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management]<br />
* In case of deployment of a major update of a tool, a contingency plan must be agreed with the team who operates the tool, to handle major disruptions caused to production activities by problems in the new version of the tool.<br />
<br />
= Acceptance criteria = <br />
<br />
A new release of a Tool can be deployed in production if:<br />
* All the prerequisites are satisfied<br />
* The results of the testing in step ''3b'' do not show any major problem:<br />
** The tool is usable in all its features<br />
** The interoperability with the other tools is not broken<br />
<br />
= Steps =<br />
<br />
{| width="906" height="305" class="wikitable"<br />
|-<br />
! <br> <br />
! Responsible <br />
! Action <br />
! Notes<br />
|- valign="top"<br />
| 1<br><br />
| Service Provider team<br><br />
| <br />
Once release is ready the team opens a GGUS ticket to Operations with the following information:<br />
<br />
*Name of the tool<br />
*Date of release<br />
*Release notes<br />
*Suggested deployment date<br />
*Testing instance url and testing instructions <br />
*Names of testers if testing is manual (if not defined Development team may ask to appoint testers)<br />
<br />
| <br><br />
|-<br />
| 2<br />
| Operations Team<br />
|<br />
*Inform the Noc-Managers about the upcoming release, asking if there is anyone else interested in performing the tests<br />
*can add further people for performing the tests<br />
*The suggested duration of the test phase is two weeks<br />
*Update the ticket<br />
|-<br />
| 3a<br />
| Operations Team / Noc-Managers<br />
| Update the ticket with the information on the performed tests and their result<br />
|<br />
|-<br />
| 3b<br />
| Service Provider team<br />
| Update the ticket with information about results of the overall testing phase<br><br />
| <br><br />
|-<br />
| 4<br><br />
| Service Provider team<br />
| Provide in the ticket the link to updated documentation<br><br />
| <br><br />
|-<br />
| 5<br />
| Service Provider team and Operations team<br><br />
| Agree on deployment date and update the ticket<br />
| <br><br />
|-<br />
| 6<br />
| Operations team<br />
| 10 days before the upcoming deployment, inform the Noc-Managers.<br />
Update the ticket<br />
| <br><br />
|-<br />
| 7<br />
| Service Provider team<br />
| Schedule a downtime of the service in case it is needed<br />
|-<br />
| 8<br />
| Service Provider team<br />
| Deploy release and update the ticket<br />
| <br><br />
|-<br />
|9<br />
|Product team or Operations team<br />
|Link the changes (RT tickets) that are implemented to this release in the GGUS ticket.<br />
|<br><br />
|-<br />
| 10<br />
| Operations team<br />
| Close the GGUS ticket after a week of the deployment only if the release was successful<br />
|<br> <br />
|}<br />
<br />
= Revision History =<br />
<br />
{| class="wikitable"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| <br><br />
| Alessandro Paolini<br />
| 2016-07-25<br />
| added the new AAI in the tools list<br />
|-<br />
|<br />
| Alessandro Paolini<br />
| 2016-03-22<br />
| procedure revised and made some changes<br />
|}<br />
<br />
[[Category:Operations_Procedures]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Core_Activities_and_Services_PHASE_III&diff=97791Core Activities and Services PHASE III2017-11-07T10:43:59Z<p>Psolagna: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} {{Core_services_menubar}}<br />
[[Category:Operations]]<br />
<br />
<br> This page will list the EGI.eu core activities provided by EGI.eu partners for the period: '''January 2018 - December 2020''' <br />
<br />
Proposals have been evaluated and the results have been used as inputs for the EOSC-hub project (funded).<br />
<br />
'''Bidding phase III is now closed'''<br />
<br />
= List of the bidding activities =<br />
<br />
Please, find the information about the biddings in the [https://wiki.egi.eu/wiki/EGI_Core_Activities_Bidding#PHASE_III_January_2018-December_2020 Bidding page] <br />
<br />
<br> <br />
<br />
Documentation:<br> <br />
<br />
*EGI.eu Confirmation letters ... <br />
* Operation Level Agreements<br />
<br />
Each activity is obligated to deliver every 6 months report. <br />
<br />
Contact: <br />
<br />
*internal communication across activity leaders: core-egi-activities [at] mailman.egi.eu <br />
*to contact activity separately please use GGUS Support Unit <br />
*in case of any general questions: operations [at] egi.eu<br />
<br />
= Service/Activities =<br />
== Accounting repositories and portal ==<br />
'''Overview''':<br />
The Accounting repositories store computing (serial and parallel jobs), storage, and cloud resources accounting data collected from Resource Centres of the EGI Federation. Accounting information is gathered from distributed sensors into a central accounting repository where it is processed to generate summaries that are available through the EGI Accounting Portal. The Accounting Repository, based on the APEL software, has a MySQL database backend and needs to ensure the exchange of accounting information with peer e-Infrastructures.<br />
<br />
The Accounting Portal receives and stores the site, user, and VO level summaries generated by the Accounting Repository and provides views via a web portal, for example, by aggregating sites in a country on custom time intervals. The databases are organized into a CPU record database, a User record database, and a topology database.<br />
<br />
'''Consortium''': CESGA, STFC<br />
<br />
'''Contacts''': Adrian Coveney - adrian.coveney<AT>stfc.ac.uk<br />
<br />
== Application DB (virtual appliances and applications library) ==<br />
<br />
'''Overview''' <br> <br />
<br />
The EGI Applications Database (AppDB) is a central service that provides: <br />
<br />
*Information about software solutions in the form of native software products and virtual appliances, linking the programmers and the scientists who are involved, and the publications derived from the registered solutions <br />
*The tools for the distribution of the virtual machine images in the cloud sites part of the the federated cloud<br />
<br />
'''Consortium: '''GRNET <br />
<br />
'''Contacts: '''Kostas Koumantaros (kkoum<AT>grnet.gr), Marios Chatziangelou (mhaggel<AT>iasa.gr) <br><br />
<br />
== Collaboration tools ==<br />
== DIRAC4EGI ==<br />
== Helpdesk (GGUS) ==<br />
== Helpdesk human support ==<br />
== Marketplace and resource allocation ==<br />
== Message brokers ==<br />
== Monitoring ==<br />
== Online CA ==<br />
== Operations Portal ==<br />
== Security coordination and security tools ==<br />
== Service registry (GOCDB) ==<br />
== Services for AAI (CheckIn) ==<br />
== UMD and CMD quality assurance ==<br />
== UMD and CMD software provisioning infrastructure ==</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Standards&diff=96769Standards2017-08-29T14:18:34Z<p>Psolagna: /* Security.Authentication&authorization */</p>
<hr />
<div>[[Category:Policy]]<br />
This page contains references to the most relevant standards for DCI in the EGI context. They are also listed in the [https://documents.egi.eu/document/721 EGI Standards Roadmap]. For suggestions/amendements, contact [http://www.egi.eu/about/staff/ Sergio Andreozzi]. <br />
<br />
== Standards for DCIs by Capability ==<br />
<br />
=== Information.Messagging ===<br />
<br />
*AMQP 1.0 <br />
*LDAPv3 <br />
*STOMP [[http://stomp.github.com/ www]]<br />
<br />
=== Information.Model ===<br />
<br />
*GLUE 2.0 Conceptual<br />
** GLUE 2.1 under approval <br />
*GLUE 2.0 LDAP <br />
*GLUE 2.0 XML<br />
<br />
=== Storage.Management ===<br />
<br />
*CDMI 1.0 <br />
*SRM 2.2<br />
<br />
=== Storage.FileTransfer ===<br />
<br />
*GridFTP v2<br />
<br />
=== Storage.FileAccess ===<br />
<br />
*NFS 4.1 <br />
*WebDAV<br />
<br />
=== Network.Transport ===<br />
<br />
*IPv6<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*TCloud 1.0 <br />
*OVF 1.0<br />
<br />
=== Client.API ===<br />
<br />
*SAGA Core API <br />
*SAGA Advert API <br />
*SAGA Service Discovery API <br />
*SAGA C++ Language Bindings <br />
*SAGA Information Service Navigator API Extension <br />
*SAGA Python Language Bindings <br />
*SAGA Message API extension <br />
*Checkpoint and Recovery API <br />
*DRMAA V2<br />
<br />
=== Compute.JobExecution ===<br />
<br />
*BES <br />
*HPC-Basic Profile <br />
*HPC File Staging Profile <br />
*JSDL <br />
*JSDL HPC <br />
*JSDL SPMD <br />
*EMI-ES<br />
<br />
=== Compute.ParallelJobExecution ===<br />
<br />
*OpenMP <br />
*MPI<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
* OCCI 1.2<br />
** OCCI Core<br />
** OCCI Compute Resource Templates Profile<br />
** OCCI HTTP Protocol<br />
** OCCI Infrastructure<br />
** OCCI JSON rendering<br />
** OCCI Text rendering<br />
* OVF (ISO/IEC 17203:2011)<br />
<br />
=== Security.Authentication&authorization ===<br />
<br />
*X.509 <br />
*X.509 Proxy Certificate <br />
*SAML 2.0<br />
*SAML 2.0 <br />
*OpenID Connect / OAuth2<br />
<br />
=== Operations.Accounting ===<br />
<br />
*OGF&nbsp;UR 1.0<br />
*OGF&nbsp;UR 2.0<br />
*Compute extension to OGF UR 1.0 <br />
*OGF&nbsp;STAR [[https://forge.gridforum.org/sf/go/artf6532?nav=1 www]]<br></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Standards&diff=96768Standards2017-08-29T14:18:24Z<p>Psolagna: /* Security.Authentication&authorization */</p>
<hr />
<div>[[Category:Policy]]<br />
This page contains references to the most relevant standards for DCI in the EGI context. They are also listed in the [https://documents.egi.eu/document/721 EGI Standards Roadmap]. For suggestions/amendements, contact [http://www.egi.eu/about/staff/ Sergio Andreozzi]. <br />
<br />
== Standards for DCIs by Capability ==<br />
<br />
=== Information.Messagging ===<br />
<br />
*AMQP 1.0 <br />
*LDAPv3 <br />
*STOMP [[http://stomp.github.com/ www]]<br />
<br />
=== Information.Model ===<br />
<br />
*GLUE 2.0 Conceptual<br />
** GLUE 2.1 under approval <br />
*GLUE 2.0 LDAP <br />
*GLUE 2.0 XML<br />
<br />
=== Storage.Management ===<br />
<br />
*CDMI 1.0 <br />
*SRM 2.2<br />
<br />
=== Storage.FileTransfer ===<br />
<br />
*GridFTP v2<br />
<br />
=== Storage.FileAccess ===<br />
<br />
*NFS 4.1 <br />
*WebDAV<br />
<br />
=== Network.Transport ===<br />
<br />
*IPv6<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*TCloud 1.0 <br />
*OVF 1.0<br />
<br />
=== Client.API ===<br />
<br />
*SAGA Core API <br />
*SAGA Advert API <br />
*SAGA Service Discovery API <br />
*SAGA C++ Language Bindings <br />
*SAGA Information Service Navigator API Extension <br />
*SAGA Python Language Bindings <br />
*SAGA Message API extension <br />
*Checkpoint and Recovery API <br />
*DRMAA V2<br />
<br />
=== Compute.JobExecution ===<br />
<br />
*BES <br />
*HPC-Basic Profile <br />
*HPC File Staging Profile <br />
*JSDL <br />
*JSDL HPC <br />
*JSDL SPMD <br />
*EMI-ES<br />
<br />
=== Compute.ParallelJobExecution ===<br />
<br />
*OpenMP <br />
*MPI<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
* OCCI 1.2<br />
** OCCI Core<br />
** OCCI Compute Resource Templates Profile<br />
** OCCI HTTP Protocol<br />
** OCCI Infrastructure<br />
** OCCI JSON rendering<br />
** OCCI Text rendering<br />
* OVF (ISO/IEC 17203:2011)<br />
<br />
=== Security.Authentication&authorization ===<br />
<br />
*X.509 <br />
*X.509 Proxy Certificate <br />
*SAML 2.0<br />
*SAML 2.0 <br />
*OpenID Connect<br />
<br />
=== Operations.Accounting ===<br />
<br />
*OGF&nbsp;UR 1.0<br />
*OGF&nbsp;UR 2.0<br />
*Compute extension to OGF UR 1.0 <br />
*OGF&nbsp;STAR [[https://forge.gridforum.org/sf/go/artf6532?nav=1 www]]<br></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Standards&diff=96767Standards2017-08-29T14:18:16Z<p>Psolagna: /* Security.Authentication&authorization */</p>
<hr />
<div>[[Category:Policy]]<br />
This page contains references to the most relevant standards for DCI in the EGI context. They are also listed in the [https://documents.egi.eu/document/721 EGI Standards Roadmap]. For suggestions/amendements, contact [http://www.egi.eu/about/staff/ Sergio Andreozzi]. <br />
<br />
== Standards for DCIs by Capability ==<br />
<br />
=== Information.Messagging ===<br />
<br />
*AMQP 1.0 <br />
*LDAPv3 <br />
*STOMP [[http://stomp.github.com/ www]]<br />
<br />
=== Information.Model ===<br />
<br />
*GLUE 2.0 Conceptual<br />
** GLUE 2.1 under approval <br />
*GLUE 2.0 LDAP <br />
*GLUE 2.0 XML<br />
<br />
=== Storage.Management ===<br />
<br />
*CDMI 1.0 <br />
*SRM 2.2<br />
<br />
=== Storage.FileTransfer ===<br />
<br />
*GridFTP v2<br />
<br />
=== Storage.FileAccess ===<br />
<br />
*NFS 4.1 <br />
*WebDAV<br />
<br />
=== Network.Transport ===<br />
<br />
*IPv6<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*TCloud 1.0 <br />
*OVF 1.0<br />
<br />
=== Client.API ===<br />
<br />
*SAGA Core API <br />
*SAGA Advert API <br />
*SAGA Service Discovery API <br />
*SAGA C++ Language Bindings <br />
*SAGA Information Service Navigator API Extension <br />
*SAGA Python Language Bindings <br />
*SAGA Message API extension <br />
*Checkpoint and Recovery API <br />
*DRMAA V2<br />
<br />
=== Compute.JobExecution ===<br />
<br />
*BES <br />
*HPC-Basic Profile <br />
*HPC File Staging Profile <br />
*JSDL <br />
*JSDL HPC <br />
*JSDL SPMD <br />
*EMI-ES<br />
<br />
=== Compute.ParallelJobExecution ===<br />
<br />
*OpenMP <br />
*MPI<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
* OCCI 1.2<br />
** OCCI Core<br />
** OCCI Compute Resource Templates Profile<br />
** OCCI HTTP Protocol<br />
** OCCI Infrastructure<br />
** OCCI JSON rendering<br />
** OCCI Text rendering<br />
* OVF (ISO/IEC 17203:2011)<br />
<br />
=== Security.Authentication&authorization ===<br />
<br />
*X.509 <br />
*X.509 Proxy Certificate <br />
*SAML 2.0<br />
*SAML 2.0 <br />
// *XACML 2.0 */<br />
*OpenID Connect<br />
<br />
=== Operations.Accounting ===<br />
<br />
*OGF&nbsp;UR 1.0<br />
*OGF&nbsp;UR 2.0<br />
*Compute extension to OGF UR 1.0 <br />
*OGF&nbsp;STAR [[https://forge.gridforum.org/sf/go/artf6532?nav=1 www]]<br></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Standards&diff=96766Standards2017-08-29T14:18:08Z<p>Psolagna: /* Security.Authentication&authorization */</p>
<hr />
<div>[[Category:Policy]]<br />
This page contains references to the most relevant standards for DCI in the EGI context. They are also listed in the [https://documents.egi.eu/document/721 EGI Standards Roadmap]. For suggestions/amendements, contact [http://www.egi.eu/about/staff/ Sergio Andreozzi]. <br />
<br />
== Standards for DCIs by Capability ==<br />
<br />
=== Information.Messagging ===<br />
<br />
*AMQP 1.0 <br />
*LDAPv3 <br />
*STOMP [[http://stomp.github.com/ www]]<br />
<br />
=== Information.Model ===<br />
<br />
*GLUE 2.0 Conceptual<br />
** GLUE 2.1 under approval <br />
*GLUE 2.0 LDAP <br />
*GLUE 2.0 XML<br />
<br />
=== Storage.Management ===<br />
<br />
*CDMI 1.0 <br />
*SRM 2.2<br />
<br />
=== Storage.FileTransfer ===<br />
<br />
*GridFTP v2<br />
<br />
=== Storage.FileAccess ===<br />
<br />
*NFS 4.1 <br />
*WebDAV<br />
<br />
=== Network.Transport ===<br />
<br />
*IPv6<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*TCloud 1.0 <br />
*OVF 1.0<br />
<br />
=== Client.API ===<br />
<br />
*SAGA Core API <br />
*SAGA Advert API <br />
*SAGA Service Discovery API <br />
*SAGA C++ Language Bindings <br />
*SAGA Information Service Navigator API Extension <br />
*SAGA Python Language Bindings <br />
*SAGA Message API extension <br />
*Checkpoint and Recovery API <br />
*DRMAA V2<br />
<br />
=== Compute.JobExecution ===<br />
<br />
*BES <br />
*HPC-Basic Profile <br />
*HPC File Staging Profile <br />
*JSDL <br />
*JSDL HPC <br />
*JSDL SPMD <br />
*EMI-ES<br />
<br />
=== Compute.ParallelJobExecution ===<br />
<br />
*OpenMP <br />
*MPI<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
* OCCI 1.2<br />
** OCCI Core<br />
** OCCI Compute Resource Templates Profile<br />
** OCCI HTTP Protocol<br />
** OCCI Infrastructure<br />
** OCCI JSON rendering<br />
** OCCI Text rendering<br />
* OVF (ISO/IEC 17203:2011)<br />
<br />
=== Security.Authentication&authorization ===<br />
<br />
*X.509 <br />
*X.509 Proxy Certificate <br />
*SAML 2.0<br />
*SAML 2.0 <br />
/* *XACML 2.0 */<br />
*OpenID Connect<br />
<br />
=== Operations.Accounting ===<br />
<br />
*OGF&nbsp;UR 1.0<br />
*OGF&nbsp;UR 2.0<br />
*Compute extension to OGF UR 1.0 <br />
*OGF&nbsp;STAR [[https://forge.gridforum.org/sf/go/artf6532?nav=1 www]]<br></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Standards&diff=96762Standards2017-08-29T14:06:42Z<p>Psolagna: /* Information.Model */</p>
<hr />
<div>[[Category:Policy]]<br />
This page contains references to the most relevant standards for DCI in the EGI context. They are also listed in the [https://documents.egi.eu/document/721 EGI Standards Roadmap]. For suggestions/amendements, contact [http://www.egi.eu/about/staff/ Sergio Andreozzi]. <br />
<br />
== Standards for DCIs by Capability ==<br />
<br />
=== Information.Messagging ===<br />
<br />
*AMQP 1.0 <br />
*LDAPv3 <br />
*STOMP [[http://stomp.github.com/ www]]<br />
<br />
=== Information.Model ===<br />
<br />
*GLUE 2.0 Conceptual<br />
** GLUE 2.1 under approval <br />
*GLUE 2.0 LDAP <br />
*GLUE 2.0 XML<br />
<br />
=== Storage.Management ===<br />
<br />
*CDMI 1.0 <br />
*SRM 2.2<br />
<br />
=== Storage.FileTransfer ===<br />
<br />
*GridFTP v2<br />
<br />
=== Storage.FileAccess ===<br />
<br />
*NFS 4.1 <br />
*WebDAV<br />
<br />
=== Network.Transport ===<br />
<br />
*IPv6<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*TCloud 1.0 <br />
*OVF 1.0<br />
<br />
=== Client.API ===<br />
<br />
*SAGA Core API <br />
*SAGA Advert API <br />
*SAGA Service Discovery API <br />
*SAGA C++ Language Bindings <br />
*SAGA Information Service Navigator API Extension <br />
*SAGA Python Language Bindings <br />
*SAGA Message API extension <br />
*Checkpoint and Recovery API <br />
*DRMAA V2<br />
<br />
=== Compute.JobExecution ===<br />
<br />
*BES <br />
*HPC-Basic Profile <br />
*HPC File Staging Profile <br />
*JSDL <br />
*JSDL HPC <br />
*JSDL SPMD <br />
*EMI-ES<br />
<br />
=== Compute.ParallelJobExecution ===<br />
<br />
*OpenMP <br />
*MPI<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*OCCI Core <br />
*OCCI Infrastructure <br />
*OCCI HTTP Rendering<br />
<br />
=== Security.Authentication&authorization ===<br />
<br />
*X.509 <br />
*X.509 Proxy Certificate <br />
*SAML 2.0<br />
*SAML 2.0 <br />
*XACML 2.0<br />
<br />
=== Operations.Accounting ===<br />
<br />
*OGF&nbsp;UR 1.0<br />
*OGF&nbsp;UR 2.0<br />
*Compute extension to OGF UR 1.0 <br />
*OGF&nbsp;STAR [[https://forge.gridforum.org/sf/go/artf6532?nav=1 www]]<br></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Standards&diff=96761Standards2017-08-29T14:05:30Z<p>Psolagna: /* Standards for DCIs by Capability */</p>
<hr />
<div>[[Category:Policy]]<br />
This page contains references to the most relevant standards for DCI in the EGI context. They are also listed in the [https://documents.egi.eu/document/721 EGI Standards Roadmap]. For suggestions/amendements, contact [http://www.egi.eu/about/staff/ Sergio Andreozzi]. <br />
<br />
== Standards for DCIs by Capability ==<br />
<br />
=== Information.Messagging ===<br />
<br />
*AMQP 1.0 <br />
*LDAPv3 <br />
*STOMP [[http://stomp.github.com/ www]]<br />
<br />
=== Information.Model ===<br />
<br />
*GLUE 2.0 Conceptual <br />
*GLUE 2.0 LDAP <br />
*GLUE 2.0 XML<br />
<br />
=== Storage.Management ===<br />
<br />
*CDMI 1.0 <br />
*SRM 2.2<br />
<br />
=== Storage.FileTransfer ===<br />
<br />
*GridFTP v2<br />
<br />
=== Storage.FileAccess ===<br />
<br />
*NFS 4.1 <br />
*WebDAV<br />
<br />
=== Network.Transport ===<br />
<br />
*IPv6<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*TCloud 1.0 <br />
*OVF 1.0<br />
<br />
=== Client.API ===<br />
<br />
*SAGA Core API <br />
*SAGA Advert API <br />
*SAGA Service Discovery API <br />
*SAGA C++ Language Bindings <br />
*SAGA Information Service Navigator API Extension <br />
*SAGA Python Language Bindings <br />
*SAGA Message API extension <br />
*Checkpoint and Recovery API <br />
*DRMAA V2<br />
<br />
=== Compute.JobExecution ===<br />
<br />
*BES <br />
*HPC-Basic Profile <br />
*HPC File Staging Profile <br />
*JSDL <br />
*JSDL HPC <br />
*JSDL SPMD <br />
*EMI-ES<br />
<br />
=== Compute.ParallelJobExecution ===<br />
<br />
*OpenMP <br />
*MPI<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*OCCI Core <br />
*OCCI Infrastructure <br />
*OCCI HTTP Rendering<br />
<br />
=== Security.Authentication&authorization ===<br />
<br />
*X.509 <br />
*X.509 Proxy Certificate <br />
*SAML 2.0<br />
*SAML 2.0 <br />
*XACML 2.0<br />
<br />
=== Operations.Accounting ===<br />
<br />
*OGF&nbsp;UR 1.0<br />
*OGF&nbsp;UR 2.0<br />
*Compute extension to OGF UR 1.0 <br />
*OGF&nbsp;STAR [[https://forge.gridforum.org/sf/go/artf6532?nav=1 www]]<br></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Standards&diff=96760Standards2017-08-29T14:02:59Z<p>Psolagna: /* Technology Providers and Standards */</p>
<hr />
<div>[[Category:Policy]]<br />
This page contains references to the most relevant standards for DCI in the EGI context. They are also listed in the [https://documents.egi.eu/document/721 EGI Standards Roadmap]. For suggestions/amendements, contact [http://www.egi.eu/about/staff/ Sergio Andreozzi]. <br />
<br />
== Standards for DCIs by Capability ==<br />
<br />
=== Information.Messagging ===<br />
<br />
*AMQP 1.0 <br />
*LDAPv3 <br />
*STOMP [[http://stomp.github.com/ www]]<br />
<br />
=== Information.Model ===<br />
<br />
*GLUE 2.0 Conceptual <br />
*GLUE 2.0 LDAP <br />
*GLUE 2.0 XML<br />
<br />
=== Storage.Management ===<br />
<br />
*CDMI 1.0 <br />
*SRM 2.2<br />
<br />
=== Storage.FileTransfer ===<br />
<br />
*GridFTP v2<br />
<br />
=== Storage.FileAccess ===<br />
<br />
*NFS 4.1 <br />
*WebDAV<br />
<br />
=== Network.Transport ===<br />
<br />
*IPv6<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*TCloud 1.0 <br />
*OVF 1.0<br />
<br />
=== Client.API ===<br />
<br />
*SAGA Core API <br />
*SAGA Advert API <br />
*SAGA Service Discovery API <br />
*SAGA C++ Language Bindings <br />
*SAGA Information Service Navigator API Extension <br />
*SAGA Python Language Bindings <br />
*SAGA Message API extension <br />
*Checkpoint and Recovery API <br />
*DRMAA V2<br />
<br />
=== Compute.JobExecution ===<br />
<br />
*BES <br />
*HPC-Basic Profile <br />
*HPC File Staging Profile <br />
*JSDL <br />
*JSDL HPC <br />
*JSDL SPMD <br />
*EMI-ES<br />
<br />
=== Compute.ParallelJobExecution ===<br />
<br />
*OpenMP <br />
*MPI<br />
<br />
=== VirtualMachine.Management ===<br />
<br />
*OCCI Core <br />
*OCCI Infrastructure <br />
*OCCI HTTP Rendering<br />
<br />
=== Security.Authentication ===<br />
<br />
*X.509 <br />
*X.509 Proxy Certificate <br />
*SAML 2.0<br />
<br />
=== Security.Authorization ===<br />
<br />
*SAML 2.0 <br />
*XACML 2.0<br />
<br />
=== Operations.Accounting ===<br />
<br />
*OGF&nbsp;UR 1.0<br />
*OGF&nbsp;UR 2.0<br />
*Compute extension to OGF UR 1.0 <br />
*OGF&nbsp;STAR [[https://forge.gridforum.org/sf/go/artf6532?nav=1 www]]<br></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96393EGI-Engage:AMB-2017-08-012017-08-01T08:45:36Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
Email with timeline and instructions sent to Admin-Finance mailing list for effort report and cost claim:<br />
<br />
<br />
EGI-Engage Project ends on August 31st, 2017. The financial report is due within 40 days (due to the review date) thus the following timeline will apply to prepare the final cost statement:<br />
<br />
FINANCIAL REPORTING PERIOD: 1/03/2016 - 31/08/2017 - 18 months<br />
* by Fri 15/09/17: Partners report efforts and costs in Authore (see below)<br />
* 18-22/09/17: Checking data by the Project Office<br />
* Tues 26/09/17: AMB review of financial report + feedback to project office<br />
* Mon 09/10/17: Submission 1st draft financial report: (2nd review rehearsal planned on 10/10/17)<br />
* Mon 16/10/17 -strict-: Submission 2nd draft financial report to EC reviewers<br />
* Thu 23-24/10/17: Project Review in Brussels<br />
<br />
EFFORTS AND COSTS REPORT IN AUTHORE:<br />
* log in using your EGI SSO account: https://egi.authore.com<br />
** please adjust efforts in M13-18 and in M19-M24 where needed and enter actual personnel and travel costs<br />
** please complete efforts in M25-30 (Mar-Aug 2017) and enter actual personnel and travel costs<br />
** inform Project office if actual efforts and costs deviate from the plan;<br />
** contact Project office for ADJUSTMENT OF P1<br />
* Only the actual costs of personnel and travels are eligible, i.e., those costs that are verifiable in your books. The 25 % flat overhead is automatically calculated in Authore.<br />
** FAQ / Guidelines attached for your convenience (or visit our wiki here and here)<br />
<br />
After the Project Review the submission of the costs on the EC portal -deadline 30/10/2017- is done by each lead beneficiary based on the Form C validated/extracted from Authore. The lead beneficiary will encode in the system the Form C of the 3rd parties and the system will combine them into a consolidated financial statement.<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu) <br />
**Ongoing content writing; chasing of allocated actions on specific individuals: [https://docs.google.com/document/d/1dOg4p3fQDc3QzR8tczCPMU2nEy6BuZp9OWdCCOQNDHs/edit# D2.13 Google Doc] <br />
** External review next week<br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu) <br />
**Content maturing; chasing individuals for content: [https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit D2.14 Google Doc]<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Communication channels:<br />
** DI4R announcements; news about the project positive evaluation <br />
* Publications:<br />
** [https://www.egi.eu/wp-content/uploads/2017/07/EGI-CSIRT-report-July-2017.pdf EGI CSIRT report] completed and added to the EGI publication catalogue and Security Coordination service page<br />
** First (layout) drafts and concept for EGI for RIs publication<br />
** CheckIn leaflet: editing the text provided by service owners, first layout<br />
* Events:<br />
** DI4R17: first draft of the event Indico page<br />
* Website: new pages added to the service catalogues<br />
* Reporting work for D2.14<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
*Strategy <br />
** SIB: 4 members accepted, planning first meeting in September<br />
**EGI Strategy Update 2017 <br />
***Editorial Board Set <br />
***First meeting held 20 July; 4 scheduled for August: https://indico.egi.eu/indico/category/208/<br />
<br />
*IMS Updates <br />
**Management Review held 27 July: https://confluence.egi.eu/display/IMS/2017-07-27+Management+review <br />
**New internal training and certification discussed for conducting Audits: https://confluence.egi.eu/display/IMS/Auditor+Certification <br />
**Numerous usage of the IMS too many to list<br />
** Organised and chaired: SSB No 29: https://indico.egi.eu/indico/event/3407/<br />
*** Created initial service roadmap and planned major changes to be approved for next Council in October https://confluence.egi.eu/display/IMS/Service+Roadmap<br />
<br />
*FitSM <br />
**SURFsara In-House Training <br />
***Service offer accepted for a total of 6 courses (4 FND + 2 ADV) <br />
***Scheduled over Aug and Sept <br />
**OSG (US) discussions for providing FitSM support ongoing (New) <br />
**EXIN call on 27 July presenting FitSM (large certification and accreditation provider, potential to replace the void left by TUV SUD) + internal FitSM WG dicussions<br />
<br />
*Pay-for-Use <br />
**Contributions to be provided within D2.13, D2.14 and D3.16 <br />
**Additional providers under discussion thanks to NextGEOSS (clarity that P4U includes the possibility of charging for only human effort)<br />
<br />
*Collaborations <br />
**GEANT: Meeting held 31 July<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
*SME Engagement <br />
**Main activity is to collect contributions to D2.14 <br />
**Ongoing collaborations under discussion: T-Systems, UK start-up, BfR,EODC<br />
<br />
*Market Analysis <br />
**2 documents being prepared by FAO, several interviews conducted: <br />
***Service Delivery Model from data centre to community: https://docs.google.com/document/d/1L1VOOdulWU_J7IaVIm7dPmsstmQYSouV3DiX2gZuGQU/edit?ts=59761450 <br />
***Legal interoperability and data sharing - Concrete Use Case: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#heading=h.ddqrsgrf90g3<br />
<br><br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype. In external review.<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace. New version implementing reviewers' comment ready in the document server.<br />
* M30: D3.17 Final release of the accounting and operational tools: Internal review. External review will start by today.<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* Done: Provisioning of VOMS information through SAML/OIDC interfaces (Connectors to Ops Portal) done.<br />
** This enables the moving into production of the AppDB VMOps dashboard<br />
* In progress: Translation of VO information into VOMS proxies<br />
* In progress: Self-service web UI for managing OIDC/Oauth2 tokens<br />
** Relevant for the EGI FedCloud<br />
* In progress: Ops Portal and ARGO integration<br />
* Draft of a service brochure for CheckIn<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
Giuseppe, Peter and Alessandro will manage the activity during my holidays.<br />
* In progress: Service order management tool. Main features are available, minor issues to be fixed. Currently in testing.<br />
** Marketplace Integration with RT<br />
** Workflow to automate AoDS service order management<br />
** Integration with CheckIn service to record users in the vo.access.egi.eu VO<br />
* In progress: Dashboard in PrestaShop customised according EGI needs<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud Accounting<br />
** Cloud schema v0.4 rollout finalised.<br />
** Long running VM support is under testing: Some corner cases that are being tracked down. Upgrade to the HW is needed to move the features in production.<br />
* Storage accounting<br />
** 26 RPs have sent storage accounting records within the last two months.<br />
** 20 RPs validated, 3 in progress, 3 are OK but don’t have Alice usage<br />
** New service type added to GOCDB (‘eu.egi.storage.accounting’).<br />
** A few final tweaks and then planning to put into production Aug/Sept.<br />
* Accounting Portal - New release to be deployed by this week.<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Discipline account report<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops portal:<br />
** VAPOR 2.3 released. Release note: operations-portal.egi.eu/vapor_dev/releases?name=VAPOR+2.3<br />
** Ops portal 4.2 in preparation:<br />
*** integration of complementary metrics for the VO : information about accounting data and AppDB changes<br />
*** improvements on the Vo ID Card<br />
*** Integration of EGI Checkin<br />
*** Use of the new ARGO messaging system<br />
* GOCDB - ongoing tasks that will be completed by end of August:<br />
** Defining allowed methods for write API extension (on the wiki)<br />
** Write API extension for services and service endpoints.<br />
** working on data freshness check<br />
** Move to new STFC infrastructure required for IPv6 support.<br />
** GUI improvements (as defined in https://rt.egi.eu/rt/Ticket/Display.html?id=11546 & https://rt.egi.eu/rt/Ticket/Display.html?id=11217) <br />
** Bug fixes of issues in GitHub issues list: https://github.com/GOCDB/gocdb/issues<br />
* Monitoring and messagging:<br />
** many activities in progress. See https://indico.egi.eu/indico/event/3388/contribution/4/material/slides/0.pdf for details<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) Final checks, almost ready for submission<br />
* D4.10 Final CANFAR integration release (PM29) Under review (Peter and Andre Schaaff)<br />
* M4.3 Open Data Platform in the Production (PM30) Under lightweight review (Peter and Tiziana)<br />
=== Task JRA2.1 Federated Open Data ===<br />
* New bugs found in latest Onedata version, next planned date for upgrade of EGI DataHub is the end of the week<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* ENES EGI/EUDAT work now being followed by regular monthly calls. They are testing with B2STAGE/B2SAFE hosted at STFC<br />
* d4science have asked for an increase in EGI resources. Current usage is unclear due to possible problems in the accounting.<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* IISAS working with APEL team in testing GPGPU changes to accounting. If everything goes to plan, the production upgrade with this functionality will be in August<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* Still waiting inputs for D5.4<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* OMB Discussion: EGI needs to facilitate the sharing of experiences between NGIs who are providing SaaS and other managed services<br />
* Analysis of the reasons behind the VOs decreasing usage<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation of OMB<br />
* Analysis of the survey run among operations centres<br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
* Discussion with SA2 about the iMarine SLA, and a possible extension (end expansion)<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Site Security Challenge currently ongoing (10 sites involved)<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96392EGI-Engage:AMB-2017-08-012017-08-01T08:39:16Z<p>Psolagna: /* Task JRA1.1 Authentication and Authorisation Infrastructure */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
Email with timeline and instructions sent to Admin-Finance mailing list for effort report and cost claim:<br />
<br />
<br />
EGI-Engage Project ends on August 31st, 2017. The financial report is due within 40 days (due to the review date) thus the following timeline will apply to prepare the final cost statement:<br />
<br />
FINANCIAL REPORTING PERIOD: 1/03/2016 - 31/08/2017 - 18 months<br />
* by Fri 15/09/17: Partners report efforts and costs in Authore (see below)<br />
* 18-22/09/17: Checking data by the Project Office<br />
* Tues 26/09/17: AMB review of financial report + feedback to project office<br />
* Mon 09/10/17: Submission 1st draft financial report: (2nd review rehearsal planned on 10/10/17)<br />
* Mon 16/10/17 -strict-: Submission 2nd draft financial report to EC reviewers<br />
* Thu 23-24/10/17: Project Review in Brussels<br />
<br />
EFFORTS AND COSTS REPORT IN AUTHORE:<br />
* log in using your EGI SSO account: https://egi.authore.com<br />
** please adjust efforts in M13-18 and in M19-M24 where needed and enter actual personnel and travel costs<br />
** please complete efforts in M25-30 (Mar-Aug 2017) and enter actual personnel and travel costs<br />
** inform Project office if actual efforts and costs deviate from the plan;<br />
** contact Project office for ADJUSTMENT OF P1<br />
* Only the actual costs of personnel and travels are eligible, i.e., those costs that are verifiable in your books. The 25 % flat overhead is automatically calculated in Authore.<br />
** FAQ / Guidelines attached for your convenience (or visit our wiki here and here)<br />
<br />
After the Project Review the submission of the costs on the EC portal -deadline 30/10/2017- is done by each lead beneficiary based on the Form C validated/extracted from Authore. The lead beneficiary will encode in the system the Form C of the 3rd parties and the system will combine them into a consolidated financial statement.<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu) <br />
**Ongoing content writing; chasing of allocated actions on specific individuals: [https://docs.google.com/document/d/1dOg4p3fQDc3QzR8tczCPMU2nEy6BuZp9OWdCCOQNDHs/edit# D2.13 Google Doc] <br />
** External review next week<br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu) <br />
**Content maturing; chasing individuals for content: [https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit D2.14 Google Doc]<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Communication channels:<br />
** DI4R announcements; news about the project positive evaluation <br />
* Publications:<br />
** [https://www.egi.eu/wp-content/uploads/2017/07/EGI-CSIRT-report-July-2017.pdf EGI CSIRT report] completed and added to the EGI publication catalogue and Security Coordination service page<br />
** First (layout) drafts and concept for EGI for RIs publication<br />
** CheckIn leaflet: editing the text provided by service owners, first layout<br />
* Events:<br />
** DI4R17: first draft of the event Indico page<br />
* Website: new pages added to the service catalogues<br />
* Reporting work for D2.14<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
*Strategy <br />
** SIB: 4 members accepted, planning first meeting in September<br />
**EGI Strategy Update 2017 <br />
***Editorial Board Set <br />
***First meeting held 20 July; 4 scheduled for August: https://indico.egi.eu/indico/category/208/<br />
<br />
*IMS Updates <br />
**Management Review held 27 July: https://confluence.egi.eu/display/IMS/2017-07-27+Management+review <br />
**New internal training and certification discussed for conducting Audits: https://confluence.egi.eu/display/IMS/Auditor+Certification <br />
**Numerous usage of the IMS too many to list<br />
** Organised and chaired: SSB No 29: https://indico.egi.eu/indico/event/3407/<br />
*** Created initial service roadmap and planned major changes to be approved for next Council in October https://confluence.egi.eu/display/IMS/Service+Roadmap<br />
<br />
*FitSM <br />
**SURFsara In-House Training <br />
***Service offer accepted for a total of 6 courses (4 FND + 2 ADV) <br />
***Scheduled over Aug and Sept <br />
**OSG (US) discussions for providing FitSM support ongoing (New) <br />
**EXIN call on 27 July presenting FitSM (large certification and accreditation provider, potential to replace the void left by TUV SUD) + internal FitSM WG dicussions<br />
<br />
*Pay-for-Use <br />
**Contributions to be provided within D2.13, D2.14 and D3.16 <br />
**Additional providers under discussion thanks to NextGEOSS (clarity that P4U includes the possibility of charging for only human effort)<br />
<br />
*Collaborations <br />
**GEANT: Meeting held 31 July<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
*SME Engagement <br />
**Main activity is to collect contributions to D2.14 <br />
**Ongoing collaborations under discussion: T-Systems, UK start-up, BfR,EODC<br />
<br />
*Market Analysis <br />
**2 documents being prepared by FAO, several interviews conducted: <br />
***Service Delivery Model from data centre to community: https://docs.google.com/document/d/1L1VOOdulWU_J7IaVIm7dPmsstmQYSouV3DiX2gZuGQU/edit?ts=59761450 <br />
***Legal interoperability and data sharing - Concrete Use Case: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#heading=h.ddqrsgrf90g3<br />
<br><br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype. In external review.<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace. New version implementing reviewers' comment ready in the document server.<br />
* M30: D3.17 Final release of the accounting and operational tools: Internal review. External review will start by today.<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* Done: Provisioning of VOMS information through SAML/OIDC interfaces (Connectors to Ops Portal) done.<br />
** This enables the moving into production of the AppDB VMOps dashboard<br />
* In progress: Translation of VO information into VOMS proxies<br />
* In progress: Self-service web UI for managing OIDC/Oauth2 tokens<br />
** Relevant for the EGI FedCloud<br />
* In progress: Ops Portal and ARGO integration<br />
* Draft of a service brochure for CheckIn<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
Giuseppe, Peter and Alessandro will manage the activity during my holidays.<br />
* In progress: Service order management tool. Main features are available, minor issues to be fixed. Currently in testing.<br />
** Marketplace Integration with RT<br />
** Workflow to automate AoDS service order management<br />
** Integration with CheckIn service to record users in the vo.access.egi.eu VO<br />
* In progress: Dashboard in PrestaShop customised according EGI needs<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud Accounting<br />
** Cloud schema v0.4 rollout finalised.<br />
** Long running VM support is under testing: Some corner cases that are being tracked down. Upgrade to the HW is needed to move the features in production.<br />
* Storage accounting<br />
** 26 RPs have sent storage accounting records within the last two months.<br />
** 20 RPs validated, 3 in progress, 3 are OK but don’t have Alice usage<br />
** New service type added to GOCDB (‘eu.egi.storage.accounting’).<br />
** A few final tweaks and then planning to put into production Aug/Sept.<br />
* Accounting Portal - New release to be deployed by this week.<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Discipline account report<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops portal:<br />
** VAPOR 2.3 released. Release note: operations-portal.egi.eu/vapor_dev/releases?name=VAPOR+2.3<br />
** Ops portal 4.2 in preparation:<br />
*** integration of complementary metrics for the VO : information about accounting data and AppDB changes<br />
*** improvements on the Vo ID Card<br />
*** Integration of EGI Checkin<br />
*** Use of the new ARGO messaging system<br />
* GOCDB - ongoing tasks that will be completed by end of August:<br />
** Defining allowed methods for write API extension (on the wiki)<br />
** Write API extension for services and service endpoints.<br />
** working on data freshness check<br />
** Move to new STFC infrastructure required for IPv6 support.<br />
** GUI improvements (as defined in https://rt.egi.eu/rt/Ticket/Display.html?id=11546 & https://rt.egi.eu/rt/Ticket/Display.html?id=11217) <br />
** Bug fixes of issues in GitHub issues list: https://github.com/GOCDB/gocdb/issues<br />
* Monitoring and messagging:<br />
** many activities in progress. See https://indico.egi.eu/indico/event/3388/contribution/4/material/slides/0.pdf for details<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) Final checks, almost ready for submission<br />
* D4.10 Final CANFAR integration release (PM29) Under review (Peter and Andre Schaaff)<br />
* M4.3 Open Data Platform in the Production (PM30) Under lightweight review (Peter and Tiziana)<br />
=== Task JRA2.1 Federated Open Data ===<br />
* New bugs found in latest Onedata version, next planned date for upgrade of EGI DataHub is the end of the week<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* ENES EGI/EUDAT work now being followed by regular monthly calls. They are testing with B2STAGE/B2SAFE hosted at STFC<br />
* d4science have asked for an increase in EGI resources. Current usage is unclear due to possible problems in the accounting.<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* IISAS working with APEL team in testing GPGPU changes to accounting. If everything goes to plan, the production upgrade with this functionality will be in August<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* Still waiting inputs for D5.4<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* OMB Discussion: EGI needs to facilitate the sharing of experiences between NGIs who are providing SaaS and other managed services<br />
* Analysis of the reasons behind the VOs decreasing usage<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation of OMB<br />
* Analysis of the survey run among operations centres<br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Site Security Challenge currently ongoing (10 sites involved)<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96386EGI-Engage:AMB-2017-08-012017-08-01T08:31:54Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu) <br />
**Ongoing content writing; chasing of allocated actions on specific individuals: [https://docs.google.com/document/d/1dOg4p3fQDc3QzR8tczCPMU2nEy6BuZp9OWdCCOQNDHs/edit# D2.13 Google Doc] <br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu) <br />
**Content maturing; chasing individuals for content: [https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit D2.14 Google Doc]<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Communication channels:<br />
** DI4R announcements; news about the project positive evaluation <br />
* Publications:<br />
** [https://www.egi.eu/wp-content/uploads/2017/07/EGI-CSIRT-report-July-2017.pdf EGI CSIRT report] completed and added to the EGI publication catalogue and Security Coordination service page<br />
** First (layout) drafts and concept for EGI for RIs publication<br />
** CheckIn leaflet: editing the text provided by service owners, first layout<br />
* Events:<br />
** DI4R17: first draft of the event Indico page<br />
* Website: new pages added to the service catalogues<br />
* Reporting work for D2.14<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
*Strategy <br />
** SIB: 4 members accepted, planning first meeting in September<br />
**EGI Strategy Update 2017 <br />
***Editorial Board Set <br />
***First meeting held 20 July; 4 scheduled for August: https://indico.egi.eu/indico/category/208/<br />
<br />
*IMS Updates <br />
**Management Review held 27 July: https://confluence.egi.eu/display/IMS/2017-07-27+Management+review <br />
**New internal training and certification discussed for conducting Audits: https://confluence.egi.eu/display/IMS/Auditor+Certification <br />
**Numerous usage of the IMS too many to list<br />
** Organised and chaired: SSB No 29: https://indico.egi.eu/indico/event/3407/<br />
*** Created initial service roadmap and planned major changes to be approved for next Council in October https://confluence.egi.eu/display/IMS/Service+Roadmap<br />
<br />
*FitSM <br />
**SURFsara In-House Training <br />
***Service offer accepted for a total of 6 courses (4 FND + 2 ADV) <br />
***Scheduled over Aug and Sept <br />
**OSG (US) discussions for providing FitSM support ongoing (New) <br />
**EXIN call on 27 July presenting FitSM (large certification and accreditation provider, potential to replace the void left by TUV SUD) + internal FitSM WG dicussions<br />
<br />
*Pay-for-Use <br />
**Contributions to be provided within D2.13, D2.14 and D3.16 <br />
**Additional providers under discussion thanks to NextGEOSS (clarity that P4U includes the possibility of charging for only human effort)<br />
<br />
*Collaborations <br />
**GEANT: Meeting held 31 July<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
*SME Engagement <br />
**Main activity is to collect contributions to D2.14 <br />
**Ongoing collaborations under discussion: T-Systems, UK start-up, BfR,EODC<br />
<br />
*Market Analysis <br />
**2 documents being prepared by FAO, several interviews conducted: <br />
***Service Delivery Model from data centre to community: https://docs.google.com/document/d/1L1VOOdulWU_J7IaVIm7dPmsstmQYSouV3DiX2gZuGQU/edit?ts=59761450 <br />
***Legal interoperability and data sharing - Concrete Use Case: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#heading=h.ddqrsgrf90g3<br />
<br><br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype. In external review.<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace. New version implementing reviewers' comment ready in the document server.<br />
* M30: D3.17 Final release of the accounting and operational tools: Internal review. External review will start by today.<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* Done: Provisioning of VOMS information through SAML/OIDC interfaces (Connectors to Ops Portal) done.<br />
** This enables the moving into production of the AppDB VMOps dashboard<br />
* In progress: Translation of VO information into VOMS proxies<br />
* In progress: Self-service web UI for managing OIDC/Oauth2 tokens<br />
** Relevant for the EGI FedCloud<br />
* In progress: Ops Portal and ARGO integration<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
Giuseppe, Peter and Alessandro will manage the activity during my holidays.<br />
* In progress: Service order management tool. Main features are available, minor issues to be fixed. Currently in testing.<br />
** Marketplace Integration with RT<br />
** Workflow to automate AoDS service order management<br />
** Integration with CheckIn service to record users in the vo.access.egi.eu VO<br />
* In progress: Dashboard in PrestaShop customised according EGI needs<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud Accounting<br />
** Cloud schema v0.4 rollout finalised.<br />
** Long running VM support is under testing: Some corner cases that are being tracked down. Upgrade to the HW is needed to move the features in production.<br />
* Storage accounting<br />
** 26 RPs have sent storage accounting records within the last two months.<br />
** 20 RPs validated, 3 in progress, 3 are OK but don’t have Alice usage<br />
** New service type added to GOCDB (‘eu.egi.storage.accounting’).<br />
** A few final tweaks and then planning to put into production Aug/Sept.<br />
* Accounting Portal - New release to be deployed by this week.<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Discipline account report<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops portal:<br />
** VAPOR 2.3 released. Release note: operations-portal.egi.eu/vapor_dev/releases?name=VAPOR+2.3<br />
** Ops portal 4.2 in preparation:<br />
*** integration of complementary metrics for the VO : information about accounting data and AppDB changes<br />
*** improvements on the Vo ID Card<br />
*** Integration of EGI Checkin<br />
*** Use of the new ARGO messaging system<br />
* GOCDB - ongoing tasks that will be completed by end of August:<br />
** Defining allowed methods for write API extension (on the wiki)<br />
** Write API extension for services and service endpoints.<br />
** working on data freshness check<br />
** Move to new STFC infrastructure required for IPv6 support.<br />
** GUI improvements (as defined in https://rt.egi.eu/rt/Ticket/Display.html?id=11546 & https://rt.egi.eu/rt/Ticket/Display.html?id=11217) <br />
** Bug fixes of issues in GitHub issues list: https://github.com/GOCDB/gocdb/issues<br />
* Monitoring and messagging:<br />
** many activities in progress. See https://indico.egi.eu/indico/event/3388/contribution/4/material/slides/0.pdf for details<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) Final checks, almost ready for submission<br />
* D4.10 Final CANFAR integration release (PM29) Under review (Peter and Andre Schaaff)<br />
* M4.3 Open Data Platform in the Production (PM30) Under lightweight review (Peter and Tiziana)<br />
=== Task JRA2.1 Federated Open Data ===<br />
* New bugs found in latest Onedata version, next planned date for upgrade of EGI DataHub is the end of the week<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* ENES EGI/EUDAT work now being followed by regular monthly calls. They are testing with B2STAGE/B2SAFE hosted at STFC<br />
* d4science have asked for an increase in EGI resources. Current usage is unclear due to possible problems in the accounting.<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* IISAS working with APEL team in testing GPGPU changes to accounting. If everything goes to plan, the production upgrade with this functionality will be in August<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* Still waiting inputs for D5.4<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* OMB Discussion: EGI needs to facilitate the sharing of experiences between NGIs who are providing SaaS and other managed services<br />
* Analysis of the reasons behind the VOs decreasing usage<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation of OMB<br />
* Analysis of the survey run among operations centres<br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Site Security Challenge currently ongoing (10 sites involved)<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96360EGI-Engage:AMB-2017-08-012017-08-01T07:58:58Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu) <br />
**Ongoing content writing; chasing of allocated actions on specific individuals: [https://docs.google.com/document/d/1dOg4p3fQDc3QzR8tczCPMU2nEy6BuZp9OWdCCOQNDHs/edit# D2.13 Google Doc] <br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu) <br />
**Content maturing; chasing individuals for content: [https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit D2.14 Google Doc]<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Communication channels:<br />
** DI4R announcements; news about the project positive evaluation <br />
* Publications:<br />
** [https://www.egi.eu/wp-content/uploads/2017/07/EGI-CSIRT-report-July-2017.pdf EGI CSIRT report] completed and added to the EGI publication catalogue and Security Coordination service page<br />
** First (layout) drafts and concept for EGI for RIs publication<br />
** CheckIn leaflet: editing the text provided by service owners, first layout<br />
* Events:<br />
** DI4R17: first draft of the event Indico page<br />
* Website: new pages added to the service catalogues<br />
* Reporting work for D2.14<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
*Strategy <br />
**EGI Strategy Update 2017 <br />
***Editorial Board Set <br />
***First meeting held 20 July; 4 scheduled for August: https://indico.egi.eu/indico/category/208/<br />
<br />
*IMS Updates <br />
**Management Review held 27 July: https://confluence.egi.eu/display/IMS/2017-07-27+Management+review <br />
**New internal training and certification discussed for conducting Audits: https://confluence.egi.eu/display/IMS/Auditor+Certification <br />
**Numerous usage of the IMS too many to list<br />
<br />
*FitSM <br />
**SURFsara In-House Training <br />
***Service offer accepted for a total of 6 courses (4 FND + 2 ADV) <br />
***Scheduled over Aug and Sept <br />
**OSG (US) discussions for providing FitSM support ongoing (New) <br />
**EXIN call on 27 July presenting FitSM (large certification and accreditation provider, potential to replace the void left by TUV SUD) + internal FitSM WG dicussions<br />
<br />
*Pay-for-Use <br />
**Contributions to be provided within D2.13, D2.14 and D3.16 <br />
**Additional providers under discussion thanks to NextGEOSS (clarity that P4U includes the possibility of charging for only human effort)<br />
<br />
*Collaborations <br />
**GEANT: Meeting held 31 July<br />
<br><br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
*SME Engagement <br />
**Main activity is to collect contributions to D2.14 <br />
**Ongoing collaborations under discussion: T-Systems, UK start-up, BfR,EODC<br />
<br />
*Market Analysis <br />
**2 documents being prepared by FAO, several interviews conducted: <br />
***Service Delivery Model from data centre to community: https://docs.google.com/document/d/1L1VOOdulWU_J7IaVIm7dPmsstmQYSouV3DiX2gZuGQU/edit?ts=59761450 <br />
***Legal interoperability and data sharing - Concrete Use Case: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#heading=h.ddqrsgrf90g3<br />
<br><br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype. In external review.<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace. New version implementing reviewers' comment ready in the document server.<br />
* M30: D3.17 Final release of the accounting and operational tools: Internal review. External review will start by today.<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* Done: Provisioning of VOMS information through SAML/OIDC interfaces (Connectors to Ops Portal) done.<br />
** This enables the moving into production of the AppDB VMOps dashboard<br />
* In progress: Translation of VO information into VOMS proxies<br />
* In progress: Self-service web UI for managing OIDC/Oauth2 tokens<br />
** Relevant for the EGI FedCloud<br />
* In progress: Ops Portal and ARGO integration<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
Giuseppe, Peter and Alessandro will manage the activity during my holidays.<br />
* In progress: Service order management tool. Main features are available, minor issues to be fixed. Currently in testing.<br />
** Marketplace Integration with RT<br />
** Workflow to automate AoDS service order management<br />
** Integration with CheckIn service to record users in the vo.access.egi.eu VO<br />
* In progress: Dashboard in PrestaShop customised according EGI needs<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud Accounting<br />
** Cloud schema v0.4 rollout finalised.<br />
** Long running VM support is under testing: Some corner cases that are being tracked down. Upgrade to the HW is needed to move the features in production.<br />
* Storage accounting<br />
** 26 RPs have sent storage accounting records within the last two months.<br />
** 20 RPs validated, 3 in progress, 3 are OK but don’t have Alice usage<br />
** New service type added to GOCDB (‘eu.egi.storage.accounting’).<br />
** A few final tweaks and then planning to put into production Aug/Sept.<br />
* Accounting Portal - New release to be deployed by this week.<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Discipline account report<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops portal:<br />
** VAPOR 2.3 released. Release note: operations-portal.egi.eu/vapor_dev/releases?name=VAPOR+2.3<br />
** Ops portal 4.2 in preparation:<br />
*** integration of complementary metrics for the VO : information about accounting data and AppDB changes<br />
*** improvements on the Vo ID Card<br />
*** Integration of EGI Checkin<br />
*** Use of the new ARGO messaging system<br />
* GOCDB - ongoing tasks that will be completed by end of August:<br />
** Defining allowed methods for write API extension (on the wiki)<br />
** Write API extension for services and service endpoints.<br />
** working on data freshness check<br />
** Move to new STFC infrastructure required for IPv6 support.<br />
** GUI improvements (as defined in https://rt.egi.eu/rt/Ticket/Display.html?id=11546 & https://rt.egi.eu/rt/Ticket/Display.html?id=11217) <br />
** Bug fixes of issues in GitHub issues list: https://github.com/GOCDB/gocdb/issues<br />
* Monitoring and messagging:<br />
** many activities in progress. See https://indico.egi.eu/indico/event/3388/contribution/4/material/slides/0.pdf for details<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) Final checks, almost ready for submission<br />
* D4.10 Final CANFAR integration release (PM29) Under review (Peter and Andre Schaaff)<br />
* M4.3 Open Data Platform in the Production (PM30) Under lightweight review (Peter and Tiziana)<br />
=== Task JRA2.1 Federated Open Data ===<br />
* New bugs found in latest Onedata version, next planned date for upgrade of EGI DataHub is the end of the week<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* ENES EGI/EUDAT work now being followed by regular monthly calls. They are testing with B2STAGE/B2SAFE hosted at STFC<br />
* d4science have asked for an increase in EGI resources. Current usage is unclear due to possible problems in the accounting.<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* IISAS working with APEL team in testing GPGPU changes to accounting. If everything goes to plan, the production upgrade with this functionality will be in August<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* Still waiting inputs for D5.4<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* OMB Discussion: EGI needs to facilitate the sharing of experiences between NGIs who are providing SaaS and other managed services<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation of OMB<br />
* Analysis of the survey run among operations centres<br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Site Security Challenge currently ongoing (10 sites involved)<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96357EGI-Engage:AMB-2017-08-012017-08-01T07:55:55Z<p>Psolagna: /* Milestones &amp; Deliverables */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu) <br />
**Ongoing content writing; chasing of allocated actions on specific individuals: [https://docs.google.com/document/d/1dOg4p3fQDc3QzR8tczCPMU2nEy6BuZp9OWdCCOQNDHs/edit# D2.13 Google Doc] <br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu) <br />
**Content maturing; chasing individuals for content: [https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit D2.14 Google Doc]<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br><br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
*Strategy <br />
**EGI Strategy Update 2017 <br />
***Editorial Board Set <br />
***First meeting held 20 July; 4 scheduled for August: https://indico.egi.eu/indico/category/208/<br />
<br />
*IMS Updates <br />
**Management Review held 27 July: https://confluence.egi.eu/display/IMS/2017-07-27+Management+review <br />
**New internal training and certification discussed for conducting Audits: https://confluence.egi.eu/display/IMS/Auditor+Certification <br />
**Numerous usage of the IMS too many to list<br />
<br />
*FitSM <br />
**SURFsara In-House Training <br />
***Service offer accepted for a total of 6 courses (4 FND + 2 ADV) <br />
***Scheduled over Aug and Sept <br />
**OSG (US) discussions for providing FitSM support ongoing (New) <br />
**EXIN call on 27 July presenting FitSM (large certification and accreditation provider, potential to replace the void left by TUV SUD) + internal FitSM WG dicussions<br />
<br />
*Pay-for-Use <br />
**Contributions to be provided within D2.13, D2.14 and D3.16 <br />
**Additional providers under discussion thanks to NextGEOSS (clarity that P4U includes the possibility of charging for only human effort)<br />
<br />
*Collaborations <br />
**GEANT: Meeting held 31 July<br />
<br><br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
*SME Engagement <br />
**Main activity is to collect contributions to D2.14 <br />
**Ongoing collaborations under discussion: T-Systems, UK start-up, BfR,EODC<br />
<br />
*Market Analysis <br />
**2 documents being prepared by FAO, several interviews conducted: <br />
***Service Delivery Model from data centre to community: https://docs.google.com/document/d/1L1VOOdulWU_J7IaVIm7dPmsstmQYSouV3DiX2gZuGQU/edit?ts=59761450 <br />
***Legal interoperability and data sharing - Concrete Use Case: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#heading=h.ddqrsgrf90g3<br />
<br><br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype. In external review.<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace. New version implementing reviewers' comment ready in the document server.<br />
* M30: D3.17 Final release of the accounting and operational tools: Internal review. External review will start by today.<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* Done: Provisioning of VOMS information through SAML/OIDC interfaces (Connectors to Ops Portal) done.<br />
** This enables the moving into production of the AppDB VMOps dashboard<br />
* In progress: Translation of VO information into VOMS proxies<br />
* In progress: Self-service web UI for managing OIDC/Oauth2 tokens<br />
** Relevant for the EGI FedCloud<br />
* In progress: Ops Portal and ARGO integration<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
Giuseppe, Peter and Alessandro will manage the activity during my holidays.<br />
* In progress: Service order management tool. Main features are available, minor issues to be fixed. Currently in testing.<br />
** Marketplace Integration with RT<br />
** Workflow to automate AoDS service order management<br />
** Integration with CheckIn service to record users in the vo.access.egi.eu VO<br />
* In progress: Dashboard in PrestaShop customised according EGI needs<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud Accounting<br />
** Cloud schema v0.4 rollout finalised.<br />
** Long running VM support is under testing: Some corner cases that are being tracked down. Upgrade to the HW is needed to move the features in production.<br />
* Storage accounting<br />
** 26 RPs have sent storage accounting records within the last two months.<br />
** 20 RPs validated, 3 in progress, 3 are OK but don’t have Alice usage<br />
** New service type added to GOCDB (‘eu.egi.storage.accounting’).<br />
** A few final tweaks and then planning to put into production Aug/Sept.<br />
* Accounting Portal - New release to be deployed by this week.<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Discipline account report<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops portal:<br />
** VAPOR 2.3 released. Release note: operations-portal.egi.eu/vapor_dev/releases?name=VAPOR+2.3<br />
** Ops portal 4.2 in preparation:<br />
*** integration of complementary metrics for the VO : information about accounting data and AppDB changes<br />
*** improvements on the Vo ID Card<br />
*** Integration of EGI Checkin<br />
*** Use of the new ARGO messaging system<br />
* GOCDB - ongoing tasks that will be completed by end of August:<br />
** Defining allowed methods for write API extension (on the wiki)<br />
** Write API extension for services and service endpoints.<br />
** working on data freshness check<br />
** Move to new STFC infrastructure required for IPv6 support.<br />
** GUI improvements (as defined in https://rt.egi.eu/rt/Ticket/Display.html?id=11546 & https://rt.egi.eu/rt/Ticket/Display.html?id=11217) <br />
** Bug fixes of issues in GitHub issues list: https://github.com/GOCDB/gocdb/issues<br />
* Monitoring and messagging:<br />
** many activities in progress. See https://indico.egi.eu/indico/event/3388/contribution/4/material/slides/0.pdf for details<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) Final checks, almost ready for submission<br />
* D4.10 Final CANFAR integration release (PM29) Under review (Peter and Andre Schaaff)<br />
* M4.3 Open Data Platform in the Production (PM30) Under lightweight review (Peter and Tiziana)<br />
=== Task JRA2.1 Federated Open Data ===<br />
* New bugs found in latest Onedata version, next planned date for upgrade of EGI DataHub is the end of the week<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* ENES EGI/EUDAT work now being followed by regular monthly calls. They are testing with B2STAGE/B2SAFE hosted at STFC<br />
* d4science have asked for an increase in EGI resources. Current usage is unclear due to possible problems in the accounting.<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* IISAS working with APEL team in testing GPGPU changes to accounting. If everything goes to plan, the production upgrade with this functionality will be in August<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* Still waiting inputs for D5.4<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* OMB Discussion: EGI needs to foster the sharing of experiences between NGIs who are providing SaaS and other managed services<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation of OMB<br />
* Analysis of the survey run among operations centres<br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Site Security Challenge currently ongoing (10 sites involved)<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96356EGI-Engage:AMB-2017-08-012017-08-01T07:54:35Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu) <br />
**Ongoing content writing; chasing of allocated actions on specific individuals: [https://docs.google.com/document/d/1dOg4p3fQDc3QzR8tczCPMU2nEy6BuZp9OWdCCOQNDHs/edit# D2.13 Google Doc] <br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu) <br />
**Content maturing; chasing individuals for content: [https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit D2.14 Google Doc]<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br><br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
*Strategy <br />
**EGI Strategy Update 2017 <br />
***Editorial Board Set <br />
***First meeting held 20 July; 4 scheduled for August: https://indico.egi.eu/indico/category/208/<br />
<br />
*IMS Updates <br />
**Management Review held 27 July: https://confluence.egi.eu/display/IMS/2017-07-27+Management+review <br />
**New internal training and certification discussed for conducting Audits: https://confluence.egi.eu/display/IMS/Auditor+Certification <br />
**Numerous usage of the IMS too many to list<br />
<br />
*FitSM <br />
**SURFsara In-House Training <br />
***Service offer accepted for a total of 6 courses (4 FND + 2 ADV) <br />
***Scheduled over Aug and Sept <br />
**OSG (US) discussions for providing FitSM support ongoing (New) <br />
**EXIN call on 27 July presenting FitSM (large certification and accreditation provider, potential to replace the void left by TUV SUD) + internal FitSM WG dicussions<br />
<br />
*Pay-for-Use <br />
**Contributions to be provided within D2.13, D2.14 and D3.16 <br />
**Additional providers under discussion thanks to NextGEOSS (clarity that P4U includes the possibility of charging for only human effort)<br />
<br />
*Collaborations <br />
**GEANT: Meeting held 31 July<br />
<br><br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
*SME Engagement <br />
**Main activity is to collect contributions to D2.14 <br />
**Ongoing collaborations under discussion: T-Systems, UK start-up, BfR,EODC<br />
<br />
*Market Analysis <br />
**2 documents being prepared by FAO, several interviews conducted: <br />
***Service Delivery Model from data centre to community: https://docs.google.com/document/d/1L1VOOdulWU_J7IaVIm7dPmsstmQYSouV3DiX2gZuGQU/edit?ts=59761450 <br />
***Legal interoperability and data sharing - Concrete Use Case: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#heading=h.ddqrsgrf90g3<br />
<br><br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype. In external review.<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace. New version implementing reviewers' comment ready in the document server.<br />
* M30: D3.17 Final release of the accounting and operational tools: Internal review. External review will start by today.<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* Done: Provisioning of VOMS information through SAML/OIDC interfaces (Connectors to Ops Portal) done.<br />
** This enables the moving into production of the AppDB VMOps dashboard<br />
* In progress: Translation of VO information into VOMS proxies<br />
* In progress: Self-service web UI for managing OIDC/Oauth2 tokens<br />
** Relevant for the EGI FedCloud<br />
* In progress: Ops Portal and ARGO integration<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
Giuseppe, Peter and Alessandro will manage the activity during my holidays.<br />
* In progress: Service order management tool. Main features are available, minor issues to be fixed. Currently in testing.<br />
** Marketplace Integration with RT<br />
** Workflow to automate AoDS service order management<br />
** Integration with CheckIn service to record users in the vo.access.egi.eu VO<br />
* In progress: Dashboard in PrestaShop customised according EGI needs<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud Accounting<br />
** Cloud schema v0.4 rollout finalised.<br />
** Long running VM support is under testing: Some corner cases that are being tracked down. Upgrade to the HW is needed to move the features in production.<br />
* Storage accounting<br />
** 26 RPs have sent storage accounting records within the last two months.<br />
** 20 RPs validated, 3 in progress, 3 are OK but don’t have Alice usage<br />
** New service type added to GOCDB (‘eu.egi.storage.accounting’).<br />
** A few final tweaks and then planning to put into production Aug/Sept.<br />
* Accounting Portal - New release to be deployed by this week.<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Discipline account report<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops portal:<br />
** VAPOR 2.3 released. Release note: operations-portal.egi.eu/vapor_dev/releases?name=VAPOR+2.3<br />
** Ops portal 4.2 in preparation:<br />
*** integration of complementary metrics for the VO : information about accounting data and AppDB changes<br />
*** improvements on the Vo ID Card<br />
*** Integration of EGI Checkin<br />
*** Use of the new ARGO messaging system<br />
* GOCDB - ongoing tasks that will be completed by end of August:<br />
** Defining allowed methods for write API extension (on the wiki)<br />
** Write API extension for services and service endpoints.<br />
** working on data freshness check<br />
** Move to new STFC infrastructure required for IPv6 support.<br />
** GUI improvements (as defined in https://rt.egi.eu/rt/Ticket/Display.html?id=11546 & https://rt.egi.eu/rt/Ticket/Display.html?id=11217) <br />
** Bug fixes of issues in GitHub issues list: https://github.com/GOCDB/gocdb/issues<br />
* Monitoring and messagging:<br />
** many activities in progress. See https://indico.egi.eu/indico/event/3388/contribution/4/material/slides/0.pdf for details<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) Final checks, almost ready for submission<br />
* D4.10 Final CANFAR integration release (PM29) Under review (Peter and Andre Schaaff)<br />
* M4.3 Open Data Platform in the Production (PM30) Under lightweight review (Peter and Tiziana)<br />
=== Task JRA2.1 Federated Open Data ===<br />
* New bugs found in latest Onedata version, next planned date for upgrade of EGI DataHub is the end of the week<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* ENES EGI/EUDAT work now being followed by regular monthly calls. They are testing with B2STAGE/B2SAFE hosted at STFC<br />
* d4science have asked for an increase in EGI resources. Current usage is unclear due to possible problems in the accounting.<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* IISAS working with APEL team in testing GPGPU changes to accounting. If everything goes to plan, the production upgrade with this functionality will be in August<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* OMB Discussion: EGI needs to foster the sharing of experiences between NGIs who are providing SaaS and other managed services<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation of OMB<br />
* Analysis of the survey run among operations centres<br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Site Security Challenge currently ongoing (10 sites involved)<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96355EGI-Engage:AMB-2017-08-012017-08-01T07:54:00Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu) <br />
**Ongoing content writing; chasing of allocated actions on specific individuals: [https://docs.google.com/document/d/1dOg4p3fQDc3QzR8tczCPMU2nEy6BuZp9OWdCCOQNDHs/edit# D2.13 Google Doc] <br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu) <br />
**Content maturing; chasing individuals for content: [https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit D2.14 Google Doc]<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br><br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
*Strategy <br />
**EGI Strategy Update 2017 <br />
***Editorial Board Set <br />
***First meeting held 20 July; 4 scheduled for August: https://indico.egi.eu/indico/category/208/<br />
<br />
*IMS Updates <br />
**Management Review held 27 July: https://confluence.egi.eu/display/IMS/2017-07-27+Management+review <br />
**New internal training and certification discussed for conducting Audits: https://confluence.egi.eu/display/IMS/Auditor+Certification <br />
**Numerous usage of the IMS too many to list<br />
<br />
*FitSM <br />
**SURFsara In-House Training <br />
***Service offer accepted for a total of 6 courses (4 FND + 2 ADV) <br />
***Scheduled over Aug and Sept <br />
**OSG (US) discussions for providing FitSM support ongoing (New) <br />
**EXIN call on 27 July presenting FitSM (large certification and accreditation provider, potential to replace the void left by TUV SUD) + internal FitSM WG dicussions<br />
<br />
*Pay-for-Use <br />
**Contributions to be provided within D2.13, D2.14 and D3.16 <br />
**Additional providers under discussion thanks to NextGEOSS (clarity that P4U includes the possibility of charging for only human effort)<br />
<br />
*Collaborations <br />
**GEANT: Meeting held 31 July<br />
<br><br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
*SME Engagement <br />
**Main activity is to collect contributions to D2.14 <br />
**Ongoing collaborations under discussion: T-Systems, UK start-up, BfR,EODC<br />
<br />
*Market Analysis <br />
**2 documents being prepared by FAO, several interviews conducted: <br />
***Service Delivery Model from data centre to community: https://docs.google.com/document/d/1L1VOOdulWU_J7IaVIm7dPmsstmQYSouV3DiX2gZuGQU/edit?ts=59761450 <br />
***Legal interoperability and data sharing - Concrete Use Case: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#heading=h.ddqrsgrf90g3<br />
<br><br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype. In external review.<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace. New version implementing reviewers' comment ready in the document server.<br />
* M30: D3.17 Final release of the accounting and operational tools: Internal review. External review will start by today.<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* Done: Provisioning of VOMS information through SAML/OIDC interfaces (Connectors to Ops Portal) done.<br />
** This enables the moving into production of the AppDB VMOps dashboard<br />
* In progress: Translation of VO information into VOMS proxies<br />
* In progress: Self-service web UI for managing OIDC/Oauth2 tokens<br />
** Relevant for the EGI FedCloud<br />
* In progress: Ops Portal and ARGO integration<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
Giuseppe, Peter and Alessandro will manage the activity during my holidays.<br />
* In progress: Service order management tool. Main features are available, minor issues to be fixed. Currently in testing.<br />
** Marketplace Integration with RT<br />
** Workflow to automate AoDS service order management<br />
** Integration with CheckIn service to record users in the vo.access.egi.eu VO<br />
* In progress: Dashboard in PrestaShop customised according EGI needs<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud Accounting<br />
** Cloud schema v0.4 rollout finalised.<br />
** Long running VM support is under testing: Some corner cases that are being tracked down. Upgrade to the HW is needed to move the features in production.<br />
* Storage accounting<br />
** 26 RPs have sent storage accounting records within the last two months.<br />
** 20 RPs validated, 3 in progress, 3 are OK but don’t have Alice usage<br />
** New service type added to GOCDB (‘eu.egi.storage.accounting’).<br />
** A few final tweaks and then planning to put into production Aug/Sept.<br />
* Accounting Portal - New release to be deployed by this week.<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Discipline account report<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops portal:<br />
** VAPOR 2.3 released. Release note: operations-portal.egi.eu/vapor_dev/releases?name=VAPOR+2.3<br />
** Ops portal 4.2 in preparation:<br />
*** integration of complementary metrics for the VO : information about accounting data and AppDB changes<br />
*** improvements on the Vo ID Card<br />
*** Integration of EGI Checkin<br />
*** Use of the new ARGO messaging system<br />
* GOCDB - ongoing tasks that will be completed by end of August:<br />
** Defining allowed methods for write API extension (on the wiki)<br />
** Write API extension for services and service endpoints.<br />
** working on data freshness check<br />
** Move to new STFC infrastructure required for IPv6 support.<br />
** GUI improvements (as defined in https://rt.egi.eu/rt/Ticket/Display.html?id=11546 & https://rt.egi.eu/rt/Ticket/Display.html?id=11217) <br />
** Bug fixes of issues in GitHub issues list: https://github.com/GOCDB/gocdb/issues<br />
* Monitoring and messagging:<br />
** many activities in progress. See https://indico.egi.eu/indico/event/3388/contribution/4/material/slides/0.pdf for details<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) Final checks, almost ready for submission<br />
* D4.10 Final CANFAR integration release (PM29) Under review (Peter and Andre Schaaff)<br />
* M4.3 Open Data Platform in the Production (PM30) Under lightweight review (Peter and Tiziana)<br />
=== Task JRA2.1 Federated Open Data ===<br />
* New bugs found in latest Onedata version, next planned date for upgrade of EGI DataHub is the end of the week<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* ENES EGI/EUDAT work now being followed by regular monthly calls. They are testing with B2STAGE/B2SAFE hosted at STFC<br />
* d4science have asked for an increase in EGI resources. Current usage is unclear due to possible problems in the accounting.<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* IISAS working with APEL team in testing GPGPU changes to accounting. If everything goes to plan, the production upgrade with this functionality will be in August<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* OMB Discussion: EGI needs to foster the sharing of experiences between NGIs who are providing SaaS and other managed services<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation ofOMB <br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Site Security Challenge currently ongoing (10 sites involved)<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96354EGI-Engage:AMB-2017-08-012017-08-01T07:52:19Z<p>Psolagna: /* Task SA1.2 Development of Security Operations */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu) <br />
**Ongoing content writing; chasing of allocated actions on specific individuals: [https://docs.google.com/document/d/1dOg4p3fQDc3QzR8tczCPMU2nEy6BuZp9OWdCCOQNDHs/edit# D2.13 Google Doc] <br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu) <br />
**Content maturing; chasing individuals for content: [https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit D2.14 Google Doc]<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br><br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
*Strategy <br />
**EGI Strategy Update 2017 <br />
***Editorial Board Set <br />
***First meeting held 20 July; 4 scheduled for August: https://indico.egi.eu/indico/category/208/<br />
<br />
*IMS Updates <br />
**Management Review held 27 July: https://confluence.egi.eu/display/IMS/2017-07-27+Management+review <br />
**New internal training and certification discussed for conducting Audits: https://confluence.egi.eu/display/IMS/Auditor+Certification <br />
**Numerous usage of the IMS too many to list<br />
<br />
*FitSM <br />
**SURFsara In-House Training <br />
***Service offer accepted for a total of 6 courses (4 FND + 2 ADV) <br />
***Scheduled over Aug and Sept <br />
**OSG (US) discussions for providing FitSM support ongoing (New) <br />
**EXIN call on 27 July presenting FitSM (large certification and accreditation provider, potential to replace the void left by TUV SUD) + internal FitSM WG dicussions<br />
<br />
*Pay-for-Use <br />
**Contributions to be provided within D2.13, D2.14 and D3.16 <br />
**Additional providers under discussion thanks to NextGEOSS (clarity that P4U includes the possibility of charging for only human effort)<br />
<br />
*Collaborations <br />
**GEANT: Meeting held 31 July<br />
<br><br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
*SME Engagement <br />
**Main activity is to collect contributions to D2.14 <br />
**Ongoing collaborations under discussion: T-Systems, UK start-up, BfR,EODC<br />
<br />
*Market Analysis <br />
**2 documents being prepared by FAO, several interviews conducted: <br />
***Service Delivery Model from data centre to community: https://docs.google.com/document/d/1L1VOOdulWU_J7IaVIm7dPmsstmQYSouV3DiX2gZuGQU/edit?ts=59761450 <br />
***Legal interoperability and data sharing - Concrete Use Case: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#heading=h.ddqrsgrf90g3<br />
<br><br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype. In external review.<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace. New version implementing reviewers' comment ready in the document server.<br />
* M30: D3.17 Final release of the accounting and operational tools: Internal review. External review will start by today.<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* Done: Provisioning of VOMS information through SAML/OIDC interfaces (Connectors to Ops Portal) done.<br />
** This enables the moving into production of the AppDB VMOps dashboard<br />
* In progress: Translation of VO information into VOMS proxies<br />
* In progress: Self-service web UI for managing OIDC/Oauth2 tokens<br />
** Relevant for the EGI FedCloud<br />
* In progress: Ops Portal and ARGO integration<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
Giuseppe, Peter and Alessandro will manage the activity during my holidays.<br />
* In progress: Service order management tool. Main features are available, minor issues to be fixed. Currently in testing.<br />
** Marketplace Integration with RT<br />
** Workflow to automate AoDS service order management<br />
** Integration with CheckIn service to record users in the vo.access.egi.eu VO<br />
* In progress: Dashboard in PrestaShop customised according EGI needs<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud Accounting<br />
** Cloud schema v0.4 rollout finalised.<br />
** Long running VM support is under testing: Some corner cases that are being tracked down. Upgrade to the HW is needed to move the features in production.<br />
* Storage accounting<br />
** 26 RPs have sent storage accounting records within the last two months.<br />
** 20 RPs validated, 3 in progress, 3 are OK but don’t have Alice usage<br />
** New service type added to GOCDB (‘eu.egi.storage.accounting’).<br />
** A few final tweaks and then planning to put into production Aug/Sept.<br />
* Accounting Portal - New release to be deployed by this week.<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Discipline account report<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops portal:<br />
** VAPOR 2.3 released. Release note: operations-portal.egi.eu/vapor_dev/releases?name=VAPOR+2.3<br />
** Ops portal 4.2 in preparation:<br />
*** integration of complementary metrics for the VO : information about accounting data and AppDB changes<br />
*** improvements on the Vo ID Card<br />
*** Integration of EGI Checkin<br />
*** Use of the new ARGO messaging system<br />
* GOCDB - ongoing tasks that will be completed by end of August:<br />
** Defining allowed methods for write API extension (on the wiki)<br />
** Write API extension for services and service endpoints.<br />
** working on data freshness check<br />
** Move to new STFC infrastructure required for IPv6 support.<br />
** GUI improvements (as defined in https://rt.egi.eu/rt/Ticket/Display.html?id=11546 & https://rt.egi.eu/rt/Ticket/Display.html?id=11217) <br />
** Bug fixes of issues in GitHub issues list: https://github.com/GOCDB/gocdb/issues<br />
* Monitoring and messagging:<br />
** many activities in progress. See https://indico.egi.eu/indico/event/3388/contribution/4/material/slides/0.pdf for details<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) Final checks, almost ready for submission<br />
* D4.10 Final CANFAR integration release (PM29) Under review (Peter and Andre Schaaff)<br />
* M4.3 Open Data Platform in the Production (PM30) Under lightweight review (Peter and Tiziana)<br />
=== Task JRA2.1 Federated Open Data ===<br />
* New bugs found in latest Onedata version, next planned date for upgrade of EGI DataHub is the end of the week<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* ENES EGI/EUDAT work now being followed by regular monthly calls. They are testing with B2STAGE/B2SAFE hosted at STFC<br />
* d4science have asked for an increase in EGI resources. Current usage is unclear due to possible problems in the accounting.<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* IISAS working with APEL team in testing GPGPU changes to accounting. If everything goes to plan, the production upgrade with this functionality will be in August<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation ofOMB <br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Site Security Challenge currently ongoing (10 sites involved)<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96320EGI-Engage:AMB-2017-08-012017-07-31T12:43:00Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
<br />
=== Task JRA1.3 Accounting ===<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* Chaired and agenda preparation ofOMB <br />
* FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-08-01&diff=96319EGI-Engage:AMB-2017-08-012017-07-31T12:42:28Z<p>Psolagna: /* WP5 (SA1) (Peter Solagna) */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
<br />
=== Task JRA1.3 Accounting ===<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* EGI Core Services reports<br />
* SLA report: mobrain<br />
* site-bdii probes failing on some cloud sites: investigations<br />
* VO decommissioned: vo.londongrid.ac.uk <br />
* VAPOR 2.3 release<br />
* WOrk on the delverable 5.4<br />
* participation to OMB and FedCloud meetings<br />
* problem in the GGUS tickets response time computation, solved<br />
* started the recertification process of MK-04-FINKICLOUD<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:Dissemination&diff=96301EGI-Engage:Dissemination2017-07-28T08:01:00Z<p>Psolagna: /* Past */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
The '''dissemination activities''' of EGI-Engage will be tracked in this page using the following table. <br />
<br />
The table will cover all dissemination activities (e.g. training events, blog posts, articles, presentations) undertaken by the tasks/work packages. <br />
<br />
''[[EGI-Engage:Dissemination#Instructions|Instructions to fill the table]]'' <br />
<br />
<br> <br />
<br />
= Past =<br />
<br />
{| class="wikitable sortable" width="100%" border="1" cellspacing="1" cellpadding="1" align="center"<br />
|-<br />
! scope="col" | <br>Related project output<br><br> <br />
! scope="col" | Type of activities <br />
! scope="col" | Task # <br />
! scope="col" | Author (First initial. Surname)<br />
! scope="col" | Title <br />
! scope="col" | Date (year.month.day)<br />
! scope="col" | Place / Outlet /<br> Name of event <br />
! scope="col" | Type of audience <br />
! scope="col" | Size of audience <br />
! scope="col" | Countries <br />
! scope="col" | Link<br />
|-<br />
| [https://docs.google.com/spreadsheets/d/1Tmb5a5GJOB1i_IzUpuMj3xg0loSqTLZ_iUnxBLESA0w/edit#gid=0 '' Project output list ''] <br />
| '' Article? Presentation? etc ''<br />
| '' Task where the activity took place (not of the project output) '' <br />
| '' e.g. S. Coelho ''<br />
| '' of the article, the presentation, etc'' <br />
| '' 1975.06.23 '' <br />
| '' where was the event? where was the article published, etc '' <br />
| '' RIs? LToS? EGI Community? '' <br />
| <br />
| <br />
| <br />
|-<br />
| Collaboration agreements with commercial-oriented organisations <br />
| Webinar<br />
| NA2.3.1<br />
| S. Holsinger <br />
| EGI Cloud for SMEs in CAE – OpenFOAM demo <br />
| 2016.10.20 <br />
| Remote <br />
| SMEs <br />
| 25 <br />
| Europe-wide <br />
| https://indico.egi.eu/indico/event/3131/<br />
|-<br />
| Training course and online guide about the Federated Cloud (API, CMD line, GUI)<br />
| Presentation<br />
| <br />
| Y. Chen<br />
| Supporting Open Science with the EGI Federated Cloud, Experiences, success stories, lessons learnt<br />
| 2017.03.10<br />
| Taipei, China<br />
| ISGC 2017<br />
| 100<br />
| Worldwide<br />
| http://indico4.twgrid.org/indico/event/2/session/33/contribution/129<br />
|-<br />
| <br />
| Lecture<br />
| <br />
| T. Athanassiadou<br />
| EGI toward the European Open Science Cloud<br />
| 2017.05.19 <br />
| Amsterdam, The Netherlands<br />
| Scientific Community <br />
| XX<br />
| Europe-wide <br />
| https://drive.google.com/drive/u/1/folders/0B5iVqDrv0uvbMDFFZDFTV1R4OWM<br />
|-<br />
| <br />
| Workshop<br />
| <br />
| G. Sipos<br />
| EGI services<br />
| 2017.05.22 <br />
| Budapest, Hungary <br />
| Scientific Community <br />
| 53 <br />
| Europe-wide <br />
| http://mso4sc.elmerex.hu/?page_id=894 https://documents.egi.eu/document/3119<br />
|-<br />
| Support materials for NGI SME engagement <br />
| Webinar<br />
| NA2.3.1<br />
| S. Holsinger <br />
| How to Engage SMEs for NGIs <br />
| 2017.05.31 <br />
| Remote <br />
| NGIs <br />
| 15 <br />
| Europe-wide <br />
| https://indico.egi.eu/indico/event/3373/<br />
|-<br />
| EGI Applications on Demand service<br />
| Webinar<br />
| SA1.3 <br />
| G. Sipos<br />
| The Applications on Demand (AoD) service <br />
| 2017.06.13 <br />
| Remote <br />
| NGIs, RIs, LToS <br />
| 15 <br />
| Europe-wide <br />
| https://indico.egi.eu/indico/event/3378/<br />
|-<br />
| EGI Applications on Demand service<br />
| Presentation<br />
| SA1.3 <br />
| G. La Rocca <br />
| EGI Applications on Demand (AoD) service - Catering for the computational needs of the long tail of science <br />
| 2017.06.19-21 <br />
| Poznan, Poland <br />
| Science Gateways community <br />
| 30<br />
| Worldwide <br />
| http://iwsg2017.psnc.pl/ https://documents.egi.eu/public/ShowDocument?docid=3132<br />
|-<br />
| EGI CheckIn and AAI services<br />
| Presentation<br />
| JRA1.1 <br />
| P. Solagna <br />
| The EGI CheckIn service<br />
| 2017.02.20<br />
| Vienna, Austria <br />
| Research Infrastructure, Research communities. AAI experts. <br />
| 50<br />
| Worldwide <br />
| https://indico.cern.ch/event/605369/<br />
|-<br />
|}<br />
<br />
= Archive =<br />
<br />
This table is 'harvested' periodically. The archive is available as a [https://docs.google.com/spreadsheets/d/1ns8KtAwYDWvdM70HYpFEVmahuYREeWvjco29r9GBdaE/edit#gid=1684550276 google speadsheet] -> please do not edit this spreadsheet, add your events to this page<br />
<br />
Catalogue of project results: [http://go.egi.eu/egi-engage-results]. <br />
<br />
<br><br />
<br />
= Instructions =<br />
<br />
*'''Related project output''' - Describe which EGI-Engage project output will be disseminated through this action (see [http://go.egi.eu/egi-engage-results catalogue of project results]) <br />
*'''Task # '''- task number <br />
*'''Author''' - lead author <br />
**Please specify if the author is affiliated with an NGI, or a CC, or if the author is a Champion <br />
*'''Type of activities:''' <br />
**''Scientific Publications'', e.g.: papers published in journals, abstracts [This is not the place to report publications published by scientists using services resources provided by EGI or the project] <br />
**''EGI Publications'' <br />
**''News'', ''Case study'' and ''Newsletter'', articles published in EGI's communication channels <br />
**''Presentations'', e.g., talks given at external meetings <br />
**''Workshops / Tutorials'', events organised and/or ran by the WP/task <br />
**''Articles'', articles written by the WP/task member for external newsletters, news feeds, etc. <br />
**''Videos &amp; media'', media produced by, or with the participation of, the WP/task members <br />
**''Interviews'', given by the WP/task members <br />
**''Other'', please specify <br />
*'''Title''' - of the article, presentation, workshop, etc. <br />
*'''Date''' - of the article, presentation, workshop, etc. (format YYYY.MM.DD) <br />
*'''Place / Outlet / Name of event''' <br />
**For publications, articles, etc.: please state the name of the outlet (i.e. the journal, newsletter, newsfeed, video channel) <br />
**For presentations, posters, etc.: please state the event where they took place <br />
**For training events, conferences, events: please state the city/country where they were held <br />
*'''Type of audience:''' choose from - Existing User Communities, Resource Providers, NGIs/EIROs, Scientific Community at large (prospective users), Competence Centers, Long Tail of Research, SMEs and Industry, Civil Society, Policy Makers, Funding Agencies, Engage partners, Media, Other (please specify) <br />
**Feel free to use combinations of the above (e.g. NGIs/EIROs and Existing User Communities) <br />
**If something is of interest to every audience within EGI (NGIs + EIROs, user communities, technical providers, project partners), please use ''EGI Community'' <br />
*'''Size of audience''' <br />
**For publications, articles, etc.: please state the readership of the outlet/ how many people receive the newsletter? <br />
**For presentations, events, etc.: please state how many people attended the event, where at the talk. <br />
**For online items: please write ''online'' (because the range of the audience is theoretically infinite) <br />
*'''Countries addressed:''' choose from: Worldwide, Europe-wide, country (specify) <br />
*'''Link:''' <br />
**Url to the event page, or to a PDF, or a presentation. <br />
**Please type the link between straight brackets and <nowiki>[http://www.egi.eu]</nowiki> will appear as [http://www.egi.eu]<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=How_To_Join_As_A_Resource_Provider&diff=96110How To Join As A Resource Provider2017-07-18T10:23:40Z<p>Psolagna: /* General requirements */</p>
<hr />
<div>= Overview =<br />
<br />
As of June 2017, the European Grid Infrastructure (EGI) connects more than X resource centres to X users across Europe and beyond. EGI is always looking to expand the number of providers and invites unaffiliated resource centres to join in.<br />
If you are the representative of a resource centre or a cluster interested in joining the infrastructure, we invite you to go through the following steps:<br />
<br />
*CASE 1: your country is already part of EGI<br />
**Please contact the resource provider in your country and they will assist you in the process (see the general requirements at the bottom of the page).<br />
<br />
*CASE 2: your country is not on the list of EGI resource providers https://www.egi.eu/federation/data-centres/<br />
**If you are a representative from a resource centre / site / cluster, being part of EGI is still possible. Please send an e-mail to the EGI.eu Operations team (operations AT egi.eu) which can help you to become part of the infrastructure, and will assist you through the different steps, from resource centre registration to certification (see the requirements at the bottom of the page)<br />
**If you are a representative from a National Grid Initiative or other Resource Infrastructure Provider, please send an e-mail to the EGI.eu Operations team (operations AT egi.eu) which will assist you during the integration process. Please note that new resource infrastructure providers must first be accredited by the EGI Council. To do so non-European resource infrastructure providers can start a formal collaboration with EGI.eu through a Memorandum of Understanding.<br />
<br />
Either your country is already part of EGI or not, the integration process is described step by step in the [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification procedure]: the registration makes the EGI infrastructure aware of the new resources you offer, while the certification takes care of validating the registration itself and testing the services work correctly. In the context of the registration, you will become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure.<br />
<br />
= General requirements =<br />
<br />
* agreements and policies<br />
For being part of the EGI infrastructure, a resource centre will have to comply with a series of operational and security requirements by signing an [https://documents.egi.eu/public/ShowDocument?docid=31 Operational Level Agreement] (OLA), a document that defines the minimum set of operational services and the respective quality parameters that a Resource Centre is required to provide in EGI, and accepting the [https://documents.egi.eu/document/86 Grid Security Policy], the [https://documents.egi.eu/document/75 Grid Resource Centre Operations Policy], the [https://documents.egi.eu/document/76 Resource Centre Registration Security Policy] and in general all the [https://wiki.egi.eu/wiki/SPG:Documents EGI security policies].<br />
* support the X509 certificates and/or federated AAI<br />
The resource centres belonging to the EGI infrastructure have to properly configure the provided services with the EGI AAI: this means that the IGTF trust anchors CAs distribution to enable the X509 authentication have to be updated in a timely manner. Usually a new CAs release is available every month.<br />
EGI is also implementing user authentication through the CheckIn AAI platform. CheckIn is able to provide authentication information in SAML and OIDC, as an alternative to X.509.<br />
* monitoring and accounting<br />
The services provided by a resource centre have to run interfaces that allow their monitoring, in order to constantly check their functioning and periodically produce reports on the quality of service offered; at the same time the measurement of resources usage have to be allowed, through the properly tools provided by EGI.<br />
* daily operations<br />
All the EGI middleware campaigns aim at implementing service provisioning best practices and common requirments. Mitigate security vulnerabilities and update unsupported operating systems and softwares are part of the activities of a resource centre: EGI and the Operations Centres coordinate these activities in order to have them implemented in a timely manner.<br />
<br />
= Questions and answers =<br />
<br />
== '''Do I lose control on who can access my resources if I join the EGI infrastructure?''' ==<br />
'''No'''<br />
<br />
EGI uses the concept of Virtual Organisation (VO) to group users. The resource provider has complete control on the VOs accessing to the resources and on the quotas or restrictions to assign to each VO. Although not recommended, you can even restrict the automatic access of users within a VO and manually enable individual members.<br />
<br />
== '''How many components do I have to install?''' ==<br />
<br />
The minimum required set of functional capabilities to provide is described in the RC OLA.<br />
<br />
In general, there are components for:<br />
*Cloud Computing<br />
*File Transfer<br />
*Storage Management<br />
*Data Access<br />
*Metadata Catalogue<br />
*HTC Compute<br />
*additional Information Discovery capability<br />
<br />
A typical resource centre comprises components for HTC Compute, Storage Management, and Information discovery capabilities; but depending on the needs of the user communities that are mainly using your resources, the type of services exposed may vary.<br />
<br />
== '''How my daily operational activities will change?''' ==<br />
For the most part daily operations will not change.<br />
<br />
An administrator of a resource centre part of the EGI infrastructure, hence supporting international communities, has to act proactively for maintaining its services working and up-to-dated, and for providing support through the EGI official channels. This means following up GGUS tickets submitted through helpdesk.egi.eu, including either requests from user communities or tickets triggered by failures detected by the monitoring infrastructure: a team of operators checks daily the monitoring system, promptly notifying the resource centres about the occurrence of failures and providing at the same time help for solving the problems. As previously written, other requests can regard the upgrade or decommission of unsupported software, and the fixing of security vulnerabilities when discovered.<br />
<br />
In conclusion, most of the site activities that are coordinated by EGI and the NGIs are already part of the work plan of a well-maintained resource centre: the additional task for a site manager is to acknowledge to EGI that the requested action has been performed.</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=How_To_Join_As_A_Resource_Provider&diff=96109How To Join As A Resource Provider2017-07-18T10:15:05Z<p>Psolagna: /* Overview */</p>
<hr />
<div>= Overview =<br />
<br />
As of June 2017, the European Grid Infrastructure (EGI) connects more than X resource centres to X users across Europe and beyond. EGI is always looking to expand the number of providers and invites unaffiliated resource centres to join in.<br />
If you are the representative of a resource centre or a cluster interested in joining the infrastructure, we invite you to go through the following steps:<br />
<br />
*CASE 1: your country is already part of EGI<br />
**Please contact the resource provider in your country and they will assist you in the process (see the general requirements at the bottom of the page).<br />
<br />
*CASE 2: your country is not on the list of EGI resource providers https://www.egi.eu/federation/data-centres/<br />
**If you are a representative from a resource centre / site / cluster, being part of EGI is still possible. Please send an e-mail to the EGI.eu Operations team (operations AT egi.eu) which can help you to become part of the infrastructure, and will assist you through the different steps, from resource centre registration to certification (see the requirements at the bottom of the page)<br />
**If you are a representative from a National Grid Initiative or other Resource Infrastructure Provider, please send an e-mail to the EGI.eu Operations team (operations AT egi.eu) which will assist you during the integration process. Please note that new resource infrastructure providers must first be accredited by the EGI Council. To do so non-European resource infrastructure providers can start a formal collaboration with EGI.eu through a Memorandum of Understanding.<br />
<br />
Either your country is already part of EGI or not, the integration process is described step by step in the [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification procedure]: the registration makes the EGI infrastructure aware of the new resources you offer, while the certification takes care of validating the registration itself and testing the services work correctly. In the context of the registration, you will become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure.<br />
<br />
= General requirements =<br />
<br />
* agreements and policies<br />
For being part of the EGI infrastructure, a resource centre will have to comply with a series of operational and security requirements by signing an [https://documents.egi.eu/public/ShowDocument?docid=31 Operational Level Agreement] (OLA), a document that defines the minimum set of operational services and the respective quality parameters that a Resource Centre is required to provide in EGI, and accepting the [https://documents.egi.eu/document/86 Grid Security Policy], the [https://documents.egi.eu/document/75 Grid Resource Centre Operations Policy], the [https://documents.egi.eu/document/76 Resource Centre Registration Security Policy] and in general all the [https://wiki.egi.eu/wiki/SPG:Documents EGI security policies].<br />
* support the X509 certificates<br />
The resource centres belonging to the EGI infrastructure have to properly configure the provided services with the EGI AAI: this means that the IGTF trust anchors CAs distribution to enable the X509 authentication have to be updated in a timely manner. Usually a new CAs release is available every month.<br />
* monitoring and accounting<br />
The services provided by a resource centre have to run interfaces that allow their monitoring, in order to constantly check their functioning and periodically produce reports on the quality of service offered; at the same time the measurement of resources usage have to be allowed, through the properly tools provided by EGI.<br />
* daily operations<br />
All the EGI middleware campaigns aim at implementing service provisioning best practices and common requirments. Mitigate security vulnerabilities and update unsupported operating systems and softwares are part of the activities of a resource centre: EGI and the Operations Centres coordinate these activities in order to have them implemented in a timely manner.<br />
<br />
= Questions and answers =<br />
<br />
== '''Do I lose control on who can access my resources if I join the EGI infrastructure?''' ==<br />
'''No'''<br />
<br />
EGI uses the concept of Virtual Organisation (VO) to group users. The resource provider has complete control on the VOs accessing to the resources and on the quotas or restrictions to assign to each VO. Although not recommended, you can even restrict the automatic access of users within a VO and manually enable individual members.<br />
<br />
== '''How many components do I have to install?''' ==<br />
<br />
The minimum required set of functional capabilities to provide is described in the RC OLA.<br />
<br />
In general, there are components for:<br />
*Cloud Computing<br />
*File Transfer<br />
*Storage Management<br />
*Data Access<br />
*Metadata Catalogue<br />
*HTC Compute<br />
*additional Information Discovery capability<br />
<br />
A typical resource centre comprises components for HTC Compute, Storage Management, and Information discovery capabilities; but depending on the needs of the user communities that are mainly using your resources, the type of services exposed may vary.<br />
<br />
== '''How my daily operational activities will change?''' ==<br />
For the most part daily operations will not change.<br />
<br />
An administrator of a resource centre part of the EGI infrastructure, hence supporting international communities, has to act proactively for maintaining its services working and up-to-dated, and for providing support through the EGI official channels. This means following up GGUS tickets submitted through helpdesk.egi.eu, including either requests from user communities or tickets triggered by failures detected by the monitoring infrastructure: a team of operators checks daily the monitoring system, promptly notifying the resource centres about the occurrence of failures and providing at the same time help for solving the problems. As previously written, other requests can regard the upgrade or decommission of unsupported software, and the fixing of security vulnerabilities when discovered.<br />
<br />
In conclusion, most of the site activities that are coordinated by EGI and the NGIs are already part of the work plan of a well-maintained resource centre: the additional task for a site manager is to acknowledge to EGI that the requested action has been performed.</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=AAI_FAQ&diff=96080AAI FAQ2017-07-17T09:20:09Z<p>Psolagna: /* Connect to CheckIn an IdP federated in an hub and spoke federations */</p>
<hr />
<div>{{TOC_right}} <br />
<br />
= AAI and CheckIn FAQ =<br />
<br />
== IdP and user questions ==<br />
=== Connect to CheckIn an IdP federated in an hub and spoke federations ===<br />
'''Question: I get an error similar to: "Error - No connection between institution and service" (SURFconext example)'''<br />
<br />
Answer:<br />
<br />
In case of a "hub and spoke" federation the federation coordinator may require that the IdP administrators explicitly request to connect to a SP and let their users to authenticate on these SP.<br />
<br />
In most of the cases this is not a configuration problem neither for the CheckIn service nor for the Identity provider. The connection needs to be implemented in the hub and spoke IdP Proxy. <br />
<br />
One example of such federation is SURFconext, the national IdP federation for research and education in the Netherlands operated by SURFnet. If you are using credentials from a Dutch IdP in eduGAIN, you or your IdP administrators need to request the connection. The following steps will lead you to perform the connection:<br />
* Connect to [https://dashboard.surfconext.nl/apps SURFconext dashboard]<br />
* Search for "EGI AAI Service provider proxy"<br />
** If the service does not show in the search, you need to ask SURFnet to add it in the dashboard, please write to support at surfconext dot nl<br />
* In the dashboard, near the "EGI AAI Service provider proxy" there should be a "Connect" button, this will create a service ticket and the SURFconext team will make the connection active.<br />
* After you received confirmation that the "EGI AAI Service provider proxy" is accessible, you will be able to login in CheckIn</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=AAI_FAQ&diff=96079AAI FAQ2017-07-17T09:19:51Z<p>Psolagna: Created page with "{{TOC_right}} = AAI and CheckIn FAQ = == IdP and user questions == == Connect to CheckIn an IdP federated in an hub and spoke federations == '''Question: I get an error simila..."</p>
<hr />
<div>{{TOC_right}} <br />
<br />
= AAI and CheckIn FAQ =<br />
<br />
== IdP and user questions ==<br />
== Connect to CheckIn an IdP federated in an hub and spoke federations ==<br />
'''Question: I get an error similar to: "Error - No connection between institution and service" (SURFconext example)'''<br />
<br />
Answer:<br />
<br />
In case of a "hub and spoke" federation the federation coordinator may require that the IdP administrators explicitly request to connect to a SP and let their users to authenticate on these SP.<br />
<br />
In most of the cases this is not a configuration problem neither for the CheckIn service nor for the Identity provider. The connection needs to be implemented in the hub and spoke IdP Proxy. <br />
<br />
One example of such federation is SURFconext, the national IdP federation for research and education in the Netherlands operated by SURFnet. If you are using credentials from a Dutch IdP in eduGAIN, you or your IdP administrators need to request the connection. The following steps will lead you to perform the connection:<br />
* Connect to [https://dashboard.surfconext.nl/apps SURFconext dashboard]<br />
* Search for "EGI AAI Service provider proxy"<br />
** If the service does not show in the search, you need to ask SURFnet to add it in the dashboard, please write to support at surfconext dot nl<br />
* In the dashboard, near the "EGI AAI Service provider proxy" there should be a "Connect" button, this will create a service ticket and the SURFconext team will make the connection active.<br />
* After you received confirmation that the "EGI AAI Service provider proxy" is accessible, you will be able to login in CheckIn</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=AAI&diff=96078AAI2017-07-17T08:42:41Z<p>Psolagna: /* Documentation */</p>
<hr />
<div><!--{{Template:Op menubar}} --> {{Template:Tools menubar}} {{TOC_right}} <br />
<br />
The EGI CheckIn service (also called EGI AAI proxy) enables access to EGI services and resources using federated authentication mechanisms. Specifically, the proxy service is operated as a central hub between federated Identity Providers (IdPs) residing ‘outside’ of the EGI ecosystem, and Service Providers (SPs) that are part of EGI. The main advantage of this design principle is that all entities need to establish and maintain technical and trust relation only to a single entity, the EGI AAI proxy, instead of managing many-to-many relationships. In this context, the proxy acts as a Service Provider towards the Identity Providers and as an Identity Provider towards the Service Providers. <br />
<br />
Through the EGI AAI proxy, users are able to authenticate with the credentials provided by the IdP of their Home Organisation (e.g. via eduGAIN), as well as using social identity providers, or other selected external identity providers (support for eGOV IDs is also foreseen). To achieve this, the EGI AAI has built-in support for SAML, OpenID Connect and OAuth2 providers and already enables user logins through Facebook, Google, LinkedIn, and ORCID. In addition to serving as an authentication proxy, the EGI AAI provides a central Discovery Service (Where Are You From – WAYF) for users to select their preferred IdP. <br />
<br />
The EGI AAI proxy is also responsible for aggregating user attributes originating from various authoritative sources (IdPs and attribute provider services) and delivering them to the connected EGI service providers in a harmonised and transparent way. Service Providers can use the received attributes for authorisation purposes, i.e. determining the resources the user has access to. <br />
<br />
{| class="wikitable"<br />
|-<br />
| '''Tool name''' <br />
| ''EGI AAI Checkin Service''<br />
|-<br />
| '''Tool Category and description''' <br />
| ''EGI Core service'' <br />
Provides Authentication and Authorisation capabilities enabling user-friendly and secure access to EGI services <br />
<br />
|-<br />
| '''Tool url''' <br />
| https://aai.egi.eu/<br><br />
|-<br />
| '''Email''' <br />
| egi-aai-checkin@lists.grnet.gr<br />
|-<br />
| '''GGUS Support unit''' <br />
| N/A<br />
|-<br />
| '''GOCDB entry''' <br />
| [https://goc.egi.eu/portal/index.php?Page_Type=Site&id=1825 GRIDOPS-CheckIn]<br />
|-<br />
| '''Requirements tracking - EGI tracker''' <br />
| N/A<br />
|-<br />
| '''Issue tracking - Developers tracker''' <br />
| N/A<br />
|-<br />
| '''Release schedule''' <br />
| https://wiki.egi.eu/wiki/EGI-Engage:TASK_JRA1.1_Authentication_and_Authorisation_Infrastructure#Development_Roadmap<br />
|-<br />
| '''Release notes''' <br />
| Ν/Α<br />
|-<br />
| '''Roadmap''' <br />
| <span style="font-size: 13.28px;">https://wiki.egi.eu/wiki/EGI-Engage:TASK_JRA1.1_Authentication_and_Authorisation_Infrastructure</span><br />
|-<br />
| '''Related OLA''' <br />
| ''N/A''<br />
|-<br />
| '''Test instance url''' <br />
| https://aai-dev.egi.eu/<br><br />
|-<br />
| '''Documentation''' <br />
| https://wiki.egi.eu/wiki/AAI#Documentation<br />
|-<br />
| '''License''' <br />
| Apache License 2.0<br />
|-<br />
| '''Provider''' <br />
| GRNET<br />
|-<br />
| '''Source code''' <br />
| https://github.com/rciam<br />
|}<br />
<br />
<br> <br />
<br />
= Change, Release and Deployment =<br />
<br />
TBD <br />
<br />
<br> <br />
<br />
= Documentation =<br />
<br />
*[[AAI usage guide|EGI AAI Usage Guide ]]<br />
*[[AAI guide for IdPs|EGI AAI Integration Guide for Identity Providers ]]<br />
*[[AAI guide for SPs|EGI AAI Integration Guide for Service Providers ]]<br />
* [[AAI FAQ]]<br />
[[Category:Tools]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-07-11&diff=95968EGI-Engage:AMB-2017-07-112017-07-11T07:47:18Z<p>Psolagna: /* WP5 (SA1) (Peter Solagna) */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* processes review <br />
* preparing Authore tool for periodic report<br />
<br />
<br> <br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
<br />
=== Task JRA1.3 Accounting ===<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D5.3 in progress, still some sections to be distributed to sub-authors<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* Working on the Fedcloud use model<br />
* Working on a security certification document for non-EGI services (but interacting with EGI)<br />
* Globus TK support: building communication channels between WLCG/OSG/EGI/...<br />
* RC and RP OLA monthly enforcing<br />
* Review of the wiki page https://wiki.egi.eu/wiki/Training_Guides<br />
* Finalising the OLA with DIRAC4EGI<br />
* New VAPOR version (2.3) testing<br />
* Preparation of OMB agenda and chairing, as well for UMD meeting<br />
* Release of Preview 1.13 and 2.13<br />
* Yearly review of the monitoring and accounting services OLA<br />
* Testing the new release of the accounting portal<br />
* SLA reports: drihm, terradue<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* SPG F2F, Community security policies updates<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* M28: D6.21 Second version of enhanced portal for EISCAT_3D (OTHER) - Some sections are still missing<br />
* M29: D6.22 Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment (DEM) - Full draft expected next week<br />
* M30: D6.16 Evaluated cloud environment and demonstrator of analysis workflow for biobank studies (DEM) - Under development<br />
* M30: D6.23 Report on evaluation of EPOS EGI pilot studies (R) - Nearly full draft<br />
* M30: D6.15 Demonstrator for ELIXIR workflows implemented in the EGI Federated cloud (DEM) - Under development<br />
* Final and periodic reports - Template is needed<br />
* D2.14 - User engagement (T6.2) - Under preparation in a google doc<br />
* CCs was requested to update/complete dissemination table in Wiki<br />
<br />
=== Task SA2.1 Training ===<br />
* EGI talk delivered at EUDAT school <br />
* Preparation ongoing to CODATA-RDA summer school (Cloud tutorial)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Writing input for D2.14<br />
* Updated/updating customers and Business Opportunities in Confluence<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
* Finalising demonstrators, reporting them in deliverable<br />
* Planning next (final?) EGI-Engage CC telco for late July<br />
<br />
=== Task SA2.4 BBMRI ===<br />
* Finalising demonstrators, reporting them in deliverable<br />
* VM was prepared for BBMRI.NL in fedcloud<br />
<br />
=== Task SA2.5 MoBrain ===<br />
No update<br />
<br />
=== Task SA2.6 DARIAH ===<br />
No update<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
No update<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* Finalising deliverable<br />
* New member of staff at CNRS for DIRAC<br />
<br />
=== Task SA2.9 EPOS ===<br />
* Finalising deliverable (full draft available)<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
* working on deliverable<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-27&diff=95755EGI-Engage:AMB-2017-06-272017-06-27T11:53:36Z<p>Psolagna: /* Task SA1.2 Development of Security Operations */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* Preparing for ITSM audit<br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu)<br />
**ToC started: https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu)<br />
**ToC planned for first week of July<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br><br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
*Strategy<br />
** Preparation doc from survey for EGI Council (29 June)<br />
** Policy brief to update the EGI Council on service portfolio changes<br />
<br />
*IMS Updates<br />
** IMS Ops Meeting (Sy, Yannick, Mal) - 27 May<br />
** Several updated through IMS by many<br />
** 1st of 3 Internal audits for EGI IMS on the 30th of June in preparation to the audit conducted by TUV in November; first will focus on the ITSM processes. All have been informed and is planned. Thomas will be in Amsterdam.<br />
<br />
*FitSM<br />
**Conducted 2 Open Registration courses<br />
***Advanced SOC (Enol and Tiziana)<br />
***Expert<br />
****6 participants (5 from EGI, 1 from CSC)<br />
**In-house discussions ongoing: EBI and SURFsara<br />
<br><br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
*FAO<br />
**Started preparing their final document: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#<br />
*UberCloud<br />
**Worked to recover the container created for the EGI/UC webinar last November to make available for the ENVRI<br />
** Refined the business model behind this offer, which includes pricing/costs<br />
** EGI would provide the CRM side with UC on the backend.<br />
*Final deliverables will be the focus of the last 2 months (see deliverable/milestone section)<br />
<br />
*BDVA<br />
**General Assembly last week and group meetings<br />
***Was the voting for the board of directors - EGI (Yannick) was voted and accepted as a member of the BoD within the “other” categories<br />
****News Item published: https://www.egi.eu/news/egi-joins-the-board-of-directors-of-the-big-data-value-association/ <br />
**iSpaces redefinition was also revised which now also includes Federations. Formal accreditation process in place. EGI who was originally rejected as federations weren’t covered, we are now able to “reapply” in the context of “Federation”. The process will be straightforward. A ceremony for iSpace labels within the Big Data Forum [roberta to add where and when]. This is important as there are dedicated funding streams for iSpaces<br />
White paper on EO big data generation (currently writing)<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
<br />
=== Task JRA1.3 Accounting ===<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) ToC agreed, now working on content. Ready for internal review: 7 July<br />
* D4.10 Final CANFAR integration release (PM29) ToC agreed, now working on content. Ready for internal review: 7 July<br />
* M4.3 Open Data Platform in the Production (PM30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
Latest developments:<br />
* Handling multiple small files<br />
* Import of existing data<br />
* Added extended attributes support<br />
* Added administrator manual<br />
=== Task JRA2.2 Federated Cloud ===<br />
* OOI: bugfixes for networking with Neutron, merged this week, to be released this week<br />
* cloud-info-provider: work ongoing with Baptiste on adding V3 auth to Keystone<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* D4Science now confirmed to be running in production in Fedcloud<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Modification done with cASO to send GPGPU accounting info along with the standard record. Awaiting testing from STFC<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* Updating the VO SLA for fedcloud vo<br />
* Review IMS<br />
* Circulated a broadcast to warn VOs about end of support for WMS<br />
* Prepared the list of middleware affected by Globus EOL<br />
* Preparation of OMB meeting<br />
* Follow up of the deployment of new probes in ARGO for fedcloud<br />
* Definietion of the DIRAC OLA (overall agreement)<br />
* Review of the ELIXIR Operations Centre<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* F2F SPG meeting<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
Terradue<br />
* All sites have been tested but CESGA and OKEANOS<br />
**Production: RECAS-BARI, BELNET, GWDG<br />
** Not used: 100IT and Cyfronet (waiting for an use case adaptable to the <br />
<br />
iMarine<br />
* Currently preparing an overview of the issues and the solutions<br />
<br />
LTOS<br />
*<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* 1 in review (EISCAT)<br />
* 4 in preparation (ELIXIR, BBMRI, EPOS, DM)<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
<br />
Preparation for the following f2f events:<br />
* EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
* CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Survey was sent out to NILs to update our knowledge on Engagement priorities<br />
* Discussed 'Enabling Global Infrastructures' (EGI services for RIs) brochure with press team. Working on identifying content/RIs to feature<br />
* Within UCST discussing success stories for project report and review<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* Had a CC meeting: <br />
** Distributed responsibilities on deliverable writing<br />
** OLAs look good for Steven, next step is to discuss adoption. Question is level: EBI or ELIXIR?<br />
<br />
=== Task SA2.4 BBMRI ===<br />
* Petr started collecting input for final deliverable, using the template provided by Gergely<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
* CC meeting planned for Jun 27, focus on intensifying outreach and user engagement.<br />
* Preparing workshop for July 12th, for DARIAH-HR community, demonstration and hands-on on DARIAH Science Gateway<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
* Provided input on e-infrastructure resources to support thematic services to the ERIC for their strategic meeting (Italy).<br />
<br />
* Connecting with other projects (INDIGO-DataCloud) to support applications exploiting mobile access.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* Received one of the reviews for D6.21. Two more are still missing. Working doc: https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
* Delays/stops with ticket/bug resolution by CNRS - Gergely sent an email to Andrei to investigate.<br />
<br />
=== Task SA2.9 EPOS ===<br />
*Had CC call where final deliverable was introduced. Progress is ok with AAI and Data demonstrator. The compute one will likely not reach maturity during EGI-Engage.<br />
* Next step: Daniele to circulate deliverable draft with assignment for demonstrator/pilot developers<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-27&diff=95754EGI-Engage:AMB-2017-06-272017-06-27T11:53:16Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* Preparing for ITSM audit<br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu)<br />
**ToC started: https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu)<br />
**ToC planned for first week of July<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br><br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
*Strategy<br />
** Preparation doc from survey for EGI Council (29 June)<br />
** Policy brief to update the EGI Council on service portfolio changes<br />
<br />
*IMS Updates<br />
** IMS Ops Meeting (Sy, Yannick, Mal) - 27 May<br />
** Several updated through IMS by many<br />
** 1st of 3 Internal audits for EGI IMS on the 30th of June in preparation to the audit conducted by TUV in November; first will focus on the ITSM processes. All have been informed and is planned. Thomas will be in Amsterdam.<br />
<br />
*FitSM<br />
**Conducted 2 Open Registration courses<br />
***Advanced SOC (Enol and Tiziana)<br />
***Expert<br />
****6 participants (5 from EGI, 1 from CSC)<br />
**In-house discussions ongoing: EBI and SURFsara<br />
<br><br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
*FAO<br />
**Started preparing their final document: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#<br />
*UberCloud<br />
**Worked to recover the container created for the EGI/UC webinar last November to make available for the ENVRI<br />
** Refined the business model behind this offer, which includes pricing/costs<br />
** EGI would provide the CRM side with UC on the backend.<br />
*Final deliverables will be the focus of the last 2 months (see deliverable/milestone section)<br />
<br />
*BDVA<br />
**General Assembly last week and group meetings<br />
***Was the voting for the board of directors - EGI (Yannick) was voted and accepted as a member of the BoD within the “other” categories<br />
****News Item published: https://www.egi.eu/news/egi-joins-the-board-of-directors-of-the-big-data-value-association/ <br />
**iSpaces redefinition was also revised which now also includes Federations. Formal accreditation process in place. EGI who was originally rejected as federations weren’t covered, we are now able to “reapply” in the context of “Federation”. The process will be straightforward. A ceremony for iSpace labels within the Big Data Forum [roberta to add where and when]. This is important as there are dedicated funding streams for iSpaces<br />
White paper on EO big data generation (currently writing)<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
<br />
=== Task JRA1.3 Accounting ===<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) ToC agreed, now working on content. Ready for internal review: 7 July<br />
* D4.10 Final CANFAR integration release (PM29) ToC agreed, now working on content. Ready for internal review: 7 July<br />
* M4.3 Open Data Platform in the Production (PM30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
Latest developments:<br />
* Handling multiple small files<br />
* Import of existing data<br />
* Added extended attributes support<br />
* Added administrator manual<br />
=== Task JRA2.2 Federated Cloud ===<br />
* OOI: bugfixes for networking with Neutron, merged this week, to be released this week<br />
* cloud-info-provider: work ongoing with Baptiste on adding V3 auth to Keystone<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* D4Science now confirmed to be running in production in Fedcloud<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Modification done with cASO to send GPGPU accounting info along with the standard record. Awaiting testing from STFC<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* Updating the VO SLA for fedcloud vo<br />
* Review IMS<br />
* Circulated a broadcast to warn VOs about end of support for WMS<br />
* Prepared the list of middleware affected by Globus EOL<br />
* Preparation of OMB meeting<br />
* Follow up of the deployment of new probes in ARGO for fedcloud<br />
* Definietion of the DIRAC OLA (overall agreement)<br />
* Review of the ELIXIR Operations Centre<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
Terradue<br />
* All sites have been tested but CESGA and OKEANOS<br />
**Production: RECAS-BARI, BELNET, GWDG<br />
** Not used: 100IT and Cyfronet (waiting for an use case adaptable to the <br />
<br />
iMarine<br />
* Currently preparing an overview of the issues and the solutions<br />
<br />
LTOS<br />
*<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* 1 in review (EISCAT)<br />
* 4 in preparation (ELIXIR, BBMRI, EPOS, DM)<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
<br />
Preparation for the following f2f events:<br />
* EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
* CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Survey was sent out to NILs to update our knowledge on Engagement priorities<br />
* Discussed 'Enabling Global Infrastructures' (EGI services for RIs) brochure with press team. Working on identifying content/RIs to feature<br />
* Within UCST discussing success stories for project report and review<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* Had a CC meeting: <br />
** Distributed responsibilities on deliverable writing<br />
** OLAs look good for Steven, next step is to discuss adoption. Question is level: EBI or ELIXIR?<br />
<br />
=== Task SA2.4 BBMRI ===<br />
* Petr started collecting input for final deliverable, using the template provided by Gergely<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
* CC meeting planned for Jun 27, focus on intensifying outreach and user engagement.<br />
* Preparing workshop for July 12th, for DARIAH-HR community, demonstration and hands-on on DARIAH Science Gateway<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
* Provided input on e-infrastructure resources to support thematic services to the ERIC for their strategic meeting (Italy).<br />
<br />
* Connecting with other projects (INDIGO-DataCloud) to support applications exploiting mobile access.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* Received one of the reviews for D6.21. Two more are still missing. Working doc: https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
* Delays/stops with ticket/bug resolution by CNRS - Gergely sent an email to Andrei to investigate.<br />
<br />
=== Task SA2.9 EPOS ===<br />
*Had CC call where final deliverable was introduced. Progress is ok with AAI and Data demonstrator. The compute one will likely not reach maturity during EGI-Engage.<br />
* Next step: Daniele to circulate deliverable draft with assignment for demonstrator/pilot developers<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-27&diff=95741EGI-Engage:AMB-2017-06-272017-06-27T10:54:02Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* Preparing for ITSM audit<br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu)<br />
**ToC started: https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu)<br />
**ToC planned for first week of July<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br><br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
*Strategy<br />
** Preparation doc from survey for EGI Council (29 June)<br />
** Policy brief to update the EGI Council on service portfolio changes<br />
<br />
*IMS Updates<br />
** IMS Ops Meeting (Sy, Yannick, Mal) - 27 May<br />
** Several updated through IMS by many<br />
** 1st of 3 Internal audits for EGI IMS on the 30th of June in preparation to the audit conducted by TUV in November; first will focus on the ITSM processes. All have been informed and is planned. Thomas will be in Amsterdam.<br />
<br />
*FitSM<br />
**Conducted 2 Open Registration courses<br />
***Advanced SOC (Enol and Tiziana)<br />
***Expert<br />
****6 participants (5 from EGI, 1 from CSC)<br />
**In-house discussions ongoing: EBI and SURFsara<br />
<br><br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
*FAO<br />
**Started preparing their final document: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#<br />
*UberCloud<br />
**Worked to recover the container created for the EGI/UC webinar last November to make available for the ENVRI<br />
** Refined the business model behind this offer, which includes pricing/costs<br />
** EGI would provide the CRM side with UC on the backend.<br />
*Final deliverables will be the focus of the last 2 months (see deliverable/milestone section)<br />
<br />
*BDVA<br />
**General Assembly last week and group meetings<br />
***Was the voting for the board of directors - EGI (Yannick) was voted and accepted as a member of the BoD within the “other” categories<br />
****News Item published: https://www.egi.eu/news/egi-joins-the-board-of-directors-of-the-big-data-value-association/ <br />
**iSpaces redefinition was also revised which now also includes Federations. Formal accreditation process in place. EGI who was originally rejected as federations weren’t covered, we are now able to “reapply” in the context of “Federation”. The process will be straightforward. A ceremony for iSpace labels within the Big Data Forum [roberta to add where and when]. This is important as there are dedicated funding streams for iSpaces<br />
White paper on EO big data generation (currently writing)<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
<br />
=== Task JRA1.3 Accounting ===<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) ToC agreed, now working on content. Ready for internal review: 7 July<br />
* D4.10 Final CANFAR integration release (PM29) ToC agreed, now working on content. Ready for internal review: 7 July<br />
* M4.3 Open Data Platform in the Production (PM30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
Latest developments:<br />
* Handling multiple small files<br />
* Import of existing data<br />
* Added extended attributes support<br />
* Added administrator manual<br />
=== Task JRA2.2 Federated Cloud ===<br />
* OOI: bugfixes for networking with neutron, merged this week, to be released this week<br />
* cloud-info-provider: work ongoing with Baptiste on adding V3 auth to Keystone<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* D4Science now confirmed to be running in production in Fedcloud<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Modification done with cASO to send GPGPU accounting info along with the standard record. Awaiting testing from STFC<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* Updating the VO SLA for fedcloud vo<br />
* Review IMS<br />
* Circulated a broadcast to warn VOs about end of support for WMS<br />
* Prepared the list of middleware affected by Globus EOL<br />
* Preparation of OMB meeting<br />
* Follow up of the deployment of new probes in ARGO for fedcloud<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
Terradue<br />
* All sites have been tested but CESGA and OKEANOS<br />
**Production: RECAS-BARI, BELNET, GWDG<br />
** Not used: 100IT and Cyfronet (waiting for an use case adaptable to the <br />
<br />
iMarine<br />
* Currently preparing an overview of the issues and the solutions<br />
<br />
LTOS<br />
*<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* 1 in review (EISCAT)<br />
* 4 in preparation (ELIXIR, BBMRI, EPOS, DM)<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
<br />
Preparation for the following f2f events:<br />
* EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
* CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Survey was sent out to NILs to update our knowledge on Engagement priorities<br />
* Discussed 'Enabling Global Infrastructures' (EGI services for RIs) brochure with press team. Working on identifying content/RIs to feature<br />
* Within UCST discussing success stories for project report and review<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* Had a CC meeting: <br />
** Distributed responsibilities on deliverable writing<br />
** OLAs look good for Steven, next step is to discuss adoption. Question is level: EBI or ELIXIR?<br />
<br />
=== Task SA2.4 BBMRI ===<br />
* Petr started collecting input for final deliverable, using the template provided by Gergely<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
* CC meeting planned for Jun 27, focus on intensifying outreach and user engagement.<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
* Provided input on e-infrastructure resources to support thematic services to the ERIC for their strategic meeting (Italy).<br />
<br />
* Connecting with other projects (INDIGO-DataCloud) to support applications exploiting mobile access.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* Received one of the reviews for D6.21. Two more are still missing. Working doc: https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
* Delays/stops with ticket/bug resolution by CNRS - Gergely sent an email to Andrei to investigate.<br />
<br />
=== Task SA2.9 EPOS ===<br />
*Had CC call where final deliverable was introduced. Progress is ok with AAI and Data demonstrator. The compute one will likely not reach maturity during EGI-Engage.<br />
* Next step: Daniele to circulate deliverable draft with assignment for demonstrator/pilot developers<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-27&diff=95739EGI-Engage:AMB-2017-06-272017-06-27T10:50:36Z<p>Psolagna: /* WP5 (SA1) (Peter Solagna) */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* Preparing for ITSM audit<br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
*D2.14 “Final Report on Communications, Dissemination and Engagement” (M30 - EGI.eu)<br />
**ToC started: https://docs.google.com/document/d/1Pxv63WZ0DSGg6rPiJYj1rb65m9DqH3jrct-eRNp5DN0/edit<br />
*D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu)<br />
**ToC planned for first week of July<br />
<br><br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br><br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
*Strategy<br />
** Preparation doc from survey for EGI Council (29 June)<br />
** Policy brief to update the EGI Council on service portfolio changes<br />
<br />
*IMS Updates<br />
** IMS Ops Meeting (Sy, Yannick, Mal) - 27 May<br />
** Several updated through IMS by many<br />
** 1st of 3 Internal audits for EGI IMS on the 30th of June in preparation to the audit conducted by TUV in November; first will focus on the ITSM processes. All have been informed and is planned. Thomas will be in Amsterdam.<br />
<br />
*FitSM<br />
**Conducted 2 Open Registration courses<br />
***Advanced SOC (Enol and Tiziana)<br />
***Expert<br />
****6 participants (5 from EGI, 1 from CSC)<br />
**In-house discussions ongoing: EBI and SURFsara<br />
<br><br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
*FAO<br />
**Started preparing their final document: https://docs.google.com/document/d/1Z1akX-SaIPopdsignRHod_cjHqt5D8XzDwHFrgVDM8c/edit?ts=59511a6c#<br />
*UberCloud<br />
**Worked to recover the container created for the EGI/UC webinar last November to make available for the ENVRI<br />
** Refined the business model behind this offer, which includes pricing/costs<br />
** EGI would provide the CRM side with UC on the backend.<br />
*Final deliverables will be the focus of the last 2 months (see deliverable/milestone section)<br />
<br />
*BDVA<br />
**General Assembly last week and group meetings<br />
***Was the voting for the board of directors - EGI (Yannick) was voted and accepted as a member of the BoD within the “other” categories<br />
****News Item published: https://www.egi.eu/news/egi-joins-the-board-of-directors-of-the-big-data-value-association/ <br />
**iSpaces redefinition was also revised which now also includes Federations. Formal accreditation process in place. EGI who was originally rejected as federations weren’t covered, we are now able to “reapply” in the context of “Federation”. The process will be straightforward. A ceremony for iSpace labels within the Big Data Forum [roberta to add where and when]. This is important as there are dedicated funding streams for iSpaces<br />
White paper on EO big data generation (currently writing)<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
<br />
=== Task JRA1.3 Accounting ===<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29) ToC agreed, now working on content. Ready for internal review: 7 July<br />
* D4.10 Final CANFAR integration release (PM29) ToC agreed, now working on content. Ready for internal review: 7 July<br />
* M4.3 Open Data Platform in the Production (PM30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
Latest developments:<br />
* Handling multiple small files<br />
* Import of existing data<br />
* Added extended attributes support<br />
* Added administrator manual<br />
=== Task JRA2.2 Federated Cloud ===<br />
* OOI: bugfixes for networking with neutron, merged this week, to be released this week<br />
* cloud-info-provider: work ongoing with Baptiste on adding V3 auth to Keystone<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* D4Science now confirmed to be running in production in Fedcloud<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Modification done with cASO to send GPGPU accounting info along with the standard record. Awaiting testing from STFC<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* Updating the VO SLA<br />
<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
Terradue<br />
* All sites have been tested but CESGA and OKEANOS<br />
**Production: RECAS-BARI, BELNET, GWDG<br />
** Not used: 100IT and Cyfronet (waiting for an use case adaptable to the <br />
<br />
iMarine<br />
* Currently preparing an overview of the issues and the solutions<br />
<br />
LTOS<br />
*<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* 1 in review (EISCAT)<br />
* 4 in preparation (ELIXIR, BBMRI, EPOS, DM)<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
<br />
Preparation for the following f2f events:<br />
* EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
* CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Survey was sent out to NILs to update our knowledge on Engagement priorities<br />
* Discussed 'Enabling Global Infrastructures' (EGI services for RIs) brochure with press team. Working on identifying content/RIs to feature<br />
* Within UCST discussing success stories for project report and review<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* Had a CC meeting: <br />
** Distributed responsibilities on deliverable writing<br />
** OLAs look good for Steven, next step is to discuss adoption. Question is level: EBI or ELIXIR?<br />
<br />
=== Task SA2.4 BBMRI ===<br />
* Petr started collecting input for final deliverable, using the template provided by Gergely<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
* CC meeting planned for Jun 27, focus on intensifying outreach and user engagement.<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
* Provided input on e-infrastructure resources to support thematic services to the ERIC for their strategic meeting (Italy).<br />
<br />
* Connecting with other projects (INDIGO-DataCloud) to support applications exploiting mobile access.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* Received one of the reviews for D6.21. Two more are still missing. Working doc: https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
* Delays/stops with ticket/bug resolution by CNRS - Gergely sent an email to Andrei to investigate.<br />
<br />
=== Task SA2.9 EPOS ===<br />
*Had CC call where final deliverable was introduced. Progress is ok with AAI and Data demonstrator. The compute one will likely not reach maturity during EGI-Engage.<br />
* Next step: Daniele to circulate deliverable draft with assignment for demonstrator/pilot developers<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-14&diff=95448EGI-Engage:AMB-2017-06-142017-06-14T09:27:37Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
* gathering of cloud requirements from the Blue Cloud Pilot EC initiative (Brussels 13 June)<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* process reviews - CRM, PM, SLM, SRM, ISRM<br />
* handling deliverables' reviews<br />
* assessing new tool for handling deliverables <br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Newsletter:<br />
** Publication of issue 27<br />
** Commissioning issue 28<br />
* EGI Use Cases brochure: <br />
** final content and concept <br />
** finding and briefing a designer<br />
* DI4R 2017:<br />
** first meetings<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
* Strategy<br />
** Chased Council participants to complete the survey, started analysis of review of Council answers and improved agenda for the workshop to discuss the evolution of the EGI Strategy<br />
** Presented at e-IRG work from the Open Science Policy Platform<br />
** EGI Glossary Update (started, not finished)<br />
<br />
* Service management<br />
** Organised two SSB to discuss the approval of major changes for services to be proposed to the Council; <br />
** Improved service portfolio management process (SDTP template, SPM1 procedure, service phase)<br />
** Drafted policy brief for the EGI Council<br />
<br />
* Procurement<br />
** Disseminated the results of the procurement activity at the e-IRG workshop through a dedicated session<br />
<br />
**IMS Updates<br />
***IMS Ops Meeting (Sy, Yannick, Mal) - 23 May<br />
***Individual Calls held with Matthew, Sara, Sergio<br />
***SPM update<br />
***Internal Audit planning scheduled for 30 June<br />
<br />
*FitSM<br />
**FitSM In-House Foundation Training at EBI in Cambridge (19 May)<br />
**FitSM WG F2F - Munich - 29-30 May<br />
**FitSM Open Registration Foundation Training at EGI Offices in Amsterdam (6-7 June); Attended by Sjomara, Celine and SURFnet rep<br />
**Organisation of 2 upcoming FitSM open registrations (Advanced SOC + Expert)<br />
<br />
* Collaborations<br />
** Finalised and signed the MoU between EGI and GEANT<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
*Organized and conducted a 1 hr Webinar “How to Engage SMEs for NGIs” - 30 May<br />
*FAO<br />
**Several calls to plan final effort consumption and objectives + progress update<br />
*UberCloud<br />
**Few calls and email exchanges to restart the container from the Nov webinar in order to make available for the ENVRI community<br />
**Continued to define the business model for after any trial period<br />
*Partner effort consumption and final effort reporting planning<br />
*Final deliverables will be the focus of the last 2 months<br />
*EOCD (Austria)<br />
**Internal discussions to support cloud activities and eventually business models <br />
<br />
*BDVA<br />
**We are jointly submitting a white paper on Big Data in Space in TF7<br />
***Contributions on e-infrastructures<br />
***Projects and EU-initiatives<br />
***Education<br />
**We are jointly defining the federated i-Space criteria within the i-Space subgroup<br />
**We are contributing to the SRIA update, with focus on the EOSC<br />
** We applied to be part of the Board of Director of BDVA, election will be held on June 21st<br />
<br />
<br />
*EO Pilot<br />
**Analysed involvement T-systems and OTC in the pilot<br />
** Analysed requirement for final integration of OneData and OneProvider in CESNET<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype: prototype still under development. Deliverable writing should start next week<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace: Deliverable writing will start next week.<br />
* M30: D3.17 Final release of the accounting and operational tools: Plan to write it in July<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* CheckIn moving to beta<br />
* Working to support the new LoA levels (from AARC)<br />
* Working to support the EGI FedCloud<br />
* Connectors to Ops Portal to gather information about VOs<br />
* Assessment of the support status of MyProxy in the light of the Globus EOL<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
* Integration with RT almost completed<br />
* Fixed bugs in the Cart<br />
* Integration with the Applications on demand service on-going. Specification: https://docs.google.com/document/d/1fEu3bfHD7CpuH5Uvu7D8K1kBcG_7lb1JyWh0jVG4UGs<br />
* Customer dashboard in PrestaShop<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud accounting:<br />
** New solution for accounting of the long running VMs under testing<br />
* Data accounting:<br />
** Tests with OneData are proceeding. For more details see: https://docs.google.com/document/d/1__vC6nVptyfnvKNnkOHrv_8aR4midG9gXNf4mhwIgR8/edit?usp=sharing<br />
* New release of the portal under testing. New main features:<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Maps to show the graphical distribution of the accounting data in country views: the implementation was too poor. This feature will be removed by this release and included (in a better shape) in the next.<br />
** Discipline account report<br />
** New restricted views<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops Portal: Working on integrating CheckIn and the new messaging. Interface for CheckIn to extract VO information<br />
* GOCDB: new roadmap until the end of the project defined: https://wiki.egi.eu/wiki/TASK_JRA1.4_Operations_Tools#GOCDB<br />
* ARGO: module for probes management under development, new messaging infrastructure under testing<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29)<br />
* D4.10 Final CANFAR integration release (PM30) We're working to an internal deadline of PM29 for submission readiness.<br />
* M4.3 Open Data Platform in the Production (M30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
* EGI FedData/DataHub news<br />
** Documentation being improved after EGI/STFC review within Indigo. <br />
** New homepage created for FedData: https://wiki.egi.eu/wiki/EGI_Federated_Data<br />
** Proposal to present the transition to Beta at July SSB (SDTP being updated)<br />
* Onedata outstanding problems to be addressed by next release:<br />
** small files <br />
** importing existing data<br />
* EOSCpilot demonstrators wanting to incorporate EGI DataHub into their testing: DPHEP, TextCrowd, Photon Neutron science<br />
* Contact made (and being followed up) with Marc Rousseau (ComputeCanada) at Catania - interested in testing OpenData and try joining the EGI DataHub<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
* Cloudkeeper is undergoing the verification process to be included in the CMD<br />
* Work ongoing on the glue2.1 updates for the info provider<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* 4.10 work (TOC this week with Giuliano, Sara)<br />
* initial meeting with ENES about helping their usecase as an EGI-EUDAT usecase, along with regular monthly meetings<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Documentation and administration of 2 sites with GPGPUs (IISAS-GPUCloud and IISAS-Nebula)<br />
* Preparations for Dynamic DNS to move to production<br />
* Viet has warned that they are out of funding for further EGI-Engage work (it ended in May). Work that couldn't continue (text from Viet):<br />
** cannot maintain all sites in production, mainly GPGPPU sites, that are much more demanding to manpower in comparison with normnal sites (due to inability to suspend/migrate VMs with GPGPU during update/upgrade). For information, beside the two GPGPU sites, we have a third (normal) site in EGI FedCloud, where we serve VMs from d4science.org<br />
** make sufficient suports for users with GPGPUs (solving problems with GPGPU, documentation, tutorials, ...). Giuseppe La Rocca plans to have with us a webinar soon<br />
** completing the work with BDII and accounting, we will make "best efforts" to suport/test the corresponding tools (e.g. cloudkeeper) about GPGPU properties (already proposed)<br />
* Additional effort has been estimated as 1.4PM - they are requesting 1PM<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* '''Globus toolkit EOL''', first assessment of the affected middleware<br />
* Reviewed RC-RP OLA in the light of ELIXIR comments<br />
* VO Management (vo.nextgeoss.eu registration)<br />
* VOs SLA reports: bils, extras, and lsgc<br />
* Release of Preview 1.12 and 2.12<br />
* CMD-OS release CMD-OS 1.1<br />
* Partecipation to Fedcloud TF<br />
* Chairing and agenda preparation Operations, and URT meetings<br />
* RC and RP OLA monthly enforcing<br />
* review of the new cloud infoprovider for GLUE2.1 schema<br />
* review of the new release of accounting portal<br />
* Follow-up of the issues with CREAM-CE and ARC-CE nagios probes (solved)<br />
* Follow up the deployment of new nagios probes for EGI FedCloud (occi and appdb)<br />
* Started the review of the training material in the wiki<br />
* EMI repository have been switched off<br />
* Review the Fedcloud UI docker image<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Working on the migration of the software vulnerabilities follow up process to the Operations team<br />
* SPG F2F meeting in Karlsruhe <br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
ESA<br />
* Closing of the GWDG security incident. Everything ok, false positive. As a good side-effect the VMIs have been analyzed by CSIRT and approved.<br />
* Reconfigured the network policies at the sites supporting the two terradue VOs<br />
LTOS<br />
* User support of new registrants <br />
* Wiki documentation has been updated<br />
* SDTP updated<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* D6.21 EISCAT Portal second version: Sent to external review on the 8th<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* How to engage SMEs for NGIs: https://indico.egi.eu/indico/event/3373/<br />
<br />
Preparation for the following f2f events:<br />
EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Engagement with Nordic countries at NeIC<br />
* Support for BigDataEurope project<br />
* Presentation at MSO4SC project workshop and sending a proposal for engagement<br />
* Meeting with CESSDA director<br />
* Establishing Engagement WG and arranging first meeting (Jun 9)<br />
* Organising Engagement meeting for NILs (Jun 9)<br />
* Organising UCB meeting for 'heavy user communities' (June 14)<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* EGI Federated Cloud developer from CESNET visited the META-pipe developers in Tromsö, Norway<br />
* Full-scale tests (over 400 cores) of META-pipe started in the local cloud environment of CSC <br />
* The EC project officer approved the effort re-balancing: 2 PM were moved form EBI-EMBL to CNRS and 2 PM to EGI.eu (outside the ELIXIR CC).<br />
* Phenomenal developers are starting to test ELIXIR VO in EGI federated cloud.<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
Dissemination activities:<br />
* Presenting DARIAH Competence centre outcomes and services at the EGI Conference, ''9-12 May 2017, Catania, Italy''<br />
* A pre-conference workshop abstract "''An Open DARIAH-CC - EGI Workshop in conjunction with COST ENeL''" for Digital Humanities 2017 conference submitted (not accepted)<br />
* Workshop on biodiversity and linguistic diversity for scholar from Natural History Museum, Vienna, ''6th June 2017, Vienna''<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
Support to GBIF extended with more Cloud resources.<br />
Development of tools for use of satellite images continued.<br />
Tests of implementation of SDM (MaxEnt) as dockers started.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* D6.21 was finished and sent for external review. Docuemnt is available for commenting at https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-14&diff=95446EGI-Engage:AMB-2017-06-142017-06-14T09:17:33Z<p>Psolagna: /* Task SA1.3 Integration, Deployment of Grid and Cloud Platforms */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
* gathering of cloud requirements from the Blue Cloud Pilot EC initiative (Brussels 13 June)<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* process reviews - CRM, PM, SLM, SRM, ISRM<br />
* handling deliverables' reviews<br />
* assessing new tool for handling deliverables <br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Newsletter:<br />
** Publication of issue 27<br />
** Commissioning issue 28<br />
* EGI Use Cases brochure: <br />
** final content and concept <br />
** finding and briefing a designer<br />
* DI4R 2017:<br />
** first meetings<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
* Strategy<br />
** Chased Council participants to complete the survey, started analysis of review of Council answers and improved agenda for the workshop to discuss the evolution of the EGI Strategy<br />
** Presented at e-IRG work from the Open Science Policy Platform<br />
** EGI Glossary Update (started, not finished)<br />
<br />
* Service management<br />
** Organised two SSB to discuss the approval of major changes for services to be proposed to the Council; <br />
** Improved service portfolio management process (SDTP template, SPM1 procedure, service phase)<br />
** Drafted policy brief for the EGI Council<br />
<br />
* Procurement<br />
** Disseminated the results of the procurement activity at the e-IRG workshop through a dedicated session<br />
<br />
**IMS Updates<br />
***IMS Ops Meeting (Sy, Yannick, Mal) - 23 May<br />
***Individual Calls held with Matthew, Sara, Sergio<br />
***SPM update<br />
***Internal Audit planning scheduled for 30 June<br />
<br />
*FitSM<br />
**FitSM In-House Foundation Training at EBI in Cambridge (19 May)<br />
**FitSM WG F2F - Munich - 29-30 May<br />
**FitSM Open Registration Foundation Training at EGI Offices in Amsterdam (6-7 June); Attended by Sjomara, Celine and SURFnet rep<br />
**Organisation of 2 upcoming FitSM open registrations (Advanced SOC + Expert)<br />
<br />
* Collaborations<br />
** Finalised and signed the MoU between EGI and GEANT<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
*Organized and conducted a 1 hr Webinar “How to Engage SMEs for NGIs” - 30 May<br />
*FAO<br />
**Several calls to plan final effort consumption and objectives + progress update<br />
*UberCloud<br />
**Few calls and email exchanges to restart the container from the Nov webinar in order to make available for the ENVRI community<br />
**Continued to define the business model for after any trial period<br />
*Partner effort consumption and final effort reporting planning<br />
*Final deliverables will be the focus of the last 2 months<br />
*EOCD (Austria)<br />
**Internal discussions to support cloud activities and eventually business models <br />
<br />
*BDVA<br />
**We are jointly submitting a white paper on Big Data in Space in TF7<br />
***Contributions on e-infrastructures<br />
***Projects and EU-initiatives<br />
***Education<br />
**We are jointly defining the federated i-Space criteria within the i-Space subgroup<br />
**We are contributing to the SRIA update, with focus on the EOSC<br />
** We applied to be part of the Board of Director of BDVA, election will be held on June 21st<br />
<br />
<br />
*EO Pilot<br />
**Analysed involvement T-systems and OTC in the pilot<br />
** Analysed requirement for final integration of OneData and OneProvider in CESNET<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype: prototype still under development. Deliverable writing should start next week<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace: Deliverable writing will start next week.<br />
* M30: D3.17 Final release of the accounting and operational tools: Plan to write it in July<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* CheckIn moving to beta<br />
* Working to support the new LoA levels (from AARC)<br />
* Working to support the EGI FedCloud<br />
* Connectors to Ops Portal to gather information about VOs<br />
* Assessment of the support status of MyProxy in the light of the Globus EOL<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
* Integration with RT almost completed<br />
* Fixed bugs in the Cart<br />
* Integration with the Applications on demand service on-going. Specification: https://docs.google.com/document/d/1fEu3bfHD7CpuH5Uvu7D8K1kBcG_7lb1JyWh0jVG4UGs<br />
* Customer dashboard in PrestaShop<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud accounting:<br />
** New solution for accounting of the long running VMs under testing<br />
* Data accounting:<br />
** Tests with OneData are proceeding. For more details see: https://docs.google.com/document/d/1__vC6nVptyfnvKNnkOHrv_8aR4midG9gXNf4mhwIgR8/edit?usp=sharing<br />
* New release of the portal under testing. New main features:<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Maps to show the graphical distribution of the accounting data in country views: the implementation was too poor. This feature will be removed by this release and included (in a better shape) in the next.<br />
** Discipline account report<br />
** New restricted views<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops Portal: Working on integrating CheckIn and the new messaging. Interface for CheckIn to extract VO information<br />
* GOCDB: new roadmap until the end of the project defined: https://wiki.egi.eu/wiki/TASK_JRA1.4_Operations_Tools#GOCDB<br />
* ARGO: module for probes management under development, new messaging infrastructure under testing<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29)<br />
* D4.10 Final CANFAR integration release (PM30) We're working to an internal deadline of PM29 for submission readiness.<br />
* M4.3 Open Data Platform in the Production (M30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
* EGI FedData/DataHub news<br />
** Documentation being improved after EGI/STFC review within Indigo. <br />
** New homepage created for FedData: https://wiki.egi.eu/wiki/EGI_Federated_Data<br />
** Proposal to present the transition to Beta at July SSB (SDTP being updated)<br />
* Onedata outstanding problems to be addressed by next release:<br />
** small files <br />
** importing existing data<br />
* EOSCpilot demonstrators wanting to incorporate EGI DataHub into their testing: DPHEP, TextCrowd, Photon Neutron science<br />
* Contact made (and being followed up) with Marc Rousseau (ComputeCanada) at Catania - interested in testing OpenData and try joining the EGI DataHub<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
* Cloudkeeper is undergoing the verification process to be included in the CMD<br />
* Work ongoing on the glue2.1 updates for the info provider<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* 4.10 work (TOC this week with Giuliano, Sara)<br />
* initial meeting with ENES about helping their usecase as an EGI-EUDAT usecase, along with regular monthly meetings<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Documentation and administration of 2 sites with GPGPUs (IISAS-GPUCloud and IISAS-Nebula)<br />
* Preparations for Dynamic DNS to move to production<br />
* Viet has warned that they are out of funding for further EGI-Engage work (it ended in May). Work that couldn't continue (text from Viet):<br />
** cannot maintain all sites in production, mainly GPGPPU sites, that are much more demanding to manpower in comparison with normnal sites (due to inability to suspend/migrate VMs with GPGPU during update/upgrade). For information, beside the two GPGPU sites, we have a third (normal) site in EGI FedCloud, where we serve VMs from d4science.org<br />
** make sufficient suports for users with GPGPUs (solving problems with GPGPU, documentation, tutorials, ...). Giuseppe La Rocca plans to have with us a webinar soon<br />
** completing the work with BDII and accounting, we will make "best efforts" to suport/test the corresponding tools (e.g. cloudkeeper) about GPGPU properties (already proposed)<br />
* Additional effort has been estimated as 1.4PM - they are requesting 1PM<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* '''Globus toolkit EOL''', first assessment of the affected middleware<br />
* Reviewed RC-RP OLA in the light of ELIXIR comments<br />
* VO Management (vo.nextgeoss.eu registration)<br />
* VOs SLA reports: bils, extras, and lsgc<br />
* Release of Preview 1.12 and 2.12<br />
* CMD-OS release CMD-OS 1.1<br />
* Partecipation to Fedcloud TF<br />
* Chairing and agenda preparation Operations, and URT meetings<br />
* RC and RP OLA monthly enforcing<br />
* review of the new cloud infoprovider for GLUE2.1 schema<br />
* review of the new release of accounting portal<br />
* Follow-up of the issues with CREAM-CE and ARC-CE nagios probes (solved)<br />
* Follow up the deployment of new nagios probes for EGI FedCloud (occi and appdb)<br />
* Started the review of the training material in the wiki<br />
* EMI repository have been switched off<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Working on the migration of the software vulnerabilities follow up process to the Operations team<br />
* SPG F2F meeting in Karlsruhe <br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
ESA<br />
* Closing of the GWDG security incident. Everything ok, false positive. As a good side-effect the VMIs have been analyzed by CSIRT and approved.<br />
* Reconfigured the network policies at the sites supporting the two terradue VOs<br />
LTOS<br />
* User support of new registrants <br />
* Wiki documentation has been updated<br />
* SDTP updated<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* D6.21 EISCAT Portal second version: Sent to external review on the 8th<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* How to engage SMEs for NGIs: https://indico.egi.eu/indico/event/3373/<br />
<br />
Preparation for the following f2f events:<br />
EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Engagement with Nordic countries at NeIC<br />
* Support for BigDataEurope project<br />
* Presentation at MSO4SC project workshop and sending a proposal for engagement<br />
* Meeting with CESSDA director<br />
* Establishing Engagement WG and arranging first meeting (Jun 9)<br />
* Organising Engagement meeting for NILs (Jun 9)<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* EGI Federated Cloud developer from CESNET visited the META-pipe developers in Tromsö, Norway<br />
* Full-scale tests (over 400 cores) of META-pipe started in the local cloud environment of CSC <br />
* The EC project officer approved the effort re-balancing: 2 PM were moved form EBI-EMBL to CNRS and 2 PM to EGI.eu (outside the ELIXIR CC).<br />
* Phenomenal developers are starting to test ELIXIR VO in EGI federated cloud.<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
Dissemination activities:<br />
* Presenting DARIAH Competence centre outcomes and services at the EGI Conference, ''9-12 May 2017, Catania, Italy''<br />
* A pre-conference workshop abstract "''An Open DARIAH-CC - EGI Workshop in conjunction with COST ENeL''" for Digital Humanities 2017 conference submitted (not accepted)<br />
* Workshop on biodiversity and linguistic diversity for scholar from Natural History Museum, Vienna, ''6th June 2017, Vienna''<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
Support to GBIF extended with more Cloud resources.<br />
Development of tools for use of satellite images continued.<br />
Tests of implementation of SDM (MaxEnt) as dockers started.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* D6.21 was finished and sent for external review. Docuemnt is available for commenting at https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-14&diff=95442EGI-Engage:AMB-2017-06-142017-06-14T08:54:40Z<p>Psolagna: /* WP5 (SA1) (Peter Solagna) */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
* gathering of cloud requirements from the Blue Cloud Pilot EC initiative (Brussels 13 June)<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* process reviews - CRM, PM, SLM, SRM, ISRM<br />
* handling deliverables' reviews<br />
* assessing new tool for handling deliverables <br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Newsletter:<br />
** Publication of issue 27<br />
** Commissioning issue 28<br />
* EGI Use Cases brochure: <br />
** final content and concept <br />
** finding and briefing a designer<br />
* DI4R 2017:<br />
** first meetings<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype: prototype still under development. Deliverable writing should start next week<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace: Deliverable writing will start next week.<br />
* M30: D3.17 Final release of the accounting and operational tools: Plan to write it in July<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* CheckIn moving to beta<br />
* Working to support the new LoA levels (from AARC)<br />
* Working to support the EGI FedCloud<br />
* Connectors to Ops Portal to gather information about VOs<br />
* Assessment of the support status of MyProxy in the light of the Globus EOL<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
* Integration with RT almost completed<br />
* Fixed bugs in the Cart<br />
* Integration with the Applications on demand service on-going. Specification: https://docs.google.com/document/d/1fEu3bfHD7CpuH5Uvu7D8K1kBcG_7lb1JyWh0jVG4UGs<br />
* Customer dashboard in PrestaShop<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud accounting:<br />
** New solution for accounting of the long running VMs under testing<br />
* Data accounting:<br />
** Tests with OneData are proceeding. For more details see: https://docs.google.com/document/d/1__vC6nVptyfnvKNnkOHrv_8aR4midG9gXNf4mhwIgR8/edit?usp=sharing<br />
* New release of the portal under testing. New main features:<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Maps to show the graphical distribution of the accounting data in country views: the implementation was too poor. This feature will be removed by this release and included (in a better shape) in the next.<br />
** Discipline account report<br />
** New restricted views<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops Portal: Working on integrating CheckIn and the new messaging. Interface for CheckIn to extract VO information<br />
* GOCDB: new roadmap until the end of the project defined: https://wiki.egi.eu/wiki/TASK_JRA1.4_Operations_Tools#GOCDB<br />
* ARGO: module for probes management under development, new messaging infrastructure under testing<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29)<br />
* D4.10 Final CANFAR integration release (PM30) We're working to an internal deadline of PM29 for submission readiness.<br />
* M4.3 Open Data Platform in the Production (M30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
* EGI FedData/DataHub news<br />
** Documentation being improved after EGI/STFC review within Indigo. <br />
** New homepage created for FedData: https://wiki.egi.eu/wiki/EGI_Federated_Data<br />
** Proposal to present the transition to Beta at July SSB (SDTP being updated)<br />
* Onedata outstanding problems to be addressed by next release:<br />
** small files <br />
** importing existing data<br />
* EOSCpilot demonstrators wanting to incorporate EGI DataHub into their testing: DPHEP, TextCrowd, Photon Neutron science<br />
* Contact made (and being followed up) with Marc Rousseau (ComputeCanada) at Catania - interested in testing OpenData and try joining the EGI DataHub<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
* Cloudkeeper is undergoing the verification process to be included in the CMD<br />
* Work ongoing on the glue2.1 updates for the info provider<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* 4.10 work (TOC this week with Giuliano, Sara)<br />
* initial meeting with ENES about helping their usecase as an EGI-EUDAT usecase, along with regular monthly meetings<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Documentation and administration of 2 sites with GPGPUs (IISAS-GPUCloud and IISAS-Nebula)<br />
* Preparations for Dynamic DNS to move to production<br />
* Viet has warned that they are out of funding for further EGI-Engage work (it ended in May). Work that couldn't continue (text from Viet):<br />
** cannot maintain all sites in production, mainly GPGPPU sites, that are much more demanding to manpower in comparison with normnal sites (due to inability to suspend/migrate VMs with GPGPU during update/upgrade). For information, beside the two GPGPU sites, we have a third (normal) site in EGI FedCloud, where we serve VMs from d4science.org<br />
** make sufficient suports for users with GPGPUs (solving problems with GPGPU, documentation, tutorials, ...). Giuseppe La Rocca plans to have with us a webinar soon<br />
** completing the work with BDII and accounting, we will make "best efforts" to suport/test the corresponding tools (e.g. cloudkeeper) about GPGPU properties (already proposed)<br />
* Additional effort has been estimated as 1PM<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* '''Globus toolkit EOL''', first assessment of the affected middleware<br />
* Reviewed RC-RP OLA in the light of ELIXIR comments<br />
* VO Management (vo.nextgeoss.eu registration)<br />
* VOs SLA reports: bils, extras, and lsgc<br />
* Release of Preview 1.12 and 2.12<br />
* CMD-OS release CMD-OS 1.1<br />
* Partecipation to Fedcloud TF<br />
* Chairing and agenda preparation Operations, and URT meetings<br />
* RC and RP OLA monthly enforcing<br />
* review of the new cloud infoprovider for GLUE2.1 schema<br />
* review of the new release of accounting portal<br />
* Follow-up of the issues with CREAM-CE and ARC-CE nagios probes (solved)<br />
* Follow up the deployment of new nagios probes for EGI FedCloud (occi and appdb)<br />
* Started the review of the training material in the wiki<br />
* EMI repository have been switched off<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Working on the migration of the software vulnerabilities follow up process to the Operations team<br />
* SPG F2F meeting in Karlsruhe <br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
ESA<br />
* Closing of the GWDG security incident. Everything ok, false positive. As a good side-effect the VMIs have been analyzed by CSIRT and approved.<br />
* Reconfigured the network policies at the sites supporting the two terradue VOs<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* D6.21 EISCAT Portal second version: Sent to external review on the 8th<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* How to engage SMEs for NGIs: https://indico.egi.eu/indico/event/3373/<br />
<br />
Preparation for the following f2f events:<br />
EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Engagement with Nordic countries at NeIC<br />
* Support for BigDataEurope project<br />
* Presentation at MSO4SC project workshop and sending a proposal for engagement<br />
* Meeting with CESSDA director<br />
* Establishing Engagement WG and arranging first meeting (Jun 9)<br />
* Organising Engagement meeting for NILs (Jun 9)<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* EGI Federated Cloud developer from CESNET visited the META-pipe developers in Tromsö, Norway<br />
* Full-scale tests (over 400 cores) of META-pipe started in the local cloud environment of CSC <br />
* The EC project officer approved the effort re-balancing: 2 PM were moved form EBI-EMBL to CNRS and 2 PM to EGI.eu (outside the ELIXIR CC).<br />
* Phenomenal developers are starting to test ELIXIR VO in EGI federated cloud.<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
Dissemination activities:<br />
* Presenting DARIAH Competence centre outcomes and services at the EGI Conference, ''9-12 May 2017, Catania, Italy''<br />
* A pre-conference workshop abstract "''An Open DARIAH-CC - EGI Workshop in conjunction with COST ENeL''" for Digital Humanities 2017 conference submitted (not accepted)<br />
* Workshop on biodiversity and linguistic diversity for scholar from Natural History Museum, Vienna, ''6th June 2017, Vienna''<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
Support to GBIF extended with more Cloud resources.<br />
Development of tools for use of satellite images continued.<br />
Tests of implementation of SDM (MaxEnt) as dockers started.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* D6.21 was finished and sent for external review. Docuemnt is available for commenting at https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-14&diff=95437EGI-Engage:AMB-2017-06-142017-06-14T08:13:06Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
* gathering of cloud requirements from the Blue Cloud Pilot EC initiative (Brussels 13 June)<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* process reviews - CRM, PM, SLM, SRM, ISRM<br />
* handling deliverables' reviews<br />
* assessing new tool for handling deliverables <br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Newsletter:<br />
** Publication of issue 27<br />
** Commissioning issue 28<br />
* EGI Use Cases brochure: <br />
** final content and concept <br />
** finding and briefing a designer<br />
* DI4R 2017:<br />
** first meetings<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype: prototype still under development. Deliverable writing should start next week<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace: Deliverable writing will start next week.<br />
* M30: D3.17 Final release of the accounting and operational tools: Plan to write it in July<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* CheckIn moving to beta<br />
* Working to support the new LoA levels (from AARC)<br />
* Working to support the EGI FedCloud<br />
* Connectors to Ops Portal to gather information about VOs<br />
* Assessment of the support status of MyProxy in the light of the Globus EOL<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
* Integration with RT almost completed<br />
* Fixed bugs in the Cart<br />
* Integration with the Applications on demand service on-going. Specification: https://docs.google.com/document/d/1fEu3bfHD7CpuH5Uvu7D8K1kBcG_7lb1JyWh0jVG4UGs<br />
* Customer dashboard in PrestaShop<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud accounting:<br />
** New solution for accounting of the long running VMs under testing<br />
* Data accounting:<br />
** Tests with OneData are proceeding. For more details see: https://docs.google.com/document/d/1__vC6nVptyfnvKNnkOHrv_8aR4midG9gXNf4mhwIgR8/edit?usp=sharing<br />
* New release of the portal under testing. New main features:<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Maps to show the graphical distribution of the accounting data in country views: the implementation was too poor. This feature will be removed by this release and included (in a better shape) in the next.<br />
** Discipline account report<br />
** New restricted views<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops Portal: Working on integrating CheckIn and the new messaging. Interface for CheckIn to extract VO information<br />
* GOCDB: new roadmap until the end of the project defined: https://wiki.egi.eu/wiki/TASK_JRA1.4_Operations_Tools#GOCDB<br />
* ARGO: module for probes management under development, new messaging infrastructure under testing<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29)<br />
* D4.10 Final CANFAR integration release (PM30) We're working to an internal deadline of PM29 for submission readiness.<br />
* M4.3 Open Data Platform in the Production (M30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
* EGI FedData/DataHub news<br />
** Documentation being improved after EGI/STFC review within Indigo. <br />
** New homepage created for FedData: https://wiki.egi.eu/wiki/EGI_Federated_Data<br />
** Proposal to present the transition to Beta at July SSB (SDTP being updated)<br />
* Onedata outstanding problems to be addressed by next release:<br />
** small files <br />
** importing existing data<br />
* EOSCpilot demonstrators wanting to incorporate EGI DataHub into their testing: DPHEP, TextCrowd, Photon Neutron science<br />
* Contact made (and being followed up) with Marc Rousseau (ComputeCanada) at Catania - interested in testing OpenData and try joining the EGI DataHub<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
* Cloudkeeper is undergoing the verification process to be included in the CMD<br />
* Work ongoing on the glue2.1 updates for the info provider<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* 4.10 work (TOC this week with Giuliano, Sara)<br />
* initial meeting with ENES about helping their usecase as an EGI-EUDAT usecase, along with regular monthly meetings<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Documentation and administration of 2 sites with GPGPUs (IISAS-GPUCloud and IISAS-Nebula)<br />
* Preparations for Dynamic DNS to move to production<br />
* Viet has warned that they are out of funding for further EGI-Engage work. Has asked Ladislav to contact MV with more details - hasn't happened yet.<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* '''Globus toolkit EOL''', first assessment of the affected middleware<br />
* Reviewed RC-RP OLA in the light of ELIXIR comments<br />
* VO Management (vo.nextgeoss.eu registration)<br />
* VOs SLA reports: bils, extras, and lsgc<br />
* Release of Preview 1.12 and 2.12<br />
* CMD-OS release CMD-OS 1.1<br />
* Partecipation to Fedcloud TF<br />
* Chairing and agenda preparation Operations, and URT meetings<br />
* RC and RP OLA monthly enforcing<br />
* review of the new cloud infoprovider for GLUE2.1 schema<br />
* review of the new release of accounting portal<br />
* Follow-up of the issues with CREAM-CE and ARC-CE nagios probes (solved)<br />
* Follow up the deployment of new nagios probes for EGI FedCloud (occi and appdb)<br />
* Started the review of the training material in the wiki<br />
* EMI repository have been switched off<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* D6.21 EISCAT Portal second version: Sent to external review on the 8th<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* How to engage SMEs for NGIs: https://indico.egi.eu/indico/event/3373/<br />
<br />
Preparation for the following f2f events:<br />
EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Engagement with Nordic countries at NeIC<br />
* Support for BigDataEurope project<br />
* Presentation at MSO4SC project workshop and sending a proposal for engagement<br />
* Meeting with CESSDA director<br />
* Establishing Engagement WG and arranging first meeting (Jun 9)<br />
* Organising Engagement meeting for NILs (Jun 9)<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* EGI Federated Cloud developer from CESNET visited the META-pipe developers in Tromsö, Norway<br />
* Full-scale tests (over 400 cores) of META-pipe started in the local cloud environment of CSC <br />
* The EC project officer approved the effort re-balancing: 2 PM were moved form EBI-EMBL to CNRS and 2 PM to EGI.eu (outside the ELIXIR CC).<br />
* Phenomenal developers are starting to test ELIXIR VO in EGI federated cloud.<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
Dissemination activities:<br />
* Presenting DARIAH Competence centre outcomes and services at the EGI Conference, ''9-12 May 2017, Catania, Italy''<br />
* A pre-conference workshop abstract "''An Open DARIAH-CC - EGI Workshop in conjunction with COST ENeL''" for Digital Humanities 2017 conference submitted (not accepted)<br />
* Workshop on biodiversity and linguistic diversity for scholar from Natural History Museum, Vienna, ''6th June 2017, Vienna''<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
Support to GBIF extended with more Cloud resources.<br />
Development of tools for use of satellite images continued.<br />
Tests of implementation of SDM (MaxEnt) as dockers started.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* D6.21 was finished and sent for external review. Docuemnt is available for commenting at https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-14&diff=95436EGI-Engage:AMB-2017-06-142017-06-14T08:12:50Z<p>Psolagna: /* WP5 (SA1) (Peter Solagna) */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
* gathering of cloud requirements from the Blue Cloud Pilot EC initiative (Brussels 13 June)<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* process reviews - CRM, PM, SLM, SRM, ISRM<br />
* handling deliverables' reviews<br />
* assessing new tool for handling deliverables <br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
* Newsletter:<br />
** Publication of issue 27<br />
** Commissioning issue 28<br />
* EGI Use Cases brochure: <br />
** final content and concept <br />
** finding and briefing a designer<br />
* DI4R 2017:<br />
** first meetings<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype: prototype still under development. Deliverable writing should start next week<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace: Deliverable writing will start next week.<br />
* M30: D3.17 Final release of the accounting and operational tools: Plan to write it in July<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* CheckIn moving to beta<br />
* Working to support the new LoA levels (from AARC)<br />
* Working to support the EGI FedCloud<br />
* Connectors to Ops Portal to gather information about VOs<br />
* Assessment of the support status of MyProxy in the light of the Globus EOL<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
* Integration with RT almost completed<br />
* Fixed bugs in the Cart<br />
* Integration with the Applications on demand service on-going. Specification: https://docs.google.com/document/d/1fEu3bfHD7CpuH5Uvu7D8K1kBcG_7lb1JyWh0jVG4UGs<br />
* Customer dashboard in PrestaShop<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud accounting:<br />
** New solution for accounting of the long running VMs under testing<br />
* Data accounting:<br />
** Tests with OneData are proceeding. For more details see: https://docs.google.com/document/d/1__vC6nVptyfnvKNnkOHrv_8aR4midG9gXNf4mhwIgR8/edit?usp=sharing<br />
* New release of the portal under testing. New main features:<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Maps to show the graphical distribution of the accounting data in country views: the implementation was too poor. This feature will be removed by this release and included (in a better shape) in the next.<br />
** Discipline account report<br />
** New restricted views<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops Portal: Working on integrating CheckIn and the new messaging. Interface for CheckIn to extract VO information<br />
* GOCDB: new roadmap until the end of the project defined: https://wiki.egi.eu/wiki/TASK_JRA1.4_Operations_Tools#GOCDB<br />
* ARGO: module for probes management under development, new messaging infrastructure under testing<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29)<br />
* D4.10 Final CANFAR integration release (PM30) We're working to an internal deadline of PM29 for submission readiness.<br />
* M4.3 Open Data Platform in the Production (M30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
* EGI FedData/DataHub news<br />
** Documentation being improved after EGI/STFC review within Indigo. <br />
** New homepage created for FedData: https://wiki.egi.eu/wiki/EGI_Federated_Data<br />
** Proposal to present the transition to Beta at July SSB (SDTP being updated)<br />
* Onedata outstanding problems to be addressed by next release:<br />
** small files <br />
** importing existing data<br />
* EOSCpilot demonstrators wanting to incorporate EGI DataHub into their testing: DPHEP, TextCrowd, Photon Neutron science<br />
* Contact made (and being followed up) with Marc Rousseau (ComputeCanada) at Catania - interested in testing OpenData and try joining the EGI DataHub<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
* Cloudkeeper is undergoing the verification process to be included in the CMD<br />
* Work ongoing on the glue2.1 updates for the info provider<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* 4.10 work (TOC this week with Giuliano, Sara)<br />
* initial meeting with ENES about helping their usecase as an EGI-EUDAT usecase, along with regular monthly meetings<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Documentation and administration of 2 sites with GPGPUs (IISAS-GPUCloud and IISAS-Nebula)<br />
* Preparations for Dynamic DNS to move to production<br />
* Viet has warned that they are out of funding for further EGI-Engage work. Has asked Ladislav to contact MV with more details - hasn't happened yet.<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* Globus toolkit EOL, first assessment of the affected middleware<br />
* Reviewed RC-RP OLA in the light of ELIXIR comments<br />
* VO Management (vo.nextgeoss.eu registration)<br />
* VOs SLA reports: bils, extras, and lsgc<br />
* Release of Preview 1.12 and 2.12<br />
* CMD-OS release CMD-OS 1.1<br />
* Partecipation to Fedcloud TF<br />
* Chairing and agenda preparation Operations, and URT meetings<br />
* RC and RP OLA monthly enforcing<br />
* review of the new cloud infoprovider for GLUE2.1 schema<br />
* review of the new release of accounting portal<br />
* Follow-up of the issues with CREAM-CE and ARC-CE nagios probes (solved)<br />
* Follow up the deployment of new nagios probes for EGI FedCloud (occi and appdb)<br />
* Started the review of the training material in the wiki<br />
* EMI repository have been switched off<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* D6.21 EISCAT Portal second version: Sent to external review on the 8th<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* How to engage SMEs for NGIs: https://indico.egi.eu/indico/event/3373/<br />
<br />
Preparation for the following f2f events:<br />
EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Engagement with Nordic countries at NeIC<br />
* Support for BigDataEurope project<br />
* Presentation at MSO4SC project workshop and sending a proposal for engagement<br />
* Meeting with CESSDA director<br />
* Establishing Engagement WG and arranging first meeting (Jun 9)<br />
* Organising Engagement meeting for NILs (Jun 9)<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* EGI Federated Cloud developer from CESNET visited the META-pipe developers in Tromsö, Norway<br />
* Full-scale tests (over 400 cores) of META-pipe started in the local cloud environment of CSC <br />
* The EC project officer approved the effort re-balancing: 2 PM were moved form EBI-EMBL to CNRS and 2 PM to EGI.eu (outside the ELIXIR CC).<br />
* Phenomenal developers are starting to test ELIXIR VO in EGI federated cloud.<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
Dissemination activities:<br />
* Presenting DARIAH Competence centre outcomes and services at the EGI Conference, ''9-12 May 2017, Catania, Italy''<br />
* A pre-conference workshop abstract "''An Open DARIAH-CC - EGI Workshop in conjunction with COST ENeL''" for Digital Humanities 2017 conference submitted (not accepted)<br />
* Workshop on biodiversity and linguistic diversity for scholar from Natural History Museum, Vienna, ''6th June 2017, Vienna''<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
Support to GBIF extended with more Cloud resources.<br />
Development of tools for use of satellite images continued.<br />
Tests of implementation of SDM (MaxEnt) as dockers started.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* D6.21 was finished and sent for external review. Docuemnt is available for commenting at https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-06-14&diff=95432EGI-Engage:AMB-2017-06-142017-06-14T07:54:14Z<p>Psolagna: /* Task JRA1.1 Authentication and Authorisation Infrastructure */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
=== Task NA1.2 Technical Management ===<br />
* gathering of cloud requirements from the Blue Cloud Pilot EC initiative<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
* process reviews - CRM, PM, SLM, SRM, ISRM<br />
* handling deliverables' reviews<br />
* assessing new tool for handling deliverables <br />
<br><br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* M28: D3.15 Second Data Accounting prototype: prototype still under development. Deliverable writing should start next week<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace: Deliverable writing will start next week.<br />
* M30: D3.17 Final release of the accounting and operational tools: Plan to write it in July<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* CheckIn moving to beta<br />
* Working to support the new LoA levels (from AARC)<br />
* Working to support the EGI FedCloud<br />
* Connectors to Ops Portal to gather information about VOs<br />
* Assessment of the support status of MyProxy in the light of the Globus EOL<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
* Integration with RT almost completed<br />
* Fixed bugs in the Cart<br />
* Integration with the Applications on demand service on-going. Specification: https://docs.google.com/document/d/1fEu3bfHD7CpuH5Uvu7D8K1kBcG_7lb1JyWh0jVG4UGs<br />
* Customer dashboard in PrestaShop<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud accounting:<br />
** New solution for accounting of the long running VMs under testing<br />
* Data accounting:<br />
** Tests with OneData are proceeding. For more details see: https://docs.google.com/document/d/1__vC6nVptyfnvKNnkOHrv_8aR4midG9gXNf4mhwIgR8/edit?usp=sharing<br />
* New release of the portal under testing. New main features:<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Maps to show the graphical distribution of the accounting data in country views: the implementation was too poor. This feature will be removed by this release and included (in a better shape) in the next.<br />
** Discipline account report<br />
** New restricted views<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops Portal: Working on integrating CheckIn and the new messaging. Interface for CheckIn to extract VO information<br />
* GOCDB: new roadmap until the end of the project defined: https://wiki.egi.eu/wiki/TASK_JRA1.4_Operations_Tools#GOCDB<br />
* ARGO: module for probes management under development, new messaging infrastructure under testing<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29)<br />
* D4.10 Final CANFAR integration release (PM30) We're working to an internal deadline of PM29 for submission readiness.<br />
* M4.3 Open Data Platform in the Production (M30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
* EGI FedData/DataHub news<br />
** Documentation being improved after EGI/STFC review within Indigo. <br />
** New homepage created for FedData: https://wiki.egi.eu/wiki/EGI_Federated_Data<br />
** Proposal to present the transition to Beta at July SSB (SDTP being updated)<br />
* Onedata outstanding problems to be addressed by next release:<br />
** small files <br />
** importing existing data<br />
* EOSCpilot demonstrators wanting to incorporate EGI DataHub into their testing: DPHEP, TextCrowd, Photon Neutron science<br />
* Contact made (and being followed up) with Marc Rousseau (ComputeCanada) at Catania - interested in testing OpenData and try joining the EGI DataHub<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
* Cloudkeeper is undergoing the verification process to be included in the CMD<br />
* Work ongoing on the glue2.1 updates for the info provider<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* 4.10 work (TOC this week with Giuliano, Sara)<br />
* initial meeting with ENES about helping their usecase as an EGI-EUDAT usecase, along with regular monthly meetings<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Documentation and administration of 2 sites with GPGPUs<br />
* Preparations for Dynamic DNS to move to production<br />
* Viet has warned that they are out of funding for further EGI-Engage work. Has asked Ladislav to contact MV with more details - hasn't happened yet.<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
* D6.21 EISCAT Portal second version: Sent to external review on the 8th<br />
<br />
=== Task SA2.1 Training ===<br />
Delivered a webinar:<br />
* How to engage SMEs for NGIs: https://indico.egi.eu/indico/event/3373/<br />
<br />
Preparation for the following f2f events:<br />
EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017 (EGI training infrastructure provided to support the school)<br />
<br />
Preparation for the following webinar events:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs): https://indico.egi.eu/indico/event/3378/<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRAC staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Engagement with Nordic countries at NeIC<br />
* Support for BigDataEurope project<br />
* Presentation at MSO4SC project workshop and sending a proposal for engagement<br />
* Meeting with CESSDA director<br />
* Establishing Engagement WG and arranging first meeting (Jun 9)<br />
* Organising Engagement meeting for NILs (Jun 9)<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
* EGI Federated Cloud developer from CESNET visited the META-pipe developers in Tromsö, Norway<br />
* Full-scale tests (over 400 cores) of META-pipe started in the local cloud environment of CSC <br />
* The EC project officer approved the effort re-balancing: 2 PM were moved form EBI-EMBL to CNRS and 2 PM to EGI.eu (outside the ELIXIR CC).<br />
* Phenomenal developers are starting to test ELIXIR VO in EGI federated cloud.<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
Dissemination events:<br />
<br />
* ''Molecular dynamics of proteins in the cloud''. Data Management Services in the Cloud (co-located at the Ninth RDA Plenary), Barcelona, Spain, April 4, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. ELIXIR workshop on “Computational Approaches to the Study of Protein Interaction and Drug Design”, Padova, Italy, April 10-14, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Understanding Protein Interactions: From Molecules to Organisms. Lyon, France, April 24-26, 2017<br />
<br />
* ''High-resolution, integrative modelling of biomolecular complexes from fuzzy data''. Meeting of the groupe de graphisme et modélisation moléculaire (GGMM). Rheims, France, May 9-11, 2017<br />
<br />
* ''MoBrain - A competence center to serve translational research from molecule to brain'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''DisVis and PowerFit: Explorative and Integrative Modeling of Biomolecular Complexes harvesting EGI GPGPU resources'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''ScipionCloud: Large scale cryo electron microscopy image processing on commercial and academic clouds'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''GPGPU computing support on HTC'', EGI Conference 2017, Catania, Italy, May 9-12, 2017<br />
<br />
* ''HADDOCK workshop in information-driven modelling of biomolecular complexes''. KAUST, Saudi Arabia, May 24-25, 2017<br />
<br />
=== Task SA2.6 DARIAH ===<br />
Dissemination activities:<br />
* Presenting DARIAH Competence centre outcomes and services at the EGI Conference, ''9-12 May 2017, Catania, Italy''<br />
* A pre-conference workshop abstract "''An Open DARIAH-CC - EGI Workshop in conjunction with COST ENeL''" for Digital Humanities 2017 conference submitted (not accepted)<br />
* Workshop on biodiversity and linguistic diversity for scholar from Natural History Museum, Vienna, ''6th June 2017, Vienna''<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
Support to GBIF extended with more Cloud resources.<br />
Development of tools for use of satellite images continued.<br />
Tests of implementation of SDM (MaxEnt) as dockers started.<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
* D6.21 was finished and sent for external review. Docuemnt is available for commenting at https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI/edit#<br />
* EISCAT_3D construction received green light and funding last week.(total cost of 685 million Swedish crowns, distributed across three sites, project will start in September 2017 with site preparations to begin in summer 2018. The radar is expected to be operational in 2021.)<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
* Started working on D6.22 (Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment)<br />
<br />
[[Category:EGI-Engage]]</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI_Change_Management&diff=95415EGI Change Management2017-06-13T14:01:33Z<p>Psolagna: /* Services that fall under Change Control */</p>
<hr />
<div>= The EGI&nbsp;Change Management (CHM)&nbsp;Process Introduction<br> =<br />
<br />
This is the homepage on the EGI&nbsp;Wiki of the EGI&nbsp;Change Management Process.&nbsp; <br><br />
<br />
Ensuring effective change management within the EGI’s production IT environment is extremely important in ensuring high-quality delivery of IT services.<br />
<br />
The purpose of the IT Change Management Policy is to manage changes in a planned and predictable manner in order to assess risks, assign resources, and minimize any potential negative impact to services. This is done by requiring change owners to prepare a Request for Change ([[File:Request+for+change+template.doc]]) where a set of standard questions regarding the change are answered and presented to the Change Advisory Board (CAB). <br />
<br />
The CAB meets to assess and approve changes and is coordinated on the '''egi-cab@mailman.egi.eu''' mailing list. It consists of employees of the EGI Foundation including the Technical Director and members of the senior operations and management team. Currently the chair of the CAB is Matthew Viljoen. Other members include: Tiziana Ferrari, Vincenzo Spinoso, Alessandro Paolini, Diego Scardacci, Peter Solagna and Gergely Sipos. Others may be invited to join to provide additional expertise when discussing specific changes.<br />
<br />
Changes are tracked as [https://rt.egi.eu/rt/index.html RT] tickets on the '''change-mgmnt''' queue, while people can submit a completed RfC ([[File:Request+for+change+template.doc]]) to: '''change-mgmnt@rt.egi.eu'''. The change risk (likelihood X impact) should then be evaluated by the Service Owner and recorded as custom fields on the ticket in preparation for the CAB review. Further details about evaluating risk may be found here: [[File:IMS-RMGuideline-060117-1020-4791.pdf]].<br />
<br />
Click https://documents.egi.eu/public/ShowDocument?docid=2944 for a presentation introducing the process.<br />
<br />
== Services that fall under Change Control == <br />
<br />
{| width="776" cellspacing="1" cellpadding="1" border="1" height="78"<br />
|-<br />
| '''Service Title<br>'''<br />
| '''Person(s) Managing the Service'''<br><br />
|-<br />
| EGI DataHub<br><br />
| Lukasz Dutka, Barosz Kryza<br><br />
|-<br />
| EGI AppDB<br><br />
| Marios Chatziangelou<br><br />
|-<br />
| Operations Portal<br><br />
| Cyril L'Orphelin<br><br />
|-<br />
| Service Monitoring - ARGO<br><br />
| Kostas Koumantaros<br><br />
|-<br />
| Configuration Database - GOCDB<br><br />
| David Meredith<br><br />
|-<br />
| Helpdesk - GGUS<br><br />
| Guenter Grein, Helmut Dres<br><br />
|-<br />
| Accounting - Accounting repository (Computing and Grid)<br><br />
| Adrian Coveney<br><br />
|-<br />
| Accounting - Accounting Portal<br><br />
| Iván Díaz Álvarez<br><br />
|-<br />
| Messaging<br><br />
| Christos Kanellopoulos<br><br />
|-<br />
| Training Infrastructure<br><br />
| Gergely Sipos<br><br />
|-<br />
|CheckIn<br><br />
|Nicolas Liampotis<br><br />
|}<br />
<br />
== Standard Changes ==<br />
<br />
This is the list of standard, or pre-approved changes, listed by Service.<br><br />
<br />
=== Helpdesk - GGUS ===<br />
<br />
{| width="776" cellspacing="1" cellpadding="1" border="1" height="78"<br />
|-<br />
| '''Title<br>'''<br />
| '''Description'''<br><br />
| '''RT&nbsp;Ticket Reference'''<br><br />
|-<br />
| Install patches on GGUS servers<br><br />
| The installation of patches is required on all GGUS servers for keeping the system secure.<br><br />
| [https://rt.egi.eu/rt/Ticket/Display.html?id=12262 RT#12262]<br><br />
|}<br />
<br />
== Software Development changes ==<br />
<br />
Most changes that fall under the scope of CHM will likely be to production service delivery (e.g. upgrades, major hardware changes etc). However, changes may also be in the form of software development to production services. For example, if a user community requests new functionality from developers that requires 2 months of development effort, there may be a risk of insufficient funded effort, or reduced manpower elsewhere in the project. This can especially be the case if such development is unforeseen at the beginning of a project. In such cases, persons managing services are encouraged to bring such changes to the CAB for discussion, approval and (where appropriate) appropriation of development effort.<br />
<br />
== Full Procedure Documentation ==<br />
<br />
CHM procedure documentation is available on the EGI Confluence. These pages are only accessible to EGI Employees, so PDF versions of these pages are additionally available here:<br><br />
[[File:IMS-Changemanagementpolicy-060117-1500-4793.pdf]]<br/><br />
[[File:IMS-CHM1Managechangesincludingemergencychanges-060117-1500-4795.pdf]]<br/><br />
[[File:IMS-CHM2Maintainthelist,descriptionsandstep-by-stepworkflowsforwell-knownandrecurringchanges-060117-1500-4797.pdf]]<br/></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Policies_and_Procedures&diff=94901Policies and Procedures2017-05-18T16:58:14Z<p>Psolagna: </p>
<hr />
<div>= Policies = <br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
! scope="col" | Relevant agreements <ref> This column links the policies to the main agreement types in the EGI Infrastructure. This information is provided for the convenience of the parties participating to a new agreement (e.g. a new Resource Centre accepting the RC OLA) to focus on the most important policies for the agreement being signed. Given the diverse nature of the EGI Infrastructure services the suggested policies may not be sufficient or not applicable to a specific party. <br />
<br />
The agreements are:<br />
*RC OLA: Resource Centre OLA<br />
*RP OLA: Resource infrastructure Provider OLA<br />
*VO OLA: Virtual Organisation OLA<br />
*VO SLA: Virtual Organisation SLA<br />
*UA: Underpinning agreement </ref><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/3015 EGI Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/1475 Service Operations Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/77 VO Operations Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/78 Virtual Organisation Registration Security Policy]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/79 Virtual Organisation Membership Management Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2932 Portal Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2934 Traceability and Logging Policy]<br />
| Infrastructure / Technology Providers / Users<br />
| RC OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2935 Security Incident Response Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2933 Policy on e-Infrastructure Multi-User Pilot Jobs]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2732 Policy on the Processing of Personal Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/85 Grid Policy on the Handling of User-Level Job Accounting Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/71 Security Policy Glossary of Terms]<br />
| Infrastructure / Users<br />
| <br><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2930 Acceptable Authentication Assurance]<br />
| Infrastructure<br />
| RC OLA, RP OLA, VO OLA, VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2729 Security Policy for the Endorsement and Operation of Virtual Machine Images]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|}<br />
<br />
= Procedures = <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
|-<br />
| SVG<br />
| [https://documents.egi.eu/document/2538 EGI Software Vulnerability Issue Handling Procedure]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| CSIRT<br />
| [https://documents.egi.eu/document/710 Security Incident Handling procedure]<br />
| Infrastructure<br />
|-<br />
| CSIRT<br />
| [https://wiki.egi.eu/wiki/SEC03 Critical Vulnerability Operational Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC01 COD escalation procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC02 Operations Centre creation]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC03 Operations Centre decommission process coordination]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC04 Follow up of availability and reliability statistics - Process for quality verification]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC05 Validation of a ROC/NGI Nagios]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC06 Setting a Nagios test status to Operations]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC08 Management of the EGI OPS Availability and Reliability Profile]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC07 Adding new probes to SAM]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC17 Decommissioning of Service Type Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC10 Procedure for the recomputation of SAM results and availability/reliability]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC11 Resource Centre Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC12 Production Service Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC13 VO deregistration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC14 VO registration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC15 Procedure for renaming a Resource Center]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC16 Procedure for decommissioning of unsupported software]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| UCB<br />
| [https://documents.egi.eu/document/253 Virtual Research Community accreditation]<br />
| Users<br />
|-<br />
| TCB<br />
| [https://documents.egi.eu/document/440 TCB Requirements management process]<br />
| Infrastructure / Technology Providers<br />
|}<br />
<br />
<br />
<br />
<references /></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Policies_and_Procedures&diff=94900Policies and Procedures2017-05-18T16:57:48Z<p>Psolagna: /* Policies */</p>
<hr />
<div>= Policies = <br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
! scope="col" | Relevant agreements <ref> This column links the policies to the main agreement types in the EGI Infrastructure. This information is provided for the convenience of the parties participating to a new agreement (e.g. a new Resource Centre accepting the RC OLA) to focus on the most important policies for the agreement being signed. Given the diverse nature of the EGI Infrastructure services the suggested policies may not be sufficient or not applicable to a specific party. <br />
<br />
The agreements are:<br />
*RC OLA: Resource Centre OLA<br />
*RP OLA: Resource infrastructure Provider OLA<br />
*VO OLA: Virtual Organisation OLA<br />
*VO SLA: Virtual Organisation SLA<br />
*UA: Underpinning agreement </ref><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/3015 EGI Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/1475 Service Operations Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/77 VO Operations Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/78 Virtual Organisation Registration Security Policy]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/79 Virtual Organisation Membership Management Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2932 Portal Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2934 Traceability and Logging Policy]<br />
| Infrastructure / Technology Providers / Users<br />
| RC OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2935 Security Incident Response Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2933 Policy on e-Infrastructure Multi-User Pilot Jobs]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2732 Policy on the Processing of Personal Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/85 Grid Policy on the Handling of User-Level Job Accounting Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/71 Security Policy Glossary of Terms]<br />
| Infrastructure / Users<br />
| <br><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2930 Acceptable Authentication Assurance]<br />
| Infrastructure<br />
| RC OLA, RP OLA, VO OLA, VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2729 Security Policy for the Endorsement and Operation of Virtual Machine Images]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|}<br />
<br />
= Procedures = <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
|-<br />
| SVG<br />
| [https://documents.egi.eu/document/2538 EGI Software Vulnerability Issue Handling Procedure]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| CSIRT<br />
| [https://documents.egi.eu/document/710 Security Incident Handling procedure]<br />
| Infrastructure<br />
|-<br />
| CSIRT<br />
| [https://wiki.egi.eu/wiki/SEC03 Critical Vulnerability Operational Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC01 COD escalation procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC02 Operations Centre creation]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC03 Operations Centre decommission process coordination]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC04 Follow up of availability and reliability statistics - Process for quality verification]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC05 Validation of a ROC/NGI Nagios]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC06 Setting a Nagios test status to Operations]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC08 Management of the EGI OPS Availability and Reliability Profile]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC07 Adding new probes to SAM]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC17 Decommissioning of Service Type Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC10 Procedure for the recomputation of SAM results and availability/reliability]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC11 Resource Centre Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC12 Production Service Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC13 VO deregistration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC14 VO registration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC15 Procedure for renaming a Resource Center]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC16 Procedure for decommissioning of unsupported software]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| UCB<br />
| [https://documents.egi.eu/document/253 Virtual Research Community accreditation]<br />
| Users<br />
|-<br />
| TCB<br />
| [https://documents.egi.eu/document/440 TCB Requirements management process]<br />
| Infrastructure / Technology Providers<br />
|}<br />
<br />
<references /></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Policies_and_Procedures&diff=94898Policies and Procedures2017-05-18T16:56:30Z<p>Psolagna: /* Policies */</p>
<hr />
<div>= Policies = <br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
! scope="col" | Relevant agreements <ref> This column links the policies to the main agreement types in the EGI Infrastructure. This information is provided for the convenience of the parties participating to a new agreement (e.g. a new Resource Centre accepting the RC OLA) to focus on the most important policies for the agreement being signed. Given the diverse nature of the EGI Infrastructure services the suggested policies may not be sufficient or not applicable to a specific party. </ref><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/3015 EGI Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/1475 Service Operations Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/77 VO Operations Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/78 Virtual Organisation Registration Security Policy]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/79 Virtual Organisation Membership Management Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2932 Portal Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2934 Traceability and Logging Policy]<br />
| Infrastructure / Technology Providers / Users<br />
| RC OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2935 Security Incident Response Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2933 Policy on e-Infrastructure Multi-User Pilot Jobs]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2732 Policy on the Processing of Personal Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/85 Grid Policy on the Handling of User-Level Job Accounting Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/71 Security Policy Glossary of Terms]<br />
| Infrastructure / Users<br />
| <br><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2930 Acceptable Authentication Assurance]<br />
| Infrastructure<br />
| RC OLA, RP OLA, VO OLA, VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2729 Security Policy for the Endorsement and Operation of Virtual Machine Images]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|}<br />
<br />
= Procedures = <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
|-<br />
| SVG<br />
| [https://documents.egi.eu/document/2538 EGI Software Vulnerability Issue Handling Procedure]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| CSIRT<br />
| [https://documents.egi.eu/document/710 Security Incident Handling procedure]<br />
| Infrastructure<br />
|-<br />
| CSIRT<br />
| [https://wiki.egi.eu/wiki/SEC03 Critical Vulnerability Operational Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC01 COD escalation procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC02 Operations Centre creation]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC03 Operations Centre decommission process coordination]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC04 Follow up of availability and reliability statistics - Process for quality verification]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC05 Validation of a ROC/NGI Nagios]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC06 Setting a Nagios test status to Operations]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC08 Management of the EGI OPS Availability and Reliability Profile]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC07 Adding new probes to SAM]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC17 Decommissioning of Service Type Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC10 Procedure for the recomputation of SAM results and availability/reliability]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC11 Resource Centre Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC12 Production Service Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC13 VO deregistration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC14 VO registration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC15 Procedure for renaming a Resource Center]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC16 Procedure for decommissioning of unsupported software]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| UCB<br />
| [https://documents.egi.eu/document/253 Virtual Research Community accreditation]<br />
| Users<br />
|-<br />
| TCB<br />
| [https://documents.egi.eu/document/440 TCB Requirements management process]<br />
| Infrastructure / Technology Providers<br />
|}<br />
<br />
<references /></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Policies_and_Procedures&diff=94897Policies and Procedures2017-05-18T16:55:48Z<p>Psolagna: </p>
<hr />
<div>= Policies = <br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
! scope="col" | Relevant agreements <ref> This column links the policies to the most important agreement types in the EGI Infrastructure. This information is provided for the convenience of the parties participating to a new agreement (e.g. a new Resource Centre accepting the RC OLA) to focus on the most important policies for the agreement being signed. Given the diverse nature of the EGI Infrastructure services the suggested policies may not be sufficient or not applicable to a specific party. </ref><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/3015 EGI Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/1475 Service Operations Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/77 VO Operations Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/78 Virtual Organisation Registration Security Policy]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/79 Virtual Organisation Membership Management Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2932 Portal Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2934 Traceability and Logging Policy]<br />
| Infrastructure / Technology Providers / Users<br />
| RC OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2935 Security Incident Response Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2933 Policy on e-Infrastructure Multi-User Pilot Jobs]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2732 Policy on the Processing of Personal Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/85 Grid Policy on the Handling of User-Level Job Accounting Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/71 Security Policy Glossary of Terms]<br />
| Infrastructure / Users<br />
| <br><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2930 Acceptable Authentication Assurance]<br />
| Infrastructure<br />
| RC OLA, RP OLA, VO OLA, VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2729 Security Policy for the Endorsement and Operation of Virtual Machine Images]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|}<br />
<br />
= Procedures = <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
|-<br />
| SVG<br />
| [https://documents.egi.eu/document/2538 EGI Software Vulnerability Issue Handling Procedure]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| CSIRT<br />
| [https://documents.egi.eu/document/710 Security Incident Handling procedure]<br />
| Infrastructure<br />
|-<br />
| CSIRT<br />
| [https://wiki.egi.eu/wiki/SEC03 Critical Vulnerability Operational Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC01 COD escalation procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC02 Operations Centre creation]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC03 Operations Centre decommission process coordination]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC04 Follow up of availability and reliability statistics - Process for quality verification]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC05 Validation of a ROC/NGI Nagios]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC06 Setting a Nagios test status to Operations]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC08 Management of the EGI OPS Availability and Reliability Profile]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC07 Adding new probes to SAM]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC17 Decommissioning of Service Type Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC10 Procedure for the recomputation of SAM results and availability/reliability]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC11 Resource Centre Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC12 Production Service Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC13 VO deregistration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC14 VO registration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC15 Procedure for renaming a Resource Center]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC16 Procedure for decommissioning of unsupported software]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| UCB<br />
| [https://documents.egi.eu/document/253 Virtual Research Community accreditation]<br />
| Users<br />
|-<br />
| TCB<br />
| [https://documents.egi.eu/document/440 TCB Requirements management process]<br />
| Infrastructure / Technology Providers<br />
|}<br />
<br />
<references /></div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Policies_and_Procedures&diff=94894Policies and Procedures2017-05-18T16:49:35Z<p>Psolagna: /* Policies */</p>
<hr />
<div>= Policies = <br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
! scope="col" | Relevant agreements <ref> This column links the policies to the most important agreement types in the EGI Infrastructure. This information is provided for the convenience of the parties participating to a new agreement (e.g. a new Resource Centre accepting the RC OLA) to focus on the most important policies for the agreement being signed. Given the diverse nature of the EGI Infrastructure services the suggested policies may not be sufficient or not applicable to a specific party. </ref><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/3015 EGI Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/1475 Service Operations Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/77 VO Operations Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/78 Virtual Organisation Registration Security Policy]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/79 Virtual Organisation Membership Management Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2932 Portal Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2934 Traceability and Logging Policy]<br />
| Infrastructure / Technology Providers / Users<br />
| RC OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2935 Security Incident Response Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2933 Policy on e-Infrastructure Multi-User Pilot Jobs]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2732 Policy on the Processing of Personal Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/85 Grid Policy on the Handling of User-Level Job Accounting Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/71 Security Policy Glossary of Terms]<br />
| Infrastructure / Users<br />
| <br><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2930 Acceptable Authentication Assurance]<br />
| Infrastructure<br />
| RC OLA, RP OLA, VO OLA, VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2729 Security Policy for the Endorsement and Operation of Virtual Machine Images]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|}<br />
<br />
= Procedures = <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
|-<br />
| SVG<br />
| [https://documents.egi.eu/document/2538 EGI Software Vulnerability Issue Handling Procedure]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| CSIRT<br />
| [https://documents.egi.eu/document/710 Security Incident Handling procedure]<br />
| Infrastructure<br />
|-<br />
| CSIRT<br />
| [https://wiki.egi.eu/wiki/SEC03 Critical Vulnerability Operational Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC01 COD escalation procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC02 Operations Centre creation]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC03 Operations Centre decommission process coordination]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC04 Follow up of availability and reliability statistics - Process for quality verification]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC05 Validation of a ROC/NGI Nagios]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC06 Setting a Nagios test status to Operations]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC08 Management of the EGI OPS Availability and Reliability Profile]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC07 Adding new probes to SAM]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC17 Decommissioning of Service Type Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC10 Procedure for the recomputation of SAM results and availability/reliability]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC11 Resource Centre Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC12 Production Service Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC13 VO deregistration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC14 VO registration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC15 Procedure for renaming a Resource Center]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC16 Procedure for decommissioning of unsupported software]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| UCB<br />
| [https://documents.egi.eu/document/253 Virtual Research Community accreditation]<br />
| Users<br />
|-<br />
| TCB<br />
| [https://documents.egi.eu/document/440 TCB Requirements management process]<br />
| Infrastructure / Technology Providers<br />
|}</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Policies_and_Procedures&diff=94893Policies and Procedures2017-05-18T16:48:40Z<p>Psolagna: /* Policies */</p>
<hr />
<div>= Policies = <br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
! scope="col" | Relevant agreements <ref> This column links the policies to the most important agreement types in the EGI Infrastructure. This information is provided for the convenience of the parties participating to a new agreement (e.g. a new Resource Centre accepting the RC OLA) to focus on the most important policies for the agreement being signed. Given the diverse nature of the EGI Infrastructure services the suggested policies may not be sufficient or not applicable to a specific party. </ref><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/3015 EGI Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/1475 Service Operations Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/77 VO Operations Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/78 Virtual Organisation Registration Security Policy]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/79 Virtual Organisation Membership Management Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2932 Portal Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2934 Traceability and Logging Policy]<br />
| Infrastructure / Technology Providers / Users<br />
| RC OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2935 Security Incident Response Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2933 Policy on e-Infrastructure Multi-User Pilot Jobs]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2732 Policy on the Processing of Personal Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/85 Grid Policy on the Handling of User-Level Job Accounting Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/71 Security Policy Glossary of Terms]<br />
| Infrastructure / Users<br />
| <br><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2930 Acceptable Authentication Assurance]<br />
| Infrastructure<br />
| RC OLA, RP OLA, VO OLA, VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2729 Security Policy for the Endorsement and Operation of Virtual Machine Images]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|}<br />
{{reflist}}<br />
<br />
= Procedures = <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
|-<br />
| SVG<br />
| [https://documents.egi.eu/document/2538 EGI Software Vulnerability Issue Handling Procedure]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| CSIRT<br />
| [https://documents.egi.eu/document/710 Security Incident Handling procedure]<br />
| Infrastructure<br />
|-<br />
| CSIRT<br />
| [https://wiki.egi.eu/wiki/SEC03 Critical Vulnerability Operational Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC01 COD escalation procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC02 Operations Centre creation]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC03 Operations Centre decommission process coordination]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC04 Follow up of availability and reliability statistics - Process for quality verification]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC05 Validation of a ROC/NGI Nagios]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC06 Setting a Nagios test status to Operations]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC08 Management of the EGI OPS Availability and Reliability Profile]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC07 Adding new probes to SAM]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC17 Decommissioning of Service Type Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC10 Procedure for the recomputation of SAM results and availability/reliability]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC11 Resource Centre Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC12 Production Service Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC13 VO deregistration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC14 VO registration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC15 Procedure for renaming a Resource Center]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC16 Procedure for decommissioning of unsupported software]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| UCB<br />
| [https://documents.egi.eu/document/253 Virtual Research Community accreditation]<br />
| Users<br />
|-<br />
| TCB<br />
| [https://documents.egi.eu/document/440 TCB Requirements management process]<br />
| Infrastructure / Technology Providers<br />
|}</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Policies_and_Procedures&diff=94892Policies and Procedures2017-05-18T16:43:35Z<p>Psolagna: /* Policies */</p>
<hr />
<div>= Policies = <br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
! scope="col" | Relevant agreements <ref> This column links the policies to the most important agreement types in the EGI Infrastructure. This information is provided for the convenience of the parties participating to a new agreement (e.g. a new Resource Centre accepting the RC OLA) to focus on the most important policies for the agreement being signed. Given the diverse nature of the EGI Infrastructure services the suggested policies may not be sufficient or not applicable to a specific party. </ref><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/3015 EGI Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/1475 Service Operations Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/77 VO Operations Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/78 Virtual Organisation Registration Security Policy]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/79 Virtual Organisation Membership Management Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2932 Portal Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2934 Traceability and Logging Policy]<br />
| Infrastructure / Technology Providers / Users<br />
| RC OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2935 Security Incident Response Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2933 Policy on e-Infrastructure Multi-User Pilot Jobs]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2732 Policy on the Processing of Personal Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/85 Grid Policy on the Handling of User-Level Job Accounting Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/71 Security Policy Glossary of Terms]<br />
| Infrastructure / Users<br />
| <br><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2930 Acceptable Authentication Assurance]<br />
| Infrastructure<br />
| RC OLA, RP OLA, VO OLA, VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2729 Security Policy for the Endorsement and Operation of Virtual Machine Images]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|}<br />
<br />
= Procedures = <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
|-<br />
| SVG<br />
| [https://documents.egi.eu/document/2538 EGI Software Vulnerability Issue Handling Procedure]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| CSIRT<br />
| [https://documents.egi.eu/document/710 Security Incident Handling procedure]<br />
| Infrastructure<br />
|-<br />
| CSIRT<br />
| [https://wiki.egi.eu/wiki/SEC03 Critical Vulnerability Operational Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC01 COD escalation procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC02 Operations Centre creation]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC03 Operations Centre decommission process coordination]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC04 Follow up of availability and reliability statistics - Process for quality verification]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC05 Validation of a ROC/NGI Nagios]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC06 Setting a Nagios test status to Operations]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC08 Management of the EGI OPS Availability and Reliability Profile]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC07 Adding new probes to SAM]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC17 Decommissioning of Service Type Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC10 Procedure for the recomputation of SAM results and availability/reliability]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC11 Resource Centre Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC12 Production Service Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC13 VO deregistration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC14 VO registration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC15 Procedure for renaming a Resource Center]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC16 Procedure for decommissioning of unsupported software]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| UCB<br />
| [https://documents.egi.eu/document/253 Virtual Research Community accreditation]<br />
| Users<br />
|-<br />
| TCB<br />
| [https://documents.egi.eu/document/440 TCB Requirements management process]<br />
| Infrastructure / Technology Providers<br />
|}</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=Policies_and_Procedures&diff=94890Policies and Procedures2017-05-18T16:30:38Z<p>Psolagna: /* Policies */</p>
<hr />
<div>= Policies = <br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
! scope="col" | Relevant agreements<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/3015 EGI Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/1475 Service Operations Security Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/77 VO Operations Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/78 Virtual Organisation Registration Security Policy]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/79 Virtual Organisation Membership Management Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2932 Portal Policy]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2934 Traceability and Logging Policy]<br />
| Infrastructure / Technology Providers / Users<br />
| RC OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2935 Security Incident Response Policy]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA, VO SLA, UA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2933 Policy on e-Infrastructure Multi-User Pilot Jobs]<br />
| Users<br />
| VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2732 Policy on the Processing of Personal Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA, VO OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/85 Grid Policy on the Handling of User-Level Job Accounting Data]<br />
| Infrastructure / Users<br />
| RC OLA, RP OLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/71 Security Policy Glossary of Terms]<br />
| Infrastructure / Users<br />
| <br><br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2930 Acceptable Authentication Assurance]<br />
| Infrastructure<br />
| RC OLA, RP OLA, VO OLA, VO SLA<br />
|-<br />
| SPG<br />
| [https://documents.egi.eu/document/2729 Security Policy for the Endorsement and Operation of Virtual Machine Images]<br />
| Infrastructure / Users<br />
| VO SLA<br />
|}<br />
<br />
= Procedures = <br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%" align="center" class="wikitable sortable"<br />
|-<br />
! scope="col" | Policy group<br />
! scope="col" | Title<br />
! scope="col" | Applies to<br />
|-<br />
| SVG<br />
| [https://documents.egi.eu/document/2538 EGI Software Vulnerability Issue Handling Procedure]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| CSIRT<br />
| [https://documents.egi.eu/document/710 Security Incident Handling procedure]<br />
| Infrastructure<br />
|-<br />
| CSIRT<br />
| [https://wiki.egi.eu/wiki/SEC03 Critical Vulnerability Operational Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC01 COD escalation procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC02 Operations Centre creation]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC03 Operations Centre decommission process coordination]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC04 Follow up of availability and reliability statistics - Process for quality verification]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC05 Validation of a ROC/NGI Nagios]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC06 Setting a Nagios test status to Operations]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC08 Management of the EGI OPS Availability and Reliability Profile]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC07 Adding new probes to SAM]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC09 Resource Centre Registration and Certification Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC17 Decommissioning of Service Type Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC10 Procedure for the recomputation of SAM results and availability/reliability]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC11 Resource Centre Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC12 Production Service Decommissioning Procedure]<br />
| Infrastructure<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC13 VO deregistration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC14 VO registration procedure]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC15 Procedure for renaming a Resource Center]<br />
| Infrastructure / Users<br />
|-<br />
| OMB<br />
| [https://wiki.egi.eu/wiki/PROC16 Procedure for decommissioning of unsupported software]<br />
| Infrastructure / Technology Providers / Users<br />
|-<br />
| UCB<br />
| [https://documents.egi.eu/document/253 Virtual Research Community accreditation]<br />
| Users<br />
|-<br />
| TCB<br />
| [https://documents.egi.eu/document/440 TCB Requirements management process]<br />
| Infrastructure / Technology Providers<br />
|}</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=AAI_usage_guide&diff=94887AAI usage guide2017-05-18T14:00:49Z<p>Psolagna: /* Signing Up for an EGI Account */</p>
<hr />
<div>{{TOC_right}} <br />
<br />
= Overview =<br />
<br />
This wiki page contains information about registering an account with the [[AAI|EGI AAI]] in order to access a variety of EGI tools and services using the same account.<br />
<br />
This process is not about creating yet another (username/password) credential but to link user's existing credential (for example using an eduGAIN IdP) with EGI.<br />
<br />
= Signing Up for an EGI Account =<br />
<br />
To access EGI resources, you need to sign up for an account. As part of this process you will be assigned a personal '''EGI ID''', which will then be used across all EGI tools and services. To register your account, follow the instructions below: <br />
<br />
{|<br />
|- style="vertical-align:top;"<br />
!1. <br />
|Enter the following URL in a browser: https://aai.egi.eu/signup <br />
|[[Image:AAI signup url.png|thumb|250px]]<br />
|- style="vertical-align:top;"<br />
!2.<br />
|Select your Identity Provider from the discovery page: <br />
* browse through the list of Identity Providers to find your Home Organisation; <br />
*: ''or, alternatively,'' <br />
*type the name of your Home Organisation in the search box. Note that this filter only matches entries within the currently selected view (tab) of Identity Providers and is localised based on the selected language.<br />
|[[Image:AAI IdP discovery.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!3.<br />
|Enter your login credentials to authenticate yourself with your Home Organisation <br />
|<br />
|- style="vertical-align:top;"<br />
!4.<br />
|After successful authentication, you may be prompted by your Home Organisation to consent to the release of personal information to the '''EGI AAI Service Provider Proxy'''. <br />
|<br />
|- style="vertical-align:top;"<br />
!5.<br />
|On the EGI AAI Consent about releasing personal information page, click '''Yes, continue''' to consent to the release of personal information to the '''EGI User Account Registry'''. If you select the '''Remember''' option, your browser will remember your choice unless you clear your cookies or restart the browser.<br />
|[[Image:AAI consent.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!6.<br />
|After successful authentication, you will be redirected to the EGI account registration form. On the introductory page, click '''Begin''' to start the registration process.<br />
|[[Image:AAI sign up intro.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!7.<br />
| Depending on the attributes released by your Identity Provider, you will need to go through one of the following account registration processes: <br />
#'''Self-service Sign Up''': Allows you to join the EGI User Community without approval by an administrator if all the information below is asserted by your Home Organisation: <br />
##at least one of the following unique user identifiers: <br />
##*your pseudonymous, non-reassignable identifier (<tt>eduPersonUniqueId</tt> attribute); <br />
##*your name-based identifier (<tt>eduPersonPrincipalName</tt> attribute); <br />
##*your pseudonymous identifier (<tt>eduPersonTargetedID</tt> attribute or SAML persistent identifier) <br />
##your first name (<tt>givenName</tt> attribute) <br />
##your surname (<tt>sn</tt> attribute) <br />
##your email address (<tt>mail</tt> attribute) <br />
##your role (affiliation) in your Home Organisation (<tt>eduPersonScopedAffiliation</tt> attribute) <br />
#'''Sign Up''': If any of the information above cannot be released by your Home Organisation, you will need to provide the values of the missing attributes yourself. Your request to join the EGI User Community must then be approved by an ''EGI User Sponsor''. You may optionally select a particular individual to review your request through the Sponsor dropdown list. <br />
|[[Image:AAI signup attributes.png|thumb|350px]][[Image:AAI signup sponsors.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!8.<br />
|On the registration form, click '''Review Terms and Conditions''' ([https://documents.egi.eu/document/2623 Acceptable Use Policy and Conditions of Use - EGI AUP]). <br />
|[[Image:AAI GAUP.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!9.<br />
|If you agree to the EGI AAI Terms of Use, select the '''I Agree''' option. ''Important: You will not be able to agree to the terms until you review them.'' <br />
|[[Image:AAI ToU agreement.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!10.<br />
|Finally, click '''Submit''' to submit your request. ''Important: You will not be able to submit your request until you agree to the terms.'' <br />
|<br />
|- style="vertical-align:top;"<br />
!11.<br />
|After submitting your request, EGI AAI will send you an email with a verification link in it. After you click that link, you'll be taken to the request confirmation page. <br />
|<br />
|- style="vertical-align:top;"<br />
!12.<br />
|After reviewing your request, click '''Confirm''' and re-authenticate yourself using the Identity Provider you selected in '''Step 2'''. <br />
|<br />
|- style="vertical-align:top;"<br />
!13.<br />
|In the case of the '''Sign Up''' registration, you need to wait for an EGI User Sponsor to approve your request to join the EGI User Community. Upon approval, EGI AAI will send you a notification email.<br />
|<br />
|}<br />
<br />
Note: After your registration has been completed, you can manage your profile through the EGI Account Registry portal at https://aai.egi.eu/registry.<br />
<br />
= Linking Additional Organisational/Social Identities to your EGI Account =<br />
<br />
Identity linking allows you to access EGI resources with your existing personal EGI ID, using any of the login credentials you have linked to your account. You can use any of your organisational or social login credentials for this purpose. To link a new organisational or social identity to your EGI account: <br />
<br />
{|<br />
|- style="vertical-align:top;"<br />
!1. <br />
|Enter the following URL in a browser: https://aai.egi.eu/registry<br />
|[[Image:AAI registry url.png|thumb|250px]]<br />
|- style="vertical-align:top;"<br />
!2. <br />
|Click '''Login''' and authenticate using any of the login credentials ''already'' linked to your EGI account <br />
|[[Image:AAI registry login.png|thumb|250px]]<br />
|- style="vertical-align:top;"<br />
!3.<br />
|Navigate to '''My EGI User Community Account''' page in one of the following ways: <br />
*hover over your display name next to the gear icon on the top right corner of the page; <br />
*: ''or, alternatively,'' <br />
*select '''EGI User Community''' from the list of available Collaborations and then click '''My EGI User Community Account''' from the '''People''' menu <br />
|[[Image:AAI my account.png|thumb|250px]]<br />
|- style="vertical-align:top;"<br />
!4.<br />
|Under the '''Organisational Identities''' section of your profile page, click '''Link New Identity'''. <br />
|[[Image:AAI link new identity.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!5.<br />
|On the introductory page for Identity Linking, click '''Begin''' <br />
|[[Image:AAI link new identity intro.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!6.<br />
|On the Link New Identity form, click '''Review Terms and Conditions''' ([https://documents.egi.eu/document/74 Grid Acceptable Use Policy - Grid AUP]). <br />
|[[Image:AAI link new identity form.png|thumb|350px]][[Image:AAI GAUP.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!7.<br />
|If you agree to the EGI AAI Terms of Use, select the '''I Agree''' option. ''Important: You will not be able to agree to the terms until you review them.'' <br />
|[[Image:AAI ToU agreement.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!8.<br />
|Finally, click '''Submit''' to submit your request. ''Important: You will not be able to submit your request until you agree to the terms.''<br />
|<br />
|- style="vertical-align:top;"<br />
!9.<br />
|After submitting your request, EGI AAI will send you an email with a link in it. After you click that link, you'll be taken to the Link New Identity confirmation page. <br />
|[[Image:AAI link new identity submitted.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!10.<br />
|On the Link New Identity confirmation page, click '''Confirm''' <br />
|[[Image:AAI link new identity confirm.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!11.<br />
|After confirmation, you will need to sign in using the login credentials from the Institutional/Social Identity Provider you want to link to your account.<br />
|[[Image:AAI IdP discovery.png|thumb|350px]]<br />
|- style="vertical-align:top;"<br />
!12.<br />
|After successful authentication, you'll be able to access EGI resources with your existing personal EGI ID using the login credentials of the Identity Provider you selected in '''Step 11'''.<br />
|[[Image:AAI link new identity confirmed.png|thumb|350px]]<br />
|}</div>Psolagnahttps://wiki.egi.eu/w/index.php?title=EGI-Engage:AMB-2017-05-18&diff=94875EGI-Engage:AMB-2017-05-182017-05-18T09:23:09Z<p>Psolagna: /* Task SA1.1 Operations Coordination */</p>
<hr />
<div>{{Template:EGI-Engage menubar}} {{TOC_right}} <br />
<br />
= Activity Reports =<br />
<br />
== WP1 (NA1) (Yannick Legre) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA1.1 Administrative and Financial Management ===<br />
<br />
Proposal for payment at next PMB 25 May 2017<br> attached to agenda PMB:https://indico.egi.eu/indico/event/3308/<br />
<br />
[[File:Example.jpg]]<br />
=== Task NA1.2 Technical Management ===<br />
* Submission and review of PY2 pending deliverables <br />
* Preparation of activity report for May Collaboration Board<br />
* Preparation of May PMB agenda<br />
<br />
=== Task NA1.3 Quality and Risk Management ===<br />
No progress - quality manager on holidays and attending EGI conference (Collaboration board meeting)<br />
<br />
== WP2 (NA2) (Sergio Andreozzi) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task NA2.1 Communication and Dissemination ===<br />
<br />
=== Task NA2.2 Strategy, Business Development and Exploitation ===<br />
* Strategy<br />
** Opened survey for the EGI Council for strategy update - deadline end May <br />
*IMS<br />
**Individual meetings being held with Process Managers and Service Owners<br />
**Preparation for 1 of 3 internal audits - 30 June<br />
*Pay-for-Use<br />
**Presentation in EGI Marketplace session in Catania; updated requirements<br />
*FitSM<br />
**EBI In-house Foundation training - 19 May in Cambridge<br />
**FitSM WG F2F 29-30 May in Munich (planning)<br />
**Promotion and organisation of June batch open registration trainings<br />
* Procurement<br />
** Organised session in Catania to disseminate the results and discuss future activities<br />
** Oganised session at e-IRG to disseminate project results<br />
<br />
=== Task NA2.3 SME/Industry Engagement and Big Data Value Chain ===<br />
*Webinar “How to engage SMEs for NGIs” to be held 31 May 15:00-16:00<br />
**Draft promotional text being finalized<br />
**Draft presentation structure<br />
*Workplan covering final months of project in progress<br />
<br />
*BDVA<br />
**Contribution to federated i-Space definition<br />
**EGI is taking part in the i-Space selection committee <br />
**Analysis of how BDVA i-Spaces relate to Digital Innovation Hubs<br />
**Contributing to white paper on Big Data for space in the space subgroup<br />
<br />
*Earth Observation Pilot<br />
**Presented at EGI conference<br />
**Analysed involvement T-systems and OTC in the pilot<br />
**Planned participation for next EOSCpilot open call<br />
**Exploring synergies with EinfraCentral and EOSC<br />
<br />
== WP3 (JRA1) (Diego Scardaci) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
* D3.14 - Data Accounting: submitted to EC<br />
* D3.13 and M3.6 (Marketplace): submitted to EC<br />
<br />
Next deliverables:<br />
* M28: D3.15 Second Data Accounting prototype<br />
* M28: D3.16 Final report on EGI Service Registry and Marketplace<br />
* M30: D3.17 Final release of the accounting and operational tools<br />
<br />
=== Task JRA1.1 Authentication and Authorisation Infrastructure ===<br />
* CheckIn moving to beta<br />
* Connectors to Perun for managing VO memberships under testing<br />
* Working to support the new LoA levels (from AARC)<br />
* Working to support the EGI FedCloud<br />
* Connectors to Ops Portal to gather information about VOs<br />
* Discussion with Compute Canada for information sharing in the light of future interoperability.<br />
<br />
=== Task JRA1.2 Service Registry and Marketplace ===<br />
* Marketplace SDTP ready for SSB review<br />
* Specification for RT queue to store service orders: https://docs.google.com/document/d/1qJ0Af60qCv9cF7Cm-uKklLnkn8MwHXr6iy2Hp76Sv0I/edit#heading=h.dvopl56vjyxx<br />
* Platform to manage orders in PrestaShop<br />
* Service order queue created in RT<br />
* Integration with RT on-going<br />
* Defined the workflow to integrate the Applications On Demand Platform<br />
<br />
=== Task JRA1.3 Accounting ===<br />
* Cloud accounting:<br />
** New solution for accounting of the long running VMs under testing --> it should be ready next week<br />
** Minor change on the cloud accounting usage record to increase the performance<br />
** Meeting at the EGI Conference in Catania to discuss Cloud Accounting evolution:<br />
*** new usage record to be defined for block storage<br />
*** new usage record to be defined for public IP addresses<br />
* Data accounting:<br />
** Meeting at the EGI Conference in Catania with OneData team to agree on how to proceed with test. For more details see: https://docs.google.com/document/d/1__vC6nVptyfnvKNnkOHrv_8aR4midG9gXNf4mhwIgR8/edit?usp=sharing<br />
* New release of the portal under testing. New main features:<br />
** API to get accounting data directly from the accounting portal <br />
** Cloud views updated to support the new usage record<br />
*** Wallclock time multiplied per the number of CPU cores<br />
** Possibility to select a measurement unit (day, month, etc)<br />
** Maps to show the graphical distribution of the accounting data in country views<br />
** Discipline account report<br />
** New restricted views<br />
<br />
=== Task JRA1.4 Operations Tools ===<br />
* Ops Portal: Working on integrating CheckIn and the new messaging. Interface for CheckIn to extract VO information<br />
* GOCDB: new roadmap until the end of the project defined: https://wiki.egi.eu/wiki/TASK_JRA1.4_Operations_Tools#GOCDB<br />
* ARGO: module for probes management under development, new messaging infrastructure under testing<br />
* SECANT: integration with the AppDB ongoing<br />
<br />
=== Task JRA1.5 Resource Allocation – e-GRANT ===<br />
* see TJRA1.2<br />
<br />
== WP4 (JRA2) (Matthew Viljoen) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
Upcoming:<br />
* D4.9 Open Data Platform: Demonstrator, Experience Report and Use Cases (PM29)<br />
* D4.10 Final CANFAR integration release (PM30)<br />
* M 4.3 Open Data Platform in the Production (M30)<br />
<br />
=== Task JRA2.1 Federated Open Data ===<br />
* EGI DataHub now upgraded to rc14, involving CYFRONET and CESNET (soon)<br />
* Security/documentation review work is ongoing The next (and final) review will be at the end of this month.<br />
* Earth Observation PoC to start using CESNET Copernicus datasets using EGI DataHub<br />
* Desire to move EGI DataHub from Alpha to Beta<br />
<br />
=== Task JRA2.2 Federated Cloud ===<br />
* Work ongoing to sort out discrepancies in the accounting records <br />
* The work in the Glue 2 support in the information system is ongoing.<br />
<br />
=== Task JRA2.3 e-Infrastructures Integration ===<br />
* iMarine/D4Science plan to move to production this month<br />
* Demo at Catania by CANFAR integration people showing how EU-side identities can be used to effectively share data with researchers on the Canadian side.<br />
* collaboration with T-System in discussion for the post INDIGO phase<br />
<br />
=== Task JRA2.4 Accelerated Computing ===<br />
* Positive feedback from LXD hypervisor GPGPU use over KVM. Also noteworthy is improved block storage access of LXD. However, accounting of GPGPU is still needed. STFC have produced a Draft GPU Accounting Usage Record Schema but no firm date yet. <br />
* Discussion with Astrophysics community who are very interested in GPGPU.<br />
<br />
== WP5 (SA1) (Peter Solagna) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA1.1 Operations Coordination ===<br />
* OMB Chaired and agenda preparation<br />
* Discussion with SA1.2 about the possible security improvements for the fedcloud<br />
* Update of the policies page: link between policies and referring agreements (OLA, SLA, UA...)<br />
* EGI Operations meeting, chaired and agenda preparation<br />
* URT meeting, chaired and agenda preparation<br />
* Following up on CMD-OS Trusty repo resigning with SHA256 (SHA1 will be deprecated), performed on May16 without issues<br />
* Planning releases for CMS-OS and UMD (regular releases)<br />
* Preparation of Fedcloud sites for SSC (basic OCCI capability test): 12 out of 24 are ok.<br />
* Webdav nagios probes testing: fixed configuration issues<br />
* Follow up with issues with the new nagios probes for CREAM-CE that may affect A/R statistics<br />
** Action: review the probes release process<br />
* Started yearly review of the EGI services OLA agreements<br />
<br />
=== Task SA1.2 Development of Security Operations ===<br />
* Preparation of the CSIRT F2F<br />
* Sessions at the EGI Conference<br />
* Discussion about the Fedcloud security issues<br />
<br />
=== Task SA1.3 Integration, Deployment of Grid and Cloud Platforms ===<br />
'''Terradue'''<br />
* DLR InSAR Browse Medium Resolution in production @ BEGRID-BELNET<br />
* Reconfiguration of BELgrid network to secure VMs<br />
* Initial actions to respond to a security incident<br />
* Solved issue with image replication<br />
<br />
'''LTOS'''<br />
* Enabled in the test GGUS instance the ticket creation by email<br />
<br />
== WP6 (SA2) (Gergely Sipos) ==<br />
<br />
[[EGI-Engage:Dissemination|Dissemination reports]] <br />
* All CC tasks presented in Catania. Gergely to follow-up individually questions and outputs aiming at project final report<br />
<br />
=== Milestones &amp; Deliverables ===<br />
<br />
=== Task SA2.1 Training ===<br />
Preparation for the following f2f events:<br />
* EUDAT Summer School, EGI FedCloud theme, FORTH, Heraklion, Crete, Greece, 3-7/7/2017<br />
* CODATA-RDA Research Data Science Summer School: http://indico.ictp.it/event/7974 (Contribute with a FedCloud tutorial), Trieste, 10-21/July/2017<br />
Preparation for the following webinar events:<br />
* Webinar about the Applications On Demand Platform (mainly for NGIs and their USTs)<br />
* A webinar for NGIs on how to engage and work with industry.<br />
* Since the Workload Management System is coming to end-of-life, EGI is trying to push for the adoption of DIRAC. We are evaluation the possibility to have another webinar (depends on DIRACT staffing)<br />
<br />
=== Task SA2.2 Technical User Support ===<br />
* Preparation of EGI talks at Community Application Support workshop (Catania)<br />
* Updated paper about Applications On Demand Service for International Workshop on Science Gateways<br />
* EMSODEV and ICOS presentations in the CC sessions (Catania)<br />
<br />
=== Task SA2.3 ELIXIR ===<br />
<br />
=== Task SA2.4 BBMRI ===<br />
<br />
=== Task SA2.5 MoBrain ===<br />
<br />
=== Task SA2.6 DARIAH ===<br />
<br />
=== Task SA2.7 LifeWatch ===<br />
<br />
=== Task SA2.8 EISCAT_3D ===<br />
PMs have been transferred from Umu and UAB to CPPM to be able to do the final developments of the Dirac portal. Decided at the Collaboration Board meeting in Catania.<br />
<br />
Continued work on the EISCAT_3D data model, with a two-day face-to-face meeting in Kiruna between UmU and EISCAT, including development engineers.<br />
<br />
Work have been started on D6.21: https://docs.google.com/document/d/1W6WVvWEzFBp0xon7Vmgra0DHMRMrWQMi4YqTkBJAujI<br />
<br />
=== Task SA2.9 EPOS ===<br />
<br />
=== Task SA2.10 Disaster Mitigation ===<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
[[Category:EGI-Engage]]</div>Psolagna