forked from johnpolacek/scrolldeck.js
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
997 lines (757 loc) · 20.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
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"/>
<title>ansible for nclug</title>
<link rel="stylesheet" href="css/normalize.css" type="text/css"/>
<link rel="stylesheet" href="css/style.css" type="text/css"/>
<link rel="author" href="plus.google.com/107232890922656215803"/>
<script src="js/jquery-1.8.2.min.js"></script>
<script src="js/jquery.scrollTo-1.4.3.1.min.js"></script>
<script src="js/jquery.scrollorama.js"></script>
<script src="js/jquery.easing.1.3.js"></script>
<script src="js/jquery.scrolldeck.js"></script>
</head>
<body>
<div class="slide" id="landing">
<h2>introduction to</h2>
<h1><a href="http://docs.ansible.com/">Ansible</a><span style="font-size:50%">,</span></h1>
<h2>by example</h2>
<br>
<br>
<br>
<br>
<hr width="25%">
<h2>Brian Grossman</h2>
<hr width="25%">
<br>
<a href="https://github.com/bugi/deck-nclug-ansible">https://github.com/bugi/deck-nclug-ansible</a>
<div class="page" style="font-size:2rem">0</div>
</div>
<div class="slide" id="what is ansible">
<!--
-x- Here's what I plan to cover.
-x- A bit about ansible and the problem space it covers.
-x- Then some examples.
-->
<h1>coverage</h1>
<br>
<div class="centerable">
<ul>
<li><a href="#about">about ansible</a><ul></ul></li>
<li>examples<ul>
<li><a href="#modes.cli">command line one-offs</a></li>
<li><a href="#modes.playbook">playbooks</a></li>
<!--
<li>a complex example</li>
-->
</ul></li>
<li><a href="#inventory">inventory</a><ul></ul></li>
<li><a href="#getting.started">getting started</a><ul></ul></li>
<!--
<li><a href="#end.notes">resources and references</a><ul></ul></li>
-->
</ul>
</div>
<div class="page" style="font-size:2rem">1</div>
</div>
<a id="intro"></a>
<div class="slide" id="ansible is">
<!--
-x- Ansible addresses much the same problem space
-x- as several other tools.
-x-
-x- Is everyone familiar with some of these?
-x-
-x- Ansible is a tool for automating
-x- * deployment
-x- * configuration
-x- * orchestration
-x-
-x-
-x- The main difference between these tools and ansible is...
-->
<h1>tl;dr</h1>
<br>
<div class="centerable">
<ul>
<li>Ansible is similar to<ul>
<li>puppet</li>
<li>salt</li>
<li>chef</li>
<li>rex</li>
<li>cfengine</li>
</ul>
<li><div class="animate-build" data-build="1">
Ansible is
a tool for automating<ul>
<li><i>deployment</i> of software and systems</li>
<li><i>configuration</i> of software and systems</li>
<li><i>orchestration</i> of deployment and configuration</li>
</ul>
</div>
</li>
</ul>
</div>
<div class="page" style="font-size:2rem">2</div>
</div>
<div class="slide" id="ansible is awesome">
<!--
-x- ... that I like ansible better than I like those.
-x-
-x- I hope that after a little more review then some
-x- examples you'll see why.
-x-
-x- I've tried most of those other tools.
-x- I've rolled my own.
-x-
-x-
-x- Ansible is far and away the best automation tool I've used.
-x-
-x- It's quick to get started with.
-x- It applies well to tasks both large and small.
-x- It has minimal infrastructure requirements.
-x-
-x-
-x- I'll touch more on some of these later.
-->
<!--
<h1>ansible is awesome</h1>
-->
<h2>&hype;</h2>
<br>
<div class="centerable">
<ul>
<li>Ansible is<ul>
<li>quick to <a href="http://docs.ansible.com/intro.html">get started with</a></li>
<li>easy to use day to day</li>
<li>useful for big tasks and little</li>
<li>powerful</li>
<li>minimal infrastructure requirement</li>
</ul>
</ul>
</div>
<br>
<br>
<br>
<h1 style="color:pink">❤ • ❤ • ❤</h1>
<div class="page" style="font-size:2rem">3</div>
</div>
<div class="slide" id="what is ansible">
<!--
-x- Compared to most similar tools, ansible is quite young.
-x- I started applying it in earnest about a year ago, and
-x- can happily report that the rough edges are now pretty
-x- well smoothed.
-x-
-x- Here's a few things that set ansible apart.
-x-
-x- It just needs ssh and python.
-x-
-x- It's agentless, so you push rather than pull.
-x- Among other things, that means you don't have to
-x- worry about all the puppet daemons hitting your repo
-x- all at once.
-x-
-x- You tell it the desired states in yaml.
-x- That's infrastructure as data.
-x- Your infrastructure is in version control.
-x- Your infrastructure is repeatable.
-x-
-->
<h1>how ansible is different</h1>
<br>
<div class="centerable">
<ul>
<li>new on the scene: 2012<ul></ul></li>
<li>minimal infrastructure: ssh and python<ul></ul></li>
<li>push / agentless<ul>
<!--
<li>most others are pull</li>
<li>ansible can also pull, but push is the norm</li>
-->
</ul></li>
<li>yaml<ul>
<li>desired states are specified in yaml</li>
<li>yaml is easy to read and write</li>
<!--
<li>salt also uses yaml, but not as well IMO</li>
-->
</ul></li>
<li>python<ul>
<li>base is python</li>
<!--
<li>modules just have to talk JSON</li>
-->
</ul></li>
</ul>
</div>
<div class="page" style="font-size:2rem">4</div>
</div>
<div class="slide" id="prerequisites">
<!--
-x- Here's a little more detail on prerequisites.
-x-
-x- One nice thing about few prerequisites is that
-x- it's very compatible.
-x-
-x- Even so, there are caveates.
-x-
-x- (switch)
-x-
-x- Be careful if you're using an ancient python.
-x- Python-simplejson is included with 2.5 and later.
-x-
-x- Centos 6 and earlier use an ancient openssh, so won't
-x- do ansible justice in speed.
-x-
-->
<h1>prerequisites</h1>
<br>
<div class="centerable">
<ul>
<li>ssh</li>
<li>python 2.[67] for control host</li>
<li>python 2.[4-7] for managed nodes</li>
</ul>
<div class="animate-build" data-build="1">
<br>
<h1>caveats</h1>
<br>
<ul>
<li>add python-simplejson if python ≤ 2.5<ul></ul></li>
<li>epel ≤ 6 have an ancient openssh<ul>
<li>without ControlPersist,</li>
<li>so it won't be as fast</li>
</ul></li>
</ul>
</div>
</div>
<div class="page" style="font-size:2rem">5</div>
</div>
<div class="slide" id="modes.cli">
<!--
-x- Ansible has two main usages, command-line and playbooks.
-x-
-x- Playbooks is where you get into orchestration.
-x-
-x- Command-line mode is more like a batch-mode parallel ssh.
-x- It's handy for one-offs and for learning.
-x-
-x- Speaking of which...
-x-
-x-
-x-
-x-
-->
<h1>modes</h1>
<br>
<div class="centerable">
<ul>
<li><b>straight command-line
<br>(for simple one-offs)
<br>
<br>
</b>
</li>
<li>playbooks
<br>(for complex tasks and orchestration)
</li>
</ul>
</div>
<div class="page" style="font-size:2rem">6</div>
</div>
<div class="slide" id="eg.cli">
<!--
-x- ... for your first example
-x-
-x- ... PING!
-x- I should note that this isn't an ICMP ping, but
-x- just checks that the communication channel works as
-x- expected.
-x-
-x-
-x- Second up is asking the remote host its name.
-x-
-x- My laptop is called stomp.
-x-
-x-
-x- In both cases we're talking to localhost.
-x-
-x- The default module that ansible will use in command-line mode
-x- is the "command" module.
-x-
-x- Here's a couple more examples.
-x-
-x-
-->
<h1>command-line</h1>
<div class="animate-build" data-build="1">
••• ping •••
<br>
••• (ssh, not ICMP) •••
<blockquote><pre>
% ansible localhost -m ping
<div style="color:green">localhost | success >> {
"changed": false,
"ping": "pong"
}</div></pre></blockquote>
</div>
<br>
<div class="animate-build" data-build="2">
••• who are you? •••
<blockquote><pre>
% ansible localhost -m command -a hostname
<div style="color:green">localhost | success | rc=0 >>
stomp</div></pre></blockquote>
</div>
<div class="page" style="font-size:2rem">7</div>
</div>
<div class="slide" id="eg.cli.2">
<!--
-x- Here's how to bootstrap your ancient python into
-x- speaking json. Only the "raw" module can do this.
-x- It's very limited.
-x-
-x- The "shell" module is like the system(3) system call,
-x- while the command and raw modules are more like exec(3).
-x-
-->
<br>
••• raw for when the remote doesn't have a sane python •••
<div class="animate-build" data-build="2">
(oh wait, this is Debian)
</div>
<div class="animate-build" data-build="1" data-animation="fly-in-left">
<blockquote><pre>
% ansible localhost -m raw -a 'yum install python-simplejson -y'
<div style="color:red">localhost | FAILED | rc=127 >>
/bin/sh: 1: yum: not found</div></pre></blockquote>
</div>
<br>
••• command is the default module (-m) •••
<div class="animate-build" data-build="3" data-animation="fly-in-right">
••• or there's shell •••
<blockquote><pre>
% ansible localhost -m shell -a 'hostname > /tmp/j ; cat /tmp/j'
<div style="color:green">localhost | success | rc=0 >>
stomp</div></pre></blockquote>
</div>
<div class="page" style="font-size:2rem">8</div>
</div>
<div class="slide">
<!--
-x- Those three modules are special. Unlike just about all
-x- the others, they're not idempotent.
-x-
-x- But idempotence is important. In fact here's a whole
-x- slide on idempotence.
-x-
-x- Idempotence means that ansible will avoid making a
-x- change unless it's actually needed. Such modules
-x- can be run more than once without ill effect.
-x-
-x-
-x- For example...
-->
<h1>idempotence</h1>
<h3>(not unique to ansible)</h3>
<h3>(but important)</h3>
<br>
<br>
<div class="centerable" style="width: 70%;">
<ul>
<li>Modules are idempotent.</li>
<li>They will seek to avoid changing the
system unless a change needs to be made.</li>
<li>They can safely be run more than once.</li>
</ul>
<br>
(The shell module and friends are not idempotent.)
</div>
<div class="page" style="font-size:2rem">9</div>
</div>
<div class="slide">
<!--
-x- There's a module to set a line in a file.
-x-
-x- Earlier we put our hostname into /tmp/j.
-x- Now we'll edit that file.
-x-
-x- Notice how the returned json says that the
-x- action caused change.
-x-
-->
<h2>set a line in a file</h2>
<br>
<div class="animate-build" data-build="1">
<blockquote><pre>
% cat /tmp/j
stomp
% ansible localhost -m lineinfile -a 'regexp=^st line=st0mp dest=/tmp/j'
<div style="color:green">localhost | success >> {
"backup": "",
"changed": <font size="5rem"><b>true</b></font>,
"msg": "line replaced"
}</div>
% cat /tmp/j
st<font size="5rem">0</font>mp</pre></blockquote>
</div>
<div class="page" style="font-size:2rem">10</div>
</div>
<div class="slide">
<!--
-x- Here's the same thing again.
-x-
-x- But ansible says it didn't change anything.
-x-
-x- It didn't just write over the file with the same thing.
-x- It noticed that the file wouldn't be changed by
-x- the action, so no action was necessary.
-x-
-x-
-->
<h2>again</h2>
<br>
<blockquote><pre>
% cat /tmp/j
st0mp
% ansible localhost -m lineinfile -a 'regexp=^st line=st0mp dest=/tmp/j'
<div style="color:green">localhost | success >> {
"backup": "",
"changed": <font size="5rem"><b>false</b></font>,
"msg": ""
}</div>
% cat /tmp/j
st0mp</pre></blockquote>
<div class="page" style="font-size:2rem">11</div>
</div>
<div class="slide">
<!--
-x- Let's delete /tmp/j.
-x-
-x- In this case, the module is "file". You would
-x- also use file for chmod-ing and chown-ing
-x- and symlinking.
-x-
-x- Here we give file two arguments, the path of interest
-x- and what state we want it in.
-x-
-->
<h2>delete the file</h2>
<br>
<blockquote><pre>
% cat /tmp/j
st0mp
% ansible localhost -m file -a 'path=/tmp/j <b>state=absent</b>'
<div style="color:green">localhost | success >> {
"changed": <font size="5rem"><b>true</b></font>,
"path": "/tmp/j",
"state": "absent"
}</div>
% ls -l /tmp/j
/bin/ls: cannot access /tmp/j: No such file or directory</pre></blockquote>
<div class="page" style="font-size:2rem">12</div>
</div>
<div class="slide">
<!--
-x- Here's a couple more useful command-line tricks before
-x- we go on to playbooks.
-x-
-x- First, it's a lot easier to grep if you use one-line.
-x-
-x-
-->
<h2>again, with less noise</h2>
<br>
<blockquote><pre>
% ansible localhost -m file -a 'path=/tmp/j state=absent' \
<font size="6rem"><b>--one-line</b></font>
<div style="color:green;font-size:2.7rem;">localhost | success >> {"changed": <font size="5rem"><b>false</b></font>, "path": "/tmp/j", "state": "absent"}</div></pre></blockquote>
<div class="animate-build" data-build="1">
<br><br>
<h3>handy for groups of hosts</h3>
<blockquote><pre>
% ansible doublestomp -i hosts -a hostname --one-line |grep rc=0
localhost | success | <span style="color:red">rc=0</span> | (stdout) stomp
stomp | success | <span style="color:red">rc=0</span> | (stdout) stomp</pre></blockquote>
</div>
<div class="page" style="font-size:2rem">13</div>
</div>
<div class="slide">
<!--
-x- On the other hand, if you operate on a lot of hosts
-x- you might want to record the results for later
-x- processing. Meet the tree.
-x-
-x- Any questions before we move on to playbooks?
-->
<h2>or record for posterity</h2>
<br>
<blockquote><pre>
% ansible localhost -m file -a 'path=/tmp/j state=absent' \
--one-line <font size="6rem"><b>--tree=my_tree</b></font>
<div style="color:green;font-size:2.7rem;">localhost | success >> {"changed": false, "path": "/tmp/j", "state": "absent"}</div></pre></blockquote>
<div class="animate-build" data-build="1">
<blockquote><pre>
% find my_tree/ -type f
my_tree/localhost</pre></blockquote>
<blockquote><pre>
% cat my_tree/localhost
{
"changed": false,
"path": "/tmp/j",
"state": "absent"
}</pre></blockquote>
</div>
<div class="page" style="font-size:2rem">14</div>
</div>
<div class="slide" id="modes.playbook">
<!--
-x- Playbooks is where we get into orchestrating
-x- multiple tasks.
-x-
-->
<h1>modes</h1>
<br>
<div class="centerable">
<ul>
<li>straight command-line
<br>(for simple one-offs)
<br>
<br>
</li>
<li><b>playbooks
<br>(for complex tasks and orchestration)
</b>
</li>
</ul>
</div>
<div class="page" style="font-size:2rem">15</div>
</div>
<div class="slide" id="eg.playbook">
<!--
-x- Here's some yaml for you.
-x-
-x- There's our friend localhost.
-x- And some tasks for him.
-x- We'll delete his buddy /tmp/j
-x- and ask who ansible thinks he is.
-x-
-x- Note how each task gets a name.
-x- That's not actually required,
-x- but it's [* a really good idea *].
-->
<h1>playbook</h1>
<blockquote><pre>
% cat site.yml
---
- hosts: localhost
tasks:
- name: /tmp/j deserves this, honest
file: path=/tmp/j state=absent
- name: identify!
debug: msg="{{ inventory_hostname }}"
</pre></blockquote>
<div class="page" style="font-size:2rem">16</div>
</div>
<div class="slide">
<!--
-x- Ignore the GATHERING FACTS. That's just ansible
-x- figuring out where your ethernet ports are and whatnot.
-x- It can be turned off if you don't need it.
-x-
-x- First up, /tmp/j got deleted. That was a change though,
-x- so it's noted in orange.
-x-
-x- The second task though, I bet you expected the message
-x- to say stomp. In this case though it's localhost
-x- because that's what we called it. That's its
-x- inventory_hostname you might say.
-x-
-x- And we wouldn't want to ignore the summary.
-->
<blockquote><pre>
% echo st0mp > /tmp/j
</pre></blockquote>
<blockquote><pre>
% ansible-playbook -i hosts site.yml
PLAY [localhost] *************************************************
GATHERING FACTS **************************************************
<span style="color:green">ok: [localhost]</span>
TASK: [/tmp/j deserves this, honest] *****************************
<span style="color:orange">ok: [localhost]</span>
TASK: [identify!] ************************************************
<span style="color:green">ok: [localhost] => {
"msg": "localhost"
}</span>
PLAY RECAP *******************************************************
<span style="color:orange">localhost</span> : <span style="color:green">ok=3</span> <span style="color:orange">changed=1</span> unreachable=0 failed=0
</pre></blockquote>
<div class="page" style="font-size:2rem">17</div>
</div>
<div class="slide">
<!--
-x- Here's another playbook.
-x-
-x- Instead of listing tasks, we list a role.
-x- Using roles, we can split up tasks into reusable chunks.
-x-
-x- This role's pretty simple. It just has a couple of tasks.
-x-
-x- The tasks here first call stat, then tell us the result.
-->
<h1>another playbook</h1>
<blockquote><pre>
% cat site.yml
---
- hosts: doublestomp
gather_facts: False
roles:
- example2
</pre></blockquote>
<!--
<blockquote><pre>
% find roles/ -type f
roles/example2/tasks/main.yml
</pre></blockquote>
-->
<div class="animate-build" data-build="1">
<blockquote><pre>
% cat roles/example2/tasks/main.yml
---
- stat: path=/etc/hosts
register: st
- name: tell about it
debug: msg="{{ st.stat.pw_name }} {{ st.stat.md5 }}"
</pre></blockquote>
</div>
<div class="page" style="font-size:2rem">18</div>
</div>
<div class="slide">
<!--
-x- Pretty boring I know, but did you notice I used
-x- a group of hosts instead of just localhost?
-x-
-x- Incidentally, you can tell stat to not compute
-x- the md5. That's handy when you want to stat
-x- a large file.
-x-
-x- Now about that host group...
-->
<blockquote><pre>
% ansible-playbook -i hosts site.yml
PLAY [doublestomp] ******************************************************
TASK: [example2 | stat path=/etc/hosts] ************************
<span style="color:green">ok: [stomp]
ok: [localhost]</span>
TASK: [example2 | tell about it] *******************************
<span style="color:green">ok: [localhost] => {
"msg": "root 8745e97bcd300e2cb3d3e267e6ed01f8"
}
ok: [stomp] => {
"msg": "root 8745e97bcd300e2cb3d3e267e6ed01f8"
}</span>
PLAY RECAP *****************************************************
<span style="color:green">localhost : ok=2</span> changed=0 unreachable=0 failed=0
<span style="color:green">stomp : ok=2</span> changed=0 unreachable=0 failed=0
</pre></blockquote>
<div class="page" style="font-size:2rem">19</div>
</div>
<div class="slide" id="inventory">
<!--
-x- Here's the short version.
-x-
-x- I'm tired though.
-->
<h1>inventory</h1>
<blockquote><pre>
% cat hosts
[doublestomp]
localhost
stomp
</pre></blockquote>
<br>
<div class="centerable">
<ul>
<li>inventory docs<ul>
<li><a href="http://docs.ansible.com/intro_inventory.html">intro</a></li>
<li><a href="http://docs.ansible.com/developing_inventory.html">writing your own dynamic inventory</a>
</ul>
</ul>
</div>
<div class="page" style="font-size:2rem">20</div>
</div>
<div class="slide" id="getting.started">
<h1>where to start</h1>
<br>
<div class="centerable">
<ul>
<li>start here:
<a href="http://docs.ansible.com/">http://docs.ansible.com/</a>
</li>
<li>starter project: ansiblize your laptop</li>
</ul>
</div>
<div class="page" style="font-size:2rem">21</div>
</div>
<a id="end.notes"></a>
<div class="slide">
an introduction to<br>
<a href="http://docs.ansible.com/">Ansible</a>,<br>
by example<br>
<br>
<br>
<hr width="25%">
Brian Grossman<br>
<hr width="25%">
<br>
<br>
slides at <a href="https://github.com/bugi/deck-nclug-ansible">https://github.com/bugi/deck-nclug-ansible</a>
<br>
<br>
html view at <a href="http://htmlpreview.github.io/?https://github.com/bugi/deck-nclug-ansible/blob/master/index.html">http://htmlpreview.github.io/?https://github.com/bugi/deck-nclug-ansible/blob/master/index.html</a>
<br>
<br>
effects derived from scrolldeck, <a href="http://johnpolacek.github.io/scrolldeck.js/">http://johnpolacek.github.io/scrolldeck.js/</a>
<div class="page" style="font-size:2rem">22</div>
</div>
<div class="slide" id="what is ansible">
<h1>origin of the word</h1>
<br>
<div class="centerable">
<ul>
<li>An ansible is a fictional machine capable of instantaneous or superluminal communication.</li>
<li>Ursula K. Le Guin origininally used the word in <i>Rocannon's World</i>.</li>
<li>Many other SF authors have used it since.</li>
</ul>
</div>
<br>
<br>
<br>
(From Wikipedia's article on <a href="http://en.wikipedia.org/wiki/Ansible">ansible</a>.)
<div class="page" style="font-size:2rem">23</div>
</div>
<script>
$(document).ready(function() {
var deck = new $.scrolldeck({
buttons: '.nav-button',
easing: 'easeInOutExpo'
});
// add other animations using the scrolldeck.controller (see Scrollorama plugin)
console.log(deck.controller);
deck.controller.animate('#instructions',{ duration: 100, property:'opacity', end: 0 });
});
</script>
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-2821890-9']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</body></html>