deploy: EGI-Federation/documentation@ac3da05

EGI-Federation · Oct 12, 2023 · dbe74fc · dbe74fc
1 parent c4237bd
commit dbe74fc
Show file tree

Hide file tree

Showing 236 changed files with 554 additions and 3,282 deletions.
diff --git a/about/concepts/index.html b/about/concepts/index.html
diff --git a/about/contributing/git/index.html b/about/contributing/git/index.html
diff --git a/about/contributing/index.html b/about/contributing/index.html
diff --git a/about/contributing/shortcodes/index.html b/about/contributing/shortcodes/index.html
diff --git a/about/contributing/style/index.html b/about/contributing/style/index.html
diff --git a/about/index.html b/about/index.html
diff --git a/internal/accounting/index.html b/internal/accounting/index.html
diff --git a/internal/accounting/service-information/index.html b/internal/accounting/service-information/index.html
diff --git a/internal/collaboration-tools/certificates/index.html b/internal/collaboration-tools/certificates/index.html
diff --git a/internal/collaboration-tools/index.html b/internal/collaboration-tools/index.html
diff --git a/internal/collaboration-tools/mailing-lists/index.html b/internal/collaboration-tools/mailing-lists/index.html
diff --git a/internal/collaboration-tools/service-information/index.html b/internal/collaboration-tools/service-information/index.html
diff --git a/internal/collaboration-tools/sso/index.html b/internal/collaboration-tools/sso/index.html
diff --git a/internal/configuration-database/access/index.html b/internal/configuration-database/access/index.html
diff --git a/internal/configuration-database/adding-new-projects/index.html b/internal/configuration-database/adding-new-projects/index.html
diff --git a/internal/configuration-database/adding-service-endpoint/index.html b/internal/configuration-database/adding-service-endpoint/index.html
diff --git a/internal/configuration-database/api/index.html b/internal/configuration-database/api/index.html
diff --git a/internal/configuration-database/downtimes/index.html b/internal/configuration-database/downtimes/index.html
diff --git a/internal/configuration-database/extension-properties/index.html b/internal/configuration-database/extension-properties/index.html
diff --git a/internal/configuration-database/faq/index.html b/internal/configuration-database/faq/index.html
diff --git a/internal/configuration-database/index.html b/internal/configuration-database/index.html
diff --git a/internal/configuration-database/ngi-core-services/index.html b/internal/configuration-database/ngi-core-services/index.html
diff --git a/internal/configuration-database/ngis/index.html b/internal/configuration-database/ngis/index.html
diff --git a/internal/configuration-database/scopes/index.html b/internal/configuration-database/scopes/index.html
diff --git a/internal/configuration-database/service-entities/index.html b/internal/configuration-database/service-entities/index.html
diff --git a/internal/configuration-database/service-groups/index.html b/internal/configuration-database/service-groups/index.html
diff --git a/internal/configuration-database/service-information/index.html b/internal/configuration-database/service-information/index.html
diff --git a/internal/configuration-database/service-registration-requirements/index.html b/internal/configuration-database/service-registration-requirements/index.html
diff --git a/internal/configuration-database/service-types/index.html b/internal/configuration-database/service-types/index.html
diff --git a/internal/configuration-database/sites/index.html b/internal/configuration-database/sites/index.html
diff --git a/internal/configuration-database/users-roles/approve-revoke/index.html b/internal/configuration-database/users-roles/approve-revoke/index.html
diff --git a/internal/configuration-database/users-roles/index.html b/internal/configuration-database/users-roles/index.html
diff --git a/internal/configuration-database/users-roles/managing-accounts/index.html b/internal/configuration-database/users-roles/managing-accounts/index.html
diff --git a/internal/configuration-database/users-roles/managing-roles/index.html b/internal/configuration-database/users-roles/managing-roles/index.html
diff --git a/internal/getting-started/index.html b/internal/getting-started/index.html
diff --git a/internal/guidelines-software-development/index.html b/internal/guidelines-software-development/index.html
diff --git a/internal/helpdesk/account-and-privileges/index.html b/internal/helpdesk/account-and-privileges/index.html
diff --git a/internal/helpdesk/features/alarm-tickets/index.html b/internal/helpdesk/features/alarm-tickets/index.html
diff --git a/internal/helpdesk/features/index.html b/internal/helpdesk/features/index.html
diff --git a/internal/helpdesk/features/issue-type-values/index.html b/internal/helpdesk/features/issue-type-values/index.html
diff --git a/internal/helpdesk/features/quality-of-support-levels/index.html b/internal/helpdesk/features/quality-of-support-levels/index.html
diff --git a/internal/helpdesk/features/report-generator/index.html b/internal/helpdesk/features/report-generator/index.html
diff --git a/internal/helpdesk/features/team-tickets/index.html b/internal/helpdesk/features/team-tickets/index.html
diff --git a/internal/helpdesk/features/ticket-priority/index.html b/internal/helpdesk/features/ticket-priority/index.html
diff --git a/internal/helpdesk/features/ticket-scope/index.html b/internal/helpdesk/features/ticket-scope/index.html
diff --git a/internal/helpdesk/features/tickets-to-multiple-sites/index.html b/internal/helpdesk/features/tickets-to-multiple-sites/index.html
diff --git a/internal/helpdesk/index.html b/internal/helpdesk/index.html
diff --git a/internal/helpdesk/service-information/index.html b/internal/helpdesk/service-information/index.html
diff --git a/internal/helpdesk/support-staff-guide/index.html b/internal/helpdesk/support-staff-guide/index.html
diff --git a/internal/helpdesk/user-guide/index.html b/internal/helpdesk/user-guide/index.html
diff --git a/internal/helpdesk/workflows/index.html b/internal/helpdesk/workflows/index.html
diff --git a/internal/helpdesk/workflows/waiting-for-submitter/index.html b/internal/helpdesk/workflows/waiting-for-submitter/index.html
diff --git a/internal/index.html b/internal/index.html
diff --git a/internal/messaging/index.html b/internal/messaging/index.html
diff --git a/internal/messaging/service-information/index.html b/internal/messaging/service-information/index.html
diff --git a/internal/monitoring/index.html b/internal/monitoring/index.html
diff --git a/internal/monitoring/service-information/index.html b/internal/monitoring/service-information/index.html
diff --git a/internal/operations-portal/index.html b/internal/operations-portal/index.html
diff --git a/internal/operations-portal/service-information/index.html b/internal/operations-portal/service-information/index.html
diff --git a/internal/operations-portal/using-vapor/index.html b/internal/operations-portal/using-vapor/index.html
diff --git a/internal/security-coordination/index.html b/internal/security-coordination/index.html
diff --git a/internal/security-coordination/monitoring/index.html b/internal/security-coordination/monitoring/index.html
diff --git a/internal/security-coordination/monitoring/pakiti/index.html b/internal/security-coordination/monitoring/pakiti/index.html
diff --git a/internal/security-coordination/service-information/index.html b/internal/security-coordination/service-information/index.html
diff --git a/offline-search-index.a04caffe343d6d5881eff0e1d05e841d.json b/offline-search-index.a04caffe343d6d5881eff0e1d05e841d.json
diff --git a/offline-search-index.cc0ad8e8c4f264ad05890a1aff3cae11.json b/offline-search-index.cc0ad8e8c4f264ad05890a1aff3cae11.json
diff --git a/providers/check-in/idp/index.html b/providers/check-in/idp/index.html
diff --git a/providers/check-in/index.html b/providers/check-in/index.html
diff --git a/providers/check-in/sp/index.html b/providers/check-in/sp/index.html
diff --git a/providers/cloud-compute/faq/index.html b/providers/cloud-compute/faq/index.html
diff --git a/providers/cloud-compute/index.html b/providers/cloud-compute/index.html
diff --git a/providers/cloud-compute/openstack/aai/index.html b/providers/cloud-compute/openstack/aai/index.html
diff --git a/providers/cloud-compute/openstack/accounting/index.html b/providers/cloud-compute/openstack/accounting/index.html
diff --git a/providers/cloud-compute/openstack/cloud-info/index.html b/providers/cloud-compute/openstack/cloud-info/index.html
diff --git a/providers/cloud-compute/openstack/cloudkeeper/index.html b/providers/cloud-compute/openstack/cloudkeeper/index.html
diff --git a/providers/cloud-compute/openstack/gpu/index.html b/providers/cloud-compute/openstack/gpu/index.html
diff --git a/providers/cloud-compute/openstack/index.html b/providers/cloud-compute/openstack/index.html
diff --git a/providers/cloud-compute/openstack/vo_config/index.html b/providers/cloud-compute/openstack/vo_config/index.html
diff --git a/providers/cloud-compute/registration/index.html b/providers/cloud-compute/registration/index.html
diff --git a/providers/cloud-compute/requirements/index.html b/providers/cloud-compute/requirements/index.html
diff --git a/providers/cloud-compute/validation/index.html b/providers/cloud-compute/validation/index.html
diff --git a/providers/datahub/index.html b/providers/datahub/index.html
diff --git a/providers/datahub/oneprovider/index.html b/providers/datahub/oneprovider/index.html
diff --git a/providers/high-throughput-compute/changing-site-bdii/index.html b/providers/high-throughput-compute/changing-site-bdii/index.html
diff --git a/providers/high-throughput-compute/htcondor-ce-accounting/index.html b/providers/high-throughput-compute/htcondor-ce-accounting/index.html
diff --git a/providers/high-throughput-compute/index.html b/providers/high-throughput-compute/index.html
diff --git a/providers/high-throughput-compute/storage-accounting/index.html b/providers/high-throughput-compute/storage-accounting/index.html
diff --git a/providers/index.html b/providers/index.html
diff --git a/providers/joining/core-service/index.html b/providers/joining/core-service/index.html
diff --git a/providers/joining/federated-resource-centre/index.html b/providers/joining/federated-resource-centre/index.html
diff --git a/providers/joining/index.html b/providers/joining/index.html
diff --git a/providers/joining/new-provider/index.html b/providers/joining/new-provider/index.html
diff --git a/providers/joining/new-service/index.html b/providers/joining/new-service/index.html
diff --git a/providers/joining/technology-provider/index.html b/providers/joining/technology-provider/index.html
diff --git a/providers/notebooks/architecture/index.html b/providers/notebooks/architecture/index.html
diff --git a/providers/notebooks/index.html b/providers/notebooks/index.html
diff --git a/providers/notebooks/operations/index.html b/providers/notebooks/operations/index.html
diff --git a/providers/online-storage/index.html b/providers/online-storage/index.html
diff --git a/providers/online-storage/minio-oidc/index.html b/providers/online-storage/minio-oidc/index.html
diff --git a/providers/operations-manuals/faq-hepspec06/index.html b/providers/operations-manuals/faq-hepspec06/index.html
diff --git a/providers/operations-manuals/howto01_using_igtf_ca_distribution/index.html b/providers/operations-manuals/howto01_using_igtf_ca_distribution/index.html
diff --git a/providers/operations-manuals/howto02_site_certification_required_documentation/index.html b/providers/operations-manuals/howto02_site_certification_required_documentation/index.html
diff --git a/providers/operations-manuals/howto03_site_certification_giis_check/index.html b/providers/operations-manuals/howto03_site_certification_giis_check/index.html
diff --git a/providers/operations-manuals/howto04_site_certification_manual_tests/index.html b/providers/operations-manuals/howto04_site_certification_manual_tests/index.html
diff --git a/providers/operations-manuals/index.html b/providers/operations-manuals/index.html
diff --git a/providers/operations-manuals/integration-checklist/index.html b/providers/operations-manuals/integration-checklist/index.html
diff --git a/providers/operations-manuals/man01_how_to_publish_site_information/index.html b/providers/operations-manuals/man01_how_to_publish_site_information/index.html
diff --git a/providers/operations-manuals/man02_service_intervention_management/index.html b/providers/operations-manuals/man02_service_intervention_management/index.html
diff --git a/providers/operations-manuals/man04_tool_intervention_management/index.html b/providers/operations-manuals/man04_tool_intervention_management/index.html
diff --git a/providers/operations-manuals/man05_top_and_site_bdii_high_availability/index.html b/providers/operations-manuals/man05_top_and_site_bdii_high_availability/index.html
diff --git a/providers/operations-manuals/man06_failover_for_mysql_grid_based_services/index.html b/providers/operations-manuals/man06_failover_for_mysql_grid_based_services/index.html
diff --git a/providers/operations-manuals/man07_voms_replication/index.html b/providers/operations-manuals/man07_voms_replication/index.html
diff --git a/providers/operations-manuals/man09_accounting_data_publishing/index.html b/providers/operations-manuals/man09_accounting_data_publishing/index.html
diff --git a/providers/operations-manuals/operations-start-guide/index.html b/providers/operations-manuals/operations-start-guide/index.html
diff --git a/providers/rod/alarms-tickets/index.html b/providers/rod/alarms-tickets/index.html
diff --git a/providers/rod/communication/index.html b/providers/rod/communication/index.html
diff --git a/providers/rod/downtimes/index.html b/providers/rod/downtimes/index.html
diff --git a/providers/rod/duties/index.html b/providers/rod/duties/index.html
diff --git a/providers/rod/faq/index.html b/providers/rod/faq/index.html
diff --git a/providers/rod/index.html b/providers/rod/index.html
diff --git a/providers/rod/overview/index.html b/providers/rod/overview/index.html
diff --git a/providers/rod/security/index.html b/providers/rod/security/index.html
diff --git a/sitemap.xml b/sitemap.xml
diff --git a/support/index.html b/support/index.html
diff --git a/users/aai/check-in/faq/index.html b/users/aai/check-in/faq/index.html
diff --git a/users/aai/check-in/index.html b/users/aai/check-in/index.html
diff --git a/users/aai/check-in/joining-virtual-organisation/index.html b/users/aai/check-in/joining-virtual-organisation/index.html
diff --git a/users/aai/check-in/linking/index.html b/users/aai/check-in/linking/index.html
diff --git a/users/aai/check-in/obtaining-tokens/index.html b/users/aai/check-in/obtaining-tokens/index.html
diff --git a/users/aai/check-in/obtaining-tokens/oidc-agent/index.html b/users/aai/check-in/obtaining-tokens/oidc-agent/index.html
diff --git a/users/aai/check-in/obtaining-tokens/token-portal/index.html b/users/aai/check-in/obtaining-tokens/token-portal/index.html
diff --git a/users/aai/check-in/signup/index.html b/users/aai/check-in/signup/index.html
diff --git a/users/aai/check-in/vos/expressing-vo-information/index.html b/users/aai/check-in/vos/expressing-vo-information/index.html
diff --git a/users/aai/check-in/vos/index.html b/users/aai/check-in/vos/index.html
diff --git a/users/aai/check-in/vos/perun/index.html b/users/aai/check-in/vos/perun/index.html
diff --git a/users/aai/check-in/vos/voms/index.html b/users/aai/check-in/vos/voms/index.html
diff --git a/users/aai/index.html b/users/aai/index.html
diff --git a/users/compute/cloud-compute/appdb/index.html b/users/compute/cloud-compute/appdb/index.html
diff --git a/users/compute/cloud-compute/auth/index.html b/users/compute/cloud-compute/auth/index.html
diff --git a/users/compute/cloud-compute/automate/index.html b/users/compute/cloud-compute/automate/index.html
diff --git a/users/compute/cloud-compute/dynamic-dns/index.html b/users/compute/cloud-compute/dynamic-dns/index.html
diff --git a/users/compute/cloud-compute/faq/index.html b/users/compute/cloud-compute/faq/index.html
diff --git a/users/compute/cloud-compute/gpgpu/index.html b/users/compute/cloud-compute/gpgpu/index.html
diff --git a/users/compute/cloud-compute/images/index.html b/users/compute/cloud-compute/images/index.html
diff --git a/users/compute/cloud-compute/index.html b/users/compute/cloud-compute/index.html
diff --git a/users/compute/cloud-compute/monitor/index.html b/users/compute/cloud-compute/monitor/index.html
diff --git a/users/compute/cloud-compute/openstack/index.html b/users/compute/cloud-compute/openstack/index.html
diff --git a/users/compute/cloud-container-compute/docker/index.html b/users/compute/cloud-container-compute/docker/index.html
diff --git a/users/compute/cloud-container-compute/index.html b/users/compute/cloud-container-compute/index.html
diff --git a/users/compute/cloud-container-compute/k8s/index.html b/users/compute/cloud-container-compute/k8s/index.html
diff --git a/users/compute/high-throughput-compute/index.html b/users/compute/high-throughput-compute/index.html
diff --git a/users/compute/high-throughput-compute/querying-information-system/index.html b/users/compute/high-throughput-compute/querying-information-system/index.html
diff --git a/users/compute/index.html b/users/compute/index.html
diff --git a/users/compute/orchestration/dodas/index.html b/users/compute/orchestration/dodas/index.html
diff --git a/users/compute/orchestration/ec3/apps/ecas/index.html b/users/compute/orchestration/ec3/apps/ecas/index.html
diff --git a/users/compute/orchestration/ec3/apps/htc/index.html b/users/compute/orchestration/ec3/apps/htc/index.html
diff --git a/users/compute/orchestration/ec3/apps/index.html b/users/compute/orchestration/ec3/apps/index.html
diff --git a/users/compute/orchestration/ec3/cli/index.html b/users/compute/orchestration/ec3/cli/index.html
diff --git a/users/compute/orchestration/ec3/developers/index.html b/users/compute/orchestration/ec3/developers/index.html
diff --git a/users/compute/orchestration/ec3/index.html b/users/compute/orchestration/ec3/index.html
diff --git a/users/compute/orchestration/ec3/portal/index.html b/users/compute/orchestration/ec3/portal/index.html
diff --git a/users/compute/orchestration/im/cli/index.html b/users/compute/orchestration/im/cli/index.html
diff --git a/users/compute/orchestration/im/dashboard/index.html b/users/compute/orchestration/im/dashboard/index.html
diff --git a/users/compute/orchestration/im/index.html b/users/compute/orchestration/im/index.html
diff --git a/users/compute/orchestration/index.html b/users/compute/orchestration/index.html
diff --git a/users/compute/orchestration/workload-manager/index.html b/users/compute/orchestration/workload-manager/index.html
diff --git a/users/compute/software-distribution/index.html b/users/compute/software-distribution/index.html
diff --git a/users/data/index.html b/users/data/index.html
diff --git a/users/data/index.xml b/users/data/index.xml
@@ -67,53 +67,41 @@ with the advanced EGI services and platforms
 &lt;a href="../../compute/orchestration">cloud orchestrators&lt;/a>),
 and can be accessed from most &lt;a href="../../compute">compute services&lt;/a>.&lt;/p>
 &lt;h2 id="generic-data-management">Generic data management&lt;/h2>
