►
Description
In this short demo-driven meetup, we’ll help you get a handle on what’s changing and how it will impact your DevOps practice.
We’ll cover:
– What are the operational limitations of containers in production?
– How do you get visibility inside containers without super-human effort?
– How do you look into Openshift performance, and not just container performance?
– A live install of Sysdig Cloud on a running environment.
For the latest information on OpenShift 3.2 and available briefings, please visit http://commons.openshift.org or subscribe to the OpenShift Blog (https://blog.openshift.com).
The OpenShift Commons exists to provide a platform for customers, partners, developers and other open source technology initiatives to collaborate, share and accelerate the pace of innovation and adoption of OpenShift globally.
The OpenShift Commons represents a new open collaborative community model designed to facilitate communication and sharing of best practices, feedback and development across the many open source initiatives that integrate with OpenShift. The best way to get involved is to join the conversation today at http://commons.openshift.org
A
A
Oh
hello
and
welcome
everybody
to
yet
another
OpenShift
Commons
briefing.
We're
really
pleased
today
to
have
with
us
Knox
Anderson
from
the
product
team
at
sisty.
He
is
going
to
give
us
a
walkthrough
and
a
demo
of
the
container
native
monitoring
solution
that
Cystic
is
assisting
cloud
and
make
wealth
specialists
so
that
he
gives
his
presentation.
His
demo
will
pause
halfway
through
and
asking
a
few
questions
and
then
go
on
you.
A
Please
use
the
chat
to
put
your
questions
in,
as
we
usually
do
with
these
in
these
sessions
and
at
the
end,
we'll
read
off
all
of
the
questions
that
you
have
that
remain
and
have
an
open,
Q&A
conversation.
So
with
that
I'm
going
to
give
Knox
the
floor
and
that
didn't
drive
the
conversation
in
the
presentation.
This
would
be
thanks.
Not
awesome.
B
So
the
reason
that
we're
all
here
today
is
that
monitoring
containers
is
different
and
micro
services
and
containers
break
legacy,
monitoring
and
analytics
tools.
So
what
we
did
here
at
Cystic
is
built
a
new
product
through
a
unique
kernel
level
approach
that
can
natively,
monitor
any
infrastructure
and
app,
including
container
based
ones.
So
before
I
go
any
further
I'm
just
going
to
give
you
a
little
bit
of
background
about
our
company,
our
founder
Laura
schedule
was
also
behind
a
popular
tool
called
Wireshark.
B
It's
a
network
packet
analyzer
had
200
or
sorry
20
million
open
source
users
and
what
he
learned
there.
He
used
to
build
Cystic,
which
is
a
next-generation.
A
deep
system,
visibility
tool
and
the
Cystic
open
source
product
was
launched
in
2013
got
a
couple
hundred
thousand
users.
Its
kernel
module
is
the
basis
of
our
cystic
cloud
product
that
I'll
be
showing
to
you
later
today
and
then
also
our
new
security
product
that
we
just
launched.
It's
a
super
cool
technology
really
excited
to
get
get
into
it
further.
B
B
So,
first
off,
as
many
of
you
have
deployed,
containers
you've
figured
out
that
getting
visibility
inside
them
is
really
hard.
So
legacy
monitoring,
approaches
can't
see
inside
your
containers
and
the
things
that
make
containers
really
portable.
The
ability
to
move
them
from
your
laptop
to
a
server
or
from
a
development
environment
through
production
also
makes
it
really
hard
to
see
what's
inside
that
container
and
so
that
process.
Isolation
is
something
that's
really
nice,
but
makes
it
really
difficult
to
pull
metrics
from
the
inside.
B
One
of
the
things
you
could
do
is
connect
to
the
docker
stats
API,
but
then
you'll
just
get
something
like
CPU
memory
and
network,
not
really
get
deep
visibility.
So
one
of
the
things
that
people
do
to
get
deep
visibility
is
install
an
agent
inside
each
container,
but
if
you're
doing
that
you're
adding
a
bunch
of
dependencies
you're,
actually
putting
an
initial
product
and
another
process
inside
that
container,
so
you're
kind
of
losing
the
fundamental
reason
why
people
went
to
containers
for
the
first
place
and
stopping
that
process.
B
Isolation
and
then
last,
if
you're,
using
tools
like
openshift
and
you
have
a
scheduler.
That's
spinning
up.
Multiple
containers
and
deploying
micro
service
environment
correlating
your
different
containers
and
your
different
services
and
grouping
them
into
a
whole.
It's
something
that
really
the
legacy
monitoring
tools
don't
understand.
B
So
what
we've
done
here
at
Cystic
is
built
a
unique
system
instrumentation,
which
we
call
container
vision,
and
this
allows
us
to
see
inside
your
containers
from
the
outside.
So
we
can
see
network
information
what
containers
you're
running,
how
they're
talking
to
each
other
the
applications
running
inside
them
even
down
to
or
up
to
the
orchestration
tool
that
you're
using
to
manage
these
containers
and
the
network
traffic,
and
basically
everything
that's
going
on
in
that
host.
B
So
what
we're
looking
at
now
is
just
a
really
simple
application
that
I've
running
on
a
toast,
and
so
you
have
a
couple
apps.
You
have
some
containers
with
things
running
inside
that
and
they're
all
talking
to
the
kernel,
and
so
what
we've
done
at
Cystic
is
built
a
unique
kernel
module,
and
this
allows
us
to
see
all
the
system
calls
that
are
happening
on
that
host,
so
we're
actually
individually
tracing
every
single
system.
Call
that's
going
on
and
getting
deep
visibility
into.
B
Basically,
everything
that's
happening
on
that
host
and
what
we'll
do
is
install
our
Cystic
agent,
and
this
runs
as
either
a
privilege
container
or
as
a
process
on
that
host,
and
this
is
that
allows
us
to
install
our
kernel
module
and
from
there
we
actually
collect
and
analyze.
All
those
system
calls
and
then
send
them
to
our
back-end,
and
you
can
use
Cystic
cloud
as
a
service
or
you
can
actually
deploy
the
service
as
a
whole
on
your
own
machines.
B
A
B
B
Another
great
question:
so
our
agent
is
actually
really
efficient
and
that's
one
of
the
things
that
makes
our
product
really
unique,
so
our
agent
usually
has
somewhere
between
1
and
1.5%
CPU
overhead
on
the
host,
so
really
minimal
impact
and
then
just
sending
data
to
the
backend.
It's
usually
four
kilobytes
per
second,
so
really
minimal.
On
that
end,
as
well.
A
A
B
So
that's
actually
a
great
question.
We
actually
look
at
C
groups
and
namespaces
to
kind
of
see
what's
running
on
that
host,
so
we
actually
leverage
those
utilities
and
our
that's.
What
we
use
to
detect,
which
calls
are
coming
from
which
place
we're
prepackaged
in
Debian
we're
working
really
closely
with
the
rel
team
as
well.
We're
prepackaged
in
core
OS.
So
yes,
C
groups
and
namespaces
are
a
fundamental
part
of
the
Cystic
kernel
module.
A
B
A
B
We're
actually
going
to
be
will
have
a
booth
at
Linux
coin
container.
Con
we're
gonna
have
multiple
members
of
our
team
out
there.
So
if
you're
going
to
be
at
that
conference,
please
stop
by
and
we
can
show
you
some
more.
We've
introduced
some
pretty
cool
new
functionality
to
our
open-source
tool.
So
that's
another
great
thing
that
we
can
show
you
there
all.
A
B
All
right
so
to
get
back
to
the
presentation,
so
this
instrumentation
gives
us
much
better
visibility
and
typical
infrastructure
monitoring
products
can
tell
you
things
like
if
a
host
is
up
if
host
is
down
what
your
CPU
and
memory
usage
are
are
doing,
but
they're
not
really
giving
you
a
good
view
into
how
your
services
are
performing.
So
this
instrumentation
gives
us
that
service-oriented
view.
B
We
also
are
able
to
auto,
discover
your
applications
and
then
apply
alerts
across
your
whole
infrastructure,
based
on
the
metadata
that
we
pick
up
and
then,
lastly,
we're
able
to
move
past
a
spike
in
a
dashboard
and
kind
of
get
down
to
all
the
system
calls
that
were
running
when
an
alert
fired
so
to
start
off,
I'll
go
to
the
service-oriented
performance
management,
and
a
lot
of
you
are
deploying
applications
that
look
like
this.
So
it's
across
multiple
nodes.
B
You
have
multiple
containers
on
each
node
that
make
up
different
services
and
making
sense
of
these
services
and
how
they
interact
with
each
other.
Isn't
something
that
you
want
to
do
on
a
host
by
host
basis?
You
want
to
do
it
on
a
service
basis
and
what
Cystic
can
do
is
trace
each
individual
process
and
aggregate
those
services
as
a
whole
and
give
you
an
answer
to
something
like.
What's
the
response
time
of
my
Cassandra
service,
that's
currently
distributed
over
three
data.
What
are
the
slowest
queries?
B
We
also
have
a
real,
deep,
real
time,
understanding
of
the
orchestration
metadata
so
working
really
closely
with
people
like
docker
and
kubernetes.
We
are
actually
one
of
the
original
members
of
the
openshift
prime
program
that
launched
a
couple
weeks
ago.
We're
really
excited
to
see
where
that
goes,
I
think
it's
a
great
place
for
anyone,
who's
thinking
about
deploying
openshift
to
go
and
learn
best
practices,
see
the
different
tools
and
I'm
really
excited
to
see
how
that
community
grows
over
time.
B
So
getting
down
into
how
we
work
with
openshift.
You
said
you
set
up
assisted
cloud
project
in
your
open,
shipped
environment.
You
have
to
modify
a
little
bit
of
the
security
policies
and
then
the
coolest
part
here
is
you
install
our
agent
and
the
kubernetes
daemon
set,
and
then
we
get
full
visibility
into
your
entire
cluster.
So
it's
really
a
single
change
that
you
make
and
then
you
get
complete
visibility
across
all
your
hosts.
B
It's
a
really
insulin
cool
installation
process
when
I
go
through
it
with
people
and
they
install
and
basically
our
whole
UI
fills
up
with
all
this
information
they
didn't
have
before
it's
something
that
is
really
exciting
to
go
with
go
through
with
the
person
so
back
to
the
application
auto-discovery,
we
discover
all
the
applications
that
are
running
on
your
hosts,
so
no
plugins
required.
We
look
at
each
system,
call
and
detect
those
and
then,
since
we
detect
those,
we
have
a
bunch
of
pre-built
templates,
which
you
can
think
of
as
mini
dashboards.
B
B
So
if
you're
using
stats
the
year
JMX,
you
don't
have
to
install
an
agent,
you
can
even
write
your
stats,
the
metrics
to
localhost
or
dev
dev,
slash
null,
and
since
we
see
that
system
call
being
made
we're
gonna,
autodiscover
those
metrics
and
allow
you
to
alert
on
them
graph
them
do
whatever
and
then
last
with
the
anomaly
detection,
cystic
cloud
stores
your
password
and
from
there
we
can
set
alerts
and
actually
alert
you
based
on
deviation
against
that
performance.
And
then
you
can
spin
up
new
services
and
will
Auto
discover
this
as
well.
B
B
Ok,
so
the
last
part
here
is
trace
chip
and
troubleshooting,
and
this
is
one
of
the
things
that
I
think
is
the
coolest
about
cystic
cloud.
It's
a
really
nice
blend
between
our
open-source
tool
and
our
commercial
product,
and
so
we're
in
alert
fires.
We
can
actually
get
a
trace
of
every
single
system
called
that
was
happening
at
that
point
in
time,
and
so
you
can
see
basically
past
this
bike
in
the
dashboard.
Pull
down
that
SCAP
file
and
start
tracing
down
to
each
system.
Call
that
a
Redis
container
made
when
the
alert
went
off.
B
B
Okay,
so
what
we're
looking
at
now
is
a
simple
four
node
OpenShift
cluster
and
the,
and
we
get
a
this
deep
visibility
to
OpenShift
kind
of
through
a
lot
of
the
things
that
kubernetes
used
as
well.
So
I
can
drill
down
into
any
physical
host,
see
all
the
containers
that
are
running
on
that
host
down
to
the
individual
network
connections
between
containers
and
then
even
down
to
the
process.
That's
running
inside
each
container
and
as
you
can
see,
this
is
a
pretty
messy
environment.
B
B
So
if
you
look
at
this
map
now
we're
looking
at
the
four
different
namespaces
that
I
have
running
and
I
can
drill
into
my
production
namespace
and
actually
see
how
my
different
services
are
talking
to
each
other.
So
this
is
completely
abstracting
away.
The
host
and
giving
me
a
nice
service
level
view
of
what's
going
on
and
I
can
drill
into
any
service.
See
all
the
pods
that
are
managing
the
containers
and
then
down
any
inside
each
pod
down
to
the
container
and
the
individual
process.
B
That's
running
there
as
well
with
the
same
network
connections
for
going
in
and
out
and
any
of
these
you
can
dynamically
change
to
show
whatever
you
want.
So,
if
I
wanted
to
go
from
CPUs
percent,
do
let's
see
the
memory
bytes
total?
That's
something
I
could
switch
if
I
wanted
to
look
at
maximums
or
minimums
I
can
do
that
as
well.
B
B
Okay,
one
of
the
other
things
that
our
open
ship
users
really
like
is
the
ability
to
look
at
how
you're
different
opens
shift.
Services
are
performing
so
for
the
clip
click
on
open,
shipped
overview
here.
I
can
actually
see
the
top
namespaces
that
I
have
running
in
terms
of
the
amount
of
containers
that
are
running
on
them.
My
top
services
as
a
whole,
so
I
can
see.
B
B
So
looking
at
things
like
sequel
errors,
average
and
max
request
time,
the
top
queries
that
you're
running
the
top
tables
slows
query
slowest
tables,
so
things
that
you
would
kind
of
expect
from
more
of
a
APM
link
tool.
We're
gonna
pull
automatically
out
of
the
box
without
any
configuration
on
your
end.
B
So
now,
let's
switch
to
the
explore
tab,
and
this
is
the
place
that
our
users
use
the
most
to
get
really
deep
visibility
into
your
system
and
think
of
this
as
a
massive
pivot
table
for
your
environment.
So
you
can
change
how
this
table
looks
drill
down
into
different
services.
However,
you
want
what
we're
looking
at
now
is
kind
of
a
view
that
you
would
get
from
a
typical
monitoring
tool.
B
So
since
OpenShift
uses
a
lot
of
the
same
things
as
kubernetes,
I
can
actually
apply
those
labels
and
what
we're
getting
now
is
a
nice
table
of
all
the
different
namespaces
that
are
running
and
so
I
can
actually
open
up
my
production
namespace
and
see
all
those
services
that
are
running
and
then
you
can
go
into
each
service,
see
the
pods
down
to
the
each
container.
That's
running
there.
B
Table
opens
below
and
think
of
this
as
a
bunch
of
mini
dashboards
that
we
automatically
provide.
So
you
can
get
information
about
how
that
service
is
running
and
I
can
actually
drill
down
further
with
this
WordPress
service
and
I.
Could
click
on
an
individual,
pod
and
I'd
get
the
performance
of
how
that
pod
is
running,
and
this
will
dynamically
change,
so
you
can
do
it
from
a
service.
You
can
do
that
a
pod
level
or
you
can
do
it-
eat
down
to
the
individual
container
and
you'll
automatically
get
things
like
CPU
usage
memory
Network.
B
But
since
it's
a
WordPress
service,
you
might
want
to
look
at
things
like
HTTP,
specific
metrics.
So
if
I
click
on
HTTP
here,
we'll
start
getting
things
like
request,
counts,
error,
counts,
average,
request
time,
top
URL
slowest
URL
status
codes
and
any
of
these
applications
that
you
see
on
the
side
will
automatically
build
these
mini
dashboards
for
you
and
allow
you
to
really
get
deep
visibility
with
no
work
on
your
end
to
see
what's
going
on.
B
If
you
see
anything
interesting
here
that
you
might
want
to
look
at
later,
it's
really
easy
to
just
click.
Pin
to
a
dashboard,
and
then
this
specific
panel
that
you're
looking
at
can
be
pinned
to
a
dashboard
for
you
to
monitor
over
time.
So
one
of
the
things
I'll
do
is
if
I
ever
find
a
bug.
That
is
something
that
pops
up
more
than
once.
B
So
one
of
the
other
cool
things
we
can
do
is
our
alerting,
and
so,
if
I
click
on
this
alert
ad
alert
button,
it's
automatically
set
this
scope
to
my
WordPress
service,
because
that's
what
we've
drilled
into
and
we
have
a
couple
different
alert
types
you
can
set
so
a
manual
or
this
is
your
basic
threshold
type
alerting.
You
can
look
at
baseline
alerts,
so
this
looks
at
the
past
performance
and
tries
to
spot
anomalies
against
it
or
you
can
do
a
host
comparison
alert.
B
We
also
have
advanced,
alerting
capabilities
that
are
kind
of
familiar
to
anyone
that
have
done
boolean
a
lodge
boolean
logic
alerting,
so
you
can
look
at
things
like
I
only
want
to
be
alerted
if
my
transactions
are
down
and
my
memories
high.
This
really
helps
reduce
the
pager
fatigue
and
lets.
You
really
fine-tune,
though,
alerts
that
you
set
for
your
service
or
for
your
host
or
really
whatever
you
choose
from
there.
We
can
send
the
alerts
to
slack.
We
can
send
them
to
pager
duty.
B
We
can
send
them
via
email,
we're
gonna,
be
sending
out
a
victory
offs
capability
for
alerting
as
well,
and
then
we
also
actually
released
a
really
new
cool
slack
integration,
where
you
can
actually
wrap
anything
that
goes
into
slack
too
to
Cystic
clouds,
so
I'll
cover
that
a
little
bit
later.
The
last
thing
here
is
the
Cystic
capture,
and
this
will
get
me
that
trace
file
of
all
the
system
calls
that
were
going
on
at
that
point
in
time,
definite
as
I
enable
this
I
can
change.
B
The
name
of
the
alert
I
can
set
the
timeframe
that
I
want
that
alert
to
run
or
that
capture
to
run
for
and
then
that
cache
will
be
taken
and
draw
an
s3
bucket.
You
can
keep
it
stored
in
system
cloud.
You
can
configure
your
own
storage
in
point,
and
this
allows
you
to
really
pull
down
that
capture
file
and
be
able
to
go
through
and
trace
it
without
even
needing
host
access
to
that
environment.
So
it
makes
it
a
lot
of
times
like
I'll,
get
locked
out
of
a
box
or
I.
B
Just
don't
even
have
SSH
access,
and
you
can
just
send
us
that
Tracy
or
you
can
just
pull
down
that
trace
capture
and
really
get
down
to
what
went
wrong.
The
other
really
cool
thing
is
a
lot
of
times.
I'll
just
kill
a
container
for
a
problem,
and
then
I
can
go
back
and
look
at
that
trace
capture
and
get
a
really
good
nice
deep
picture
of
what's
going
on
so
if
I
switch
over
to
my
terminal.
B
This
is
a
capture
that
I
had
previously
downloaded
and
if
you've
ever
used,
H
type
before
this
is
a
really
similar
look
and
feel
so
what
we
can
do
here
is
so
you
can
see
I've
got.
This
is
a
view
of
all
the
processes
that
were
running
on
the
machine
when
that
alert
went
off,
but
I
can
apply
different
filters.
So
let's
go
and
look
at
the
containers
that
were
running
on
that
host
when
the
alert
went
off
from
here,
I
can
actually
drop
into
my
Redis
container.
B
Be
that
single
Redis
process
that
was
running
and
maybe
I
want
to
print
out
all
the
system
calls
that
went
on
so
now
you
can
see
these
were
all
the
system
calls
that
that
Redis
process
made
when
that
alert
went
off.
So
it's
kind
of
doing
a
heartbeat
getting
the
time
of
day.
It
opened
a
file
and
read
from
it.
It
closed
it,
and
this
this
allows
me
to
really
get
a
nice
picture,
especially
in
containerized
environments
of
what
was
going
on.
B
Another
cool
thing
you
can
do
is
actually
inspect
each
individual
Redis
transaction
that
went
through.
So
let
me
make
this
a
little
bit
easier
to
read
and
you
can
see
like
26
bytes
were
read
from
this
host
over
this
port,
the
individual
raddest
transaction
that
went
through
and
there's
a
lot
of
different
things.
You
can
do
with
that
open
source
tool
that
we
have
a
ton
of
videos
on
YouTube,
a
lot
of
different
blog
posts
about
use
cases
for
it.
You
can
actually
go
look
at
really
a
host
of
different
things
that
were
going
on.
B
So
I
could
look
at
the
different
system.
Call
types
that
were
made
I
want
to
see
everything
that
did
are
right
on
the
host.
So
really
any
you
name
it.
You
can
kind
of
pull
it
down
from
there
all
right.
So
let's
go
back
to
the
application
and
look
at
some
of
the
things
that
we
can
do
with
custom
events
that
are
running.
B
So
we
automatically
will
pick
up
OpenShift
events
out
of
the
box,
and
so
you
can
look
at
things
like
pod
restarts
containers,
killed,
set
alerts
like
that.
Go
on
and
alert
see
the
specific
chart
if
I
click
explore.
This
will
actually
take
me
back
in
time
to
when
that
alert
was
fired.
So
a
really
deep
amount
of
capabilities
here
that
allow
you
to
troubleshoot
really
at
any
point
in
time.
Since
we
store
all
data
forever
insisted
cloud,
you're
actually
able
to
go
back
and
troubleshoot
things
really
easily.
B
The
other
thing
that
we
have
is
custom
events,
so
actually
don't
have
any
custom
events
running
in
this
environment
now.
But
what
you
can
do
is
add
this
description,
basically
to
anything
that
you're
running
and
then
that'll
send
custom
events,
the
Cystic
cloud,
one
of
the
really
cool
things
that
we
added
recently,
though,
is
this
Cystic
slack,
but
and
then
anything
that
you
send
to
that
Cystic
channel
or
that's
Cystic,
slack
bot,
channel
it'll
route
to
the
Cystic
cloud
application.
B
B
If
I
switch
to
two
weeks,
you'll
get
a
view
like
this,
though,
if
I
go
over
I
can
see,
there
was
a
custom
event
that
went
off
here,
an
alert
fired,
so
the
cube
demo
was
load
network
on
the
Redis
pod,
really
anything
that
you
set
here.
So
there
was
a
little
outage
that
went
on
here
at
our
demo
environment.
Those
things
are
automatically
fired,
and
so
it
allows
kind
of
you
to
correlate
something
that
happened
outside
of
your
environment.
B
You
can
deploy
it
as
the
cloud
service
or
on
Prem,
and
if
you
just
go
to
Cystic
calm,
it
will
be
on
the
home
page
and
it's
really
easy
to
get
started
there
or
you
can
actually
go
to
the
open
shift
hub,
we'll
kind
of
have
more
openshift
specific
stuff
there,
and
then
we
have
links
to
where
you
can
start
a
free
trial.
So
thanks
everyone
for
joining
and
I'm
excited
to
see
what
questions
you
have
so.
A
This
was
this
is
an
awesome.
My
mind
has
completely
been
blown
here,
because
this
this
is
the
kind
of
thing
that
you
know.
Often
people
ask
us
why
we
don't
have
this
stuff
built
and
baked
into
OpenShift
already,
and
this
is
why
we're
not
reinventing
the
wheel.
People
like
you
guys,
are
building
awesome
tools
to
work
and
monitor
and
manage
the
backend
and
follow
this
stuff.
I'm.
C
B
So
our
back
end
is
the
Cassandra
cluster
and
then
we
have
a
little
bit
of
my
sequel
in
there
as
well
for
events
correlation
and
things
like
that.
Basically,
if
you,
if
we
send
it
to
you
as
if
you
choose
the
on-prem
option,
we
basically
package
up
our
entire
application
into
containers
and
then
you
can
scale
it.
However,
you
want
so
it's
a
construct.
B
A
C
C
B
A
A
B
B
So
the
kernel
module
is
fully
open
source.
You
can
see
that
on
our
github
page,
that's
kind
of
the
basis
for
how
we
collect
all
this
information.
The
Cystic
command-line
utility
that
I
showed
is
also
fully
open
sourced.
We
actually
released
a
really
cool
functionality
last
week
that
allows
you
to
trace
basically
any
individual
transaction
through
the
open-source
tool.
So
I
could
tag
a
method.
I
could
do
a
network
request
basically
and
see
how
long
the
each
one
of
those
takes
to
basically
go
through
the
system.
So
that's
really
cool.
B
Our
security
project
is
also
fully
open
source.
That's
called
cystic
falco
that
looks
at
anomaly
detection,
so
you
could
write
a
rule.
That's
hey!
If
someone
runs
a
shell
in
my
container
alert
me
or
if
elasticsearch
has
an
outbound
connection
to
a
port
that
it
shouldn't,
send
me
alert
so
really
cool
stuff
going
through
with
that
as
well.
The
cloud
product
that
we
showed
today
is
not
open
source.
That's
basically
a
commercial
entity,
but
besides
that,
basically
everything
else
is
fully.
A
A
A
C
B
I'm
not
sure
about
that
that
answer
I'll
definitely
have
someone
follow
up
it
to
you
about
that
and
kind
of
look
at
your
reference
architecture
and
see
how
would
fit
in
there.
But
I.
Don't
I,
don't
have
an
answer
for
that
right
now,
all
right.
So
what
we're
looking
at
now
is
just
a
home
page.
If
you
click
free
trial,
basically
sign
up
so
first
name
last
name
email
and
then
you
can
get
going
perfect.
B
The
OpenShift
specific
installation
instructions.
Once
you
start
your
free
trial,
they'll
just
be
a
button
that
says
install
like
OpenShift
install
and
then
it's
a
couple
of
things
that
you
need
to
change
with
some
networking
and
security
functions
and
then
basically
use
the
daemon
set
installation
and
you're
done
so
pretty
cool,
install
process.
A
Like
those
easy
ones
yeah,
this
is
awesome.
The
really
Knox.
Thank
you
for
coming
in
and
doing
this,
the
there
is
one
other
thing
you
said
you
would
show
us
too,
and
I
think
that
you
just
the
slack
integration
which,
for
the
alert
and
I
and
I,
think
there's
I
thought
I
saw
a
blog
post
about
that
on
recently
as
well,
but
it's
for
the
blog
or
a
doc
yeah
more
useful
things.
That's
coming
up
and
request
it.
Often
too.
B
So
yeah
the
really
cool
thing
with
this
is
basically
you
can
design
a
stage
slack
channel
to
send
anything
to
sustain
cloud.
So
I
could
write
in
something
like
I
had
a
big
Chinese
lunch
today
and
I
might
be
sleepy
in
the
afternoon
and
push
some
bad
code
and
then
that'll
be
sent
to
systick
since
a
cloud.
So
what
a
lot
of
customers
are
starting
to
do
is
take
everything
that
they
have
that
sends
them
notifications
and
then
pump
those
into
system
cloud.
So
then
they
can
correlate.
B
B
A
Get
a
lot
of
founders
that
do
that
on
the
weekend
so
yeah
this
is.
This
is
a
pretty
awesome
tool
and
it's
wonderful
not
to
have
to
reinvent
the
wheel
and
to
have
this
available
for
open
ship
and
all
the
kubernetes
stuff.
That's
under
the
hood
that
OpenShift
as
well!
So
thanks
for
for
doing
this
today
and
when
you
get
to
your
next
releases
and
your
new
features
will
do
that
and
I'm
going
to
reach
out
and
see
if
we
can't
be
hook
this
up
through
the
cluster.
A
That's
all
in
with
ciencia
cloud,
if
they're
standing
up
for
us,
so
that
would
be
in
that
another
way
of
showing
some
more
deeper
dives
as
well.
So
that
could
be
a
a
future
briefing
and
we
show
that
and
something
more
than
WordPress
like.
But
that's
the
word
right,
I'm,
not
that
WordPress
is
everybody's
favorite
thing
to
demo
and
nobody's
favorite
thing
to
actually
use
and
deploy.
So
all
good.