-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.html
83 lines (77 loc) · 5.45 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
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<link rel="stylesheet" type="text/css" href="stylesheets/stylesheet.css" media="screen" />
<link rel="stylesheet" type="text/css" href="stylesheets/pygment_trac.css" media="screen" />
<link rel="stylesheet" type="text/css" href="stylesheets/print.css" media="print" />
<link rel="stylesheet" type="text/css" href="css/topcoat-desktop-min.css">
<title>Devops Mercenaries by devopsmercenaries</title>
</head>
<body class="bg-slategray">
<header>
<div class="container">
<img src="./images/devopsmercs.png" style="width:200px;border:4px solid gray;"/>
<h1>Devops Mercenaries</h1>
<a href="https://github.com/devopsmercenaries" class="btn btn-github"><span class="icon"></span>View on GitHub</a><br/>
<a href="https://twitter.com/DevopsMercs" class="btn btn-twitter" data-show-count="false" data-size="large">Follow @DevopsMercs on Twitter</a>
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
</div>
</header>
<h1>Devops Mercenaries workshop, Devoxx France 2014: Results from the brainstorming session</h1>
<div class="container">
<section id="main_content">
<ul><li>Categorisation of Buzz tag cloud<ul><li>OPS<ul><li>Run</li><li>Provisioning</li><li>Capacity planning</li></ul></li><li>DELIVERY<ul><li>Flow</li><li>Lead time</li><li>Continuous delivery</li><li>Deployment</li></ul></li><li>USER FEEDBACK<ul><li>A/B Testing</li><li>Feature flags</li><li>UX Testing</li><li>Business monitoring</li><li>Time-to-market</li><li>Frequent deliveries</li></ul></li><li>QA<ul><li>TDD</li><li>Quality Management</li><li>Continuous Inspection</li><li>Error Diagnostic</li><li>System Thinking</li></ul></li><li>TOOLS<ul><li>Automation</li><li>Continuous Integration</li><li>Source control</li><li>Scripting</li><li>Infrastructure as code</li></ul></li><li>VIRTUALISATION<ul><li>Docker.io</li><li>Puppet, Chef, Ansible, CFEngine, Fabric</li><li>VMWare, HyperV, Xen</li><li>Virtual machines</li><li>Vagrant, Virtualbox</li><li>Linux/Unix</li></ul></li><li>CLOUD<ul><li>IAAS</li><li>PAAS</li><li>SAAS</li><li>Amazon Web Services</li><li>Google Compute Engine</li><li>Heroku</li><li>Azure</li></ul></li><li>PROCESS<ul><li>Agile practices</li><li>Kanban</li><li>Continuous improvement</li><li>Collaboration</li><li>ITIL</li></ul></li><li>PEOPLE<ul><li>Abilities</li><li>Feature team</li><li>Knowledge</li><li>Responsibilities</li><li>Purpose</li><li>NoOPS</li><li>Skills</li></ul></li><li>MEASUREMENT<ul><li>Monitoring</li><li>Log analysis</li><li>Availability</li><li>Reliability</li><li>Alerting</li></ul></li></ul></li><li>What is devops?<ul><li>CAMS (Tag cloud categories in context)<ul><li>Culture<ul><li>PEOPLE</li><li>PROCESS</li></ul></li><li>Automation<ul><li>TOOLS</li><li>VIRTUALISATION</li><li>DELIVERY</li><li>CLOUD</li><li>OPS</li></ul></li><li>Measurement<ul><li>QA</li><li>USER FEEDBACK</li></ul></li><li>Sharing<ul><li>PEOPLE</li><li>PROCESS</li></ul></li></ul></li><li>Origins: convergence of trends<ul><li>WWW Pure-players<ul><li>Scalability</li><li>Big data / NOSQL</li><li>Infrastructure as a commodity</li></ul></li><li>Rise of Agile practices<ul><li>Shorter feedback loops for development</li><li>Adaptation to change</li><li>Automation</li><li>Focus on sufficient quality</li></ul></li></ul></li></ul></li></ul>
</section>
</div>
<hr />
<h1>
Les mercenaires de Devops, Atelier à Devoxx France 2014
</h1>
<div class="container">
<section id="main_content">
<p>1 : 10h40 - 11h30 Devops Brainstorming / Kanban des questions à répondre dans la journée</p>
<ul>
<li>1/ Culture (communication et discipline)</li>
<li>2/ Automatisation (vitesse et scalabilité)</li>
<li>3/ Mesure (vérification et certitudes)</li>
<li>4/ Partage (grossir la communauté)</li>
</ul>
</section>
<section id="main_content">
<p>2 : 11h45 - 12h35 Expériences heureuses/malheureuses avec DevOps</p>
<ul>
<li>1/ LesFurets.com (Petits pas vers le daily delivery)</li>
<li>2/ Société Générale (Q/A)</li>
<li>3/ Témoignages</li>
</ul>
</section>
<section id="main_content">
<p>3 : 13h30 - 14h20 DevOps : Quels outils et pour quoi faire ?</p>
<ul>
<li>1/ Infrastructure as Code</li>
<li>2/ Automatisation</li>
<li>3/ Monitoring</li>
<li>4/ Testing</li>
<ul>
</section>
<section id="main_content">
<p>4 : 14h35 - 15h25 DevOps : Culture du Delivery</p>
<ul>
<li>1/ Questionnaire "Delivery Maturity Checklist"</li>
<li>2/ Continuous integration and delivery (par Henri Gomez)</li>
</ul>
</section>
<section id="main_content">
<p>5 : 15h40 - 16h30 DevOps : C'est décidé, je commence lundi !</p>
<ul>
<li>1/ Je ne sais pas quoi faire (savoir)</li>
<li>2/ Je ne sais pas comment faire (méthode)</li>
<li>3/ Je ne sais pas valider mes progrès (mesurer)</li>
<li>4/ Je ne sais pas qui pilote (automatisation)</li>
</ul>
</section>
</div>
</body>
</html>