UMIACS - User contributions [en]

PythonVirtualEnv

2019-04-09T21:25:14Z

Sattwood:

A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).
 
While virtualenv should be installed on most UMIACS supported machines, the source can be downloaded from the project's GitHub:
:<code>https://github.com/pypa/virtualenv</code>
 

==Basic Usage==
The following steps outline how to create a virtual environment using the system Python.
''Please note the that following examples were done using RHEL5. Please adjust the commands to reflect the OS you are on.''

====Creating the virtual environment (example)====
<pre>
-bash-3.2$ git clone https://github.com/pypa/virtualenv.git
-bash-3.2$ python virtualenv/virtualenv.py env
New python executable in env/bin/python
Installing setuptools.............done.

-bash-3.2$ source env/bin/activate

(env)-bash-3.2$ which python
~/env/bin/python
</pre>

We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following.

<pre>
pip install --upgrade pip
</pre>

You will notice that once you have created your virtual environment, you will need to use the 'source' command to load it into your environment. In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code>

====Installing Python Modules====
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.

<pre>
(env)-bash-3.2$ pip install nose
Downloading/unpacking nose
Downloading nose-1.3.3.tar.gz (274Kb): 274Kb downloaded
Running setup.py egg_info for package nose

...output omitted for brevity...

Successfully installed nose
Cleaning up...
(env)-bash-3.2$
</pre>

====Listing installed Python Modules====
<pre>
(env)-bash-3.2$ pip freeze
nose==1.3.3
</pre>
====Uninstalling Python Modules====
'pip' can also be used to remove a module from the environment.
<pre>
(env)-bash-3.2$ pip uninstall nose
Uninstalling nose:
/chimerahomes/sabobbin/env/bin/nosetests
/chimerahomes/sabobbin/env/bin/nosetests-2.4
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose-1.3.3-py2.4.egg-info
/chimerahomes/sabobbin/env/man/man1/nosetests.1
Proceed (y/n)? y
Successfully uninstalled nose
</pre>

===Switching between virtual environments===
To switch between different environments, simply deactivate your current virtual environment, and source the other.
<pre>
(env)-bash-3.2$ which python
~/env/bin/python

(env)-bash-3.2$ deactivate

-bash-3.2$ source env2.7/bin/activate

(env2.7)-bash-3.2$ which python
~/env2.7/bin/python
</pre>

==Using a different python version==
To create a virtual environment that uses a version of python that is different then the system default, simply create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.

<pre>
-bash-3.2$ module load Python

-bash-3.2$ which python
/usr/local/stow/python-2.7.2/bin/python
</pre>
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.
<pre>
-bash-3.2$ echo $PYTHONPATH
/usr/local/stow/python-commonmodules-2.7.2.0/lib/python2.7/site-packages

-bash-3.2$ PYTHONPATH=''
</pre>
<pre>
-bash-3.2$ /usr/local/stow/virtualenv-1.5.1/virtualenv.py env2.7
New python executable in env2.7/bin/python
Installing setuptools....................done.

-bash-3.2$ source env2.7/bin/activate
(env2.7)-bash-3.2$ which python
~/env2.7/bin/python
</pre>

PythonVirtualEnv

2018-11-07T21:16:34Z

Sattwood:

A virtual environment is an isolated working copy of Python, which allows you to work on specific projects without affecting others. It creates an environment that has its own installation directories and that does not share libraries with other virtualenv environments (and optionally doesn’t access the globally-installed libraries either).
 
While virtualenv should be installed on most UMIACS supported machines, the source can be downloaded from the project's GitHub:
:<code>https://github.com/pypa/virtualenv</code>
 

==Basic Usage==
The following steps outline how to create a virtual environment using the system Python.
''Please note the that following examples were done using RHEL5. Please adjust the commands to reflect the OS you are on.''

====Creating the virtual environment (example)====
<pre>
-bash-3.2$ git clone https://github.com/pypa/virtualenv.git
-bash-3.2$ python virtualenv/src/virtualenv.py env
New python executable in env/bin/python
Installing setuptools.............done.

-bash-3.2$ source env/bin/activate

(env)-bash-3.2$ which python
~/env/bin/python
</pre>

We also suggest the first thing you do is to ensure you have an updated version of pip installed in your environment. Make sure you have sourced your environment, and then run the following.

<pre>
pip install --upgrade pip
</pre>

You will notice that once you have created your virtual environment, you will need to use the 'source' command to load it into your environment. In bash and tcsh, the environment can be deactivated by typing <code>deactivate</code>

====Installing Python Modules====
Once you have created your virtual environment and sourced it, you can install additional modules using the 'pip' command.

<pre>
(env)-bash-3.2$ pip install nose
Downloading/unpacking nose
Downloading nose-1.3.3.tar.gz (274Kb): 274Kb downloaded
Running setup.py egg_info for package nose