-&lt;p>These higher-level data management services are available to researchers:&lt;/p>
+&lt;p>This higher-level data management service is available to researchers:&lt;/p>
 &lt;ul>
-&lt;li>&lt;a href="rucio">EGI Rucio&lt;/a> is tailored to medium/big scientific collaborations, allowing
-users to organise, manage, and access their data at scale. Data can be distributed
-across heterogeneous data centers at widely distributed locations.&lt;/li>
 &lt;li>&lt;a href="datahub">EGI DataHub&lt;/a> is a high-performance data management solution that
 offers unified data access across multiple types of underlying storage, allowing
 users to share, collaborate and easily perform computations on the stored data.&lt;/li>
 &lt;/ul>
 &lt;h2 id="specialized-data-management">Specialized data management&lt;/h2>
-&lt;p>The following specialized data management services are also available:&lt;/p>
+&lt;p>The following specialized data management service is also available:&lt;/p>
 &lt;ul>
 &lt;li>&lt;a href="data-transfer">EGI Data Transfer&lt;/a> is a low-level service to move data from
 one &lt;a href="../storage/grid-storage">Grid&lt;/a> or &lt;a href="../storage/object-storage">Object&lt;/a> storage
-to another. It is used internally by &lt;a href="rucio">Rucio&lt;/a> to schedule transfers based
-on the data policies defined by the users.&lt;/li>
-&lt;li>&lt;a href="open-rdm">openRDM&lt;/a> is a combined &lt;a href="https://en.wikipedia.org/wiki/FAIR_data">FAIR&lt;/a>
-data management platform, Electronic Laboratory Notebook (ELN) and Inventory Management System
-allowing a complete overview of workflows and information, from initial data generation
-to data analysis and publication.&lt;/li>
+to another.&lt;/li>
 &lt;/ul>
