https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&user=Dahmed&feedformat=atomUMIACS - User contributions [en]2024-03-28T08:10:22ZUser contributionsMediaWiki 1.39.6https://wiki.umiacs.umd.edu/umiacs/index.php?title=Working_with_External_Collaborators&diff=7886Working with External Collaborators2018-08-08T16:16:08Z<p>Dahmed: </p>
<hr />
<div>= Collaborator Account Introduction =<br />
<br />
UMIACS provides [[CollaboratorAccount| collaborator accounts]] to facilitate collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as GitLab, UMobjstore, Wikis, and other web-based applications. These accounts do not have storage and access to UMIACS workstations however. Full accounts are needed to access resources [[Accounts/Collaborator|collaborator accounts]] do not have access to.<br />
<br />
==How do I create a Collaborator Account?==<br />
<br />
A UMIACS Account holder has to sponsor the Collaborator Account. This is done in our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/new UMIACS Requests Application]. This will send an email to the Collaborator to set their details (including a username and password). Once the Collaborator has created their account, an email will be sent to both the account sponsor and the Collaborator that the account is ready to use.<br />
<br />
=GitLab=<br />
<br />
[[GitLab]] is a source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS credentials in the "UMIACS Onsite/LDAP" tab:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
==GitLab Collaborators==<br />
<br />
Any UMIACS user can now create an unlimited number of offsite collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create repositories or groups, but may be given access to your repositories or groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
=Security Groups=<br />
<br />
[[SecGroups|SecGroup]] are authentication groups that give pis the ability to manage which users should have access to different applications that they manage.<br />
They provide fine-grained access control to wikis, source code repositories, and certain web applications. [[SecGroups]] are the replacement for [[ApplicationResource|ARs]]<br />
<br />
==Viewing Security Groups==<br />
<br />
You can view which SecGroups you are in through the directory app [https://intranet.umiacs.umd.edu/directory/secgroup/ SecGroups]<br />
<br />
=Obj=<br />
<br />
UMobjstore is the Django web application component complementing [[UMobj]], the command-line utility. UMobjstore gives users a convenient interface to our Ceph Object Stores which are distributed across different machines, so that machines can fail and the cluster keep functioning<br />
<br />
==When to use UMobj==<br />
<br />
Use umobj if:<br />
* you have a large number of files to upload (hundreds or thousands of files)<br />
* you are uploading large files (files greater than 4GB in size)<br />
<br />
==Supported object storage clusters==<br />
<br />
* https://obj.umiacs.umd.edu/obj<br />
* https://gembox.cbcb.umd.edu/gembox<br />
<br />
=Wikis=<br />
<br />
Wikis are great for providing documentation through static websites. In order to access a particular wiki a user will first have to be added to the respective [[SecGroups|SecGroup]].</div>Dahmedhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Working_with_External_Collaborators&diff=7885Working with External Collaborators2018-08-08T16:11:26Z<p>Dahmed: </p>
<hr />
<div>= Collaborator Account Introduction =<br />
<br />
UMIACS provides [[CollaboratorAccount| collaborator accounts]] to facilitate collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as our GitLab source code and project management tool, our ObjectStore , Wikis, and other web-based applications. These accounts do not have storage and access to GitLab repositories, ObjectStore buckets, etc. fall under their account sponsor and/or the PI. Full accounts are needed to access resources [[Accounts/Collaborator|collaborator accounts]] do not have access to.<br />
<br />
==How do I create a Collaborator Account?==<br />
<br />
A UMIACS Account holder has to sponsor the Collaborator Account. This is done in our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/new UMIACS Requests Application]. This will send an email to the Collaborator to set their details (including a username and password). Once the Collaborator has created their account, an email will be sent to both the account sponsor and the Collaborator that the account is ready to use.<br />
<br />
=GitLab=<br />
<br />
[[GitLab]] is a source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS credentials in the "UMIACS Onsite/LDAP" tab:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
==GitLab Collaborators==<br />
<br />
Any UMIACS user can now create an unlimited number of offsite collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create repositories or groups, but may be given access to your repositories or groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
=Security Groups=<br />
<br />
[[SecGroups|SecGroup]] are authentication groups that give pis the ability to manage which users should have access to different applications that they manage.<br />
They provide fine-grained access control to wikis, source code repositories, and certain web applications. [[SecGroups]] are the replacement for [[ApplicationResource|ARs]]<br />
<br />
==Viewing Security Groups==<br />
<br />
You can view which SecGroups you are in through the directory app [https://intranet.umiacs.umd.edu/directory/secgroup/ SecGroups]<br />
<br />
=Obj=<br />
<br />
UMobjstore is the Django web application component complementing [[UMobj]], the command-line utility. UMobjstore gives users a convenient interface to our Ceph Object Stores which are distributed across different machines, so that machines can fail and the cluster keep functioning<br />
<br />
==When to use UMobj==<br />
<br />
Use umobj if:<br />
* you have a large number of files to upload (hundreds or thousands of files)<br />
* you are uploading large files (files greater than 4GB in size)<br />
<br />
==Supported object storage clusters==<br />
<br />
* https://obj.umiacs.umd.edu/obj<br />
* https://gembox.cbcb.umd.edu/gembox<br />
<br />
=Wikis=<br />
<br />
Wikis are great for providing documentation through static websites. In order to access a particular wiki a user will first have to be added to the respective [[SecGroups|SecGroup]].</div>Dahmedhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Working_with_External_Collaborators&diff=7884Working with External Collaborators2018-08-08T15:20:26Z<p>Dahmed: </p>
<hr />
<div>= Collaborator Account Introduction =<br />
<br />
UMIACS provides [[CollaboratorAccount| collaborator accounts]] to facilitate collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as our GitLab source code and project management tool, our ObjectStore , Wikis, and other web-based applications. These accounts do not have storage and access to GitLab repositories, ObjectStore buckets, etc. fall under their account sponsor and/or the PI. Full accounts are needed to access resources [[Accounts/Collaborator|collaborator accounts]] do not have access to.<br />
<br />
==How do I create a Collaborator Account?==<br />
A UMIACS Account holder has to sponsor the Collaborator Account. This is done in our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/new UMIACS Requests Application]. This will send an email to the Collaborator to set their details (including a username and password). Once the Collaborator has created their account, an email will be sent to both the account sponsor and the Collaborator that the account is ready to use.<br />
<br />
=GitLab=<br />
<br />
[[GitLab]] is a source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS credentials in the "UMIACS Onsite/LDAP" tab:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
==GitLab Collaborators==<br />
<br />
Any UMIACS user can now create an unlimited number of offsite collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create repositories or groups, but may be given access to your repositories or groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
=Security Groups=<br />
<br />
[[SecGroups|SecGroup]] are authentication groups that give pis the ability to manage which users should have access to different applications that they manage.<br />
They provide fine-grained access control to wikis, source code repositories, and certain web applications. [[SecGroups]] are the replacement for [[ApplicationResource|ARs]]<br />
<br />
==Viewing Security Groups==<br />
<br />
You can view which SecGroups you are in through the directory app [https://intranet.umiacs.umd.edu/directory/secgroup/ SecGroups]<br />
<br />
=Obj=<br />
<br />
UMobjstore is the Django web application component complementing [[UMobj]], the command-line utility. UMobjstore gives users a convenient interface to our Ceph Object Stores which are distributed across different machines, so that machines can fail and the cluster keep functioning<br />
<br />
==When to use UMobj==<br />
Use umobj if:<br />
* you have a large number of files to upload (hundreds or thousands of files)<br />
* you are uploading large files (files greater than 4GB in size)<br />
<br />
==Supported object storage clusters==<br />
* https://obj.umiacs.umd.edu/obj<br />
* https://gembox.cbcb.umd.edu/gembox</div>Dahmedhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Working_with_External_Collaborators&diff=7882Working with External Collaborators2018-08-08T14:32:04Z<p>Dahmed: </p>
<hr />
<div>= Collaborator Account Introduction =<br />
<br />
UMIACS provides [[CollaboratorAccount| collaborator accounts]] to facilitate collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as our GitLab source code and project management tool, our ObjectStore , Wikis, and other web-based applications. These accounts do not have storage and access to GitLab repositories, ObjectStore buckets, etc. fall under their account sponsor and/or the PI. Full accounts are needed to access resources [[Accounts/Collaborator|collaborator accounts]] do not have access to.<br />
<br />
==How do I create a Collaborator Account?==<br />
A UMIACS Account holder has to sponsor the Collaborator Account. This is done in our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/new UMIACS Requests Application]. This will send an email to the Collaborator to set their details (including a username and password). Once the Collaborator has created their account, an email will be sent to both the account sponsor and the Collaborator that the account is ready to use.<br />
<br />
=GitLab=<br />
<br />
[[GitLab]] is a source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS credentials in the "UMIACS Onsite/LDAP" tab:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
==GitLab Collaborators==<br />
<br />
Any UMIACS user can now create an unlimited number of offsite collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create repositories or groups, but may be given access to your repositories or groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
=Security Groups=<br />
<br />
[[SecGroups|SecGroup]] are authentication groups that give pis the ability to manage which users should have access to different applications that they manage.<br />
They provide fine-grained access control to wikis, source code repositories, and certain web applications. [[SecGroups]] are the replacement for [[ApplicationResource|ARs]]<br />
<br />
==Viewing Security Groups==<br />
<br />
You can view which SecGroups you are in through the directory app [https://intranet.umiacs.umd.edu/directory/secgroup/ SecGroups]</div>Dahmedhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Working_with_External_Collaborators&diff=7870Working with External Collaborators2018-07-26T18:51:16Z<p>Dahmed: </p>
<hr />
<div>= Collaborator Account Introduction =<br />
<br />
UMIACS provides [[CollaboratorAccount| collaborator accounts]] to facilitate collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as our GitLab source code and project management tool, our ObjectStore , Wikis, and other web-based applications. These accounts do not have storage and access to GitLab repositories, ObjectStore buckets, etc. fall under their account sponsor and/or the PI. Full accounts are needed to access resources [[Accounts/Collaborator|collaborator accounts]] do not have access to.<br />
<br />
==How do I create a Collaborator Account?==<br />
A UMIACS Account holder has to sponsor the Collaborator Account. This is done in our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/new UMIACS Requests Application]. This will send an email to the Collaborator to set their details (including a username and password). Once the Collaborator has created their account, an email will be sent to both the account sponsor and the Collaborator that the account is ready to use.<br />
<br />
=GitLab=<br />
<br />
[[GitLab]] is a source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS credentials in the "UMIACS Onsite/LDAP" tab:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
==GitLab Collaborators==<br />
<br />
Any UMIACS user can now create an unlimited number of offsite collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create repositories or groups, but may be given access to your repositories or groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].</div>Dahmedhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Working_with_External_Collaborators&diff=7869Working with External Collaborators2018-07-26T17:51:38Z<p>Dahmed: Created page with "== Collaborator Account Introduction == UMIACS provides collaborator accounts to facilitate collaboration with non-UMIACS Faculty, Staff and Employee..."</p>
<hr />
<div>== Collaborator Account Introduction ==<br />
<br />
UMIACS provides [[CollaboratorAccount| collaborator accounts]] to facilitate collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as our GitLab source code and project management tool, our ObjectStore , Wikis, and other web-based applications. These accounts do not have storage and access to GitLab repositories, ObjectStore buckets, etc. fall under their account sponsor and/or the PI. Full accounts are needed to access resources [[Accounts/Collaborator|collaborator accounts]] do not have access to.</div>Dahmedhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Snapshots&diff=7799Snapshots2018-06-15T16:38:04Z<p>Dahmed: </p>
<hr />
<div>Snapshots are a implementation of [http://en.wikipedia.org/wiki/Copy-on-write copy-on-write] that allows for a file system to quickly take a point-in-time copy of the file system and provide access to the data through a .snapshot directory. Snapshots provide a fast, user-accessible way to recover data that has been accidentally deleted or corrupted within a recent time window -- rather than having to retrieve the data from comparatively slow tape backups. They also help to span the time gap between full backups.<br />
<br />
We provide [[Snapshots]] on our [[SnapshotsNexenta | Nexenta]] and [[Snapshots:FluidFS | FluidFS]] filers to certain file systems. If you are ever unsure if a particular volume has Snapshots enabled, please contact the [[HelpDesk | Help Desk]].<br />
<br />
==Snapshot Policy==<br />
<br />
Our core file systems in the department are on a 4 hour snapshot cycle. Snapshots are taken at,<br />
<br />
{| style="color:green; background-color:#ffffcc;" cellpadding="5" cellspacing="0"<br />
| 12am<br />
| 4am<br />
| 8am<br />
| 12pm<br />
| 4pm<br />
| 8pm<br />
|}<br />
<br />
We retain up to 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot.<br />
<br />
==Snapshot Restoring==<br />
<br />
If you have deleted a file by mistake and you need to get it back, you can use the snapshots directory to recopy the file. This directory can typically be found in your home directory; it will be prepended by a ., so you will need to use the command "ls -a" to find it. It will be either:<br />
<br />
* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer<br />
* .zfs/snapshots for the [[SnapshotsNexenta | Nexenta]] / [[Snapshots:ZFS | ZFS]] filers<br />
<br />
The inside of one of these will look something like:<br />
<br />
[[File:Screen shot.png]]<br />
<br />
For an example of file restoration, please see [[Snapshots:Example | this page]].<br />
<br />
<br />
[[Category:Snapshots]]<br />
__NOTOC__</div>Dahmedhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=File:Screen_shot.png&diff=7798File:Screen shot.png2018-06-15T16:36:11Z<p>Dahmed: screenshot</p>
<hr />
<div>screenshot</div>Dahmed