...output omitted for brevity...

Successfully installed nose
Cleaning up...
(env)-bash-3.2$
</pre>

====Listing installed Python Modules====
<pre>
(env)-bash-3.2$ pip freeze
nose==1.3.3
</pre>
====Uninstalling Python Modules====
'pip' can also be used to remove a module from the environment.
<pre>
(env)-bash-3.2$ pip uninstall nose
Uninstalling nose:
/chimerahomes/sabobbin/env/bin/nosetests
/chimerahomes/sabobbin/env/bin/nosetests-2.4
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose
/chimerahomes/sabobbin/env/lib/python2.4/site-packages/nose-1.3.3-py2.4.egg-info
/chimerahomes/sabobbin/env/man/man1/nosetests.1
Proceed (y/n)? y
Successfully uninstalled nose
</pre>

===Switching between virtual environments===
To switch between different environments, simply deactivate your current virtual environment, and source the other.
<pre>
(env)-bash-3.2$ which python
~/env/bin/python

(env)-bash-3.2$ deactivate

-bash-3.2$ source env2.7/bin/activate

(env2.7)-bash-3.2$ which python
~/env2.7/bin/python
</pre>

==Using a different python version==
To create a virtual environment that uses a version of python that is different then the system default, simply create the virtualenv with your target version of Python. This could be a Python build we provide via [[Modules]], or one you've built yourself. Virtualenv will pick up the first python version it finds in your $PATH, or you can direct it to a specific location with the "--python" flag.

<pre>
-bash-3.2$ module load Python

-bash-3.2$ which python
/usr/local/stow/python-2.7.2/bin/python
</pre>
'''Important:''' virtualenv will include any modules listed in your PYTHONPATH when initializing the virtual environment. To ensure a vanilla environment, it might be a good idea to verify your PYTHONPATH is empty.
<pre>
-bash-3.2$ echo $PYTHONPATH
/usr/local/stow/python-commonmodules-2.7.2.0/lib/python2.7/site-packages

-bash-3.2$ PYTHONPATH=''
</pre>
<pre>
-bash-3.2$ /usr/local/stow/virtualenv-1.5.1/virtualenv.py env2.7
New python executable in env2.7/bin/python
Installing setuptools....................done.

-bash-3.2$ source env2.7/bin/activate
(env2.7)-bash-3.2$ which python
~/env2.7/bin/python
</pre>

Snapshots:Example

2018-06-15T18:59:11Z

Sattwood:

Note that in this example, the directory ".snapshots" could also be ".zfs/snapshot" depending on the filer serving your host. You can try to 'ls' one and if it doesn't exist try the other.

----

Changing to my virtual environment directory.
<pre>
sattwood@zaphod:~/virtualenv$ pwd
/nfshomes/sattwood/virtualenv
</pre>
I see that I have a python file called '''virtualenv.py'''.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>
<pre>
sattwood@zaphod:~/virtualenv$ ls -lah virtualenv.py
-rwxrwxr-x. 1 sattwood sattwood 98K Jun 12 13:54 virtualenv.py
</pre>
I will remove it from the current file system.
<pre>
sattwood@zaphod:~/virtualenv$ rm virtualenv.py
</pre>
As you can see it no longer is there.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv_support
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded
</pre>
I am going to go into the most recent hourly snapshot, in this case: '''hourly_2018_06_15__12_00'''
<pre>
sattwood@zaphod:~/virtualenv$ ls /nfshomes/sattwood/.snapshots
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__00_00
</pre>
<pre>
sattwood@zaphod:~/virtualenv$ cd /nfshomes/sattwood/.snapshots/hourly_2018_06_15__12_00/virtualenv
</pre>
As you can see the file is still here.
<pre>
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>
I copy it back to the original directory.
<pre>
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cp virtualenv.py /nfshomes/sattwood/virtualenv/
</pre>
Change back to the original directory.
<pre>
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cd /nfshomes/sattwood/virtualenv/
</pre>
And it is back.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>

[[Category:Snapshots]]
__NOTOC__

Snapshots:Example

2018-06-15T18:53:05Z

Sattwood:

Note that in this example, the directory ".snapshots" could also be ".zfs/snapshot" depending on the filer serving your host. You can try to 'ls' one and if it doesn't exist try the other.

----

