You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/why-bioshell.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,17 +7,19 @@ description: An introduction to virtual machines, cloud computing, and why BioSh
7
7
If you are new to bioinformatics and the world of high computing, this page explains what cloud
8
8
computing is, when to use it, and why BioShell makes it easy to get started.
9
9
10
+
{% include callout.html type="note" content="Why 'cloud'? The name comes from old network diagrams, engineers would draw a cloud symbol for the internet or any infrastructure whose exact physical location did not matter to the diagram. The name stuck: your data and computing actually run on real servers in a data centre somewhere, but you do not need to know or care where, you just connect over the internet and use it." %}
11
+
10
12
11
13
## What is a virtual machine? {#what-is-a-vm}
12
14
13
15
A virtual machine is a computer that runs inside another computer, delivered to you over the
14
16
internet. You connect to it from your laptop or desktop, and it behaves like a full computer
15
-
you have complete control over. You do not need to worry about your own hardware specs,
16
-
operating system, or software installation.
17
+
you have complete control over. You do not need to worry about your own hardware specs or
18
+
operating system, and unlike an HPC system, you have the administrator access to install and
19
+
configure software yourself, no need to work around module systems or wait on sysadmin
20
+
approval. [Shelley](tools) is there to make that installation step fast.
17
21
18
-
> Think of it like a fully-equipped lab bench that is always ready, you just sit down and
19
-
> start working, then leave when you are done. The bench does not belong to you, but it is
20
-
> set up exactly the way you need it.
22
+
{% include callout.html type="tip" content="Think of it like a fully-equipped lab bench that is always ready, you just sit down and start working, then leave when you are done. The bench does not belong to you, but it is set up exactly the way you need it." %}
21
23
22
24
With a virtual machine you can:
23
25
@@ -38,7 +40,7 @@ powerful research tools, but they suit different types of work.
38
40
|--|-----------------|---------------------|
39
41
|**Session type**| Interactive - work in real time | Batch - submit jobs and come back later |
40
42
|**Interfaces**| JupyterLab, RStudio, CLI | CLI only (PBS/Slurm schedulers) |
41
-
|**Setup required**|None - environment is preconfigured| Familiarity with job schedulers required |
43
+
|**Setup required**|You install your own tools (Shelley makes this quick), with full admin control and none of an HPC's module or approval restrictions| Familiarity with job schedulers required |
|**Scaling**| Flexible - choose your VM size on demand | Fixed allocations managed through project quotas |
44
46
@@ -57,7 +59,7 @@ teaching. BioShell solves this.
57
59
|---------|----------------------|
58
60
|**Ready on any device**| Every participant gets the same preconfigured environment regardless of whether they are on Windows, macOS, or Linux with no device-specific setup required |
59
61
|**More power than your laptop**| Use familiar tools like RStudio and JupyterLab, but backed by cloud compute that is not competing with your browser, email, or background applications |
60
-
|**Tool discovery built in**|[Bio-Shelley](tools), BioShell's command-line assistant, makes finding and installing tools from a catalogue of over 20,000 containers as simple as `shelley-bio build samtools`, no container knowledge needed |
62
+
|**Tool discovery built in**|[Shelley](tools), BioShell's command-line assistant, makes finding and installing tools from a catalogue of over 20,000 containers as simple as `Shelley build samtools`, no container knowledge needed |
61
63
|**Reproducible workshops**| Version-controlled environments mean you can build a workshop once and rerun it identically next year, or share it with another trainer at another institution |
62
64
|**Easier access than HPC**| Getting time on a national HPC requires project allocation, queue estimates, and job scheduler knowledge. BioShell access is fast, self-service, and does not require you to know in advance exactly what you will run |
63
65
|**Admin access, safely sandboxed**| You have full administrator privileges on your own VM, install anything and break things without affecting other users or needing HPC sysadmin approval |
0 commit comments