-
Notifications
You must be signed in to change notification settings - Fork 0
/
mlbparks-binary-build.html
342 lines (267 loc) · 13.4 KB
/
mlbparks-binary-build.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
<!DOCTYPE html>
<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">
<link rel="apple-touch-icon" sizes="180x180" href="apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="favicon-16x16.png">
<link rel="manifest" href="site.webmanifest">
<link rel="mask-icon" href="safari-pinned-tab.svg" color="#5bbad5">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="theme-color" content="#ffffff">
<script src="jquery/jquery.min.js"></script>
<script src="popper/popper.min.js"></script>
<script src="bootstrap/js/bootstrap.min.js"></script>
<script src="requirejs/require.js"></script>
<script>var workshop_base_url = "/user/user3/workshop";</script>
<link rel="stylesheet" href="asciidoctor/css/asciidoctor.css">
<link rel="stylesheet" href="bootstrap/css/bootstrap.min.css">
<link rel="stylesheet" href="fontawesome/css/all.min.css">
<link rel="stylesheet" href="css/workshop.css">
<link rel="stylesheet" href="css/workshop-asciidoc.css">
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-135921114-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag("js", new Date());
gtag("config", "UA-135921114-11");
</script>
</head>
</body>
<!-- Header -->
<header class="header">
<div class="container-fluid">
<div class="row">
<div class="col-sm-6">
<a href="" class="logo">Starter Labs (Java)</a>
</div>
</div>
</div>
</header>
<!-- Main -->
<div class="container-fluid">
<div class="row">
<div class="col-sm-3 d-sm-block d-none">
<!-- Table of Contents -->
<ul class="menu">
<li class="category">
<ul class="modules">
<h5 class="category-title">Workshop Modules</h5>
<li class="page"><a href="common-workshop-summary.html">Workshop Summary</a></li>
<li class="page"><a href="common-environment.html">Environment Overview</a></li>
<li class="page"><a href="common-using-homeroom.html">Using Homeroom</a></li>
<li class="page"><a href="common-parksmap-architecture.html">Architecture Overview of the ParksMap Application</a></li>
<li class="page"><a href="common-explore.html">Exploring the CLI and Web Console</a></li>
<li class="page"><a href="parksmap-container-image.html">Deploying Your First Container Image</a></li>
<li class="page"><a href="parksmap-scaling.html">Scaling and Self Healing</a></li>
<li class="page"><a href="parksmap-routes.html">Exposing Your Application to the Outside World</a></li>
<li class="page"><a href="parksmap-logging.html">Exploring OpenShift's Logging Capabilities</a></li>
<li class="page"><a href="parksmap-permissions.html">Role-Based Access Control</a></li>
<li class="page"><a href="parksmap-rsh.html">Remote Access to Your Application</a></li>
<li class="page"><a href="nationalparks-java.html">Deploying Java Code</a></li>
<li class="page"><a href="nationalparks-java-databases.html">Adding a Database (MongoDB)</a></li>
<li class="page"><a href="nationalparks-java-application-health.html">Application Health</a></li>
<li class="page"><a href="nationalparks-java-pipeline.html">Automate Build and Deployment with Pipelines</a></li>
<li class="page"><a href="nationalparks-java-pipeline-codechanges-gogs.html">Automation for Your Application on Code Changes</a></li>
<li class="page"><a href="mlbparks-templates.html">Using Application Templates</a></li>
<li class="page active"><a href="mlbparks-binary-build.html">Binary Builds for Day to Day Development</a></li>
<li class="page"><a href="common-further-resources.html">Further Resources</a></li>
<li class="page"><a href="common-workshop-links.html">Workshop Links</a></li>
</ul>
</li>
</ul>
</div>
<div class="col-sm-9">
<section class="page-content">
<!-- Top Navigation -->
<div class="btn-group btn-group-xs float-right">
<button type="button" onclick="location.href='mlbparks-templates';" class="btn btn-xs btn-transparent" aria-label="Prev">
<span class="fas fa-arrow-left" aria-hidden="true"></span>
</button>
<button type="button" onclick="location.href='';" class="btn btn-xs btn-transparent" aria-label="Home">
<span class="fas fa-home" aria-hidden="true"></span>
</button>
<button type="button" onclick="location.href='common-further-resources';" class="btn btn-xs btn-transparent" aria-label="Next">
<span class="fas fa-arrow-right" aria-hidden="true"></span>
</button>
</div>
<!-- Title -->
<h1 class="title">Binary Builds for Day to Day Development</h1>
<!-- Content -->
<div class="sect1">
<h2 id="_moving_on_from_s2i">Moving on From S2I</h2>
<div class="sectionbody">
<div class="paragraph">
<p>As you saw before S2I is a great way to get from source code to a container, but the process is a bit too slow for daily fast iterative
development. For example, if you want to change some CSS or change one method in a class you don’t want to go through
a full git commit and build cycle. In this lab we are going to show you a more efficient method for quick iteration. While
we are at it we will also show you how to debug your code.</p>
</div>
<div class="paragraph">
<p>Now that we built the MLB parks service let’s go ahead and make some quick changes.</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_fast_iterative_code_change_using_binary_deploy">Fast Iterative Code Change Using Binary Deploy</h2>
<div class="sectionbody">
<div class="paragraph">
<p>The OpenShift command line has the ability to do a deployment from your local machine. In this case we are going to use S2I,
but we are going to tell OpenShift to just take the war file from our local machine and bake it in the image.</p>
</div>
<div class="paragraph">
<p>Doing this pattern of development lets us do quick builds on our local machine (benefitting from our local cache and
all the horsepower on our machine) and then just quickly send up the war file.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
You could also use this pattern to actually send up your working directory to the S2I builder to have it do the Maven build
on OpenShift. Using the local directory would relieve you from having Maven or any of the Java toolchain on your local
machine AND would also not require git commit with a push. Read more in the
<a href="https://docs.openshift.com/container-platform/latest/dev_guide/dev_tutorials/binary_builds.html">official documentation</a>
</td>
</tr>
</table>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_exercise_using_binary_deployment">Exercise: Using Binary Deployment</h2>
<div class="sectionbody">
<div class="sect2">
<h3 id="_clone_source">Clone source</h3>
<div class="paragraph">
<p>The first step is to clone the MLB source code from GitHub to your workshop environment:</p>
</div>
<div class="listingblock execute-1">
<div class="content">
<pre class="highlight"><code class="language-bash" data-lang="bash">git clone https://github.com/openshift-roadshow/mlbparks.git</code></pre>
</div>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
We are using Intellij here in the guide for screenshots but this should work regardless of your tool chain. JBoss
Developer Studio and JBoss Developer Tools have built in functionality that makes this close to seamless right from the IDE.
</td>
</tr>
</table>
</div>
</div>
<div class="sect2">
<h3 id="_setup_the_build_of_the_war_file">Setup the Build of the war file</h3>
<div class="paragraph">
<p>If you have Maven all set up on your machine, then you can <code>cd</code> into the <code>mlbparks</code> directory and run <code>mvn package</code></p>
</div>
<div class="listingblock execute-1">
<div class="content">
<pre class="highlight"><code class="language-bash" data-lang="bash">cd mlbparks
mvn package</code></pre>
</div>
</div>
<div class="paragraph">
<p>Pay attention to the output location for the ROOT.war, we will need that directory later.</p>
</div>
</div>
<div class="sect2">
<h3 id="_code_change">Code Change</h3>
<div class="paragraph">
<p>Time for a source code change! Go to <code>src/main/java/com/openshift/evg/roadshow/rest/BackendController.java</code>.and edit it with <code>vi</code> or <code>nano</code>.
This is the REST endpoint that gives basic info on the service and can be reached at:</p>
</div>
<div class="listingblock copypaste">
<div class="content">
<pre class="highlight"><code class="language-bash" data-lang="bash">http://mlbparks-user3.apps.cluster-test-efcf.test-efcf.example.opentlc.com/ws/info/</code></pre>
</div>
</div>
<div class="paragraph">
<p>Please change line 23 to add a <em>AMAZING</em> in front of "MLB Parks" look like this:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="highlight"><code class="language-java" data-lang="java">return new Backend("mlbparks", "AMAZING MLB Parks", new Coordinates("39.82", "-98.57"), 5);</code></pre>
</div>
</div>
<div class="paragraph">
<p>Don’t forget to save the file and run <code>mvn package</code> again:</p>
</div>
<div class="listingblock execute-1">
<div class="content">
<pre class="highlight"><code class="language-bash" data-lang="bash">cd /opt/app-root/src/mlbparks
mvn package</code></pre>
</div>
</div>
</div>
<div class="sect2">
<h3 id="_doing_the_binary_build">Doing the Binary Build</h3>
<div class="paragraph">
<p>Alright we have our war file built, time to kick off a build using it.</p>
</div>
<div class="paragraph">
<p>If you built your war with Maven:</p>
</div>
<div class="listingblock execute-1">
<div class="content">
<pre class="highlight"><code class="language-bash" data-lang="bash">oc start-build bc/mlbparks --from-file=target/ROOT.war --follow</code></pre>
</div>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
The --follow is optional if you want to follow the build output in your terminal.
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>Using labels and a recreate deployment strategy, as soon as the new deployment finishes the map name will be updated. Under a recreate deployment strategy we first tear down the pod before doing our new deployment.
When the pod is torn down, the parksmap service removes the MLBParks map from the layers. When it comes back up, the layer
automatically gets added back with our new title. This would not have happened with a rolling deployment because
rolling spins up the new version of the pod before it takes down the old one. Rolling strategy enables a zero-downtime deployment.</p>
</div>
<div class="paragraph">
<p>You can follow the deployment in progress from Topology view, and when it is completed, you will see the new content at:</p>
</div>
<div class="listingblock copypaste">
<div class="content">
<pre class="highlight"><code class="language-bash" data-lang="bash">http://mlbparks-user3.apps.cluster-test-efcf.test-efcf.example.opentlc.com/ws/info/</code></pre>
</div>
</div>
<div class="paragraph">
<p>So now you have seen how we can speed up the build and deploy process.</p>
</div>
</div>
</div>
</div>
<!-- Bottom Navigation -->
<div class="page-meta clearfix">
<input type="button" class="btn btn-lg btn-primary float-right" onclick="location.href='common-further-resources';" value="Continue" />
</div>
</section>
</div>
</div>
</div>
<!-- Footer -->
<footer class="footer">
</footer>
<!-- Javascript-->
<script src="js/workshop.js"></script>
<script src="js/workshop-asciidoc.js"></script>
</body>
</html>