Changing to my virtual environment directory.
<pre>
sattwood@zaphod:~/virtualenv$ pwd
/nfshomes/sattwood/virtualenv
</pre>
I see that I have a python file called '''virtualenv.py'''.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>
<pre>
sattwood@zaphod:~/virtualenv$ ls -lah virtualenv.py
-rwxrwxr-x. 1 sattwood sattwood 98K Jun 12 13:54 virtualenv.py
</pre>
I will remove it from the current file system.
<pre>
sattwood@zaphod:~/virtualenv$ rm virtualenv.py
</pre>
As you can see it no longer is there.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv_support
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded
</pre>
I am going to go into the most recent hourly snapshot, in this case: '''hourly_2018_06_15__12_00'''
<pre>
sattwood@zaphod:~/virtualenv$ ls /nfshomes/sattwood/.snapshots
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__00_00
sattwood@zaphod:~/virtualenv$ cd /nfshomes/sattwood/.snapshots/hourly_2018_06_15__12_00/virtualenv
</pre>
As you can see the file is still here.
<pre>
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>
I copy it back to the original directory.
<pre>
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cp virtualenv.py /nfshomes/sattwood/virtualenv/
</pre>
Change back to the original directory.
<pre>
sattwood@zaphod:~/.snapshots/hourly_2018_06_15__12_00/virtualenv$ cd /nfshomes/sattwood/virtualenv/
</pre>
And it is back.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>

[[Category:Snapshots]]
__NOTOC__

Snapshots:Example

2018-06-15T18:46:51Z

Sattwood:

Note that in this example, the directory ".snapshots" could also be ".zfs/snapshot" depending on the filer serving your host. You can try to 'ls' one and if it doesn't exist try the other.

----

Changing to my virtual environment directory.
<pre>
sattwood@zaphod:~/virtualenv$ pwd
/nfshomes/sattwood/virtualenv
</pre>
I see that I have a python file called '''virtualenv.py'''.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>
<pre>
sattwood@zaphod:~/virtualenv$ ls -lah virtualenv.py
-rwxrwxr-x. 1 sattwood sattwood 98K Jun 12 13:54 virtualenv.py
</pre>
I will remove it from the current file system.
<pre>
sattwood@zaphod:~/virtualenv$ rm virtualenv.py
</pre>
As you can see it no longer is there.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv_support
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded
</pre>
I am going to go into the most recent hourly snapshot, in this case: '''hourly_2018_06_15__12_00'''
<pre>
sattwood@zaphod:~/virtualenv$ ls .snapshots
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00
sattwood@zaphod:~/virtualenv$ cd .snapshots/hourly_2018_06_15__12_00/
</pre>
As you can see the file is still here.
<pre>
sattwood@zaphod:~/virtualenv/.snapshots/hourly_2018_06_15__12_00$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>
I copy it back to the original directory.
<pre>
sattwood@zaphod:~/virtualenv/.snapshots/hourly_2018_06_15__12_00$ cp virtualenv.py /nfshomes/sattwood/virtualenv/
</pre>
Change back to the original directory.
<pre>
sattwood@zaphod:~/virtualenv/.snapshots/hourly_2018_06_15__12_00$ cd /nfshomes/sattwood/virtualenv/
</pre>
And it is back.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>

[[Category:Snapshots]]
__NOTOC__

Snapshots:Example

2018-06-15T18:44:33Z

Sattwood:

Note that in this example, the directory ".snapshot" could also be either ".snapshots" or ".zfs/snapshot" depending on the filer serving your host. Just look for one of these three when you use the "ls -a" command.

----

Changing to my virtual environment directory.
<pre>
sattwood@zaphod:~/virtualenv$ pwd
/nfshomes/sattwood/virtualenv
</pre>
I see that I have a python file called '''virtualenv.py'''.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>
<pre>
sattwood@zaphod:~/virtualenv$ ls -lah virtualenv.py
-rwxrwxr-x. 1 sattwood sattwood 98K Jun 12 13:54 virtualenv.py
</pre>
I will remove it from the current file system.
<pre>
sattwood@zaphod:~/virtualenv$ rm virtualenv.py
</pre>
As you can see it no longer is there.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv_support
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded
</pre>
I am going to go into the most recent hourly snapshot, in this case: '''hourly_2018_06_15__12_00'''
<pre>
sattwood@zaphod:~/virtualenv$ ls .snapshots
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00
sattwood@zaphod:~/virtualenv$ cd .snapshots/hourly_2018_06_15__12_00/
</pre>
As you can see the file is still here.
<pre>
sattwood@zaphod:~/virtualenv/.snapshots/hourly_2018_06_15__12_00$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>
I copy it back to the original directory.
<pre>
sattwood@zaphod:~/virtualenv/.snapshots/hourly_2018_06_15__12_00$ cp virtualenv.py /nfshomes/sattwood/virtualenv/
</pre>
Change back to the original directory.
<pre>
sattwood@zaphod:~/virtualenv/.snapshots/hourly_2018_06_15__12_00$ cd /nfshomes/sattwood/virtualenv/
</pre>
And it is back.
<pre>
sattwood@zaphod:~/virtualenv$ ls
appveyor.yml bin docs MANIFEST.in scripts setup.py tox.ini virtualenv.py
AUTHORS.txt CONTRIBUTING.rst LICENSE.txt README.rst setup.cfg tests virtualenv_embedded virtualenv_support
</pre>

