►
Description
Speakers: Ilya Buziuk
If you are a developer interested in cloud native application development, you are probably having trouble following the fast changing world of the development tools in this space. You might have questions like:
What are the benefits of such tools for cloud development?
What is new with Eclipse Che?
What does its roadmap look like?
How does it integrate with OpenShift and Kubernetes?
The goal of this talk is to provide an insightful view into cloud development tools. Eclipse Che will be used to show short live demos of what the Cloud Development entails today. We will discuss how this project and its roadmap may affect your cloud development decisions.
[ https://sched.co/YOxx ]
--
Recordings of talks at DevConf are a community effort. Unfortunately not everything works perfectly every time. If you're interested in helping us improve, let us know.
A
Hello:
everybody
thanks
for
coming.
My
name
is
Ilya
I
work
for
Red,
Hat,
I'm,
also
part
of
the
Klipsch
foundation,
I'm
Eclipse
J,
and
a
clip
JavaScript
development
to
commuter
I,
enjoy
conferences
and
really
happy
to
open
2020.
My
2020
speaking
season
here
was
you
in
Brno
and
today
we
are
going
to
talk
about
eclipses,
share
and
open
source
project
on
the
eclipse
public
license.
It
is
web
ID
that
is
designed
to
make
contain
a
native
development
super-easy
and
before
we
start,
I
actually
have
a
question
for
you.
A
A
So,
according
to
the
Evans
Data
Corporation
report,
24%
of
teams,
time
is
spent
exactly
on
configuration
and
setup,
not
on
coding,
not
on
meetings
on
configuration
and
setup,
and
it's
big
figure.
If
you
think
about
it,
is
more
than
one
day
of
work
right
so,
and
it
was
not
always
like
that
because
if
you,
if
you
think
about
it,
what
was
development
looked
like
10-15
years
ago?
It
was
completely
different
story.
A
For
example,
10-15
years
ago
it
was
Java
apps,
for
example,
and
it
was
Java
from
front
to
back
from
top
to
bottom,
you
had
one
version
of
GBM
one
version
of
the
application
server,
and
that
was
pretty
much
good,
but
now
this
story
is
different,
so
here
you
can
see
on
the
next
slide,
the
cloud
native
landscape
and,
if
you,
if
you're
a
cloud
native
developer
and
if
you
work
with
micro
services,
this
is
their
tools
and
technologies.
You
have
to
work
on
on
a
daily
basis
and
complexity
of
the
application
has
changed
dramatically.
A
Also,
if
you
think
about
it,
our
laptops
are
not
ideally
suited
for
this
landscape,
because
in
order
to
develop
cloud
native
tools,
you
need
sufficient
amount
of
CPU
sufficient
out
of
RAM
on
your
laptop,
and
it's
not
the
case
currently
so
to
develop
in
this
environment
to
be
comfortable
with.
You
need
laptops,
we
at
very
least
24
32
gigs
of
ram
so,
and
this
becomes
the
first
problem.
The
second
thing
is
the
onboarding
process.
If
you
read
these
books,
this
is
brilliant
book
about
80,
it's
a
page-turner.
Actually,
so
it's
called
the
Phoenix
project.
A
It's
described
the
project
which
has
which
has
a
lot
of
issues.
One
of
the
issues
is
the
onboarding,
so
it's
quote
from
the
book
for
Phoenix.
It
takes
us
three
or
four
weeks
for
new
developers
to
get
built
running
on
their
machines,
and
that's
it
actually,
not
exaggeration.
It's
pretty
much.
The
situation
with
relatively
big
companies
face
nowadays,
so
the
setup
and
configuration
is
a
big
process
nowadays
and
onboarding
can
takes
weeks.
A
So
this
kind
of
solution
for
this
in
the
book
was
using
the
virtual
machines
and
the
book
was
written
in
late
2013,
and
we
know
that
the
first
version
of
docker
and
first
version
kubernetes
we're
roughly
at
the
same
time
where
release
roughly
at
the
same
time.
So
if
the
book
was
written
a
little
bit
later,
it
would
definitely
talk
about
the
containers
and
the
orchestration
instead
of
virtual
machines
and
those
two
problems.
Configuration
and
setup
plus,
the
onboarding
is
other
problems
that
we
want
to
solve
with
eclipse
channel.
A
So,
as
I
said,
Eclipse
share
is
the
web
ID,
but
more
important.
Its
kubernetes
native
ID
for
developers
and
teams
and
the
motor
of
the
project
is
that
anyone
anytime
can
contribute
to
a
project
without
actually
installing
software
and
now
I
want
to
show
you
how
it
looks
like
how
it
feels
like
to
develop
in
a
way.
So,
let's
imagine
it's
your
first
day
at
work
and
you
are
in
a
new
company
and
you
are
signed
to
a
new
project.
A
So
let's
go
to
the
github
page
of
this
project
and
we
see
that
it
is
quark
career,
just
posted
application
and
the
application
is
actually
deployed
on
OpenShift.
So
one
openshift
fool:
there
is
a
very
nice
topology
view,
so
we
see
it
consists
of
three
micro
services.
So
it's
not
front-end
quark
is
back
end
and
MongoDB
for
persistent
data.
The
application
is
pretty
trivial,
but
still
it
consists
of
three
micro
services
and
here
how
it
looks
like
so
we
have
an
input
field,
we
can
input
the
title
and
the
content.
A
Present
submit
button
and
we
have
a
post
persisted
and
the
database
and
reflected
on
the
UI.
Even
though
it's
pretty
simple
application,
development
development
setup
might
be
pretty
complex
because
you
know
you
need
to
install
you
need
to
install
build
tools.
You
need
to
run
the
node,
rounded
workers
get
it
together
so
that
it
will
run
smoothly,
so
you
could
easily
spend.
Even
though
you
are
a
skilled
developer,
you
could
easily
spend
one
day
of
work
just
for
environment
setup
and
you
are
assigned
to
a
new
issue.
A
So,
let's
open
it,
it's
in
the
github
so
displays
the
title
of
each
post
in
the
upper
case,
pretty
simple
one.
So
what
you
would
normally
do
in
the
regular
environment,
you
would,
you
know,
install
all
the
tools,
try
to
setup
connections
between
micro
services
and
fix
it,
and
now
I
will
show
you
how
we
promote
what
the
flow
flow
we
promote
with
Eclipse
share.
So
at
the
bottom
of
the
issue,
you
can
see
that
there
is
a
developer
workspace
button
and
if
I
click
on
it
I
will
be
switched
to
the
login
page.
A
So
I
will
be
provided
with
the
credentials
for
my
account
and
once
I
log
in
a
new
environment
will
be
created
for
me
with
not
only
the
source
code,
which
is
an
important
part,
but
you
importantly,
it
would
contain
all
the
tools
and
all
the
runtimes
for
starting
development
of
the
application
on
the
fly.
So,
let's
try
to
open
some
files.
A
We
can
open
posts,
both
Java
file,
post
resources,
to
understand
what
what
it
looks
like.
So
we
have
a
co-worker's
controller.
Here
we
have
a
MongoDB
running,
so
I
can
log
in
to
take
a
look
at
the.
What
databases
are
there
and
I
can
start
my
co-workers
back-end
right
right
from
clicking
on
one
button,
which
defines
the
command
for
running
the
app
oops
and
their
route
exposed
for
the
quark
is
back-end
and
I,
so
I
can
see
it
on
preview
and
I
can
also
access
it
through
the
regular
browser
since
its
route
is
exposed.
A
So
Quercus
is
running
it's
just
as
simple
patience.
Quadra
sees
back-end
part,
but
it's
just
a
sample
index.html.
That
shows
you
the
state
of
the
application.
So
it's
just
for
development
purposes.
Now,
let's
run
the
front-end
part,
also
one
click
and
I
have
all
the
commands
running
for
start
in
the
note
and
on
port
3000
I
have
a
note
run
it
now.
So
let's
write
so
it's
my
development
environment
to
clicks,
to
build
commands.
I,
have
everything
set
up,
live
demo
and
content.
A
A
Let
me
put
some
breakpoints
in
the
code,
so
the
in
the
issue.
We
need
to
change
the
title
right,
so
I
will
put
the
breakpoint
in
the
get
title
method
and
I
will
run
the
debugging.
So
I'll
start
the
debug
session
right
away,
and
let
me
refresh
the
page,
okay
and
I'm
in
the
debug
view
now
so
I
can
see
all
the
local
variables
of
the
of
the
post
I
can
see
information
about
the
title.
A
I
can
skip
it
right
now,
so
debugging
also
works
fine
and
I
think
that
I
figure
out
what
the
trick
is
and
I
need
just
to
get
title
to
the
upper
case.
So
you
see
I
have
a
pretty
nice
content
assist
here
to
upper
case.
I
forgot
to
put
the
brackets,
so
I
immediately
get
the
error.
Marker
I'll,
put
it
here
and
I
also
have
the
nice
docs
in
order
to
get
information
about
what
the
upper
case
is
for
the
string
method
and
since
it
is
Quercus
is
sub-atomic.
A
A
A
I
can
send
a
pull
request
right
away
so
and
imagine
everything
was
done
inside
the
browser,
so
I
did
all
the
interactions
with
the
applications,
starting
from
the
onboarding.
We
are
the
single
click
to
commit
in
from
my
browser,
and,
more
importantly,
so
the
point
is
that
if
you
want
to
develop
micro-services
and
if
you
develop
in
the
cold
native
landscape,
you
should
be
able
not
only
run
your
apps
on
the
kubernetes
or
open
ships,
you
should
run
all
the
tools
and
all
the
environment
also
on
kubernetes
or
OpenShift.
A
A
A
A
And
on
the
topology
you
can
see
is
that
the
new
micro
service
is
about
to
start.
So
that's
what
I
wanted
to
show
you
during
this
demo
during
this
live
session,
that
first
of
all
first
day
at
work,
could
be
different
thingy
in
the
cloud
native
environment
and
we
move
all
the
complexity
and
all
the
tools
to
the
cloud.
So
we
do
not
develop
on
localhost
anymore.
A
So
I
will
just
quickly
touch
the
Qi
architecture,
because
the
important
thing
here
before
we
go
into
this
detailed
diagram
is
that
we
can
imagine
that
eclipse
a
consists
of
two
parts,
its
controller
plot,
so
the
main
part
which
is
called
kubernetes
api,
which
spin-ups
the
workspaces
which
are
literally
a
ports.
That
can
data
consists
of
a
couple
of
containers
for
tooling
for
runtime,
for
for
testing,
etc.
A
So
the
most
important
thing
that
everything
is
running
inside
containers
and
ports,
then
going
to
this
diagram,
we
can
see
that
there
is
a
country
can
take
on
the
bottom.
We
can
see
a
containing
our
castrator
and
the
scene
is
that
eclipse
chase
cloud
native
ID
that
is
run
on
top
of
kubernetes
or
openshift,
which
is
downstream
projector
of
kubernetes
on
on
the
top.
We
can
see
browser
and
it's
not
surprised
because
all
the
interactions
happens
from
the
browser,
and
you
see
how
fast
it
was.
A
So
you
even
might
not
recognize
that
I
developed
inside
the
browser
not
inside
my
I,
don't
know
GWT
or
swing
IDE
right.
Then
there
is
a
chess
server
pad
and
it's
actually
the
controller
of
you
know
everything
inside
share,
so
it
in
charge
of
artificial
work.
Space
shuttle
and
scalability
house
check
monitoring.
A
We
use
key
clock
for
Identity
Management
post-grad
database
for
per
system
the
data,
but
your
server
is
actually
the
control
part
that
creates
workspaces
and
workspaces
is
basically,
as
I
said,
port,
which
consists
of
containers
for
IDE
for
runtimes
for
development,
for
tools
in
j7.
We
define
in
a
new
kind
of
work
space,
so
we
contain
arising
the
idea
with
zero
install
and
automated
configuration,
so
that
onboarding
could
happen
just
with
one
click
and
you
might
recognize
similar.
A
You
acts
to
the
vs
code
and
the
thing
is
that
Eclipse
J
uses
by
default,
chit,
dia,
ID
and
T
ID,
is
basically
promoted
as
a
BS
code
in
browser
it
uses
the
very
same
editor
which
use
via
Scott.
It's
called
Minako
editor.
That's
why
Luke
and
Phil
is
very
similar
to
vs
code.
We
have
support
of
language
server
protocols
and
debug
adapter
protocols,
so
I
saw
I
showed
it
in
the
demo
and
the
one
of
the
most
important
things
here
that
Eclipse
is
compatible
with
vs
code
extensions.
A
A
This
code,
I,
will
only
touch
the
basis
on
that.
So
basically
it's
a
llamo
definition
of
your
development
environment.
So
for
my
application,
it
was
something
like
that.
So
I
can
show
you
the
raw
version
of
it.
So
in
this
Yama
file,
you
explicitly
specify
everything
you
need
for
your
project,
so
starting
from
the
containers
go
into
the
tools,
build
commands,
databases
etc.
So,
here
in
the
declarative
way,
you
define
project
ID,
built
environment,
runtime,
environment,
test,
environment
commands
it's
the.
A
The
idea
is
similar
to
what,
for
example,
build
tools
like
Jenkins,
promote
that
they
have
their
file
and
Jenkins
understand
it.
So
here
we
have
def
file
that
Eclipse
to
understand
and
creates
the
environment
for
you
with
all
you
need
for
development,
so
again
encourage
you
to
visit
the
session.
Folks
will
tell
a
lot
more
about
that
quickly.
A
Talk
about
the
roadmap,
our
roadmap
for
the
next
six
twelve
months
is
played
in
into
four
major
sections.
You
can
find
it
on
the
eclipse
github
in
the
wiki
page,
but
basically
it's
just
the
following
easy
to
use.
We
want
to
make
it
easy
to
use.
We
want
to
improve
developer
experience,
improve
performance
and
the
last
button
of
this
part
is
hybrid
clouds.
A
What
we
want
to
allow
not
only
run
in
the
containers
but
also
built
in
the
containers-
and
there
are
already
proof
of
concept
with
pod
man
4
for
that,
and
if
you
want
to
try
it,
you
should
go
to
eclipse
org
dot
share
website.
Here
you
can
find
all
the
getting
started
guides
downloads,
documentation,
reference
to
Almaty,
Mouse
channel,
so
feel
free
to
join
and
the
last,
but
not
least,
is
that
we
also
have
hosted
version
of
Eclipse
chair.
A
It's
called
shadow
drop,
achieved,
OTO
or
Eclipse
share,
hosted
by
Red
Hat
and
the
easiest
way
to
try.
It
is
basically
you
go
to
eclipse
orgia.
Then
you
have
this
SAS
workspace
template,
and
here
we
have
a
set
of
dev
files
ready
to
go
to
start.
You
know
coding
instantly
on
hosted
version
of
chess,
so
we
here
we
have
sprint,
vertex,
go
Java,
Gradle,
Java,
maven,
node,
etc.
So
you
just
go
there.
You
click
a
button.
For
example,
go
lunch,
workspace
and
you'll
be
redirected
to
the
Red
Hat
login
page.
A
A
A
A
That
is
called
Eclipse
plugin
registry,
but
literally
it's
go
node.js
Java,
Python
PHP.
There
is
a
contributions
brought
from
for
Kabul
I
think
there
is
unfortunately
no
proper
document
that
shows
it.
But
if
you
go
to
plug-in
registry
you
could
fight
all
the
things
that
we
currently
support,
because
it's
keep
growing
every
day.
Currently
I
think
there
are
around
60
language
services.
Not
all
of
them
are
contributed
to
chair,
but
you
know
it's
it's
everyday,
it's
enhancing,
so
the
basic
one
are
spotted
next
question.
A
So
the
question
is:
what
amount
of
work
is
required
to
support
a
brand
new
language
when
there
is
already
a
language
server?
I
think
it
should
be
relatively
easy.
So
if
it
is
supported
inside
the
BS
code,
it
should
be
quite
easy
to
backport
it
to
eclipse
chair.
It
should
be
actually
just
a
matter
of
embedding
the
via
scott
extension
that
provides
a
support.
For
example,
we
got
a
support
for
coworkers
and
it
was
just
you
know,
contribution
of
the
embedding
of
the
via
scott
extension.
A
So
there
might
be
some
api
incompatibilities
between
vs
code
satya
and
here,
but
in
general
it
shouldn't
be
a
very
difficult
as
soon
as
there
is
a
vs
code
extension,
the
porting
new
language
to
chair
shouldn't
be
a
difficult
task.
Next
question
so
looks
like
no
questions.
We
are
just
on
time.
Thank
you
very
much
for
coming.