Public PIC Wiki - User contributions [en]

Main Page

2024-07-19T09:46:15Z

Jcasals:

== Getting started ==
* [[PIC description|PIC in an image]]
* [[PIC account|Get a PIC account]]
* [[PIC_User_Manual | User manual]]

== Services ==
* [[HTCondor]]
* [[Storage]]
* [[JupyterHub]]
* [[Gitlab]]
* [[CosmoHub]]
* Spark:
** [[Spark on Hadoop|on Hadoop]]
** [[Spark_on_farm|on HTCondor]]
* [[Transferring data to/from PIC]]

== Experiments ==

* [[Euclid]]
* [[AGN ICE]]

== More technical information ==

* [[Storage Department]]

Main Page

2024-07-19T09:46:07Z

Jcasals:

hola

== Getting started ==
* [[PIC description|PIC in an image]]
* [[PIC account|Get a PIC account]]
* [[PIC_User_Manual | User manual]]

== Services ==
* [[HTCondor]]
* [[Storage]]
* [[JupyterHub]]
* [[Gitlab]]
* [[CosmoHub]]
* Spark:
** [[Spark on Hadoop|on Hadoop]]
** [[Spark_on_farm|on HTCondor]]
* [[Transferring data to/from PIC]]

== Experiments ==

* [[Euclid]]
* [[AGN ICE]]

== More technical information ==

* [[Storage Department]]

Gitlab Migration

2019-01-09T09:33:33Z

Jcasals: /* TCP connection reset by peer */

In order to upgrade the gitlab service, it was required to move it to a new host.
The migration of the git repositories from the old host to the new one cannot be done transparently because the previous version has not easy upgrade procedure.
For newer releases, all information will be preserved and the procedure will be done without any user intervention.

'''Also, note that for this particular upgrade, all information from tickets, merge requests and wiki WILL NOT BE MIGRATED.'''

In order to migrate your git repositories to the new host, follow these instructions:

1) Log into https://gitlab.pic.es with your PIC credentials

2) If you use want to use SSH authentication, you have to upload the corresponding public key. You can access this from the ''Settings'' drop-down menu in the top-left of the screen.

3) For each git repository that you want to migrate, execute the the following commands onto the directory it resides:

# Update the URL of the repository
$ git remote set-url origin $(git remote show -n origin | grep "Fetch URL" | awk '{print $3}' | sed s/gitlab0[12].pic.es/gitlab.pic.es/g)

# Remove old gitlab01.pic.es host key
$ ssh-keygen -R gitlab.pic.es

# Push everything to new remote
$ git push origin --all
$ git push origin --tags

The old gitlab service will still be available on read-only at gitlab01.pic.es until the end of February 2019, when it will be finally decomissioned.

'''For users of projects (i.e. CTA) that already migrated, you still need to update your remote URL (step 3) to be able to take advantage of future upgrades.'''

== Issues and Troubleshooting ==
=== TCP connection reset by peer ===
You may be one of the few unlucky users that see this error appearing when trying to clone or fetch from gitlab.
git clone https://gitlab.pic.es/user/repository.git
fatal: unable to access 'https://gitlab.pic.es/user/repository.git': TCP connection reset by peer
As [https://stackoverflow.com/questions/53594412/what-version-of-git-supports-tls-1-2#answer-53594630 this note] from Stack Overflow says, the version of the git package included on Red Hat version 5, lower than 6.8 and lower than 7.2 doesn't support TLSv1.2, the one needed for SSL transfers.

Please, update your Operating System or [https://confluence.atlassian.com/crucible/installing-and-upgrading-git-679608571.html try to update] your git version.

Gitlab Migration

2019-01-09T09:33:07Z

Jcasals:

In order to upgrade the gitlab service, it was required to move it to a new host.
The migration of the git repositories from the old host to the new one cannot be done transparently because the previous version has not easy upgrade procedure.
For newer releases, all information will be preserved and the procedure will be done without any user intervention.

'''Also, note that for this particular upgrade, all information from tickets, merge requests and wiki WILL NOT BE MIGRATED.'''

In order to migrate your git repositories to the new host, follow these instructions:

1) Log into https://gitlab.pic.es with your PIC credentials

2) If you use want to use SSH authentication, you have to upload the corresponding public key. You can access this from the ''Settings'' drop-down menu in the top-left of the screen.

3) For each git repository that you want to migrate, execute the the following commands onto the directory it resides:

# Update the URL of the repository
$ git remote set-url origin $(git remote show -n origin | grep "Fetch URL" | awk '{print $3}' | sed s/gitlab0[12].pic.es/gitlab.pic.es/g)

# Remove old gitlab01.pic.es host key
$ ssh-keygen -R gitlab.pic.es

# Push everything to new remote
$ git push origin --all
$ git push origin --tags

The old gitlab service will still be available on read-only at gitlab01.pic.es until the end of February 2019, when it will be finally decomissioned.

'''For users of projects (i.e. CTA) that already migrated, you still need to update your remote URL (step 3) to be able to take advantage of future upgrades.'''