[[Category:Snapshots]]
__NOTOC__

Snapshots

2018-06-15T18:12:09Z

Sattwood:

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.

We provide [[Snapshots]] on our ZFS 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]].

==Snapshot Policy==

Our core file systems in the department are on a 4 hour snapshot cycle. Snapshots are taken at,

{| style="color:green; background-color:#ffffcc;" cellpadding="5" cellspacing="0"
| 12am
| 4am
| 8am
| 12pm
| 4pm
| 8pm
|}

We retain up to 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot.

==Snapshot Restoring==

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 generally will not be visible, even when viewing hidden directories.

'''It will be either''':

* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer
* .zfs/snapshot for the ZFS filer

The inside of one of these will look something like this on a FluidFS filesystem:
<pre>
sattwood@zaphod:~$ pwd
/nfshomes/sattwood
sattwood@zaphod:~$ cd .snapshots
sattwood@zaphod:~/.snapshots$ ls
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__00_00
</pre>
Or this, on a ZFS filesystem:
<pre>
sattwood@swirl:~$ pwd
/nmhomes/sattwood
sattwood@swirl:~$ cd .zfs/snapshot
sattwood@swirl:~/.zfs/snapshot$ ls
zfs-auto-snap_daily-2018-06-13-01h00 zfs-auto-snap_hourly-2018-05-28-00h00
zfs-auto-snap_daily-2018-06-14-01h00 zfs-auto-snap_hourly-2018-05-29-00h00
zfs-auto-snap_daily-2018-06-15-01h00 zfs-auto-snap_hourly-2018-06-03-16h00
zfs-auto-snap_hourly-2018-05-24-00h00 zfs-auto-snap_hourly-2018-06-10-08h00
zfs-auto-snap_hourly-2018-05-25-00h00 zfs-auto-snap_hourly-2018-06-15-12h00
zfs-auto-snap_hourly-2018-05-26-00h00 zfs-auto-snap_weekly-2018-06-09-03h00
</pre>

For an example of file restoration, please see [[Snapshots:Example | this page]].

[[Category:Snapshots]]
__NOTOC__

Snapshots

2018-06-15T18:08:58Z

Sattwood:

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.

We provide [[Snapshots]] on our ZFS 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]].

==Snapshot Policy==

Our core file systems in the department are on a 4 hour snapshot cycle. Snapshots are taken at,

{| style="color:green; background-color:#ffffcc;" cellpadding="5" cellspacing="0"
| 12am
| 4am
| 8am
| 12pm
| 4pm
| 8pm
|}

We retain up to 8 hourly snapshots, 2 daily snapshots and 1 weekly snapshot.

==Snapshot Restoring==

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 either''':

* .snapshots for the [[Snapshots:FluidFS | FluidFS]] filer
* .zfs/snapshot for the ZFS filer

The inside of one of these will look something like this on a FluidFS filesystem:
<pre>
sattwood@zaphod:~$ pwd
/nfshomes/sattwood
sattwood@zaphod:~$ cd .snapshots
sattwood@zaphod:~/.snapshots$ ls
daily_2018_06_13__00_00 hourly_2018_06_14__04_00 hourly_2018_06_14__16_00 hourly_2018_06_15__08_00
daily_2018_06_14__00_00 hourly_2018_06_14__08_00 hourly_2018_06_14__20_00 hourly_2018_06_15__12_00
daily_2018_06_15__00_00 hourly_2018_06_14__12_00 hourly_2018_06_15__04_00 weekly_2018_06_09__00_00
</pre>
Or this, on a ZFS filesystem:
<pre>
sattwood@swirl:~$ pwd
/nmhomes/sattwood
sattwood@swirl:~$ cd .zfs/snapshot
sattwood@swirl:~/.zfs/snapshot$ ls
zfs-auto-snap_daily-2018-06-13-01h00 zfs-auto-snap_hourly-2018-05-28-00h00
zfs-auto-snap_daily-2018-06-14-01h00 zfs-auto-snap_hourly-2018-05-29-00h00
zfs-auto-snap_daily-2018-06-15-01h00 zfs-auto-snap_hourly-2018-06-03-16h00
zfs-auto-snap_hourly-2018-05-24-00h00 zfs-auto-snap_hourly-2018-06-10-08h00
zfs-auto-snap_hourly-2018-05-25-00h00 zfs-auto-snap_hourly-2018-06-15-12h00
zfs-auto-snap_hourly-2018-05-26-00h00 zfs-auto-snap_weekly-2018-06-09-03h00
</pre>

For an example of file restoration, please see [[Snapshots:Example | this page]].

[[Category:Snapshots]]
__NOTOC__

Network/VPN

2018-03-01T22:35:18Z

Sattwood: /* Getting Connected */

A virtual private network (VPN) extends a private network across a public network, and enables users to send and receive data across shared or public networks as if their computing devices were directly connected to the private network. UMIACS current provides VPN access through a Pulse Secure SSL VPN.

==Getting Connected==
* [[Network/VPN/Windows|Configuring a Windows SSL VPN Connection]]
* [[Network/VPN/OSX|Configuring a macOS VPN Connection]]
* [[Network/VPN/Ubuntu|Configuring an Ubuntu VPN Connection]]
* '''Mobile Devices:'''
:* [[Network/VPN/IOS | Configuring an iOS device]]
Once connected to the VPN you can use the [[Remote_Desktop| Remote Desktop client]] to access a Windows machine, as well as access other UMIACS resources.

== Enabling MultiFactor Authentication ==
* [[Network/VPN/MFA|Setup Pulse VPN for MFA]]

Network/VPN/Linux

2018-03-01T22:33:13Z

Sattwood: Created page with "'''Please note that this tutorial assumes you already have a network connection established.''' '''Authentication is handled via the Windows domain. If you have an account in..."

