-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdocs-hpc.html
613 lines (392 loc) · 32.7 KB
/
docs-hpc.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
<!DOCTYPE html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content=" Singularity on HPC One of the architecturally defined features in Singularity is that it can execute containers like they are native programs or scripts on a host computer. As a result, integration with schedulers is simple and runs exactly as you would expect. All standard input, output, error, pipes, IPC, and other communication pathways that locally running programs employ are synchronized with the applications running locally within the container.Additionally, because Singularity is not emulating a full hardware level virtualization paradigm, there is no need to separate out any sandboxed networks or file systems because there is no concept of user-escalation within a container. Users can run Singularity containers just as they run any other program on the HPC resource.WorkflowsWe are in the process of developing Singularity Hub, which will allow for generation of workflows using Singularity containers in an online interface, and easy deployment on standard research clusters (e.g., SLURM, SGE). Currently, the Singularity core software is installed on the following research clusters, meaning you can run Singularity containers as part of your jobs: The Sherlock cluster at Stanford University SDSC Comet and Gordon (XSEDE) MASSIVE M1 M2 and M3 (Monash University and Australian National Merit Allocation Scheme)Integration with MPIAnother result of the Singularity architecture is the ability to properly integrate with the Message Passing Interface (MPI). Work has already been done for out of the box compatibility with Open MPI (both in Open MPI v2.1.x as well as part of Singularity). The Open MPI/Singularity workflow works as follows: mpirun is called by the resource manager or the user directly from a shell Open MPI then calls the process management daemon (ORTED) The ORTED process launches the Singularity container requested by the mpirun command Singularity builds the container and namespace environment Singularity then launches the MPI application within the container The MPI application launches and loads the Open MPI libraries The Open MPI libraries connect back to the ORTED process via the Process Management Interface (PMI) At this point the processes within the container run as they would normally directly on the host.This entire process happens behind the scenes, and from the user’s perspective running via MPI is as simple as just calling mpirun on the host as they would normally.Below are example snippets of building and installing OpenMPI into a container and then running an example MPI program through Singularity.Tutorials Using Host libraries: GPU drivers and OpenMPI BTLsMPI Development ExampleWhat are supported Open MPI Version(s)?To achieve proper container’ized Open MPI support, you should use Open MPI version 2.1. There are however three caveats: Open MPI 1.10.x may work but we expect you will need exactly matching version of PMI and Open MPI on both host and container (the 2.1 series should relax this requirement) Open MPI 2.1.0 has a bug affecting compilation of libraries for some interfaces (particularly Mellanox interfaces using libmxm are known to fail). If your in this situation you should usethe master branch of Open MPI rather than the release. Using Open MPI 2.1 does not magically allow your container to connect to networking fabric libraries in the host. If your cluster has, for example, an infiniband network you still need to install OFED libraries into the container. Alternatively you could bind mount both Open MPI and networking libraries into the container, but this could run afoul of glib compatibility issues (its generally OK if the container glibc is more recent than the host, but not the other way around)Code Example using Open MPI 2.1.0 Stable$ # Include the appropriate development tools into the container (notice we are calling$ # singularity as root and the container is writeable)$ sudo singularity exec -w /tmp/Centos-7.img yum groupinstall "Development Tools"$$ # Obtain the development version of Open MPI$ wget https://www.open-mpi.org/software/ompi/v2.1/downloads/openmpi-2.1.0.tar.bz2$ tar jtf openmpi-2.1.0.tar.bz2$ cd openmpi-2.1.0$$ singularity exec /tmp/Centos-7.img ./configure --prefix=/usr/local$ singularity exec /tmp/Centos-7.img make$$ # Install OpenMPI into the container (notice now running as root and container is writeable)$ sudo singularity exec -w -B /home /tmp/Centos-7.img make install$$ # Build the OpenMPI ring example and place the binary in this directory$ singularity exec /tmp/Centos-7.img mpicc examples/ring_c.c -o ring$$ # Install the MPI binary into the container at /usr/bin/ring$ sudo singularity copy /tmp/Centos-7.img ./ring /usr/bin/$$ # Run the MPI program within the container by calling the MPIRUN on the host$ mpirun -np 20 singularity exec /tmp/Centos-7.img /usr/bin/ringCode Example using Open MPI git masterThe previous example (using the Open MPI 2.1.0 stable release) should work fine on most hardware but if you have an issue, try running the example below (using the Open MPI Master branch):$ # Include the appropriate development tools into the container (notice we are calling$ # singularity as root and the container is writeable)$ sudo singularity exec -w /tmp/Centos-7.img yum groupinstall "Development Tools"$$ # Clone the OpenMPI GitHub master branch in current directory (on host)$ git clone https://github.com/open-mpi/ompi.git$ cd ompi$$ # Build OpenMPI in the working directory, using the tool chain within the container$ singularity exec /tmp/Centos-7.img ./autogen.pl$ singularity exec /tmp/Centos-7.img ./configure --prefix=/usr/local$ singularity exec /tmp/Centos-7.img make$$ # Install OpenMPI into the container (notice now running as root and container is writeable)$ sudo singularity exec -w -B /home /tmp/Centos-7.img make install$$ # Build the OpenMPI ring example and place the binary in this directory$ singularity exec /tmp/Centos-7.img mpicc examples/ring_c.c -o ring$$ # Install the MPI binary into the container at /usr/bin/ring$ sudo singularity copy /tmp/Centos-7.img ./ring /usr/bin/$$ # Run the MPI program within the container by calling the MPIRUN on the host$ mpirun -np 20 singularity exec /tmp/Centos-7.img /usr/bin/ringProcess 0 sending 10 to 1, tag 201 (20 processes in ring)Process 0 sent to 1Process 0 decremented value: 9Process 0 decremented value: 8Process 0 decremented value: 7Process 0 decremented value: 6Process 0 decremented value: 5Process 0 decremented value: 4Process 0 decremented value: 3Process 0 decremented value: 2Process 0 decremented value: 1Process 0 decremented value: 0Process 0 exitingProcess 1 exitingProcess 2 exitingProcess 3 exitingProcess 4 exitingProcess 5 exitingProcess 6 exitingProcess 7 exitingProcess 8 exitingProcess 9 exitingProcess 10 exitingProcess 11 exitingProcess 12 exitingProcess 13 exitingProcess 14 exitingProcess 15 exitingProcess 16 exitingProcess 17 exitingProcess 18 exitingProcess 19 exiting Previous Next Edit me Site last generated: Jul 26, 2017 ">
<meta name="name" content="Singularity on HPC">
<meta name="thumbnail" content="http://singularity.lbl.gov/images/logo/logo.svg">
<title>Singularity on HPC | Singularity</title>
<link rel="stylesheet" href="assets/css/syntax.css">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
<link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet">
<!--<link rel="stylesheet" type="text/css" href="css/bootstrap.min.css">-->
<link rel="stylesheet" href="assets/css/modern-business.css">
<link rel="stylesheet" href="assets/css/lavish-bootstrap.css">
<link rel="stylesheet" href="assets/css/customstyles.css">
<link rel="stylesheet" href="assets/css/theme-blue.css">
<link rel="stylesheet" type="text/css" href="assets/css/asciinema-player.css" />
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery-cookie/1.4.1/jquery.cookie.min.js"></script>
<script src="assets/js/jquery.navgoco.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/anchor-js/2.0.0/anchor.min.js"></script>
<script src="assets/js/toc.js"></script>
<script src="assets/js/customscripts.js"></script>
<link rel="shortcut icon" href="images/favicon/favicon.ico">
<!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
<script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script>
<![endif]-->
<link rel="alternate" type="application/rss+xml" title="" href="http://localhost:4005feed.xml">
<script>
$(document).ready(function() {
// Initialize navgoco with default options
$("#mysidebar").navgoco({
caretHtml: '',
accordion: true,
openClass: 'active', // open
save: false, // leave false or nav highlighting doesn't work right
cookie: {
name: 'navgoco',
expires: false,
path: '/'
},
slide: {
duration: 400,
easing: 'swing'
}
});
$("#collapseAll").click(function(e) {
e.preventDefault();
$("#mysidebar").navgoco('toggle', false);
});
$("#expandAll").click(function(e) {
e.preventDefault();
$("#mysidebar").navgoco('toggle', true);
});
});
</script>
<script>
$(function () {
$('[data-toggle="tooltip"]').tooltip()
})
</script>
</head>
<body>
<!-- asciinema player -->
<script src="assets/js/asciinema-player.js"></script>
<!-- Show or hide players on button clicks-->
<script>
$( document ).ready(function() {
$(".asciinema-button").click(function(){
var asciinemaVideo = "#asciinema-" + $(this).attr('id');
if ($(asciinemaVideo).hasClass('hidden')){
$(asciinemaVideo).removeClass('hidden');
$(this).text('Hide Tutorial')
} else {
$(asciinemaVideo).addClass('hidden');
$(this).text('Show Tutorial')
}
});
});
</script>
<!-- Navigation -->
<nav class="navbar navbar-inverse navbar-fixed-top">
<div class="container topnavlinks">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.html"> <span class="projectTitle"> Singularity</span></a>
</div>
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav navbar-right">
<!-- entries without drop-downs appear here -->
<li><a href="blog">News</a></li>
<!-- entries with drop-downs appear here -->
<!-- conditional logic to control which topnav appears for the audience defined in the configuration file.-->
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Docs<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="admin-guide">Admin Guide</a></li>
<li><a href="user-guide">User Guide</a></li>
<li><a href="links">Contributed Content</a></li>
</ul>
</li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Quick Links<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://github.com/singularityware/singularity" target="_blank">Github Repo</a></li>
<li><a href="https://groups.google.com/a/lbl.gov/forum/#!forum/singularity" target="_blank">Google Group</a></li>
<li><a href="http://stackoverflow.com/questions/tagged/singularity" target="_blank">Singularity on Stack Overflow</a></li>
<li><a href="https://singularity-hub.org/faq" target="_blank">Singularity Hub</a></li>
<li><a href="https://singularity-container.slack.com" target="_blank">Slack</a></li>
<li><a href="faq#troubleshooting">Troubleshooting</a></li>
</ul>
</li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">People<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="https://github.com/gmkurtzer" target="_blank">Gregory M. Kurtzer</a></li>
<li><a href="https://github.com/vsoch" target="_blank">Vanessa Sochat</a></li>
<li><a href="https://github.com/bauerm97" target="_blank">Michael Bauer</a></li>
<li><a href="https://github.com/bbockelm" target="_blank">Brian Bockelman</a></li>
<li><a href="https://github.com/singularityware/singularity/blob/master/AUTHORS" target="_blank">Complete Authors List</a></li>
</ul>
</li>
<li><a href="/search"><i class="fa fa-search"></i></li>
<!-- jekyll search hidden in favor of google
<li>
<div id="search-demo-container">
<input type="text" id="search-input" placeholder="search...">
<ul id="results-container"></ul>
</div>
<script src="assets/js/jekyll-search.js" type="text/javascript"></script>
<script type="text/javascript">
SimpleJekyllSearch.init({
searchInput: document.getElementById('search-input'),
resultsContainer: document.getElementById('results-container'),
dataSource: 'search.json',
searchResultTemplate: '<li><a href="{url}" title="Singularity on HPC">{title}</a></li>',
noResultsText: 'No results found.',
limit: 10,
fuzzy: true,
})
</script>
end search-->
</li>
</ul>
</div>
</div>
<!-- /.container -->
</nav>
<!-- Page Content -->
<div class="container">
<div class="col-lg-12"> </div>
<!-- Content Row -->
<div class="row">
<!-- Sidebar Column -->
<div class="col-md-3">
<div class="shiny"><a href="\"><figure><img src="/images/logo/logo.svg" class="sidebar-logo"/></figure></a></div>
<ul id="mysidebar" class="nav">
<li class="sidebarTitle">Admin Guide</li>
<li>
<a href="#">Quick Start</a>
<ul>
<li><a href="admin-guide">Administration QuickStart</a></li>
<li><a href="docs-security">Security</a></li>
<li><a href="docs-config">The Singularity Config File</a></li>
<li><a href="docs-troubleshooting">Troubleshooting</a></li>
</ul>
<li>
<a href="#">Installation Environments</a>
<ul>
<li class="active"><a href="docs-hpc">Singularity on HPC</a></li>
<li><a href="image-environment">Image Environment</a></li>
<li><a href="docs-license">License</a></li>
</ul>
<!-- if you aren't using the accordion, uncomment this block:
<p class="external">
<a href="#" id="collapseAll">Collapse All</a> | <a href="#" id="expandAll">Expand All</a>
</p>
-->
</li>
</ul>
</div>
<!-- this highlights the active parent class in the navgoco sidebar. this is critical so that the parent expands when you're viewing a page. This must appear below the sidebar code above. Otherwise, if placed inside customscripts.js, the script runs before the sidebar code runs and the class never gets inserted.-->
<script>$("li.active").parents('li').toggleClass("active");</script>
<!-- Content Column -->
<div class="col-md-9">
<div class="post-header">
<h1 class="post-title-main">Singularity on HPC</h1>
</div>
<div class="post-content">
<!-- Previous and next buttons-->
<div class="row" style="padding-top:30px; margin-bottom:10px"><div class="col-md-12">
<a href="#"><button style="float:left" class="hidden previous-button btn btn-circle btn-default"><i class="fa-2x fa fa-angle-double-left"></i></button></a>
<a href="#"><button style="float:right" class="hidden next-button btn btn-circle btn-default"><i class="fa fa-angle-double-right fa-2x"></i></button></a>
</div></div>
<script>
$(document).ready(function(){
var next = $("li.active").next().last().find('a').attr('href');
var previous = $("li.active").prev().last().find('a').attr('href');
// NEXT BUTTON
if (typeof next == 'undefined'){
console.log("disabling next button")
$(".next-button").addClass("hidden")
} else if (next == "#") {
next = $("li.active").next().find("li").first().find('a').attr('href');
$(".next-button").closest('a').attr('href', next)
$(".next-button").removeClass('hidden')
} else {
$(".next-button").closest('a').attr('href', next)
$(".next-button").removeClass('hidden')
}
// PREVIOUS BUTTON
if (typeof previous == 'undefined'){
console.log("disabling previous button")
$(".previous-button").addClass("hidden")
} else if (previous == "#") {
previous = $("li.active").prev().find("li").last().find('a').attr('href')
$(".previous-button").closest('a').attr('href', previous)
$(".previous-button").removeClass('hidden')
} else {
$(".previous-button").closest('a').attr('href', previous)
$(".previous-button").removeClass('hidden')
}
})
</script>
<p>One of the architecturally defined features in Singularity is that it can execute containers like they are native programs or scripts on a host computer. As a result, integration with schedulers is simple and runs exactly as you would expect. All standard input, output, error, pipes, IPC, and other communication pathways that locally running programs employ are synchronized with the applications running locally within the container.</p>
<p>Additionally, because Singularity is not emulating a full hardware level virtualization paradigm, there is no need to separate out any sandboxed networks or file systems because there is no concept of user-escalation within a container. Users can run Singularity containers just as they run any other program on the HPC resource.</p>
<h2 id="workflows">Workflows</h2>
<p>We are in the process of developing Singularity Hub, which will allow for generation of workflows using Singularity containers in an online interface, and easy deployment on standard research clusters (e.g., SLURM, SGE). Currently, the Singularity core software is installed on the following research clusters, meaning you can run Singularity containers as part of your jobs:</p>
<ul>
<li>The <a href="http://sherlock.stanford.edu" target="_blank" class="no-after">Sherlock cluster</a> at <a href="https://srcc.stanford.edu/" class="no-after" target="_blank">Stanford University</a></li>
<li><a href="https://www.xsede.org/news/-/news/item/7624" target="_blank" class="no-after">SDSC Comet and Gordon</a> (XSEDE)</li>
<li><a href="http://docs.massive.org.au/index.html" target="_blank" class="no-after">MASSIVE M1 M2 and M3</a> (Monash University and Australian National Merit Allocation Scheme)</li>
</ul>
<h3 id="integration-with-mpi">Integration with MPI</h3>
<p>Another result of the Singularity architecture is the ability to properly integrate with the Message Passing Interface (MPI). Work has already been done for out of the box compatibility with Open MPI (both in Open MPI v2.1.x as well as part of Singularity). The Open MPI/Singularity workflow works as follows:</p>
<ol>
<li>mpirun is called by the resource manager or the user directly from a shell</li>
<li>Open MPI then calls the process management daemon (ORTED)</li>
<li>The ORTED process launches the Singularity container requested by the mpirun command</li>
<li>Singularity builds the container and namespace environment</li>
<li>Singularity then launches the MPI application within the container</li>
<li>The MPI application launches and loads the Open MPI libraries</li>
<li>The Open MPI libraries connect back to the ORTED process via the Process Management Interface (PMI)</li>
<li>At this point the processes within the container run as they would normally directly on the host.</li>
</ol>
<p>This entire process happens behind the scenes, and from the user’s perspective running via MPI is as simple as just calling mpirun on the host as they would normally.</p>
<p>Below are example snippets of building and installing OpenMPI into a container and then running an example MPI program through Singularity.</p>
<h4 id="tutorials">Tutorials</h4>
<ul>
<li><a href="/tutorial-gpu-drivers-open-mpi-mtls">Using Host libraries: GPU drivers and OpenMPI BTLs</a></li>
</ul>
<h4 id="mpi-development-example">MPI Development Example</h4>
<p><strong>What are supported Open MPI Version(s)?</strong>
To achieve proper container’ized Open MPI support, you should use Open MPI version 2.1. There are however three caveats:</p>
<ol>
<li>Open MPI 1.10.x <em>may</em> work but we expect you will need exactly matching version of PMI and Open MPI on both host and container (the 2.1 series should relax this requirement)</li>
<li>Open MPI 2.1.0 has a bug affecting compilation of libraries for some interfaces (particularly Mellanox interfaces using libmxm are known to fail). If your in this situation you should use
the master branch of Open MPI rather than the release.</li>
<li>Using Open MPI 2.1 does not magically allow your container to connect to networking fabric libraries in the host. If your cluster has, for example, an infiniband network you still need to install OFED libraries into the container. Alternatively you could bind mount both Open MPI and networking libraries into the container, but this could run afoul of glib compatibility issues (its generally OK if the container glibc is more recent than the host, but not the other way around)</li>
</ol>
<h4 id="code-example-using-open-mpi-210-stable">Code Example using Open MPI 2.1.0 Stable</h4>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span><span class="c"># Include the appropriate development tools into the container (notice we are calling</span>
<span class="gp">$ </span><span class="c"># singularity as root and the container is writeable)</span>
<span class="gp">$ </span>sudo singularity <span class="nb">exec</span> -w /tmp/Centos-7.img yum groupinstall <span class="s2">"Development Tools"</span>
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Obtain the development version of Open MPI</span>
<span class="gp">$ </span>wget https://www.open-mpi.org/software/ompi/v2.1/downloads/openmpi-2.1.0.tar.bz2
<span class="gp">$ </span>tar jtf openmpi-2.1.0.tar.bz2
<span class="gp">$ </span><span class="nb">cd </span>openmpi-2.1.0
<span class="err">$</span>
<span class="gp">$ </span>singularity <span class="nb">exec</span> /tmp/Centos-7.img ./configure --prefix<span class="o">=</span>/usr/local
<span class="gp">$ </span>singularity <span class="nb">exec</span> /tmp/Centos-7.img make
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Install OpenMPI into the container (notice now running as root and container is writeable)</span>
<span class="gp">$ </span>sudo singularity <span class="nb">exec</span> -w -B /home /tmp/Centos-7.img make install
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Build the OpenMPI ring example and place the binary in this directory</span>
<span class="gp">$ </span>singularity <span class="nb">exec</span> /tmp/Centos-7.img mpicc examples/ring_c.c -o ring
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Install the MPI binary into the container at /usr/bin/ring</span>
<span class="gp">$ </span>sudo singularity copy /tmp/Centos-7.img ./ring /usr/bin/
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Run the MPI program within the container by calling the MPIRUN on the host</span>
<span class="gp">$ </span>mpirun -np 20 singularity <span class="nb">exec</span> /tmp/Centos-7.img /usr/bin/ring
</code></pre>
</div>
<h4 id="code-example-using-open-mpi-git-master">Code Example using Open MPI git master</h4>
<p>The previous example (using the Open MPI 2.1.0 stable release) should work fine on most hardware but if you have an issue, try running the example below (using the Open MPI Master branch):</p>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span><span class="c"># Include the appropriate development tools into the container (notice we are calling</span>
<span class="gp">$ </span><span class="c"># singularity as root and the container is writeable)</span>
<span class="gp">$ </span>sudo singularity <span class="nb">exec</span> -w /tmp/Centos-7.img yum groupinstall <span class="s2">"Development Tools"</span>
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Clone the OpenMPI GitHub master branch in current directory (on host)</span>
<span class="gp">$ </span>git clone https://github.com/open-mpi/ompi.git
<span class="gp">$ </span><span class="nb">cd </span>ompi
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Build OpenMPI in the working directory, using the tool chain within the container</span>
<span class="gp">$ </span>singularity <span class="nb">exec</span> /tmp/Centos-7.img ./autogen.pl
<span class="gp">$ </span>singularity <span class="nb">exec</span> /tmp/Centos-7.img ./configure --prefix<span class="o">=</span>/usr/local
<span class="gp">$ </span>singularity <span class="nb">exec</span> /tmp/Centos-7.img make
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Install OpenMPI into the container (notice now running as root and container is writeable)</span>
<span class="gp">$ </span>sudo singularity <span class="nb">exec</span> -w -B /home /tmp/Centos-7.img make install
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Build the OpenMPI ring example and place the binary in this directory</span>
<span class="gp">$ </span>singularity <span class="nb">exec</span> /tmp/Centos-7.img mpicc examples/ring_c.c -o ring
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Install the MPI binary into the container at /usr/bin/ring</span>
<span class="gp">$ </span>sudo singularity copy /tmp/Centos-7.img ./ring /usr/bin/
<span class="err">$</span>
<span class="gp">$ </span><span class="c"># Run the MPI program within the container by calling the MPIRUN on the host</span>
<span class="gp">$ </span>mpirun -np 20 singularity <span class="nb">exec</span> /tmp/Centos-7.img /usr/bin/ring
Process 0 sending 10 to 1, tag 201 <span class="o">(</span>20 processes <span class="k">in </span>ring<span class="o">)</span>
Process 0 sent to 1
Process 0 decremented value: 9
Process 0 decremented value: 8
Process 0 decremented value: 7
Process 0 decremented value: 6
Process 0 decremented value: 5
Process 0 decremented value: 4
Process 0 decremented value: 3
Process 0 decremented value: 2
Process 0 decremented value: 1
Process 0 decremented value: 0
Process 0 exiting
Process 1 exiting
Process 2 exiting
Process 3 exiting
Process 4 exiting
Process 5 exiting
Process 6 exiting
Process 7 exiting
Process 8 exiting
Process 9 exiting
Process 10 exiting
Process 11 exiting
Process 12 exiting
Process 13 exiting
Process 14 exiting
Process 15 exiting
Process 16 exiting
Process 17 exiting
Process 18 exiting
Process 19 exiting
</code></pre>
</div>
<!-- More navigation on the bottom -->
<div class="row" style="padding-top:30px; margin-bottom:10px"><div class="col-md-12">
<a href="#"><button style="width:20%; height: 70px; float:left" class="hidden previous-button btn btn-lg btn-default">Previous</button></a>
<a href="#"><button style="width:20%; height: 70px; float:right" class="hidden next-button btn btn-lg btn-default">Next</button></a>
</div></div>
<a style="margin-top:10px;margin-bottom:10px" target="_blank" href="https://github.com/singularityware/singularityware.github.io/blob/master/pages/_pages/docs/docs-hpc.md" class="btn btn-default btn-xs githubEditButton" role="button"><i class="fa fa-github fa-lg"></i> Edit me</a>
<div class="tags">
</div>
</div>
<hr class="shaded"/>
<footer>
<div class="row">
<!-- Social Media links, etc -->
<div class="col-lg-6 footer">
<a class="no-after social-icon" href="https://twitter.com/SingularityApp">
<i class="fa fa-4x fa-twitter no-after"></i>
</a>
<a class="no-after social-icon" href="https://github.com/singularityware">
<i class="fa fa-4x fa-github no-after"></i>
</a>
</div>
<div class="col-lg-6 footer">
<p><img src="images/logo/logo.png" alt="Company logo" style="width:40px;padding-bottom:10px"/></p>
Site last generated: Jul 26, 2017 <br />
</div>
</div>
</footer>
</div>
<!-- /.row -->
</div>
<!-- /.container -->
</div>
</body>
<!-- the google_analytics_id gets auto inserted from the config file -->
<script>(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','//www.google-analytics.com/analytics.js','ga');ga('create','UA-84672381-1','auto');ga('require','displayfeatures');ga('send','pageview');</script>
</html>