# Service desk orders for labs
This page list predefined service orders for activities within one lab. To place an order, click the blue button and send us a prefilled email.
TIP
(1) Send your order from your organizational email that was registered in your user agreement. (2) Send us a regular email with your request if you can't find what you are looking for on the this page.
# User management
Active lab users
Orders for active lab users, such as workbench access and password resets, are listed in our user orders page.
# Add a new lab user
Click the button below to order access for a new user to your lab.
- Who can order: Lab leaders and lab coordinators.
- Required attachment: A signed user agreement.
- Expected response time: One week.
- Expected delivery: Lab keys and VPN certificate.
- Next step: Prepare your key transfer.
- Cost: Included in your lab subscription.
# Deactivate lab user
This order closes access for lab users that no longer need to use your lab, for example when projects ends or lab users switches jobs.
- Who can order: Lab leaders and lab coordinators can deactivate access for all lab users. Lab users can deactivate their own lab access.
- Expected response time: Days.
- Expected delivery: Confirmation on email that lab access is deactivated.
- Cost: Included in your lab subscription.
# Reactivate lab user
Lab users are deactivated on request or after 180 inactive days. Lab leaders and lab coordinator can reactivate their access. We will need one order per lab for multiple lab access reactivations.
- Who can order: Lab leaders and lab coordinators.
- Required attachment: A new user agreement.
- Expected response time: One week.
- Expected delivery: Lab keys and VPN certificate.
- Next step: Prepare your key transfer.
- Cost: Included in your lab subscription.
# Compute
# Update machine size
Increase or decrease the computational power of one of your existing lab machines to a new machine type.
- Who can order: Lab leaders and lab coordinators.
- Expected response time: Days.
- Expected delivery: Lab machine with updated size.
- Requirement: The procedure require a machine restart that needs to be scheduled with your lab users.
- Cost: As specified in the Services specifications and Price list.
# New CPU machine
Add a new machine to your lab. A CPU machine is the default lab machine with CPU and memory aimed at data analysis.
- Who can order: Lab leaders and lab coordinators.
- Expected response time: Days.
- Expected delivery: New lab machine accessible from your home machine.
- Cost: As specified in the Services specifications and Price list.
# New GPU machine
Add a new GPU machine to your lab.
- Who can order: Lab leaders and lab coordinators.
- Expected response time: Days (subject to availability).
- Expected delivery: New lab machine with GPU accelerator accessible from your home machine.
- Cost: As specified in the Services specifications and Price list.
# Fleet of blue machines
Add a fleet of blue machines to distribute analysis for large scale analysis, for example by utilizing tools such as our BlueBox (opens new window).
- Who can order: Lab leaders and lab coordinators.
- Expected response time: Days (subject to availability).
- Expected delivery: Multiple blue machines accessible from your home machine.
- Cost: As specified in the Services specifications and Price list.
# Store
# Expand existing volume
You may expand the existing storage volumes inside your lab up to a maximum of 20TB. We will need separate orders for each individual volume you plan to expand.
- Who can order: Lab leaders and lab coordinators.
- Required information: lab name, machine name, volume name and intended size.
- Expected response time: One week. The volume expansion requires a machine restart that needs to be scheduled 9-11am on a workday.
- Expected delivery: Increased storage capacity.
- Cost: New storage is included in your total storage plan.
Identify the required information
You may identify lab name, machine name and volume name from your resource reports. Alternatively, you may log into your lab machine using SSH and fetch the information manually
Lab and machine name
You will find the lab and machine name for you home machine when you log into your home machine.
Welcome to `LAB NAME`.
For the record, if you shouldn't be here - please
leave and report the incident to cloud@hunt.ntnu.no.
Last login: Sun Dec 3 12:29:28 2017 from 10.10.10.10
your-username@`your-labname`-home~$
Example from above:
# -- Machine name
your-labname-home
# -- Lab name (remove -home)
your-labname
If you plan to expand volumes of machines other than home
, log into your machine of choice to identify the exact machine name:
# -- Machine name
your-labname-iaas-helya-gpu1
.
Volume name and current size
You can identify the volume name while you are logged into the machine where you need to expand the storage:
# -- Command
df -h | grep -E '(^Filesystem|/mnt/)'
# -- Output example
Filesystem Size Used Avail Use% Mounted on
/dev/vdc1 197G 61M 187G 1% /mnt/work
/dev/vdd1 493G 71M 467G 1% /mnt/archive
/dev/vde1 197G 60M 187G 1% /mnt/scratch
/dev/vdf1 99G 60M 94G 1% /mnt/cargo
The above example shows for example that /mnt/archive
has a current Size
of 493 gigabytes shown (500 gigabytes allocated).
# New volume
You may add new volumes to your lab machines. We will need separate orders for each individual volume you plan to add.
- Who can order: Lab leaders and lab coordinators.
- Required information: lab name, machine name, volume name and total size in terabytes.
- Expected response time: One week. The volume expansion requires a machine restart that needs to be scheduled 9-11 am CET on a workday.
- Expected delivery: New storage volume attached (mounted) to your lab machine.
- Cost: New storage is included in your total storage plan.
Identify the required information
You may identify lab name, machine name and volume name from your resource reports. Alternatively, you may log into your lab machine using SSH and fetch the information manually
Lab and machine name
You will find the lab and machine name for you home machine when you log into your home machine.
Welcome to `LAB NAME`.
For the record, if you shouldn't be here - please
leave and report the incident to cloud@hunt.ntnu.no.
Last login: Sun Dec 3 12:29:28 2017 from 10.10.10.10
your-username@`your-labname`-home~$
Example from above:
# -- Machine name
your-labname-home
# -- Lab name (remove -home)
your-labname
If you plan to expand volumes of machines other than home
, log into your machine of choice to identify the exact machine name:
# -- Machine name
your-labname-iaas-helya-gpu1
Volume name and current size
You can identify your current volume names while you are logged into the machine where you need to expand the storage. For example on your home machine:
# -- Command
df -h | grep -E '(^Filesystem|/mnt/)'
# -- Output example
Filesystem Size Used Avail Use% Mounted on
/dev/vdc1 197G 61M 187G 1% /mnt/work
/dev/vdd1 493G 71M 467G 1% /mnt/archive
/dev/vde1 197G 60M 187G 1% /mnt/scratch
/dev/vdf1 99G 60M 94G 1% /mnt/cargo
You may use this information to plan your new storage names and sizes. We typically recommend to go by type of storage and numbers as usage tends to change over time, such as archive2
, work2
etc.
# Data transfers
External data exports
Head over to the data space orders to request data exports outside HUNT Cloud, such as external export kistas and network openings.
# Internal kista
Internal kista is the best way to transfer data between two labs in HUNT Cloud.
- Who can order: Lab leaders or lab coordinators from the uploader lab.
- Required attachment: A signed internal kista order.
- Expected response time: Days.
- Expected delivery: Access information communicated in your Slack lab channel.
- Cost: Included in your lab subscription.
# External import kista
The external import kista allows external parties outside HUNT Cloud to transfer data directly to a lab inside HUNT Cloud in a compliant manner.
- Who can order: Lab leaders and lab coordinators.
- Required attachments: (1) A signed external kista import order, and (2) one SSH public key from the external uploader.
- Expected response time: Days.
- Expected delivery: Kista access information sent to the lab user that will import the data.
- Cost: Included in your lab subscription.
External dependency
Note that time to successful transfer depend on access to SFTP software and potential firewall adjustments for the external-party that will download data.
← Lab users Data spaces →