'''Please note that this tutorial assumes you already have a network connection established.'''
'''Authentication is handled via the Windows domain. If you have an account in the PC Active Directory, you already have access.'''

The UMIACS VPN is accessible through the Pulse Secure Client. Alternatively, you can establish a connection through a web browser.

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure.deb|Ubuntu 64 bit Pulse Secure Client]] 
#'''Navigate to the download location in terminal. e.g.: ''' <tt>cd ~/Downloads</tt>
#'''Install the package with dependencies, providing your password for sudo when requested.'''
#:<tt>sudo dpkg -i PulseSecure.deb && /usr/local/pulse/PulseClient_x86_64.sh install_dependency_packages</tt>
#:[[Image:UbuntuPulseInstall.png|thumb|center|500px|]]
#'''Start the client.'''
#:[[Image:UbuntuPulseDesktop.png|thumb|center|500px|]]
#'''and click 'Add' (+) under the connection section.'''
#:[[Image:UbuntuPulseInterface3.png|thumb|center|500px|Click the 'Add' (+) button to create a new connection.]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:UbuntuPulseInterface1.png|thumb|center|500px|Enter the name of the VPN server.]]
#'''Enter your UMIACS Windows side credentials and hit connect.'''
#:[[Image:UbuntuPulseInterface2.png|thumb|center|500px|Enter UMIACS Windows credentials.]]

You should now be connected to the UMIACS VPN. You can close the window and the VPN will remain connected.

==Checking VPN Status==
# Launch the Pulse Client GUI
#:[[Image:UbuntuPulseDesktop.png|thumb|center|280px|]]
# Select the down arrow to show connection status.
#:[[Image:UbuntuPulseInterface4.png|thumb|center|280px|]]

Network/VPN/Mobile

2017-10-10T15:48:55Z

Sattwood: /* Download and Install the Pulse Secure Client */

== Download and Install the Pulse Secure Client ==
Pulse Secure for iOS enables secure connectivity over SSL VPN to internal UMIACS resources. The app can be downloaded for free from the App Store:

https://itunes.apple.com/us/app/pulse-secure/id945832041

== Configuring the Client ==
*When the client is first launched, it will prompt you to accept it's license agreement. Click 'Accept' to continue.
*Select 'Configuration' (Note: Ipad version looks slightly different. Click on 'Connect', then 'Add', then follow the rest of the steps below)
*:[[Image:Iosjuniper1.PNG|thumb|left|300px|[iOS] Pulse Secure Client]] 
:*You will then be prompted for some basic information. You will need to provide the following information and then click 'save'
::*'''Name:''' UMIACS VPN
::*'''URL:''' vpn.umiacs.umd.edu
::*'''Username:''' your umiacs username goes here
::*[[Image:Iosjuniper2.png|thumb|left|300px|[iOS] Pulse Secure Client]] 

== Using the Client ==
*After the client has been configured, you can simply hit the 'Connect' button to start the VPN Connection.
:*[[Image:Iosjuniper3.PNG|thumb|left|300px|[iOS] Pulse Secure Client]] 
*Enter your UMIACS password, and hit 'sign in'
*:[[Image:Iosjuniper4.PNG|thumb|left|300px|[iOS] Pulse Secure Client]] 
*You are now connected. You connection status is verified by the VPN symbol in the top status bar.
*:[[Image:Iosjuniper5.png|thumb|left|300px|[iOS] Pulse Secure Client]] 
*To stop the VPN tunnel, click 'Disconnect'

NFShomes

2017-08-21T16:37:31Z

Sattwood:

===/nfshomes===

Automounted NFS file system that houses users' [[OpenLAB]] home directories.