== Issues and Troubleshooting ==
=== TCP connection reset by peer ===
You may be one of the few unlucky persons that see this error appearing when trying to clone or fetch from gitlab.
git clone https://gitlab.pic.es/user/repository.git
fatal: unable to access 'https://gitlab.pic.es/user/repository.git': TCP connection reset by peer
As [https://stackoverflow.com/questions/53594412/what-version-of-git-supports-tls-1-2#answer-53594630 this note] from Stack Overflow says, the version of the git package included on Red Hat version 5, lower than 6.8 and lower than 7.2 doesn't support TLSv1.2, the one needed for SSL transfers.

Please, update your Operating System or [https://confluence.atlassian.com/crucible/installing-and-upgrading-git-679608571.html try to update] your git version.

Main Page

2018-12-07T14:47:49Z

Jcasals: /* Astrophysics & Cosmology Department */

== Storage Department ==
* [[dCache.org]]
* [[FileSystems]]

== Astrophysics & Cosmology Department ==

*[[CosmoHub | CosmoHub User Guide]]
*[[Gitlab_Migration | Gitlab migration]]
*[[AC_UserManual | User manual]]

== Getting started ==
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

Main Page

2018-12-07T14:47:19Z

Jcasals:

== Storage Department ==
* [[dCache.org]]
* [[FileSystems]]

== Astrophysics & Cosmology Department ==

*[[AC_UserManual | User manual]]
*[[Gitlab_Migration | Gitlab migration]]
*[[CosmoHub | CosmoHub User Guide]]

== Getting started ==
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

Main Page

2018-12-07T14:33:56Z

Jcasals: /* Storage Department */

== Storage Department ==
* [[dCache.org]]
* [[FileSystems]]

== Astrophysics & Cosmology Department ==

*[[AC_UserManual | User manual]]
*[[Gitlab_Migration | Gitlab migration]]

== Getting started ==
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

Main Page

2018-12-07T14:32:47Z

Jcasals: /* Storage Department */

== Storage Department ==
==== [[dCache.org]] ====
==== [[FileSystems]] ====

== Astrophysics & Cosmology Department ==

*[[AC_UserManual | User manual]]
*[[Gitlab_Migration | Gitlab migration]]

== Getting started ==
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

Gitlab Migration

2018-10-25T13:31:07Z

Jcasals:

The gitlab service need to be upgraded to a new version and host.
It will be migrated from gitlab01.pic.es (running v6.x) to gitlab02.pic.es (running v11.x).
This upgrade cannot be done transparently to the users because the actual version is too old.
For newer releases this will be done without any user intervention.

The upgrade of the service need to be done in two steps.
First, users must migrate their repositories to the new host following these instructions:

# Create a remote called new_gitlab with the new address of the repository
$ git remote add new_gitlab $(git remote -v | awk '{print $2}' | sort -u | sed s/gitlab01.pic.es/gitlab02.pic.es/g)

# Upload the repository to the new remote
$ git push new_gitlab --all
$ git push new_gitlab --tags

# Upload the repository to the new remote
$ git push new_gitlab

# Rename the old remote
$ git remote rename origin old_gitlab

# Rename the new remote
$ git remote rename new_gitlab origin

There will be a 3 month period where both gitlab host will coexist to give time users to migrate.
After that, gitlab01 will be decomissioned and the gitlab.pic.es alias will point to gitlab02.pic.es.
Users shall then update their remotes to point to the alias so that future upgrades can be done transparently.

# Change the remote called origin with the new address of the repository
$ git remote set-url origin $(git remote -v | awk '{print $2}' | sort -u | sed s/gitlab02.pic.es/gitlab.pic.es/g)

Main Page

2018-10-25T13:26:58Z

Jcasals:

== Storage Department ==
=== [[dCache.org]] ===
=== [[FileSystems]] ===

== Astrophysics & Cosmology Department ==

*[[AC_UserManual | User manual]]
*[[Gitlab_Migration | Gitlab migration]]

== Getting started ==
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

AC GitlabMigration

2018-10-25T13:26:24Z

Jcasals: Jcasals moved page AC GitlabMigration to Gitlab Migration: Ugly name

#REDIRECT [[Gitlab Migration]]

Gitlab Migration

2018-10-25T13:26:24Z

Jcasals: Jcasals moved page AC GitlabMigration to Gitlab Migration: Ugly name

The gitlab service need to be upgraded to a new version and host.
It will be migrated from gitlab01.pic.es (running v6.x) to gitlab02.pic.es (running v11.x).
This upgrade cannot be done transparently to the users because the actual version is too old.
For newer releases this will be done without any user intervention.

The upgrade of the service need to be done in two steps.
First, users must migrate their repositories to the new host following these instructions:

# Create a remote called new_gitlab with the new address of the repository
$ git remote add new_gitlab $(git remote -v | awk '{print $2}' | sort -u | sed s/gitlab01.pic.es/gitlab02.pic.es/g)

# Upload the repository to the new remote
$ git push new_gitlab --all
$ git push new_gitlab --tags

# Upload the repository to the new remote
$ git push new_gitlab

# Rename the old remote
$ git remote rename origin old_gitlab

# Rename the new remote
$ git remote rename new_gitlab origin

There will be a 3 month period where both gitlab host will coexist to give time users to migrate.
After that, gitlab01 will be decomissioned and the gitlab.pic.es alias will point to gitlab02.pic.es.
Users shall then update their remotes to point to the alias so that future upgrades can be done transparently.

# Create a remote called new_gitlab with the new address of the repository
$ git remote set-url origin $(git remote -v | awk '{print $2}' | sort -u | sed s/gitlab02.pic.es/gitlab.pic.es/g)