forked from oliver-sanders/3rd-ENES-Workshop-Cylc-Talk
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
1251 lines (1129 loc) · 42.7 KB
/
index.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
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html lang="en">
<head>
<!-- font-face rule needed here not in css file to avoid CORS block? -->
<style>
@font-face {
font-family: 'Titillium Web';
font-style: normal;
font-weight: 400;
src: local('TitilliumWeb'),
url('fonts/TitilliumWeb/TitilliumWeb-Regular.WOFF')
format('woff');
}
</style>
<link rel="stylesheet" href="css/index.css" />
<link rel="stylesheet" href="css/print.css" />
<link rel="stylesheet" href="highlight/styles/solarized-light.css">
</head>
<body>
<div id="impress" data-transition-duration="1000">
<div id="title" class="step image" data-x="0" data-y="0"
data-scale="3">
<img src="img/supercomputer2.jpg"
style="width:100%; position:absolute; top:15%"
alt="supercomputer"
/>
<div style="position:absolute; left:100px; top:12%; color:white;
text-shadow: 0 2px 2px #000; text-align:center">
<h1 style="margin-top:5%; margin-bottom:300px">Cylc: The Path To
Exascale</h1>
<h3 style="color:white; margin-top:-10%">Hilary, Oliver, Dave<br/>
3rd ENES Workshop on Workflows<br/>
13 September 2018</h3>
</div>
<div class="notes">
</div>
</div>
<!-- Contents -->
<div id="contents" class="step" data-rel-x="500" data-rel-y="2500"
data-scale="4">
<ul style="margin-top:20%">
<li><img src="img/hilary.jpg" style="height:40px"/>
Exascale Workflow?</li>
<li><img src="img/hilary.jpg" style="height:40px"/>
Cylc (Re-)Introduction</li>
<li><img src="img/hilary.jpg" style="height:40px"/>
Exascale Challenges</li>
<li><img src="img/oliver.jpg" style="height:40px"/>
Meeting the Challenges of Exascale</li>
<li><img src="img/dave.jpg" style="height:40px"/>
Introduction to Rose</li>
</ul>
</div>
<!-- Prelude -->
<div id="prelude" class="step" data-rel-x="3000" data-rel-y="-3500">
<h1>Exascale Workflow??</h1>
<p><i>What do we mean by this?</i></p>
<div class="person">
<img src="img/hilary.jpg" />
<div class="text">
<span class="name">Hilary Oliver</span>
<br />
<span class="description">NIWA (NZ)</span>
</div>
</div>
</div>
<div class="step" data-rel-x=1500 data-rel-y=0>
<h1>Exascale Computing</h1>
<ul>
<li> early-mid 2020s?
<ul>
<li> Aurora - Argonne Lab USA, Cray, 2021?</li>
</ul>
</li>
<li> 1 exaflop = a quintillion (a billion billion) flops
<ul>
<li> approx. processing power of the human brain?</li>
<li> 1/10 flops per individual insect on planet earth!</li>
</ul>
</li>
<li> challenges?
<ul>
<li> hardware (and power 40MW = $US 40M/year)</li>
<li> software scaling</li>
<li> workflow?...</li>
</ul>
</li>
</ul>
<div class="notes">
<ul>
<li> at any given time, it is estimated that there are ten
quintillion (10,000,000,000,000,000,000) individual insects
alive on earth</li>
<li> my son once said his shoe size was 2 limes and a sandwich.</li>
</ul>
</div>
</div>
<div class="step" data-rotate="60">
<h1>Exascale Workflow?</h1>
<img src="img/exa-workflow-1.svg"
style="display:block; margin:auto"
alt="Exascale Workflow 1"/>
<p>(we've got this covered)</p>
<div class="notes">
</div>
</div>
<div class="step image" data-rotate="60">
<img src="img/stormtrooper-duck.png"
alt="Exascale Workflow 2"
style="width:100%; position:absolute; top:15%"/>
<div style="position:absolute; left:65%; top:50%; width:290px;
font-size:90%">
workflow automation is critical to utilizing these massive
rescources
</div>
<div class="notes">
<p>Even if you think the primary purpose of these machines is for
massive exascale models, much of the time will still be spent
running ensembles of (somewhat) smaller models, and processing the
vast amounts of data generated by them....</p>
</div>
</div>
<div class="step image" data-rotate="30">
<img src="img/mo-exascale-prog-scope.png"
style="width:100%; margin-top:15%"
alt="MO Exascale Scope"
class="right"/>
<div class="notes">
</div>
</div>
<!-- Introduction -->
<div id="intro" class="step" data-rel-x="0" data-rel-y="1000"
data-rel-to="prelude">
<h1>Cylc (Re-)Introduction</h1>
<p><i>The Cylc Workflow Engine</i></p>
<div class="person">
<img src="img/hilary.jpg" />
<div class="text">
<span class="name">Hilary Oliver</span>
<br />
<span class="description">NIWA (NZ)</span>
</div>
</div>
<br />
<br />
<ul>
<li> cycling workflows </li>
<li> workflow definition </li>
<li> architecture </li>
<li> user interface </li>
</ul>
<div class="notes">
Why cycling workflows?
<ul>
<li> real time environmental forecasting </li>
<li> and running the same systems off-the-clock</li>
<li> split long model integrations into many smaller chunks</li>
<li> steps in some iterative processes (e.g. model parameter tuning)</li>
<li> process a series of datasets</li>
<li> with <i>pipeline parallelism</i> (or better)</li>
</ul>
</div>
</div>
<div class="step image" data-rel-x="1500" data-rel-y="0" data-rotate="10">
<img src="img/cycling-workflow-layer8.png"
style="position:absolute; height:100%; left:60px"
alt=""
class=""/>
<img src="img/cycling-workflow-layer7.png"
style="position:absolute;height:100%; left:60px"
alt=""
class="substep"/>
<img src="img/cycling-workflow-layer6.png"
style="position:absolute; height:100%; left:60px"
alt=""
class="substep"/>
<img src="img/cycling-workflow-layer5.png"
style="position:absolute; height:100%; left:60px"
alt=""
class="substep"/>
<img src="img/cycling-workflow-layer4.png"
style="position:absolute; height:100%; left:60px"
alt=""
class="substep"/>
<img src="img/cycling-workflow-layer3.png"
style="position:absolute; height:100%; left:60px"
alt=""
class="substep"/>
<img src="img/cycling-workflow-layer2.png"
style="position:absolute; height:100%; left:60px"
alt=""
class="substep"/>
<img src="img/cycling-workflow-layer1.png"
style="position:absolute; height:100%; left:60px"
alt=""
class="substep"/>
<div class="notes">
</div>
</div>
<div class="step image" data-rotate="20">
<img src="img/animation-key-1.png" style="height:100%; margin-left:18%"
alt="animation key"
class="center"/>
<div class="notes">
</div>
</div>
<div class="step image" data-rotate="30">
<video onclick="this.paused ? this.play() : this.pause();"
style="width:100%; margin-top:20px">
<source src="img/cycling-workflow-10-retries.webm">
Your browser does not support webm video
</video>
<div class="notes">
</div>
</div>
<div class="step image" data-rotate="30">
<img src="img/dep-two-cycles.svg"
style="position:absolute; width:100%; top:10%"
alt=""
class=""/>
<img src="img/timeline-three-a.svg"
style="position:absolute; top:60%; width:100%"
alt=""
class="substep"/>
<img src="img/timeline-three.svg"
style="position:absolute; top:60%; width:100%"
alt=""
class="substep"/>
<div class="notes">
</div>
</div>
<div class="step">
<h2>What is Cylc (currently) Like?</h2>
<ul>
<li>complex "macro-scale" cycling workflows in HPC</li>
<li>text config file (with programmatic templating)
<ul>
<li>treat workflow definitions like source code</li>
<li>efficient: shared config, graph notation, families.</li>
</ul>
<li>flexible and general
<ul>
<li>ANY date-time or integer cycling sequence</li>
<li>use any command, script, or program, as a task</li>
<li>makes no assumptions about data movement</li>
</ul>
</li>
<li>distributed architecture - no central server</li>
</ul>
<div class="notes">
Note a workflow is primarily a configuration of the workflow engine,
and a config file is easier for most users and most use cases than
programming to a Python API. However, ...!
Cylc is not currently so well suited to large numbers of small
quick-running jobs (later...)
</div>
</div>
<div class="step image">
<img src="img/cylc-arch.png" style="width:100%; margin-top:40px" alt=""/>
<div class="notes">
</div>
</div>
<div class="step image">
<img src="img/gcylc-1.png"
style="position:absolute; width:100%; top:25px"
alt=""
class=""/>
<img src="img/gcylc-3.png"
style="position:absolute; width:100%; top:25px"
alt=""
class="substep"/>
<img src="img/gscan.png"
style="position:absolute; width:100%; top:25px"
alt=""
class="substep"/>
<div class="notes">
</div>
</div>
<div class="step" data-rotate="30">
<img src="img/hello.svg"
style="width:35%; position:absolute; top:35%; right:0"
alt="MO Exascale Scope"/>
<pre><code class="ini" style="position:absolute; top:0">
# Hello World! Plus
[scheduling]
[[dependencies]]
graph = "hello => farewell & goodbye"
</code></pre>
<pre class="substep"><code class="ini" style="position:absolute; top:0">
# Hello World! Plus
[scheduling]
[[dependencies]]
graph = "hello => farewell & goodbye"
[runtime]
[[hello]]
script = echo "Hello World!"
</code></pre>
<pre class="substep"><code class="ini" style="position:absolute; top:0">
# Hello World! Plus
[scheduling]
[[dependencies]]
graph = "hello => farewell & goodbye"
[runtime]
[[hello]]
script = echo "Hello World!"
[[[environment]]]
# ...
[[[remote]]]
host = hpc1.niwa.co.nz
[[[job]]]
batch system = PBS
# ...
# ...
# ...
</code></pre>
<div class="notes">
Plus:
<ul>
<li>[runtime] is an inheritance heirarchy for efficient sharing of
common settings
</li>
</ul>
</div>
</div>
<div class="step" data-rotate="30">
<img src="img/hello-0.svg"
style="width:35%; margin-top:10%; display:block; position:absolute;
right:0"
alt=""/>
<img src="img/hello.svg"
style="width:35%; margin-top:10%; display:block; position:absolute;
right:0"
class="substep"
alt=""/>
<pre><code class="ini">
#!Jinja2
{% set SAY_BYE = false %}
[scheduling]
[[dependencies]]
graph = """hello
{% if SAY_BYE %}
=> goodbye & farewell
{% endif %}
"""
[runtime]
# ...
</code></pre>
<div class="notes">
</div>
</div>
<div class="step image" data-rotate="90">
<img src="img/ensemble1.svg"
style="position:absolute; top:20%; width:30%"
alt=""/>
<img src="img/ensemble2.svg"
style="position:absolute; top:5%; right:0; width:55%"
alt=""
class="substep"/>
<img src="img/ens_plain.svg"
style="position:absolute; bottom:0; right:0; width:60%"
alt=""
class="substep"/>
<div class="notes">
</div>
</div>
<div class="step" data-rotate="40">
<img src="img/param-simple.svg"
style="width:50%; margin-left:25%"
alt="" class=""/>
<pre><code class="ini">[[dependencies]]
graph = "pre => sim<M> => post<M> => done"
# with M = 1..5</code></pre>
<img src="img/params-5.svg"
style="width:50%; margin-left:25%"
alt="" class=""/>
<div class="notes">
</div>
</div>
<div class="step" data-rotate="-30">
<img src="img/param-simple-2.svg"
style="width:70%; margin-left:15%"
alt="" class=""/>
<pre><code class="ini" style="font-size:20px">[[dependencies]]
graph = "prep => init<R> => sim<R,M> => post<R,M> => close<R> => done"
# with M = a,b,c; and R = 1..3</code></pre>
<img src="img/params-5-2.svg"
style="width:86%; margin-left:7%"
alt="" class=""/>
<div class="notes">
</div>
</div>
<div class="step" data-rotate="30">
<div style="display:block; position:absolute; top:0">
<pre><code class="ini">
[cylc]
cycle point format = %Y-%m
[scheduling]
initial cycle point = 2010-01
[[dependencies]]
[[[R1]]]
graph = "prep => foo"
</code></pre>
<div class="notes">
</div>
</div>
<div class="substep" style="display:block; position:absolute; top:0">
<pre><code class="ini">
[cylc]
cycle point format = %Y-%m
[scheduling]
initial cycle point = 2010-01
[[dependencies]]
[[[R1]]]
graph = "prep => foo"
[[[P1M]]]
graph = "foo[-P1M] => foo => bar & baz => qux"
</code></pre>
</div>
<div class="substep" style="display:block; position:absolute; top:0;">
<pre><code class="ini">
[cylc]
cycle point format = %Y-%m
[scheduling]
initial cycle point = 2010-01
[[dependencies]]
[[[R1]]]
graph = "prep => foo"
[[[P1M]]]
graph = "foo[-P1M] => foo => bar & baz => qux"
[[[R2/^+P2M/P1M]]]
graph = "baz & qux[-P2M] => boo"
</code></pre>
</div>
<div class="notes">
</div>
</div>
<div class="step image" data-rotate="90">
<img src="img/cycling-suiterc-example.svg"
style="height:100%; margin-left:10%"
alt="">
<div class="notes">
</div>
</div>
<!-- Exascale I -->
<div id="exa1" class="step" data-rel-x="0" data-rel-y="1000"
data-rel-to="intro">
<h1>Exascale Challenges</h1>
<p><i>Present capabilities and challenges</i></p>
<div class="person">
<img src="img/hilary.jpg" />
<div class="text">
<span class="name">Hilary Oliver</span>
<br />
<span class="description">NIWA (NZ)</span>
</div>
</div>
</div>
<div class="step image" data-rel-x="1500" data-rel-y="0">
<img src="img/gcylc-3.png"
style="width:100%; margin-top:25px"
alt=""
class=""/>
<div class="notes">
</div>
</div>
<div class="step" data-rotate="30">
<h2>Immediate: Web GUIs, Python 3</h2>
<img src="img/cylc-web-arch.png"
style="position:absolute; right:0; top:25%"
alt=""/>
<div style="position:absolute; width:60%">
<ul>
<li>Python 2 is near end of life</li>
<li>PyGTK GUIs are near obsolete</li>
</ul>
<ul>
<li> web GUI work starting
<ul>
<li>need new architecture!</li>
</ul>
</li>
</ul>
</div>
<div class="notes">
</div>
</div>
<div class="step image" data-rotate="60">
<img src="img/stormtrooper-duck.png"
alt="Exascale Workflow 2"
style="width:100%; position:absolute; top:15%"/>
<div style="position:absolute; left:65%; top:50%; width:310px">
THEN: scaling; config API; visualization;
light sub-suites...
</div>
<div class="notes">
<p>Even if the primary purpose of these machines is for massive
exascale models, much of the time will still be spent running
large numbers of smaller models, and associated data processing.</p>
</div>
</div>
<div class="step image">
<img src="img/nzlam-ungrouped-2.svg"
style="position:absolute; top:10%; width:100%;"
alt=""
class=""/>
<div class="notes">
A typical small regional determistic NWP suite, 3 cycles. Obs
processing tasks in yellow. A few tasks generate thousands of products
en masse, from a few large model output files.
</div>
</div>
<div class="step image" >
<img src="img/nzlam-m10.svg"
style="margin-left:35%; height:100%"
alt=""
class=""/>
<div class="notes">
... now a 10-member ensemble, ~450 tasks (3 cycles).
</div>
</div>
<div class="step image" data-rotate="70">
<img src="img/nzlam-m30.png"
style="position:absolute; top 0; left:40%; height:100%"
alt=""
class=""/>
<img src="img/nzlam-m30-zoom.png"
style="position:absolute; top 0; left:20px; height:100%"
alt=""
class="substep"/>
<div class="notes">
... now a 30-member ensemble, ~1300 tasks (3 cycles).
</div>
</div>
<div class="step" data-rotate="60">
Easily construct and control ensemble-type Cylc workflows of
thousands of tasks per cycle
<ul>
<li> Tested sans GUI at 50k tasks! (need lots of RAM)</li>
</ul>
BUT a problem use case has emerged to point the way: processing
<i>incremental outputs</i> from model ensembles, for
verification and product generation
<ul>
<li>multi-dimensional dynamic cycling</li>
<li>or light-weight sub-suites</li>
<li>bunching many small tasks ... with dependencies</li>
<li>automatic reconfiguring of huge suites</li>
</ul>
<div class="notes">
<ul>
<li>Met Office IMPROVER: 100k <i>jobs</i> per cycle.</li>
</ul>
</div>
</div>
<div class="step image" data-rotate="10">
<div style="position:absolute; background:rgb(215,215,215); height:100%;
width:100%">
<img src="img/ensemble-post-0.svg"
style="margin-left:20%; height:100%"
alt=""
class=""/>
</div>
<div style="position:absolute; background:rgb(215,215,215); height:100%;
width:100%" class="substep">
<img src="img/ensemble-post-1.svg"
style="width:100%; margin-top:100px"
alt=""/>
</div>
<div style="position:absolute; background:rgb(215,215,215); height:100%;
width:100%" class="substep">
<img src="img/ensemble-post-2.svg"
style="width:100%; margin-top:100px"
alt=""/>
</div>
<div class="substep" style="position:absolute; bottom:200px; color:hotpink">
1 model, 2 files/hour for 10 model-hours, 1 task/file ...
</div>
<div class="substep" style="position:absolute; bottom:50px">
<br/>
30 members, 7 files/hour for 10 model-days, 5 task/file ... <br/>
<span style="color:deeppink">30 x 7 x (24x10) x 5 = 250,000 jobs per
cycle!</span>
</div>
<div class="notes">
5 tasks per file: each of the pink blobs is a workflow!
</div>
</div>
<div class="step">
0.25M tasks per cycles is way too much for Cylc.
<ul>
<li> these tasks totally dominate the workflow</li>
<li> parameterized "cycle" over forecast hour (1...240)</li>
<li>can't use efficient dynamic cycling (nested!)</li>
<li> for now a lot of <i>bunching</i> is required</li>
<li> or <i>sub-suites</i>, but:
<ul>
<li> 30+ suites (per cycle) instead of 1 suite!</li>
<li> log directory housekeeping?</li>
<li> start-up, kill, restart, failure recovery etc.?</li>
</ul>
</li>
</ul>
<div class="notes">
<ul>
<li> cylc can have multiple "top-level" cycling sequences in one
suite</li>
<li> but not nested cycling</li>
<li>NOTE: the HPC infrastructure can't handle this yet either!</li>
</div>
</div>
<div class="step">
<h3>actually it's worse than this!</h3>
Real post-processing systems may:
<ul>
<li>aggregate output from multiple model suites </li>
<li>have complex verification + product-generation workflows that are
not bunching-friendly</li>
<li>require dynamic re-configuration to swap products in and out</li>
</ul>
<div class="notes">
<ul>
<li> cylc can have multiple "top-level" cycling sequences in one
suite</li>
<li> but not nested cycling</li>
</div>
</div>
<div class="step">
<h3>... the future of cylc</h3>
(Oliver)
<ul>
<li>general efficiency (e.g. don't hold job config in memory)</li>
<li>event-driven and spawn on demand</li>
<li>light-weight scheduler kernel for light-weight "sub-suites" that
don't generate all the usual log files</li>
<li>Python API </li>
<li>self-assembling workflow from task inputs and outputs </li>
</ul>
</div>
<!-- Exascale II -->
<div id="exa2" class="step" data-rel-x="0" data-rel-y="1000"
data-rel-to="exa1">
<h1>Meeting Exascale Challenges</h1>
<p><i>An outline of some potential pathways for future development</i></p>
<div class="person">
<img src="img/oliver.jpg" />
<span class="name">Oliver Sanders</span>
<br />
<span class="description">Met Office (UK)</span>
</div>
</div>
<div id="exa2-outline" class="step" data-rel-x="1500" data-rel-y="200">
<object data="img/bigger.svg" type="image.svg+xml" height="1800px">
</object>
</div>
<div id="exa2-outline-bigger" class="step" data-rel-x="1000" data-rel-y="0">
</div>
<div id="exa2-outline-bigger2" class="step" data-rel-x="1000" data-rel-y="0">
</div>
<div id="exa2-vis" class="step" data-rel-x="2200" data-rel-y="-240"
data-scale="0.10" data-rel-to="exa2-outline">
<!-- <h2>The Visualisation Problem</h2>-->
<!-- <center>-->
<!-- <object id="graph" data="img/global.svg" type="image/svg+xml">-->
<!-- </object>-->
<!-- [><object id="graph" data="img/nzlam-m30.svg" type="image/svg+xml"<]-->
<!-- [> width="1000px" height="600px"><]-->
<!-- </object>-->
<!-- </center>-->
<!-- <span class="substep" id="graph-zoom-1"></span>-->
<!-- <span class="substep" id="graph-zoom-2"></span>-->
<!-- <span class="substep" id="graph-zoom-3"></span>-->
<!--</div>-->
<!--<div id="exa2-vis1" class="step" data-rel-x="150" data-rel-y="0"-->
<!-- data-scale="0.10">-->
<h2>New Cylc GUI</h2>
<img width="250px" height="250px" src="img/html5.png">
<img width="180px" height="250px" src="img/css3.png">
</div>
<div id="exa2-vis2" class="step" data-rel-x="75" data-rel-y="0"
data-scale="0.10">
<h3>Combine <i>gscan</i> & <i>gcylc</i></h3>
<img class="full" src="img/gui-gscan-gcylc.png"/>
</div>
<div id="exa2-vis3" class="step" data-rel-x="75" data-rel-y="0"
data-scale="0.10">
<h3>View N Edges To Selected Node</h3>
<img class="full substep flash"
src="img/gui-graph-limited-nodes-1.svg"
style="position:absolute;" />
<img class="full substep flash"
src="img/gui-graph-limited-nodes-2.svg"
style="position:absolute;" />
<!-- TODO - export on a computer with better font support -->
</div>
<div id="exa2-vis4" class="step" data-rel-x="80" data-rel-y="0"
data-scale="0.10">
<h3>Alternative Views</h3>
<img class="full" src="img/gant.png" />
</div>
<div id="exa2-vis5" class="step" data-rel-x="60" data-rel-y="0"
data-scale="0.10">
<h3>Selecting Tasks Between Views</h3>
<!-- TODO - remove image background -->
<img height="380px" src="img/gui-matrix.png" />
</div>
<div id="exa2-writ-pre" class="step" data-rel-x="-800"
data-rel-y="150" data-rel-to="exa2-bigger">
</div>
<div id="exa2-writ" class="step" data-rel-x="2200" data-rel-y="-110"
data-scale="0.10" data-rel-to="exa2-outline">
<h2>The Modularity Problem</h2>
<ul>
<li>We can split the suite.rc into multiple files but...</li>
<li>Suites are monolithic</li>
<li>Developing components in isolation is difficult</li>
</ul>
</div>
<div id="exa2-writ1" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<p>It's hard to incorporate a module into a workflow</p>
<img width="1000px" src="img/sub-workflow-current.png" />
</div>
<div id="exa2-writ2" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<p>Ideally we would write dependencies to/from the module itself
rather than the tasks within it</p>
<img width="1000px" src="img/sub-workflow.png" />
</div>
<div id="exa2-writ3" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<p>Workflows could be represented as tasks</p>
<img width="500px" src="img/sub-workflow-collapsed.png" />
<pre>foo => baz => module<param> => pub</pre>
</div>
<!--<div id="exa2-writ4" class="step" data-rel-x="110" data-rel-y="0"-->
<!-- data-scale="0.10">-->
<!-- <p>Advantages of workflow modules:</p>-->
<!-- <ul>-->
<!-- <li>Re-usable workflow components</li>-->
<!-- <li>The parent workflow remains simple</li>-->
<!-- <li>Programmatic logic at the correct level (workflow/module)</li>-->
<!-- </ul>-->
<!--</div>-->
<div id="exa2-writ5" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<h3>Alternative Scheduling Paradigms</h3>
<div style="float: left; margin: 0 50px 0 0;">
<div class="bubble">Abstract dependency</div>
<code style="opacity: 0.7"><pre>foo => bar => baz</pre></code>
</div>
<div style="float: left; margin: 0 50px 0 0;">
<div class="bubble">Data dependency</div>
<code style="opacity: 0.7"><pre>foo:
out: a
bar:
in: a
out: b
baz:
in: a, b
out: c</pre></code>
</div>
<ul>
<li>Compute resource dependency?</li>
<li>Others?</li>
</ul>
</div>
<div id="exa2-writN" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<h3>Python API</h3>
<p>For truly programmatic problems Jinja2 doesn't quite cut it!</p>
TODO - this
</div>
<div id="exa2-writ-pre" class="step" data-rel-x="-800"
data-rel-y="150" data-rel-to="exa2-bigger">
</div>
<!-- TODO insert slides with profiling results -->
<div id="exa2-run1" class="step" data-rel-x="2200" data-rel-y="40"
data-scale="0.10" data-rel-to="exa2-outline">
<h3>Scaling With Dependencies</h3>
<p>Cylc can currently scale to tens of thousands of tasks and
dependencies</p>
<p>But there are limitations, for example:</p>
</div>
<div id="exa2-run2" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<img height="60%" src="img/many-to-many.png" />
<p>Many to many triggers result in NxM dependencies</p>
</div>
<div id="exa2-run3" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<img height="60%" src="img/many-many-as-one.png" />
<p>Cylc should be able to represent this as a single dependency</p>
</div>
<div id="exa2-run4" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<p>Our ambition is to work towards a leaner Cylc which can efficiently
scale to the largest suites</p>
<p>We plan to reimplement the Cylc scheduling algorithm to a more
<i class="emph">efficient</i> and <i class="emph">flexible</i> model
to solve problems like this</p>
</div>
<div id="exa2-run5" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<h3>Kernel - Shell Architecture</h3>
<center>
<p>Working towards a leaner Cylc we plan to separate the codebase into
a Kernel - Shell model</p>
<table>
<tr>
<td><div class="bubble">Shell</div></td>
<td><div class="bubble">Kernel</div></td>
</tr>
<tr>
<td class="emph">User Commands</td>
<td class="emph1">Scheduler</td>
</tr>
<tr>
<td class="emph">Suite Configuration</td>
<td class="emph1">Job Submission</td>
</tr>
</table>
</center>
</div>
<div id="exa2-run6" class="step" data-rel-x="110" data-rel-y="0"
data-scale="0.10">
<h3>Batching Jobs</h3>
<div style="float:left;">
<p>Horizontal Batching</p>
<img height="380px" src="img/batched-jobs-2.png" />
</div>
<div style="float:left;">
<p>Arbitrary Batching</p>
<img height="380px" src="img/batched-jobs-3.png" />
</div>
</div>
<div id="exa2-summary" class="step" data-rel-x="3700" data-rel-y="0"
data-rel-to="exa2-outline">
<h2>Future Challenges</h2>
<ul>
<li>Container technology<li>
<li>Computing in the cloud</li>
<li>File system usage</li>
</ul>
</div>
<!-- Rose -->
<div id="rose" class="step" data-rel-x="0" data-rel-y="1000"
data-rel-to="exa2">
<h1>Introduction to Rose</h1>
<p><i>Storage and configuration of complex Cylc workflows</i></p>
<div class="person">
<img src="img/dave.jpg" />
<div class="text">
<span class="name">David Matthews</span>
<br />
<span class="description">Met Office (UK)</span>
</div>
</div>
</div>
<div id="rose-history" class="step" data-rel-x="1500" data-rel-y="0">
<h2>History</h2>
<p>Development started late 2011 around the time we chose cylc as our workflow tool</p>
</div>
<div id="rose-motivation" class="step" data-rel-x="1500" data-rel-y="0">
<h2>Motivation</h2>
<ul style="position: absolute" class="substep flash">
<li>GUI for application configuration</li>
<li>Suite version control & identification</li>
<li><i>Enable support of multiple workflow tools</i></li>
<ul>
<li><i>Cylc may not have worked out?</i></li>
<li></i>Collaborators might require other tools?</i></li>
</ul>
<li><i>Provide essential features which were outside of the Cylc vision</i></li>
</ul>
<ul style="position: absolute" class="substep flash">
<li>GUI for application configuration</li>
<li>Suite version control & identification</li>
<li class="strike"><i>Enable support of multiple workflow tools</i></li>
<ul>
<li class="strike"><i>Cylc may not have worked out?</i></li>
<li class="strike">
</i>Collaborators might require other tools?</i></li>
</ul>
<li class="strike">
<i>Provide essential features which were outside of the Cylc
vision</i></li>
</ul>
</div>
<div id="rose-move-to-cylc" class="step" data-rel-x="1500" data-rel-y="0">
<p>Tools which have moved / will move into Cylc</p>
<ul>
<li style="color:rgb(0,150,0)">Log file retrieval</li>
<li style="color:rgb(0,150,0)">Email notifications</li>
<li style="color:rgb(0,0,150)">
rose bush - log file viewer</li>
<li style="color:rgb(0,0,150)">
rose suite-run - suite installation</li>
<li style="color:rgb(150,0,0)">
rose host-select -> cluster support</li>
<li style="color:rgb(150,0,0)">
rose bunch - run multiple small tasks in one job</li>
<li style="color:rgb(150,0,0)">Housekeeping</li>
</ul>
</div>