Found on supported [[OSSupport#UNIX | UNIX]] and [[OSSupport#MacOSX | MacOSX]] systems as

/nfshomes/username

Please note that since [[NFS]] is insecure the scope is limited to which machines can mount this file system. If you need additional access you can mount this file system using [[CIFS]] from many operating systems (including Windows) by accessing it as (substituting $username with your UMIACS username)

\\fluidfs.pc.umiacs.umd.edu\umdisk\$username\openlab

[[CIFS]] access is limited to machines in the domain so please use the [[VPN]] if you need access from outside UMIACS networks (including the wireless).

This file system has regular backups with our [[TSM]] service and has [[Snapshots:NetApp|Snapshots]] for easy user restores.

WebSpace

2017-08-21T16:34:57Z

Sattwood:

UMIACS provides web space hosting for research/lab pages and user pages.

==Main Website and Lab Pages==

<pre>http://www.umiacs.umd.edu</pre>

Users can access the main website and lab sites for editing in two ways:
* From Unix as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])
* From Windows as \\fluidfs.pc.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]

Faculty members and authorized users can modify their own public profiles on the main UMIACS homepage. For instructions, see [[ContentManagement]].

==Personal Web Space==

<pre>http://www.umiacs.umd.edu/~username</pre>

Users can access their website for editing two ways:

* From Unix as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])
* From Windows as \\fluidfs.pc.umiacs.umd.edu\www-users\username - and remotely accessed by the same file share over the [[VPN]]

In general, large datasets related to a Labs research should go into the specific lab's web tree, not the individual users. Remember that users' webpage is not permanently maintained once the user leaves UMIACS.

==Adding A Password Protected Folder To Your Web Space==

1) Create the directory you want to password protect or <tt>cd</tt> into the directory you want to password protect

2) Create a file called ''.htaccess'' (<tt> vi .htaccess</tt>) in the directory you wish to password protect.

3) In the file you just created type the following lines

<pre>
AuthUserFile "/your/directory/here/".htpasswd
AuthName "Secure Document"
AuthType Basic
require user username
</pre>

For example, if you were going to protect the <tt>/fs/www-users/username/private</tt> directory and you want the required name to be <tt>class239</tt>, then your file would look like this:
<pre>
AuthUserFile /fs/www-users/username/private/.htpasswd
AuthName "Secure Document"
AuthType Basic
require user class239
</pre>

4) Create a file called ''.htpasswd'' in the same directory as ''.htaccess''. You create this file by typing in <tt>htpasswd -c .htpasswd ''username''</tt> in the directory area to be protected.

In the example above, the username is <tt>class239</tt> so you would type <tt>htpasswd -c .htpasswd class239</tt>

You will be prompted to enter the password you want. The ''.htpasswd'' file will be created in the current directory and will contain an encrypted version of the password.

To later change the username, edit the ''.htaccess'' file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.

==Restricting Content based on IP address==
It is possible to have pages on your webspace only accessible to clients connecting from certain IP addresses. In order to accomplish this, cd in to the directory you wish to restrict, and edit your ''.htaccess'' or ''httpd.conf'' file. The example below shows how to make content only viewable to clients connecting from the UMD wifi in Apache 2.2.

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">SetEnvIF X-Forwarded-For "^128\.8\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^129\.2\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^192\.168\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^206\.196\.(?:1[6-9][0-9]|2[0-5][0-9])\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^10\.\d+\.\d+\.\d+$" UMD_NETWORK
Order Deny,Allow
Deny from all
Allow from env=UMD_NETWORK
</pre>

The SetEnvIF directive will modify one's environment if the specified attribute matches the provided regular expression. In this example, IP addresses that are forwarded from an IP within UMD's IP space are tagged with UMD_NETWORK. Then, all traffic to the example directory is blocked unless it has the UMD_NETWORK tag. See the following pages for a more in depth explanation of the commands used.

