►
Description
In the first briefing of the year, Pete Muir from Red Hat and other members of the CDK project, will give you a thorough view of what the Container Development Kit is.
For the latest information on OpenShift 3.1 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
Welcome
everybody
to
this
very
first
openshift
Commons
briefing
of
2016
and
I
annular
and
on
the
community
director
for
open
shift
and
I'm
really
pleased
to
have
with
us
today.
Peep
mirror
and
a
number
of
his
colleagues
and
friends
from
that
brought
the
containers,
development
kit,
their
cdk
project
and
they're.
Then
doing
lots
of
work
trying
to
improve
the
local
container
development
experience
and
they're
here
to
talk
through
their
approach
to
it
and
hopefully
get
your
feedback
on
it.
B
Thank
You
Diane,
so
the
kind
of
the
agenda
for
today
is
I'm
going
to
spend
about,
hopefully
10
15,
maybe
20
minutes
talking
through
kind
of
what
we
see
the
problem
to
be
what
the
goals
of
the
work
that
we've
been
doing
is
and
then
can
I
give
you
an
idea
of.
You
know
in
a
little
more
detail
about
what
we
set
out
to
do
in
order
to
meet
those
goals.
B
I'm
then
going
to
hand
over
to
a
couple
of
colleagues
who
are
going
to
give
you
a
demo
of
what
we
have
so
far.
So
I'll
start
by
introducing
myself.
So
my
name
is
Pete
Mia
I
work
for
Red,
Hat
I'm,
the
engineering
manager
at
Red,
Hat
for
developer
tools
and
with
me
we
have
a
number
of
people
from
the
team,
but
in
particular
speaking,
are
going
to
be
max
Anderson,
who
is
the
architect
and
lead
for
the
tools
that
help
people
build
and
deploy
applications
and
then
Fred,
Bree
Kahn?
B
Who
is
the
who
works
on
the
openshift
tooling
inside
of
Eclipse?
We
also
have
a
few
other
people
who
I'm
sure
will
be
contributing
by
chat,
and
you
know
perhaps
answering
some
questions
at
the
end.
So
before
we
get
started,
you
know
I
want
to
give
everybody
a
sort
of
you
know,
kind
of
an
idea
of
where
we
are
in
this
journey.
When
Diane
asked
me
to
do
this,
she
was
very
clear
that
you
know
you
guys
like
to
hear
quite
a
lot
about.
B
What's
coming
up
that
you
know
what
we
show,
you
could
be
pretty
rough
and
ready,
but
you
would
really
like
to
hear
kind
of
an
idea
of
what's
coming
up
so
I'm
very
much
we're
very
much
here.
In
that
vein,
we're
very
much
here
to
say
look.
This
is
kind
of
what
we're
working
on
I
would
describe
what
we
have
is
sort
of
probably
around
alpha
quality
at
the
moment,
we're
working
hard
to
move
that
into
beta
and
beyond
and
three
to
GA.
B
But
you
know
it
is
rough
around
the
edges,
but
the
goal
is
to
show
you
kind
of
you
know
the
direction
in
which
we're
headed
the
team
has
been
doing
an
amazing
job
of
putting
it
together.
The
first
time
we
really
manage
to
get
an
end-to-end
flow
on
this
on
the
demo
that
we're
going
to
show
you
was
a
couple
of
weeks
before
Christmas
and
also
the
team
was
mostly
us
over
Christmas.
So
you
know
I
think
we're
going
in
the
right
direction.
We've
got
really
good
velocity
going
in
that
direction.
B
So
you
know
I,
like
I,
say
you
know
earlier
earlier
doctors
at
the
moment,
but
I
definitely
encourage
people
to
check
it
out.
So
with
that
I'll
get
started,
I'll
try
not
to
talk
too
much
and
for
too
long
and
get
on
to
the
meat
which
is
the
demo.
So
if
we
could
go
to
slide
two,
please
so
I
wanted
to
start
with
a
kind
of
a
quick
problem
statement
with
a
developer
tools
team.
So
we
really
care
about
making
development
development
of
applications
easier.
B
We
see
containerized
applications
as
probably
one
of
the
most
important
trends
in
application
development
in
the
industry
for
a
very
long
time,
because
it
you
know,
because
of
all
the
well-known
benefits
of
of
containers,
of
docker
containers,
but
we
also
recognize
that
you
know
this
is
a
new
technology
and
at
times
it's
been
really
hard
to
actually
build
applications.
Many
other
kind
of
conveniences
that
we're
used
to
when
we've
built
applications
to
run
on
bare
metal
kind
of
you
know
got
lost
in
the
containerization
effort.
B
So
you
know
it
was
pretty
hard
to
get
started
with
the
times
and
it
was
also
pretty
slow.
There
were
some
really
long
turnarounds
when
you
would
have
to
you
know
change
your
code
test.
It
out,
you
know,
get
sorry
build
it
into
the
container,
get
the
container
running
and
see
those
changes
running.
You
know
that
goes
through
you
know,
so
my
background
is
with
with
Java
middle,
so
something
like
Gables.
B
Absolutely
you
know
when
I'm
running
on
bare
metal
I
can
get
a
turn
around
in
a
you
know:
2
3,
4
5
10
seconds,
with
the
application,
restarting
if
I'm
doing
that
in
a
container
that
can
be
up
to
minutes.
We
are
really
concerned
about
that,
because
we
know
that
the
kind
of
the
code
debug
cycle
that
people
work
through
needs
to
be
really
fast
in
order
for
developers
to
be
productive.
B
So
if
we
want
to
go
to
slide
3
our
goals,
like
I,
said
pretty
simple:
it
needs
to
be
really
simple
for
the
scenarios
that
we
defined,
which
is
kind
of
this
getting
started
scenario.
We
focus
very
strongly
on
Java
and
on
JavaScript.
Those
are
our
two
focus
areas
and
particularly
focusing
I
guess
on
kind
of
micro-service
the
apps
written
using
using
java.
Secondly,
it's
got
to
be
really
fast,
so
it's
very
really
fast
to
write
debug
code,
so.
B
B
So
if
we
want
to
go
to
slide
5
and
I'll
talk
a
little
bit
more
about
what
we've
been
working
on
and
kind
of,
you
know
who
your
target
audience
is
and
why
it
might
be
relevant
or
why
it's
relevant
to
you.
One
of
our.
You
know
one
of
our
guiding
principles
in
the
developer
tools.
Team
is
that
you
know
we're
quite
opinionated
about
what
we
do
so
we
took.
B
We
know
that
we
want
to
produce
a
really
productive,
really
good,
developer
experience,
but
we
know
that
you
know
if
we
try
and
do
that
for
everyone
that's
going
to
be
really
hard
to
achieve.
So
we
try
to
be
really
tightly
focused
on
some
particular
types
of
users
and
some
particular
scenarios
to
try
and
really
optimize
for
those.
B
B
B
Our
goal
for
the
first
year
was
simple,
so
we
wanted
to
make
sure
that
everything
you
needed
to
build
your
java
application
knew
your
JavaScript
application
was
included
in
the
box,
and
so
for
us
that
meant,
we
included
JBoss
developer
studio,
our
IDE
open
JDK.
In
order
to
be
able
to
run
the
IDE
running
on
your
Windows
machine,
we
included
the
container
development
kit,
which
gives
you
access
to
an
open
shift
environments
running
on
your
local
machine.
B
We
include
vagrant
in
order
to
get
the
the
cdk
up
and
running
and
VirtualBox
in
order
to
run
the
virtual
machine
with
the
cdk
runs
in
this
all
comes
in
a
single
download,
a
single
installer
and
it
runs
like
I
said
on
Windows.
So
what
if
we
go
to
slide
7,
please?
So
what
scenarios
is
this
optimized
for?
And
this
is
where
we
come
back
to
well
both
well
goals.
B
So
it's
optimized
for
running
a
what's:
develop,
studio
and
open
JDK
running
on
your
Windows
laptop,
which
then
communicates
with
an
overshift
that's
running
inside
a
virtual
machine
where
you
can
interact
with
the
lifecycle.
You
can
use
the
source
to
image
capabilities
and
you
can
interact
also
with
it
using
the
GUI
and
the
CLI
and
then
we're
looking
at
applications
which
are
running
inside
docker
containers
and
we
were
particularly
focused
on
EAP
JBoss,
EAP
applications
and
nodejs
applications.
B
B
B
So
what
was
our
kind
of
you
know
what
was
kind
of
our
conceptual
journey?
How
do
we
think?
What
do
we
think?
The
steps
that
you
needed
to
take
in
order
to
get
started
should
be,
and
then
you
can
judge
us
when
we
do
the
demo
on
how
well
you
think,
we've
attained
them.
So
if
we
go
to
slide
10
please,
so
we
assume
that
you
were
starting
with
a
pretty
much
a
bare
metal
machine.
B
B
This
description
isn't
quite
launched
yet,
which
is
going
to
make
it
somewhat
hard
to
use
right
today,
but,
like
I
said,
you
know,
we're
we're
working
on
all
of
these
items
and
getting
all
of
these
done.
So
if
we
go
to
slide
312,
please
so
haven't
got
your
redhead
comb
accounts.
The
next
we
used
to
do
is
download
and
run
the
installer,
so
the
installer
will
install
the
components
we
talked
about
in
the
box,
so
JDK
the
container
development
kit,
dev
studio
and
open
ship
Enterprise
we
go
to
slide
13.
B
B
D
Hey
Thank
You
Pete,
so
this
is
max
Anderson,
as
Pete
said:
I'm,
the
architect
behind
deployment
and
coding.
In
our
developer,
experience
in
the
past
I've
been
leading
the
developer
studio
work.
So
if
you
see
me
talk
about
Eclipse
plugins,
that's
what
I'm
doing
the
last
few
years,
but
now
we
going
into
more
clips,
tooling
and
and
and
beyond,
for
this
container
tooling,
so
I'll
show
it
in
the
last
over
yes,.
C
A
D
C
D
C
C
D
Okay,
cool
sorry:
for
that
penny,
wait
I'll,
show
the
Installer,
then
I
hand
out
sue
Fred
for
doing
the
the
tooling
workflow
and
we'll
come
back
to
me.
I'll
summarize
what
was
shown
and
some
of
the
things
that
we
couldn't
fit
into
the
demo
or
we
haven't
pulse
enough
to
show
off
yet
again
the
deer.
What
are
you
seeing
here,
I'm
showing
a
video
at
the
Installer
because
actual
running
installed
takes
a
bit
of
time,
because
it
is
it's
a
router
pick
up
that
big
download
I'll
walk
you
through.
D
So,
first
of
all,
when
you
have
the
Installer,
you
will
have
to
login
with
your
username
and
password
for
the
developer.
Rahat
developer
account-
and
this
is
purely
just
to
get
access
to
the
product
size
binary.
It's
like
home
ship
Enterprise
to
cdk
that
has
a
darker
and
Tomic
in
it
and
yeah
by
syllabus
to
do
in
there.
D
So
once
you've
logged
in
able,
of
course
verify.
If
you
haven't
don't
have
access,
it
will
tell
you
to
go
and
create
them.
So
I'll
just
pause
here
for
two
seconds
and
you'll
see
this
is
first
place
of
installer.
It
has
the
album
dyrdek,
a
v8
they'll
run
on
Windows,
a
red
container
development
toolkit
was
called
cdk.
This
is
where
we
have
darker
and
album
shifts
and
a
base
OS
to
run
on
your
Windows
machine.
D
Then
we
had
available
studio
in
this
case
is
version
9,
which
will
have
all
the
Eclipse
tooling
for
doing
Java,
EE,
JavaScript
development
and
now
container
target
welcome
to,
and
then
finally
inside
will
be
ripe.
Enterprise
and
I
go
further.
Lucila
bill
details
will
start
downloading
all
these
things.
In
the
background
we
also
have
installed.
Have
everything
bundled
it'll
probably
be
a
bit
bigger,
but
it
is.
D
It
will
start
installing,
like
cdk,
vagrant,
VirtualBox,
JDK,
abs
and
sequin
is
in
this
case,
which
is
to
get
stuff
like
our
sink
and
SSH,
which
you
need
to
talk
from
your
host,
in
this
case
windows
to
dark
current
ohm
shift
in
a
in
a
nice
manner
and
now
I'm
just
kind
of
fast
forward,
because
this
will
take
some
time
and
there's
no
fun
in
in
doing
that
life.
So
once
you're
at
the
end
and
you're
running
on
Windows,
you
get
it
in
the
folder
here
now
called
real
platform.
It
has
everything
in
it
see.
D
Dk
is
sick
when
you
decay
breaking
Birchbox
and
we
put
it
there,
so
it
doesn't
collect
anything.
Just
you
shouldn't
be
able
to
run
on
any
machine
and
the
whole
idea
as
PDS
writer
is
that
all
this
it's
just
kind
of
configured
to
work
together,
so
just
see
DK
works
on
its
own,
but
the
IDE
is
set
up
to
be
able
to
know
where
these
components
are
and
talk
to
them
and
that's
the
installer
yeah.
D
C
E
That
will
be
shown
in
service
to
you
here
so
that
CD
case
server
adapter
basically
allows
us
to
start
and
stop
the
beggar
in
the
penguin
file
that
that
starts
the
city
itself.
So
once
I've
started,
what
will
happen?
Is
it
will
spin
up
the
open
ship
instance
and
well
we'll
also
be
able
to
show
the
docker
registry
inside
that
inside
to
desiccate?
So
let
me
just
started.
C
E
E
There
you
go,
I
can
select
the
image
like
the
tag,
I
want
to
to
install
and
click
finish,
and
it
will
pull
the
image
in
my
docker
registry
so
yeah.
This
is
basically
the
internals
at
the
open
ships
instance
that
I'm
running
from
the
CDK.
So
on
the
other
side
in
the
open
Explorer,
you
will
see
that
I
have
a
new
connection
to
the
open
local
opposite
instance
provided
by
the
cdk.
E
So
in
that,
in
that
instance,
I
have
a
couple
projects
take
intact,
and
my
goal
now
is
to
to
deploy
a
Java
EE
app
on
to
OpenShift.
So
this
is
my
local
cloud
environment
running
on
my
laptop.
So
in
order
to
do
that,
what
I
can
do
is
take
any
kind
of
project
from
the
java
central
page,
which
allows
me
to
access
at
least,
say
200
examples.
So
if
I
want
to
to
create
a
rest,
rest
application
using
the
jax-rs
framework,
I
can
select,
for
instance,
little
world
RS
and
loading.
E
The
media
data
group
like
a
couple
seconds
and
the
wizard
tells
me
that
the
EDS
app
runs
on
EAP,
6
or
or
wildfly,
and
it
works
best
using
the
11c
CI
configurator.
So
I
will
not
complete
the
process
here
because
it
takes
a
few
seconds
and
I
really
already
have
it
in
my
work
place.
So
this
app
is
a
Java
EE,
app
using
rest,
endpoints
and
CDI
as
a
dependency
injection
framework.
So
the
tooling
that
we
provide
allows
you
to
quickly
navigate
through
the
rest.
E
E
So
this
is
my
java.
Ee
app
runs
locally
on
my
EOS
local
service
instance.
So
now
the
goal
is
to
run
that
same
web
app
inside
open.
So
how
would
you
do
that?
It's
as
simple
as
saying
configure,
deploy
to
open
shift
now
in
order
to
do
that.
So
this
is
the
signing
page
to
open
shift.
You
need
your
username
and
password
so
now
in
order
to
deploy
your
app
there's
one
major
prerequisite.
E
I
this
project
needs
to
be
shared
with
get
so
that
the
open
ship
instance
those
where
the
sources,
the
the
sauce
lives,
and
so
it
can
clone
the
repository
and
build
the
sources.
So
I've
done
that
before
before
creating
the
after
trading
project
before
the
demo.
Now
that
I
have
my
selected
projects,
because
this
is
a
maven
based
project,
it
has
a
pom.xml.
The
the
wizard
will
filter
the
available
templates
on
open
ship
using
the
AP
keyword,
but
I
can
select
any
other
kind
of
template
if
I
want.
E
So,
in
our
case,
I'm
gonna
just
stick
with
the
EP
6
4
basic
sty
template
it.
Will
it's
exactly
that
basically
runs
the
same
yupi
server,
but
on
open
ship.
So
here
in
the
template
parameters,
I
can
see
the
source
repository
URL
points
at
my
personal
repository
on
github,
I
click
Next
finish
and
the
the
application
has
been
created
on
the
OpenShift.
E
E
Does
bargain
okay?
So
in
my
tack
projects
my
EAP
app
is
running,
the
build
is
running
so
what
I
can
do
is
open.
The
build
log
see
what's
happening
and
I
can
see
the
the
maven
app
is
being
built,
so
it's
gonna
take
a
long
time
about
five
minutes.
So
in
the
meantime
we
can
do
some
other
things.
Probably
we
can
take
a
look
at
what
the
Explorer
provides.
E
So
we
can
see
we
can
have
access
to
build
logs,
but
we
can
also
take
another
app,
for
instance,
that
one
that
that's
already
deployed-
and
you
show
in
web
browser
and
in
that
case
I-
have
a
node.js
app,
that's
running
on
up
and
shipped
on.
My
local
machine
I
can
also
show
the
same
project
in
the
web
console.
So
this
is
the
open
chip
console.
E
So
you're
familiar
with
openshift,
then
you
will
be.
You
will
be
at
ease
here
and
another
thing
that
we
can
do
is
edit
some
configuration.
So
in
that
case
my
node
app
points
at
the
openshift
repository.
So
I
want
to
change
that.
To
use
my
own
fork,
I
can
edit
the
buildconfig
and
click
check
the
source
change
it
to
my
fork.
Save
it
and
it
will
see
the
index
up
to
explore
the
get
URL
change
to
use
my
own
for
so
I.
Don't
have
it
in
my
workspace,
but
I
can
import.
E
There
it
is
okay,
so
that
that's
one
way
to
deploy
the
your
local
project
on
open
chip,
but
it
takes
a
text
of
several
minutes.
So
the
turnaround
is
not
really
exciting,
but
we
can
do
better,
so
I'm
gonna
demo
now
how
to
get
incremental
deployment
in
a
really
really
much
faster
way,
using
the
node.js
app.
E
E
E
E
Its
done,
and
if
I
refresh
it
the
app
is
being
refreshed.
So
it's
much
much
faster
to
work.
That
way
using
the
OCR
sync
feature:
that's
hidden
behind
that
OpenShift
server
that
there
we
can
do
even
slightly
better
here,
I
had
to
to
refresh
the
browser
manually,
but
I
can
also
open
that
that
page
in
a
live,
reload
server,
so
basically
the
library
server
as
a
proxy
to
the
open
seas.
Server,
so
I
got
a
CD
well
here
I
got
a
local
URL
and
every
every
time
my
browser
receives
a
a
query.
E
E
E
So
currently
we
need
will
still
need
to
manually.
Do
the
publishing
part,
but
eventually
will
will
do
the
automatic
publishing
as
as
soon
as
you
save
your
file,
so
that
that's
a
way
to
get
a
much
much
better
turn
around
while
they're.
Looking
your
your
app
on
a
budget,
so
we
deployed
our
yipee
app
earlier.
E
E
C
D
D
A
E
D
I'll
continue,
so
everything
just
works,
the
setup
it
when
you
start
up
eclipse,
it
will
know
about
VM.
You
have
running
we
installed.
We
know
about
the
the
cdk,
the
vacant
file
that
is
used
for
starting
it.
It
will
know
about
the
darker
and
open
shifters
comes
available
when
CDKs
steps
up
and
you
don't
have
to
set
anything
up
inside
the
clips
and,
of
course
there
is
the
actual
container
two
links
which
fred
showed
like
for
darker
and
open
shapes,
etc.
D
These
are
now
being
expanded,
also
to
cover
up
shift
v3
beyond
that.
He
showed
to
take
one
of
these
quick
starts
and
load
into
eclipse,
meaning
it
was
an
existing
clips
product.
There
was
not
an
ovum
shift,
but
then
take
that
accession
product
and
deploy
up
to
to
an
overshift
instance.
Now,
in
this
case,
running
locally
on
your
CD
k.
D
If
you
know
OC
the
command
line,
this
is
similar
to
what
OC
new
app
does,
but
just
in
in
the
clip
setting,
but
now
where
it
becomes
really
Singh
is
the
incremental
deployment.
So
the
what
he
did
show
what
we
have
working
now
is
incremental
deployment
of
no
GS,
because,
as
you
noticed,
the
the
actual
the
first
deploy
on
a
Java
EE
app
might
be
a
bit
heavy,
especially
if
you're
doing
the
full
maven
build
a
full
docker,
etc.
D
So
an
ohm
shift
as
a
tool
called
OC
sync,
which
allows
you
to
comenta
Li,
do
to
take
changes
from
your
local
file
system
up
till
an
overshoot
instance,
and
what
Fred
showed
was
using
that
behind
the
scenes
in
our
adapter
to
do
for
a
node,
no
lab
and
then
to
get
her
to
no
tap.
He
had
live
reload
running
so
when
he
did
changes
in
his
ID,
they
wheeler
in
his
browser
once
they
had
published
to
the
server
and
if
you
come
from
a
local
deployment
like.
Why
is
this
interesting?
D
Like
I
said,
we've
been
doing
this
for
a
while.
Well,
that's
exactly
what
we're
trying
to
do
make
sure
that
what
you've
been
able
to
do
locally,
that
you
can
do
that
on
an
ohm
ship
instance,
whether
that
is
to
see
decay
locally
here
where's,
the
turnaround
should
be
decent
or
if
it's
in
a
cloud
where
it
might
be
a
bit
slower
because
of
network
latency,
etcetera,
but
any
any
way
the
air
is
too
local,
obvious
of
employment.
D
You
have
you,
get
almost
instant
feedback,
then
what
you
have
for
local
deployment
via
this
incremental
deployment
using
OSI
sync
and
then
the
live
reload
that
we've
had
for
a
while,
but
it's
all
integrated
now
in
the
IDE
tooling,
and
you
know,
shift
okay.
So
a
few
things
that
we
didn't
manage
to
show
you
here,
but
we
are
either
already
have
but
didn't
couldn't
fit
into
the
demo
or
we
planning
the
one
is
the
incremental
deployment
of
Java
EE.
Though
again
we
saw
that
the
rather
slow
first
apply
mono
de.
D
We
want
to
do
the
same
thing
using
a
local
build
and
the
OSI
sync
over.
So
we
can
do
the
Java
class,
replace
HTML,
CSS,
JavaScript
cetera
replacement,
but
on
top
of
that,
if
you
know
Java,
sometimes
we
change
classes.
These
changes
doesn't
take
effect
immediately.
This
is
something
that,
when
we'd
run
locally,
we
can
just
kind
of
just
restart
the
container
and
everything
is
fine,
sorry
restart
the
application
container,
but
in
the
in
a
darker
scenario
or
in
a
Microsoft
scenario,
this
might
actually
take
longer.
D
For
some
cases,
though,
we've
looked
at
integrating
what
we
call
harbor
load
of
Java
apps.
So
if
you
know
things
like
springle,
loaded
or
J
rebel,
that
kind
of
functionality,
we
are
looking
at
embedding
into
the
toolset
into
home
shift,
but
a
few
things
that
is
optimized
for
EAP,
so
you
get
the
right.
You
only
get
restarted
with
things
you
actually
need
and
again
this
is
all
to
make
sure
we
change
something
on
your
in
the
developer
environment.
You
can
see
the
chains
fast
without
having
to
rate
for
too
many
be
deployments.
D
D
Even
more
is
one
of
the
things
that
the
big
the
thing
we
we
don't
have
yet,
but
really
wanted
you
to
do
is
when
you
have
this
local
set
up
in
an
object,
application
running
locally.
How
do
I
make
that
run
on
another
objective
instance?
But
luckily,
because
we
use
in
communities,
this
should
just
be
about
taking
your
application
and
the
scriptures
in
from
communities
and
deploy
it
to
another
instance.
So
you
want
to
make
that
easy
too.
D
D
Yes
in
today,
if
you're
running
no
GS
on
shift,
it
will
run
let's
call
in
production
mode,
meaning
you'll
have
to
restart
the
full
container
to
see
changes
to
your
Java
scripts,
but
you
can
do
change
the
HTML
and
CSS
just
fine,
but
not
for
the
JavaScript
code,
which
is
kind
of
you
know
the
thing
you
want
to
change.
We
need,
you
know
GS.
D
So
we've
extended
the
the
note.
Yes,
containers
on
open
shift
to
have
again
a
similar
flag
we
can
set,
though,
when
you
run
a
node,
the
node
application,
the
ide
can
do
OC.
You
think
it
will
see
a
change
and
you'll
restart
the
node.js
container.
Not
the
whole
setup
mean
it,
meaning
you
won't
lose.
You
don't
have
to
wait
for
anything
there.
On
the
home
shift
site,
okay,
that's
kind
of
the
additional
plant
features
another
one
is
you
know:
we've
focused
very
much
on
on
eclipse
in
this
presentation.
D
What,
if
you
don't
use
Eclipse?
Well,
the
great
thing
is
that
we
all
the
tooling
active,
showed
Eclipse
didn't
use
anything.
You
know,
customer
specific.
It
was
all
using
standard
darker
protocols
over
shift,
api's,
etc,
and
that
means
existing
tooling
out
there.
Whether
that
is
you
know,
darker
command
line,
object,
command
line,
OC,
cube
control.
All
that
stuff.
You
can
run
on
your
windows
instance
and
connected
it
to
this
to
to
to
cdk.
D
There
is
a
vagrant
polling,
plug-in
called
reagan,
adb
info,
which
will
dump
out
the
information
that
is
necessary
to
set
up
these
command
line
tools.
The
view
tries
things
like
dhaka,
machine
or
making
air
box
that
that
this
works
in
same
way.
You
just
get
these
severe
environment
variables,
which
then
other
tools
can
can
use
and
connect
to.
So,
if
you
are
a
non
eclipse
user
or
command
line
user
or
IntelliJ
or
something
else,
and
they
have
similar
tooling,
this
will
work
with
it
too.
D
And
finally,
the
cdk
is
basically
a
little
pre-configured
Linux
VM,
meaning
you
can
do
vagrant
is
a
sites
into
it,
and
then
you
can
you
know
access
is,
as
you
want,
as
a
Linux
mindset.
If
you
want
that,
okay,
so
how
to
try
this
out
now,
as
Pete
said
in
the
beginning,
this
is
kind
of
alpha
quality.
There
are
some
parts
that
is
there
now,
especially
the
the
Eclipse
tooling.
That
fred
was
showing.
This
is
all
something
you
can
try
today
use
that
against
existing
darker
existent
openshift
two
instances.
D
The
part
that
is
not
in
a
easy
to
download
available
today
thing
is:
there's
the
cdk
packaged
in
a
way
that
has
open
ships
in
it
which,
but
you
can
get
the
source
for
it.
It's
all
on
github,
become
read
after
all,
the
best
tooling
OSHA
vagrant
as
some
slide
and
then
finally,
the
whole
installer.
Also
the
source
code
for
that
is
available
is
actually
electron
app.
It's
that
kind
of
thing.
D
I
just
want
to
just
point
out
that
currently
the
downside
of
these
bills
is
they
did
and
on
binary
is
only
available
inside
Red
Hat,
not
now,
but
it
can
give
you
an
idea.
What
are
you
working
on
and
we
will
update
these
three
pros,
and
this
is
actually
our
master
repo,
so
you
can
see
what
we're
working
on
and
give
feedback
once
these
things
comes
out,
okay
and
that
actually
brings
us
to
the
end
there
sure
if
Pete
have
any
final
comments.
B
A
D
A
D
A
So
you
pretty
much
one
of
the
questions
I
was
going
to
ask.
You
was
one
of
the
new
features
that
are
coming
and
I.
Think
you
covered
that
off
in
the
last
couple
of
slides.
So
thank
you
for
that.
There
was
a
earlier
question
by
Marcus,
but
I
think
you
also
mute
him
and
around
the
dependency
on
github
they've
covered
that
off.
D
I
thought
question
about
why
we
don't
allow
the
product
to
be
mounted
from
the
product
to
be
an
honor
from
your
host,
the
laptop
workspace
into
your
open
ship
container.
They
don't
have
to
commit
to
the
git
repo
and
redeploy
every
time,
so
this
is
actually
I
can
answer
that
in
a
bit
more
detail
than
I
did
on
the
on
the
chat.
The
baker
has
two
parts.
Here's
one
is
what
you
suggest
there.
Marcus
is
perfectly
doable,
especially
in
in
in
a
darker
world,
where
the
darker
is
running
in
on
you
in
machine.
D
You
can
do
what's
called
a
monitor
volume.
The
downside
currently
is
that
we
feel
running
on
windows.
Doing
mountain
or
shared
volumes
is
actually
not
very
fast
and
there's
some
tricks
to
it,
but
you
can't
actually
do
it
as
well.
If
I
can
maybe
add
a
few
slight
comments
to
the
slides
some
blocks,
we
did
a
six
to
eight
months
ago
about
how
to
actually
do
that
from
the
tooling
today.
So
you
can
do
that
in
a
talker
scenario.
D
D
There
is
Network
stuff
that
might
not
be
easily
available
for
us
and
that's
why,
as
Fred
showed
and
I
talked
about,
we
use
this
thing
called
OC
sync,
which
will
basically
take
they'll,
use
our
sync
behind
the
scenes
to
take
an
efficient,
Delta
and
copy
over
to
to
the
container,
and
that
basically
does
the
same
trick.
But
you
don't
have
to
do
to
get
committee,
etc.
So
I
hope
that
answers
the
question
that
why
we
not
Oh
Rotter,
why
we
doing
more
than
just
mounting
the
volume.
B
Also,
maybe,
from
a
kind
of
a
higher
level
perspective,
I
think
this
sort
of
problem
that
we're
talking
about
here
is
how
do
we
get
the
files
from
the
person's
local
workspace
into
the
application
right?
That's
the
kind
of
a
fundamental
problem
we're
trying
to
solve,
and
how
do
we
do
that
quickly
and
I
think
we
recognized
that
that
is
a
real
problem
that
definitely
needs
solving.
B
That
was
a
part
of
the
original
brief
for
this
initiative
that
we've
been
working
on
here.
It's
still
something
I
think
that
we
need
to
address
better
whether
it's
done
best
by
mounting
volumes
or
by
running
you
know
a
git
server
locally.
That
people
can,
you
know,
push
and
pull
from
I.
Think
there's
multiple
ways
to
solve
that
problem
of
how
do
you
get
files
from
the
workstation
and
up
into
okra
shift?
B
I
think
you
know
both
you
know
we
and
the
open
ship
team
all
recognize
that
this
needs
to
be
much
easier
than
it
needs
to
be
sort
of
pretty
much
transparent
and
quick,
but
I,
don't
think.
We've
really
focused
or
fixed
on
a
particular
today,
I
think
there's
a
variety
of
solutions
that
we
could
could
look
at.
B
Me
again
just
come
in
briefly
on
that
to
explain
our
philosophy
and
I
talked
a
little
bit
about
this
at
the
beginning,
that
our
philosophy
is
kind
of
we
optimized
for
certain
scenarios.
We
support
certain
scenarios
as
a
company
as
RedHat
supports
certain
scenarios
right
and
then
there
are
other
scenarios
that
are
possible
so
for
UPS
kind
of
that
EAP
path
and
the
nodejs
path
that
max
and
fred
showed
that's
kind
of
our
optimal
path.
That's
the
one
we're
really
focused
on
in
on
kind
of
later
focused
on.
B
There
are
others
that
we
definitely
support,
such
as
the
Tomcat
one
that
was
just
mentioned.
Is
that
the
one
that
we
spend
most
of
our
time?
You
know,
and
we
really
push
the
QA
team
to
make
sure
they're
really
doing
a
great
deal
of
testing.
That
is
that
the
one
we
show
in
demos
is
that
the
one
we
you
know
documents
the
hell
out
selves
no,
but
it
should
still
work.
It
does
still
work
and
we
still
support
it
and
then
there's
things
that
are
possible
right.
B
So
things
that
should
work-
and
maybe
you
have
to
do
a
little
bit
of
fiddling
to
get
them
going,
but
you
know
they
should
work
in
there.
So
you
know
I,
guess
I.
Think
from
my
perspective,
it
helps
to
sort
of
always
keep
that
philosophy
in
mind,
and
that
explains
why
we
always
show
particular
paths
through
the
tools.
A
D
D
But
currently
it's
a
manual
process,
but
you
can
do
it
I
hope
we
can
get
fine
away
with
a
talk
to
the
overshift
team
that
we
can
actually
because
we're
running
in
a
local
environment.
We
can
do
a
bit
more
tricks
than
in
a
full-blown
openshift,
so
we
can
basically
do
a
what's
called
a
darker
exact
behind-the-scenes
to
open
up
these
ports.
But
this
is
just
this
is
just
kind
of
ideas,
but
in
technically
it
is
possible,
but
right
now
it's
minor
process.
D
Brian
answered
I,
mean
I,
think
even
the
one
we're
using
right
now
we're
actually
using
less
it's
like
one
and
a
half
KQ
set
up
and
two
CPUs,
but
yeah
it
did.
We
have
a
default
right
now.
We
haven't
tuned
it,
but
yeah
I'll
be
somewhere
between
one
or
two
or
three,
but
the
idea
is
you:
can
you
can
you'll
have
a
default
and
you
can
override
it
if
you
want
to
depending
on
you,
you
know
experience
what
kind
of
large
supplication
you
want
to
deploy.
D
We
don't
have
specifically
like
template,
like
advanced
tooling
plan
on
this
area,
but
will
be
what
we
have
recognize
is
we're
gonna,
add
you're
working
on
adding
a
JSON
editor
to
the
Eclipse
base,
which
allows
us
to
have
content,
assist
and
basic
validation
based
on
JSON
schema.
That
alone
will
get
become
a
bit
nicer
to
edit.
If
you
notice
the
editor
that
when
fred
was
editing,
the
conflict
I
was
actually
a
syntax
highlighter
editor.
So
that's
kind
of
the
the
precursor
of
this
Jason
an
editor.
D
But
in
fact
we
can
add
the
JSON
schema
to
it
means
stuff,
like
analysis
becomes
better
and
we
are
working
on
making
that
extendable.
So
we
can
add,
like
open
ships,
specific
logic
to
to
aid
the
user
there,
but
that's
about
it
at
the
moment,
but
yeah.
It's
something
we
discussed,
but
not
nothing
specific
beyond
what
I
just
pinched.
It.
A
D
B
B
So
we're
still,
as
you
can
see,
working
on
getting
this
right,
I
don't
have
a
sort
of
sort
of
dates
that
we
can
give
at
the
moment.
Unfortunately,
that's
a
base,
but
you
know
this
is
a
year,
so
this
has
made
of
a
number
of
different
components.
Quite
a
few
of
those
components
of
you
know,
release
recently
frequency,
so
things
like
the
jbs
support
owing
max
you,
you
can
definitely
talk
about
on
the
JPS
support
for
some
of
the
features
that
we
saw
today
would
be
going
GA.
A
D
Correct
so
yeah
the
the
GA
of
the
the
tooling
we
show
today
will
be
in
March,
that's
the
the
plan,
and
then
we
will
start
doing
more
over
the
summer
and
yeah
those
those
states
and
times
are
in
our
jbs,
your
siblings.
For
it
there
was
a
question
about.
Do
you
have
integrated
VirtualBox
into
your
solution?
What
about
Auto
visualizations
tech
like
VMware?
D
So
this
is
a
fun
one
in
the
sense
that
yeah
we
had
to
take
a
pic
of
which
one
we
want
to
put
in
there
and
right
now,
VirtualBox
was
the
one
because
it
ran
on.
It
was
the
easiest
to
get
going
with
for
us
and
having
a
distribution
and
I
think
the
cdk
itself
supports
VirtualBox
and
one
more
but
yeah
brian,
says
lippert
and
others
on
horizon
for
this
scenario
here
I
think.
D
If
there's
one
we
would
target
after
this,
it
might
be
hypervisor
for
Windows,
because
we've,
if
you
run
the
the
people
who
are
running
Windows,
that
has
hypervisor,
can
actually
not
run
VirtualBox,
but
that's
the
fun
of
that.
So
the
answer
is
right.
Now
were
you
doing
virtual
box,
but
we
will
probably
do
something
more
in
the
future,
which
ones
is
undecided.
B
B
One
of
the
enhancements
we
need
to
do
as
we
go
through
at
the
beta
phase
is
adding
the
ability
to
select
existing
components
that
you
might
already
have
on
the
system
and
also
allowing
people
to
you
know,
use
things
like
other
hypervisors,
so
the
cdk
supports
a
number
of
different
virtual
machines,
so
we
want
to
be
able
to
make
sure
that
we
can.
You
know,
allow
that
to
be
selected
during
the
install
process,
if
you,
if
you
already
have
them
installed,
I
think
that
would
be
the
key
thing
right.
B
We
ready
if
we,
if
you're,
using
our
single
download
a
single
installer,
we're
gonna
the
one
we're
going
to
be
able
to
install
for
you
would
be
VirtualBox
or
possibly
in
the
future
or
use
hyper-v
in
the
future.
If
you've
got
other
ones
already
installed,
we
we
need
to
be
able
to.
You
has
a
feature
request
for
the
Installer.
We
need
to
be
able
to
make
sure
that
you
can
select
the
one
that
you
want
to
use.
A
B
To
the
github
repository
that
we
have
linked
from
slides,
we're
pretty
active
in
the
issue
tracker
there,
so
there
are
often
long
discussions
on
the
on
the
issue
tracker.
We
have
quite
a
few
contributors
from
Red
Hat
who
jump
in
and
help
out
with
with
getting
things
done
there.
So
that's
a
great
way
to
follow
along
I
think
on
both
of
those
git
repositories
that
max
linked.
You
know,
following
the
pull
requests
following
the
issues,
that's
probably
the
best
way
to
get
involved
today.
Oh.
C
A
A
Open
ship
there
are
very
good
places
to
to
ask
questions
and
to
give
suggestions,
so
the
tracking
them
through
the
issues
is
pretty
pretty
cool
and
Lions.
Just
said
for
the
cdk
on
freenode
join
atomic
and
you're
going
to
say
it
wrong.
New
Clio,
newly
cool
new
look,
you'll
really
keel.
Are
there
so
there's
lots
of
closes
places
there
and
we
can
all.
We
can
all
help
you
get
to
the
right
funnel
to
get
the
feedback,
and
so
thank
you
very
much
to
everybody
for
coming
today.
A
I
look
forward
to
when
you
go
GA
and
have
some
more
new
features
to
showcasing
it
again
and,
and
then
you
Peter
from
for
joining
us
from
that
hotel
room
wherever
you
are
and
everybody
else
could
join
its.
It
was
very
enlightening
and
I'm
looking
forward
to
being
able
to
demo
this
myself
next
time,
all
right
take.