forked from holser/openstack-summit-paris-2014
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
236 lines (192 loc) · 9.14 KB
/
index.html
File metadata and controls
236 lines (192 loc) · 9.14 KB
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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>How we fought for High Availability</title>
<meta name="description" content="A Presentation about High Availability in OpenStack based on Mirantis OpenStack">
<meta name="author" content="Vladimir Kuklin, Sergii Golovatiuk">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<link rel="stylesheet" href="reveal.js/css/reveal.min.css">
<link rel="stylesheet" href="reveal.js/css/theme/default.css" id="theme">
<!-- Custom overrides -->
<link rel="stylesheet" href="css/override.css">
<!-- For syntax highlighting -->
<link rel="stylesheet" href="reveal.js/lib/css/zenburn.css">
<!-- If the query includes 'print-pdf', include the PDF print sheet -->
<script>
if( window.location.search.match( /print-pdf/gi ) ) {
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = 'reveal.js/css/print/pdf.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
}
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<img src="https://www.mirantis.com/id/RasterMirantisLogo_HiRes_Tagline_Inverted_transparent.png"
class="mirantis-logo"/>
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1>How we fought for High Availability?</h1>
<p>
<small>Created by <a href="https://github.com/aglarendil">Vladimir Kuklin</a></small>
<small>and <a href="https://github.com/holser">Sergii Golovatiuk</a></small>
</p>
<aside class="notes">
Let me introduce ...
Vladimir Kuklin
Sergii Golovatiuk
</aside>
</section>
<section id="general_ha" data-markdown="markdown/01-Intro.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:">
</section>
<section>
<h2>OpenStack Architecture</h2>
<img src="images/openstack-arch.svg" alt="OpenStack Architecture" style="background: rgba(255, 255, 255, 1);">
<aside class="notes">
Here is a classical diagram of OpenStack and its loosely coupled components.
What is the main problems with all these componts?
You should organize High Availability for all of these components. So, in reality you should have at least 2 copies of these elements. However, I would suggest to have at least 3 copies to eleminate split brain scenarios you may have.
All components should be ready for High Availability. Some of them might be under arbitrary control, Some of them may have own healing mechanisms.
</aside>
</section>
<section id="openstack_ha_stack" data-markdown="markdown/03-OpenStack-HA-Stack.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:">
</section>
<section id="fragments">
<h1>OpenStack HA Stack</h1>
<p>Fault Tolerance of every component</p>
<ol>
<li class="fragment">Network connectivity</li>
<li class="fragment">Database -MySQL/Galera</li>
<li class="fragment">AMQP - Rabbit MQ</li>
<li class="fragment">Memcache</li>
<li class="fragment">API services</li>
<li class="fragment">Neutron/Heat/Ceilometer</li>
</ol>
<aside class="notes">
To Provide High Availability to a system. We should provide connectivity to all components. No brainer. We will not cover High Availability for DataCenter components such as Power, Cooling. All these requirements are well described in Uptime Insitute Documents. Our primary focus is OpenStack services. So ...<br /><br />
Network Connectivity. <br /><br />
Out of the box Fuel provides several options such as Active-Passive Connection or more advanced LACP (802.1ad) network connection. However, we still have separate connection for PXE network booting.<br /><br />
DataBase.<br /><br />
</aside>
</section>
<section id="database_galera" data-markdown="markdown/04-Galera.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:">
</section>
<section>
<section>
<h1>AMQP - Rabbit</h1>
<p>Problems:<br>
RabbitMQ server doesn't reassemble easily</p>
<p>Complex OCF Master/Slave script:</p>
</section>
<section id="rabbit_ocf" data-markdown="markdown/rabbit.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:" >
</section>
</section>
<section>
<h2>AMQP - oslo.messaging</h2>
<ul>
<li>AMQP - multiple rabbit support included</li>
<li>Oslo.messaging lacks of <a href="https://bugs.launchpad.net/mos/+bug/856764">heartbeats</a></li>
</ul>
</section>
<section>
<h1>API services </h1>
</section>
<section>
<h1>Keystone</h1>
</section>
<section id="neutron" data-markdown="markdown/neutron.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:" >
</section>
<section>
<h1>Heat/Ceilometer</h1>
</section>
<section>
<h1>Ceph</h1>
</section>
<section>
<section id="deployment_1" data-markdown="markdown/deployment/01.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:" >
</section>
<section id="deployment_2" data-markdown="markdown/deployment/02.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:" >
</section>
<section id="deployment_3" data-markdown="markdown/deployment/03.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:" >
</section>
<section id="deployment_4" data-markdown="markdown/deployment/04.md"
data-separator="^\n\n\n" data-vertical="^\n\n" data-notes="^Note:" >
</section>
</section>
<section>
<h1>Testing HA</h1>
</section>
<section>
<h1>Current challenges and plans for the future</h1>
<ol>
<li>OSLO.db resilience</li>
<li>Event-driven failover and evacuation (e.g. Zabbix triggers)</li>
<li>zeroMQ research</li>
<li>VRRP and DVR testing and (if needed) polishing </li>
<li>Fencing support</li>
<li>Sophisticated load balancing of services</li>
<li>Integration with hardware load balancers (e.g. F5)</li>
</ol>
</section>
<section>
<h1>Links</h1>
<ol>
<li><a href=http://wiki.openstack.org/Fuel>http://wiki.openstack.org/Fuel</a></li>
<li><a href=http://github.com/stackforge/fuel-library.git>http://github.com/stackforge/fuel-library.git</a></li>
<li>fuel-dev ML & #fuel-dev @ freenode</a></li>
<li><a href=https://etherpad.openstack.org/p/fuel-ha-fixes-catalogue>https://etherpad.openstack.org/p/fuel-ha-fixes-catalogue</a></li>
</ol>
</section>
<section>
<h1>Questions?</h1>
<p>
<small>Created by <a href="https://github.com/aglarendil">Vladimir Kuklin</a></small>
<small>and <a href="https://github.com/holser">Sergii Golovatiuk</a></small>
</p>
</section>
</div>
</div>
<script src="reveal.js/lib/js/head.min.js"></script>
<script src="reveal.js/js/reveal.min.js"></script>
<script>
// Full list of configuration options available here:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
theme: Reveal.getQueryHash().theme, // available themes are in /css/theme
transition: Reveal.getQueryHash().transition || 'default', // default/cube/page/concave/zoom/linear/fade/none
// Parallax scrolling
parallaxBackgroundSize: '2000px 714px',
// Optional libraries used to extend on reveal.js
dependencies: [
{ src: 'reveal.js/lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'reveal.js/plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'reveal.js/plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'reveal.js/plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'reveal.js/plugin/zoom-js/zoom.js', async: true, condition: function() { return !!document.body.classList; } },
{ src: 'reveal.js/plugin/notes/notes.js', async: true, condition: function() { return !!document.body.classList; } }
]
});
</script>
</body>
</html>