[https://httpd.apache.org/docs/2.2/howto/htaccess.html .htaccess], [https://httpd.apache.org/docs/2.2/mod/mod_setenvif.html#setenvif SetEnvIf], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order Order], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#deny Deny], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow Allow]

FileTransferProtocol

2017-08-21T16:33:15Z

Sattwood:

UMIACS provides FTP services for transferring data to and from external collaborators. Since the FTP protocol is conducted entirely in plaintext, external users login to the service as anonymous, and internal users can access the file directories internally. Users will never authenticate over FTP with their UMIACS account. Please see [[SFTP]] for more information on a secure file transfer protocol.

==Getting data from Collaborators==

Collaborators can drop data for users into their FTP incoming file system, located from the FTP service at

<pre>ftp://ftp.umiacs.umd.edu/incoming/<username>/</pre>

FTP logins can write to this space to upload data, but cannot list the files they have placed there. Users can then access the data in their ftpincoming space from

* '''/fs/ftp/incoming/<username>''' from supported unix machines. Click [[ FTP/macOS/Finder | here ]] to see a visual guide.
* '''\\fluidfs.pc.umiacs.umd.edu\ftp-umiacs\incoming\<username>''' - from supported windows machines. Click [[ FTP/Windows/Explorer | here ]] to see a visual guide.

/fs is an automounted file system. This means it will mount other file systems on demand. Although the ftp directory may not be visible to an ls command while in fs, one can still cd into ftp.

Please move your data as soon as possible after it is left for you - files older than 15 days are subject to deletion as necessary.

==Publishing data sets via FTP==
{{Note|'''This part of our FTP service is deprecated in favor of the UMIACS Object Store. Please see [[OBJbox]].'''}}

Users can place data to be externally accessible in their public FTP space, which is located from the FTP service as

<pre>ftp://ftp.umiacs.umd.edu/pub/<username>/</pre>

To upload data to your public site, you can upload data to,

* '''/fs/ftp/pub/<username>''' from supported unix machines
* '''\\fluidfs.pc.umiacs.umd.edu\ftp-umiacs\pub\<username>''' - from supported windows machines

==Effects of tmpwatch==
There is a configuration of tmpwatch[http://linux.die.net/man/8/tmpwatch] in place on our FTP service that will remove any files, regardless of owner or permissions, from any /fs/ftp/incoming/ directory that have not been accessed in 30 days.

NASUsers

2017-08-21T16:12:19Z

Sattwood:

===Web Pages===

Your UMIACS web page is online at

http://www.umiacs.umd.edu/~username.

You can edit it as

/fs/www-umiacs/users/username

on any supported UNIX system and you can mount it via [[CIFS]] as

\\fluidfs.pc.umiacs.umd.edu\www-users

This file system has regular backups with our [[TSM]] service and has [[Snapshots]] for easy user restores.

===Personal FTP Sites for Distributing Data===

Your ftp site is online at

ftp://ftp.umiacs.umd.edu/pub/username

On any supported UNIX workstation, you can access your ftp site as

/fs/ftp-umiacs/pub/username

Windows users can map it as a network drive from

\\fluidfs.pc.umiacs.umd.edu\ftp-umiacs\pub

You can also upload files using [[FTP]], [[SFTP]], and [[SCP]] through openlab.umiacs.umd.edu.

Please note that anyone with an internet connection can log in and download these files so please to do not use your ftp site to store confidential data.

This file system has regular backups with our [[TSM]] service and has [[Snapshots]] for easy user restores.

===Personal FTP Sites for Accepting Uploads===

You can also accept uploads through ftp at

ftp://ftp.umiacs.umd.edu/incoming/username.

To access the uploads on any supported UNIX workstation go to

/fs/ftp-umiacs/incoming/username

Please copy and then delete the uploaded files. Windows users can map the directory as

\\fluidfs.pc.umiacs.umd.edu\ftp-umiacs\incoming.

Please note that your peers will not be able to list or read the files that they upload, since this would allow unrelated third parties to upload and distribute files through our ftp service.

This file system has regular backups with our [[TSM]] service and has [[Snapshots]] for easy user restores.

===Usage Guidelines===

Personal NAS is configured to be highly available and modest in both size and usage. Please store large or heavily accessed data sets in a dedicated project storage directory that is tuned for your application.

Please avoid storing shared project data in personal storage allocations. Separating project data from personal data will simplify administration and data management for both researchers and staff.

Network/VPN/Windows

2016-10-27T15:14:59Z

Sattwood:

'''Please note that this tutorial assumes you already have a network connection established.'''
'''Authentication is handled via the Windows domain. If you have an account in the PC Active Directory, you already have access.'''

The UMIACS VPN is accessible through the Junos Pulse Client. Alternatively, you can establish a connection through a web browser.

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure.x64.msi|Windows 64 bit Pulse Secure Client]] 
#:[[Media:PulseSecure.x86.msi|Windows 32 bit Pulse Secure Client]] 
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
#'''Start the client if it is not already running - it usually starts by default on bootup'''
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu]]
#'''If the client is already running, double click it's icon from the status bar'''
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click it's status icon to open]]
#'''and click 'Add' (+) under the connection section'''
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:Pulse Connections.jpg|thumb|center|280px|[Windows] Enter the name of the vpn server]]
#'''Enter your UMIACS windows side credentials and hit connect'''
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS Windows Credentials]]

You should now be connected to the UMIACS VPN.

==Checking VPN Status==
# In the bottom right hand corner, in your status bar, you should see an S icon . If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#:[[Image:Pulseicon2.png|thumb|center|500px|]]
# You can hover over this icon and it will show you the status of your connection.
#:[[Image:PulseStatus2.png|thumb|center|500px|]]

Network/VPN/Windows

2016-10-27T15:12:09Z

Sattwood:

