Armored Node for Sensitive Data: Difference between revisions

From Grid5000
Jump to navigation Jump to search
No edit summary
Line 7: Line 7:


Reserve a node and a VLAN, for example with:
Reserve a node and a VLAN, for example with:
<code class="host">nancy frontend:</code><code class="command">oarsub -q production -t deploy -l {"type='kavlan'"}/vlan=1+{"cluster='graffiti'"}/nodes=1,walltime=<code class="replace">WALLTIME</code> -r <code class="replace">START DATE</code></code>
<code class="host">nancy frontend:</code><code class="command">oarsub -q production -t deploy -l {"type='kavlan'"}/vlan=1+{"cluster='graffiti'"}/nodes=1,walltime=<code class="replace">WALLTIME</code> -r <code class="replace">START DATE</code></code>

Revision as of 16:37, 7 April 2021

Note.png 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

Reserve a node and a VLAN, for example with:

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