Armored Node for Sensitive Data

	Note
	This page is actively maintained by the Grid'5000 team. If you encounter problems, please report them (see the Support page). Additionally, as it is a wiki page, you are free to make minor corrections yourself if needed. If you would like to suggest a more fundamental change, please contact the Grid'5000 team.

This page documents how to secure a Grid'5000 node, making it suitable to host and process more sensitive data. The process is based on a tool (g5k-armor-node.py) that runs on a debian10-x64-big environment.

Node reservation and deployment

Identify your requirements:

• Select a cluster that suits your needs (for example using the Hardware page).
• Estimate for how long you will need the resources. If they exceed what is allowed for the default queue in the Usage Policy, maybe the production queue will match your needs. If the duration also exceeds what is allowed by the production queue (more than one week needed), you should follow the procedure explained on the Usage Policy page to request an exception. Remember that your data will be destroyed at the end of the reservation.

Reserve a node and a VLAN, for example with:

nancy frontend:oarsub -q production -t deploy -l {"type='kavlan'"}/vlan=1+{"cluster='CLUSTER'"}/nodes=1,walltime=WALLTIME -r START DATE

Once the job has started, connect inside the job:

nancy frontend:oarsub -C JOB ID

Get the assigned VLAN number:

nancy frontend:kavlan -V

Get the reserved node:

nancy frontend:uniq $OAR_NODEFILE

Deploy the node with the debian10-x64-big environment, inside the VLAN:

nancy frontend:kadeploy3 -e debian10-x64-big -m NODE --vlan VLAN NUMBER -k

Now wait for the deployment to complete.