'''Please note that this tutorial assumes you already have a network connection established.'''
'''Authentication is handled via the Windows domain. If you have an account in the PC Active Directory, you already have access.'''

The UMIACS VPN is accessible through the Junos Pulse Client. Alternatively, you can establish a connection through a web browser.

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure.x64.msi|Windows 64 bit Pulse Secure Client]] 
#:[[Media:PulseSecure.x86.msi|Windows 32 bit Pulse Secure Client]] 
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
#'''Start the client if it is not already running - it usually starts by default on bootup'''
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu]]
#'''If the client is already running, double click it's icon from the status bar'''
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click it's status icon to open]]
#'''and click 'Add' (+) under the connection section'''
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:Pulse Connections.jpg|thumb|center|280px|[Windows] Enter the name of the vpn server]]
#'''Enter your UMIACS windows side credentials and hit connect'''
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS Windows Credentials]]

You should now be connected to the UMIACS VPN.

==Checking VPN Status==
# In the bottom right hand corner, in your status bar, you should see an S icon . If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#:[[Image:Pulseicon2.png|thumb|center|280px|]]
# You can hover over this icon and it will show you the status of your connection.
#:[[Image:PulseStatus2.png|thumb|center|280px|]]

Network/VPN/Windows

2016-10-27T14:49:33Z

Sattwood:

'''Please note that this tutorial assumes you already have a network connection established.'''
'''Authentication is handled via the Windows domain. If you have an account in the PC Active Directory, you already have access.'''

The UMIACS VPN is accessible through the Junos Pulse Client. Alternatively, you can establish a connection through a web browser.

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure.x64.msi|Windows 64 bit Pulse Secure Client]] 
#:[[Media:PulseSecure.x86.msi|Windows 32 bit Pulse Secure Client]] 
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
#'''Start the client if it is not already running - it usually starts by default on bootup'''
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu]]
#'''If the client is already running, double click it's icon from the status bar'''
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click it's status icon to open]]
#'''and click 'Add' (+) under the connection section'''
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:Pulse Connections.jpg|thumb|center|280px|[Windows] Enter the name of the vpn server]]
#'''Enter your UMIACS windows side credentials and hit connect'''
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS Windows Credentials]]

You should now be connected to the UMIACS VPN.

==Checking VPN Status==
# In the bottom right hand corner, in your status bar, you should see an S icon . If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#:[[Image:Pulseicon.png|thumb|center|280px|]]
# You can hover over this icon and it will show you the status of your connection.
#:[[Image:PulseStatus.png|thumb|center|280px|]]

Network/VPN/Windows

2016-10-27T14:34:09Z

Sattwood: /* Connecting through the Pulse Secure client */

'''Please note that this tutorial assumes you already have a network connection established.'''
'''Authentication is handled via the Windows domain. If you have an account in the PC Active Directory, you already have access.'''

The UMIACS VPN is accessible through the Junos Pulse Client. Alternatively, you can establish a connection through a web browser.

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure.x64.msi|Windows 64 bit Pulse Secure Client]] 
#:[[Media:PulseSecure.x86.msi|Windows 32 bit Pulse Secure Client]] 
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
#'''Start the client if it is not already running - it usually starts by default on bootup'''
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu]]
#'''If the client is already running, double click it's icon from the status bar'''
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click it's status icon to open]]
#'''and click 'Add' (+) under the connection section'''
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:Pulse Connections.jpg|thumb|center|280px|[Windows] Enter the name of the vpn server]]
#'''Enter your UMIACS windows side credentials and hit connect'''
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS Windows Credentials]]

You should now be connected to the UMIACS VPN.

Network/VPN/Windows

2016-10-27T14:33:28Z

Sattwood: /* Connecting through the Pulse Secure client */

'''Please note that this tutorial assumes you already have a network connection established.'''
'''Authentication is handled via the Windows domain. If you have an account in the PC Active Directory, you already have access.'''

The UMIACS VPN is accessible through the Junos Pulse Client. Alternatively, you can establish a connection through a web browser.

== Connecting through the Pulse Secure client ==
#'''Download the client:'''
#:[[Media:PulseSecure.x64.msi|Windows 64 bit Pulse Secure Client]] 
#:[[Media:PulseSecure.x86.msi|Windows 32 bit Pulse Secure Client]] 
#:''Upon starting the client for the first time it will ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
#'''Start the client if it is not already running - it usually starts by default on bootup'''
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu]]
#'''If the client is already running, double click it's icon from the status bar'''
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click it's status icon to open]]
#'''and click 'Add' (+) under the connection section'''
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:Pulse Connections.jpg|thumb|center|280px|[Windows] Enter the name of the vpn server]]
#'''Enter your UMIACS windows side credentials and hit connect'''
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS Windows Credentials]]

You should now be connected to the UMIACS VPN.