►
From YouTube: Scalable Multiplayer Game Design with OpenShift (E9)
Description
This monthly series explores what it takes to design a scale-out multiplayer video game architecture using containers and OpenShift. There will be live coding, philosophical design discussion, and everything in between.
Today's show will cover the integration of the game lobby and the game's web client with Red Hat SSO.
Host:
Erik Jacobs
Guests:
* Derek Reese
* Michael Clayton
* Roderick Kieley
* Jared Sprague
YouTube: https://youtu.be/BI6sV_p1k8I
Twitch: https://red.ht/twitch
A
B
C
A
The
park
got
spongebob
in
the
background
joining
us
today,
so
yeah.
What
have
we
been
up
to?
We?
We
didn't
get
to
do
last
month
because
we
had
a
lot
of
crazy
stuff
going
on
internally,
and
so
we
didn't,
we
didn't
get
a
whole
lot
done
to
actually
show
you,
but
we
did
get
a
little
bit
done
more
recently
and
what
we
did
do
or
or
what
I
did
or
what
I
butchered
probably
is
more
appropriate.
A
A
A
Then
we
have
the
actual
game
client,
which
now
is
a
true
node.js
application
running,
express
because
that's
how
we're
doing
the
key
cloak
integration
and
then
we
have
the
ruby
based
chat
lobby.
Oh
you
know.
If
I
deploy
the
game
server,
I
could
actually
just
throw
this
up
and
we
could
let
people
play
the
game
or
or
or
do
like
blow
things
up
well
anyway,
we'll
maybe
get
to
that
for
next
show.
So
if
I
open
the
chat
room
lobby,
there's
no
skinning
on
this,
I
should
probably
bootstrap
it
up
or
something.
A
A
A
This
isn't
a
permanent
url.
This
is
just
a
cluster
that
I
have
for
now,
so
it'll
probably
go
away,
but
if
you
log
in
with
your
github
id
and
type
chat
messages
in
the
box,
they'll
appear
in
here,
I
don't
know.
If
the
scroll
bar
will
ever
appear
or
whatever,
but
anyway
what
we
did
under
the
covers-
hey
mr
clayton,
there
you
go
test.
A
A
If
you
weren't
already
authenticated
enough,
and
so
one
of
the
hacks,
I
did
drop
table
spaceships.
Yes,
exactly
one
of
the
hacks
that
I
did
was
I
made
this
link
for
play
now:
a
form
that
actually
posts
your
encoded
jwt
access,
token,
and
so
it
posts
this
over
to
the
web
client.
If
I
pull
up
the
web
client
code
and
michael,
I
know
you
made
some
changes.
I
don't
have
your
changes
here,
but
I
have
enough
to
just
show
what's
going
on,
if
I
pull
up
app.js,
this
is
a
node.js
application.
A
It
uses
express
for
pretty
basic
handling,
and
so,
when
somebody
posts
it
runs
a
series
of
middleware
handlers
in
order
and
the
first
one
is
okay
check,
sso
handler
and
if
we
scroll
down
to
the
function,
the
check
sso
handler
does
a
couple.
First,
a
couple
things:
first,
it
says
all
right,
I'm
going
to
redirect
you
back
to
the
lobby
by
default.
If
anything,
if
I
can't
figure
out
what
to
do,
that's
what
I'm
going
to
do.
A
First
thing:
it
does,
it
says:
hey
if
the
request
has
an
access
token
in
the
body,
you're
sort
of
already
logged
in
most
likely,
so
we're
gonna
send
you
to
sso.
Now
this
sounds
dumb
right
like
why?
Don't
we
just
always
send
you
to
sso,
because
I
wanted
you
to
get
sent
back
to
the
lobby
if
you
weren't
logged
in
and
so
sending
you
to
sso,
if
you
are
already
logged
in
kicks
you
back
to
the
game
client,
but
doesn't
actually
send
you
away.
A
I
know
that
sounds
really
weird
but
like,
if
you
think
about
it,
if
you
just
bookmarked
the
game,
client
url
and
you
kill
their
cookies
and
you
close
your
browser
and
you
went
to
the
game.
Client.
What
we
don't
want
you
to
be
able
to
do
is
get
kicked
to
the
login
page
and
then
immediately
kick
back
to
the
game
client
without
ever
seeing
the
lobby.
A
Ideally,
players
should
start
in
the
lobby
so
that
we
can
show
them
notifications-
or
you
know
if
this
was
the
real
world,
so
that
we
could
sell
them
5
000
things
with
micro
transactions.
You
know
we.
We
definitely
want
them
to
start
at
the
lobby,
and
so
what
this
is
doing
is
it's
basically
saying:
okay.
Does
the
game
client
know
anything
about
your
session
if
it
does
we'll
send
you
to
like
double
check
your
authentication,
to
make
sure
that
you're
still
valid,
like
maybe
you're,
maybe
timed
out
or
whatever?
A
But
if
I
can't
figure
out
what's
going
on
with
you,
I'm
just
going
to
shoot
you
back
to
the
lobby
and
then
let
the
lobby
handle
showing
that
you
should
really
actually
click
the
login
button.
So
if
you
have
an
access
token
in
your
request,
we
don't
redirect
you.
If
the
server
has
session
data
for
you,
then
we
don't
redirect
you
otherwise
stuff
is
missing,
and
so
we
force
you
back
to
or
redirect
you
to
whatever
the
lobby
host
name
is
as
an
environment
variable.
A
So
pretty
simple
stuff.
We
took
all
the
existing
code
for
the
for
the
web
client,
which
was
basically
just
static,
html
and
javascript,
and
we
moved
it
into
the
public.
I
moved
it
into
the
public
folder
and
so
all
that
stuff
lives.
Here
from
a
phaser
perspective,
I
made
a
couple
of
really
minor
changes
in
the
menu
scene.
A
There's
now
a
quit
button.
So
if
I
scroll
down
here
so
there's
a
button
that
will
appear
for
quit.
So
as
soon
as
you
come
into
the
game,
client,
the
first
thing
that
happens
is
you
see
the
menu
and
one
of
the
menu
options
is
now
quick
and
then,
if
you
click
the
quit
button
from
the
menu,
it
sends
you
to
the
slash
quit
path.
A
A
So
destroying
the
session
means
that
you're
no
longer
going
to
have
this
key
cloak
data
in
the
session.
So
that's
good.
That
means
that
you'll
you'll
get
redirected
next
time
you
show
up,
and
then
it
redirects
you
back
to
the
lobby,
so
quitting
the
game
from
the
quit
menu.
Redirects
you
to
the
lobby.
A
A
A
A
I
can
still
go
to
the
lobby
and
do
things
if
I
click
play.
It's
gonna
take
me
back
into
the
game
and
then
because
I'm
posting
into
the
game,
it's
gonna
be
like
oh
cool.
I
know
who
you
are.
I'm
gonna
force
you
through
sso,
real,
quick
but
you're.
All
good!
So
quickly
turns
me
back
around
and
I'm
back
in
the
game,
and
now
I
can
just
go
and
quit
directly
from
here
same
thing.
A
A
It
didn't
redirect
me
because
I
didn't
find
any
data
to
post,
but
I'm
still
logged
in
in
terms
of
sso
and
I
still
have
a
session
in
the
lobby,
so
I
can
still
access
the
lobby
if
I
click
log
out
and
now
I
try
to
go
to
the
game-
client,
I'm
just
going
to
get
rebooted
back
to
the
lobby
again
and
if
I
try
to
access
the
lobby
now
that
I'm
like
the
actual
chat
room
part
of
the
lobby.
Now
that
I'm
locked
out
this,
I
think
just
boots
me
back
to
the
home
page.
A
A
Yeah,
so
I
was
thinking
there
is
a
an
openshift
cluster
that
the
product
managers
maintain.
I
think
it
might
be
a
public
cluster,
so
I'm
tempted
to
get
this
all
going
in
that
cluster
and
just
leave
it
up
and
and
and
see
what
happens.
I'm
sure
it'll
be
all
kinds
of
atrociously
awful
and
bad.
There's
no
profanity
filtering,
there's
nothing.
I
mean
it's
all,
it's
all
bad.
So
I
don't
know
if
that's
a
good
idea
or
not,
but
anyway,
let's
see.
Is
there
any
other
code
that
I
want
to
show?
C
A
B
B
A
B
C
B
B
A
D
A
A
B
A
D
A
Yeah
I
had
to
click
return
to
meeting
which,
like
kicked
down
the
little
menu
at
the
top
of
the
page
or
the
top
of
my
screen,
and
then
I
was
able
to
click
the
button
like
for
some
reason
when
it's
hovering
over
the
clock
in
fedora
it
just
wouldn't
it
wouldn't
do
the
right
thing
all
right.
You
do
that
I'm
gonna
try
and
get
the
game
server
running
on.
C
A
A
A
B
C
B
B
B
C
A
B
Zoom
is
it
feels
like
everything
is
in
syrup.
Everything
is
so
slow.
I'm
sharing.
This
feels
horrible
okay.
So
what
we're
going
to
do
is
try
to
make
the
games
server,
not
not
the
server
the
game,
client
launch
in
debug
mode
and
have
the
debug
mode
control
whether
sso
is
required
for
any
of
the
endpoints
that
we
might
hit
yes,
so
these
are
all
vars,
but
I'm
going
to
break
the
mold
and
do
const
bring
in
the
debug
package
and
then.
B
B
Where's
the
enabled
so
it
works
something
like
this.
You
can
query
whether
debug
is
enabled
with
the
enabled
function
and
it
has
an
optional
name
space.
So
you
can
enable
and
disable
debugging
on
subsets
of
your
modules,
but
we
don't
really
care
about
that.
So
I'm
just
going
to
run
enabled
with
no
argument
which
seems
to
I
don't
see
this
in
the
docs,
but
it
seems
to
stay
or
it
seems
to
just
be
a
wild
card.
If
you
don't
have
an
argument,
so
it'll
add
debug
to
or
it'll
check
if
default,.
B
C
B
B
C
A
B
B
A
E
A
B
A
A
C
A
B
A
B
B
C
B
A
A
A
B
B
A
D
A
A
A
It
for
you
right
so
so:
okay,
here's
the
challenge,
so
you
have
hang
on
hang
on.
You've
got
artemis,
which
is
the
message
broker,
which
is
not
the
game
server,
but
in
order
for
the
game
server
to
do
anything,
it
needs
the
message
broker
yeah.
So
what
these
instructions
are
attempting
to
do
are
telling
first
get
the
message
broker
running
then
build
the
game
server
container
image.
If
you
want
to
run
it
in
a
container,
then
run
the
container
image.
So
the
steps
are
out
of
order
and.
E
A
I
don't
even
know
I've
never
seen
this
error
on
fedora
before
so
I
don't.
I
don't
know
if
you
want
to
do
all
these
things
with
docker,
you
probably
can
without
any
of
the
pseudos
so
anyway,
so
just
get
rid
of
sudo
and
and
get
rid
of
podband
and
just
do
it
as
docker.
But
I
don't
that
that
sounds
like
a
misconfiguration
in
your
system.
C
A
B
A
B
C
C
D
A
C
A
A
B
C
C
A
B
B
A
A
A
B
A
A
B
A
A
No
because
again,
docker
and
podman.
Well,
I
don't
think
anything's
running
in
your
in
your
docker,
because
that
the
compose
blew
up,
but
they
they
have
completely
different
network
name
spaces
anyway.
That
error
is
coming
from
proton,
but
I
don't
understand
what
it
means.
Survey,
I'm
not
supported
for
ai
stock
type.
B
A
A
A
A
A
A
B
C
B
A
A
A
A
A
B
A
A
C
C
A
A
A
A
A
A
A
A
B
A
A
A
A
A
D
C
A
A
A
A
C
A
C
C
A
A
D
D
A
A
B
A
C
A
A
C
A
A
D
A
A
A
Unexpected
type
yeah,
so
something
weird
is
going
on
with
the
amqp
library
when
it's
being
loaded
this
way,
but
like
I
don't
think,
we've
changed
any
of
the
stuff
in
here,
and
so
this
is
where
the
conversion
that
jared
had
done
to
this
isn't
typescript,
whatever.
Whatever
this
formatting
or
way
of
doing
things
is
called
like.
I
have
no
idea
how
to
debug
javascript
at
this
level,
because
I
don't
know
how
to
like
in
the
console
get
into
any
of
these
things.
B
D
A
A
Yeah,
so
the
only
difference
in
like
I
don't
know
that
there's
any
difference
in
any
of
the
messaging
code,
but
when
I
checked
out
prior
to
express
and
ran
it
like,
it
worked
fine.
So
something
has
changed
in
the
way
that
the
messaging
code
is
being
loaded
executed,
used
wrapped,
like
I'm
out
of
my
league
here
in
javascript.
A
A
A
A
B
C
C
B
A
D
A
A
A
A
A
D
C
D
D
I
saw
that
so
line
97
of
ampq
or
amqp
game
client,
client
right
where
we
had
the
right
where
we
had
the
right
right
was
that
body,
maybe
not
working
previously,
and
now
it
works
like
we
were
sending
a
you
know.
This.Sender.Send
and
body
was
just
false
and
now
that
it's
populated
with
data,
it's
not
working.
A
D
D
A
D
C
A
C
E
C
A
A
A
A
A
C
A
A
A
So,
like
nodejs
and
nodejs,
dependencies
played
no
part
in
what's
happening
here,
because
all
we're
doing
is
loading
files.
So
all
of
these
files,
a
hundred
percent
of
everything
in
javascript
and
and
lib
and
scenes
and
model
and
everything
these
files
all
existed
previously
and
and
did
not
change.
Can
you.
A
D
D
A
A
A
A
So
I
think
we
are
using
different
versions
of
stuff
srt
web
client,
srt
game
server,
srt
web
client.
So
if
we
look
at
package.json
low
dash,
phaser,
protobufs,
rhea,
etc
are
now
in
here
and
they
get
copied
in,
and
so
if
I
get
blog
so
this
is
probably
a
bug
in
newer
versions
of
something
cherry
pick
migrate
to
express,
express.
A
A
A
A
A
It's
whatever
version
this
file
is,
and
so
I'm
not
really
even
sure
other
than
like
downloading
each
tagged
version
and
diffing
it
to
figure
out
which
version
it
is.
You
know
which
is
fine.
I
can
do
that.
It's
not
the
end
of
the
world,
but
that's
basically
what
what
I
think
happened.
So
if
I
come
here
and
go
to
github
rhea.
C
C
A
A
C
C
A
A
D
D
So,
what's
what's
happening
on
the
c
plus
side?
Is
it's
looking
at
the
message,
queue
with
message
being
specifically
a
protobuf
message,
and
it's
expecting
to
get
a
binary
message
and
decode
that
using
protobuf
and
instead
what
it's
getting
is
what
it
identifies
as
a
map
instead
of
a
binary
string.