-&lt;h2 id="use-cases-for-storing-and-managing-research-data">Use-cases for storing and managing research data&lt;/h2>
+&lt;h2 id="use-cases-for-storing-research-data">Use-cases for storing research data&lt;/h2>
 &lt;p>Depending on the type of the employed compute services and the use-cases being addressed,
 users might need to choose different data service to store, access, and manage data.&lt;/p>
 &lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>User&lt;/th>
 &lt;th>Data storage&lt;/th>
-&lt;th>Data management (optional)&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Cloud user&lt;/strong>&lt;/td>
 &lt;td>Block and Object storage&lt;/td>
-&lt;td>DataHub&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>HTC user&lt;/strong>&lt;/td>
 &lt;td>Grid storage&lt;/td>
-&lt;td>Rucio&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>HPC user&lt;/strong>&lt;/td>
 &lt;td>High-performance parallel file systems or Object storage&lt;/td>
-&lt;td>DataHub or Rucio&lt;/td>
 &lt;/tr>
 &lt;/tbody>
 &lt;/table>

diff --git a/users/data/management/data-transfer/api/index.html b/users/data/management/data-transfer/api/index.html
diff --git a/users/data/management/data-transfer/clients/index.html b/users/data/management/data-transfer/clients/index.html
diff --git a/users/data/management/data-transfer/index.html b/users/data/management/data-transfer/index.html
diff --git a/users/data/management/data-transfer/monitoring/index.html b/users/data/management/data-transfer/monitoring/index.html
diff --git a/users/data/management/data-transfer/webfts/index.html b/users/data/management/data-transfer/webfts/index.html
diff --git a/users/data/management/datahub/api/index.html b/users/data/management/datahub/api/index.html
diff --git a/users/data/management/datahub/clients/index.html b/users/data/management/datahub/clients/index.html
diff --git a/users/data/management/datahub/file-management/index.html b/users/data/management/datahub/file-management/index.html
diff --git a/users/data/management/datahub/index.html b/users/data/management/datahub/index.html
diff --git a/users/data/management/datahub/links/index.html b/users/data/management/datahub/links/index.html
diff --git a/users/data/management/datahub/usecases/index.html b/users/data/management/datahub/usecases/index.html
diff --git a/users/data/management/index.html b/users/data/management/index.html
diff --git a/users/data/management/index.xml b/users/data/management/index.xml
@@ -162,87 +162,4 @@ to be installed:&lt;/p>
 &lt;ul>
 &lt;li>&lt;a href="https://cafiles.cern.ch/cafiles/certificates/">CERN CA certificates&lt;/a>&lt;/li>
 &lt;li>&lt;a href="http://www.ngs.ac.uk/ukca/certificates/cacerts.html">UK eScience CA certificates&lt;/a>&lt;/li>
