►
Description
Virtual machines deployed to Red Hat OpenShift have the option of connecting to the SDN and utilizing the SDN functions the same as Pods. This means they can communicate with other Pods using Services and have Services describe how to access the virtual machine’s applications.
This video demonstrates connecting between Pods and VMs across the Red Hat OpenShift SDN, showing that whether in a container or a virtual machine, applications can seamlessly communicate when co-hosted in Red Hat OpenShift.
Learn more at openshift.com
A
A
First,
we
have
a
simple
app
pod,
which
is
a
php
pod
that
returns
back
some
information
about
the
pod
itself,
as
well
as
where
the
request
is
coming
from,
and
in
order
to
support
that
we've
created
a
service.
We
have
our
simple
service
as
well
as
a
route,
and
if
we
browse
to
that
route,
we
can
see
the
information
that
is
returned
back
where
the
request
was
coming
from.
A
A
So,
let's
first
start
by
creating
a
new
virtual
machine,
select
create
a
new
virtual
machine.
Here,
I'm
going
to
choose
this
fedora
33
template,
which
has
been
provided
by
another
administrator.
I
can
select
this
option
hit
next.
I
know
that
this
is
a
community
supported,
template,
that's,
okay!
I'm
going
to
go
ahead
and
change
our
name
here.
A
I
don't
need
to
modify
that
for
I'm
just
going
to
click
create,
and
we
will
see
after
a
moment
that
our
virtual
machine
gets
started
if
you're
a
quick
guide
and
saw
a
launcher
error
there.
That
was
because
we
were
waiting
for
the
persistent
volume
claim
to
be
created
and
the
pvc
to
be
bound,
so
our
virtual
machine
is
now
running
while
that's
booting
up
I'm
going
to
move
down
here
and
we're
going
to
create
a
service
to
point
at
our
virtual
machine.
A
So
the
first
thing
I
want
to
do
is
erase
the
existing
yaml
save
our
name,
and
then
I
happen
to
have
a
very
handy
service
template
available
for
us,
we'll
name
it
after
our
virtual
machine.
All
I'm
doing
here
is
naming
our
service
after
the
virtual
machine
and
then
telling
it.
I
want
to
select
based
off
of
the
name
of
the
virtual
machine
again,
this
time
it
is
wooden
moose,
so
we'll
hit
create
there,
and
now
we've
created
a
service
that
points
at
port
80
on
our
virtual
machine.
A
Moving
back
to
the
vm.
At
this
point
it
has
fully
booted,
so
we'll
go
ahead
and
log.
In
now
this
password
was
set
by
cloud
init
that
was
specified
in
the
virtual
machine
template
that
I
used
to
clone
the
virtual
machine.
So
if
you
don't
happen
to
know
that
vm
you
can
see
or
excuse
me
that
password
we
can
see
up
here.
The
show
password
and
it'll
actually
show
that
to
us
so
long
as
it
is
in
the
cloud
init.
A
If
we
don't
use
cloud
init,
then
it
won't
be
able
to
show
us
that
password
there.
Now
I
can
do
things
like
ping,
the
outside
world.
If
I
so
choose,
I
can
also
access
our
other
pod
based
service.
So,
for
example,
I
can
do
a
curl
dash
s
against
our
simple
service
and
we
get
back
our
simple
service
notice
that
our
requester
ip
is
going
to
be
different.
This
is
because
it's
coming
from
the
sdn.
This
is
an
sdn
ip
address,
1.31.0.164.,
let's
go
ahead
and
install
a
web.
A
A
A
If
I
do
a
curl
against
that,
we
see
that
we
get
back
our
hello
world
now
to
prove
that
we
can
connect
from
other
pods
from
other
services
running
inside
of
our
cluster.
Let's
connect
to
that
pods
template.
So
we
use
the
simple
app
that
we
used
before
and
just
like,
we
did
from
the
virtual
machine
we'll
query
for
our
virtual
machine's
name.
Remember:
it
was
wooden
moose.
A
And
we
get
back
our
hello
world,
so
this
has
been
a
very
simple,
very
quick
example
of
creating
a
virtual
machine
that
can
connect
to
pods
that
can
access
services
hosted
on
pods,
as
well
as
allowing
pods
to
access
services
hosted
in
virtual
machines
for
more
videos
about
openshift
virtualization,
be
sure
to
watch
the
channel.
Thank
you
and
have
a
great
day.