-&lt;/ul></description></item><item><title>Users: Rucio</title><link>/users/data/management/rucio/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/users/data/management/rucio/</guid><description>
-&lt;h2 id="what-is-it">What is it?&lt;/h2>
-&lt;p>Built on more than a decade of experience in LHC experiments, Rucio serves the
-data needs of any modern scientific experiments. Rucio can manage large amounts
-of data, countless numbers of files, heterogeneous storage systems, globally
-distributed data centres, with monitoring and analytics.&lt;/p>
-&lt;p>Rucio &lt;strong>allows management of data with expressive statements&lt;/strong>. You to say what
-you want, and Rucio will figure out the details of how to do it. For example,
-three copies of my file on different continents with a backup on tape. You can
-also automatically remove copies of data after a set period or once its access
-popularity drops.&lt;/p>
-&lt;p>While Rucio is extremely scalable, the STFC Rucio Data Management Service is
-designed for smaller communities, with expected data needs up to tens of
-Petabytes. The fact that the underlying Rucio infrastructure is managed by STFC,
-allows communities to easily start using and/or test Rucio with little setup
-cost.&lt;/p>
-&lt;h2 id="requirements-to-consider-to-use-rucio">Requirements to consider to use Rucio&lt;/h2>
-&lt;p>For Rucio to manage your data in this setup, Rucio will need X.509 certificate
-access, or soon, through
-&lt;a href="../../../../providers/check-in/_index.md">EGI Check-in&lt;/a> to:&lt;/p>
-&lt;ul>
-&lt;li>Your experiments Storage Element that is X.509 capable&lt;/li>
-&lt;li>Your experiments Tape Archive that is X.509 capable&lt;/li>
-&lt;li>Your experiments VOMS server information to check Users credentials against&lt;/li>
-&lt;/ul>
-&lt;p>Rucio is a system that sits on top of already established storage elements to
-unify users access for data management, and retrieval. Rucio consists of a
-database of the storage element&amp;rsquo;s details, users and their access credential
-information, access levels, the data, and its location, Rucio is not a direct
-data storage solution.&lt;/p>
-&lt;h2 id="rucio-use-cases">Rucio Use Cases&lt;/h2>
-&lt;p>Rucio is a data management software, that integrates with your experiments
-currently provisioned storage. This section will highlight some use cases that
-Rucio will fill for your experiment.&lt;/p>
-&lt;h3 id="management-of-data-for-archive-when-no-longer-used-actively">Management of data for archive when no longer used actively&lt;/h3>
-&lt;p>A simple use case for Rucio is to manage data between &amp;lsquo;hot&amp;rsquo; storage, made of
-HDDs or SSD, and &amp;lsquo;cold&amp;rsquo; storage made up of tape. When your experiment generates
-data that data will be accessed much more than older data as your colleagues work
-with the data. Within Rucio the data will be registered to be on the &amp;lsquo;hot&amp;rsquo; and
-&amp;lsquo;cold&amp;rsquo; storage. This ensures the integrity of the data by providing multiple
-copies of the data, one on the slower tape archive, and one copy on the more
-easy to access HDDs and SSDs. Then as the usage of this data declines, the data
-on the &amp;lsquo;hot&amp;rsquo; storage can be removed to make way for newer data that is more
-frequently accessed. Should the archived data be requested again Rucio can stage
-the data from tape back to disk making it available for users.&lt;/p>
-&lt;h3 id="management-of-data-between-sites-for-jobs">Management of data between sites for jobs&lt;/h3>
-&lt;p>Another useful use case for Rucio is to manage the data between different sites
-within your experiment. This can provide users with better access to the data
-that they want to work on. Another option is to have Rucio integrated with your
-workflow management software (Panda and DIRAC both have integrated with Rucio),
-so data can be moved to sites as job slots are available, streamlining the
-data flow for the user.&lt;/p>
-&lt;h2 id="official-rucio-pages">Official Rucio Pages&lt;/h2>
-&lt;ul>
-&lt;li>&lt;a href="https://rucio.cern.ch/">Rucio Homepage&lt;/a>&lt;/li>
-&lt;li>&lt;a href="https://rucio.cern.ch/documentation/">Rucio Documentation&lt;/a>&lt;/li>
-&lt;/ul>
-&lt;h2 id="multi-vo-specific-pages">Multi-VO specific pages&lt;/h2>
-&lt;ul>
-&lt;li>&lt;a href="https://www.scd.stfc.ac.uk/Pages/SCD-STFC-Rucio-Data-Management-Service.aspx">Multi-VO Rucio at RAL as a service&lt;/a>&lt;/li>
-&lt;li>&lt;a href="https://www.scd.stfc.ac.uk/Pages/STFC-Rucio-Privacy-Notice.aspx">Privacy Policy&lt;/a>&lt;/li>
-&lt;li>&lt;a href="https://www.scd.stfc.ac.uk/Pages/STFC-Rucio-Acceptable-Use-Policy.aspx">Acceptable Use Policy&lt;/a>&lt;/li>
-&lt;/ul></description></item><item><title>Users: openRDM</title><link>/users/data/management/open-rdm/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/users/data/management/open-rdm/</guid><description>
-&lt;p>While most other &lt;a href="..">data management services&lt;/a> are available in the EGI infrastructure,
-there are specialized services in the EGI portfolio that are offered for in-house
-installations by research communities, with support for customization and
-configuration from EGI.&lt;/p>
-&lt;h2 id="what-is-it">What is it?&lt;/h2>
-&lt;p>The &lt;a href="https://marketplace.eosc-portal.eu/services/openrdm-eu">openRDM&lt;/a> service,
-an Research Data Management (RDM) tool,
-offers &lt;strong>advanced organisation of data during ongoing research projects,
-as an integrated environment with data management and digital lab notebook&lt;/strong>.&lt;/p>
-&lt;p>openRDM combines a data management platform with a digital lab notebook and a sample and
-protocol management system. It enables scientists to meet the ever-increasing requirements
-from funding agencies, journals, and academic institutions to publish data according to the
-&lt;a href="https://en.wikipedia.org/wiki/FAIR_data">FAIR&lt;/a> data principles – according to which data
-should be &lt;em>Findable&lt;/em>, &lt;em>Accessible&lt;/em>, &lt;em>Interoperable&lt;/em> and &lt;em>Reusable&lt;/em>.&lt;/p>
-&lt;div class="alert alert-info" role="alert">
-&lt;h4 class="alert-heading">Note&lt;/h4>
-The openRDM service is based around the
-active research data management (ARDM) platform &lt;a href="https://openbis.ch/">openBIS&lt;/a>, see the
-&lt;a href="https://openbis.ch/index.php/docs/user-documentation/">documentation&lt;/a>
-for more details.
-&lt;/div></description></item></channel></rss>
+&lt;/ul></description></item></channel></rss>