►
From YouTube: Intro: OpenStack SIG - Chris Hoge, OpenStack Foundation
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Intro: OpenStack SIG - Chris Hoge, OpenStack Foundation
As part of the basic introduction, SIG-OpenStack will provide information on to how to enable the OpenStack cloud provider interface on Kubernetes clusters, as well as how to install a Kubernetes cluster on OpenStack clouds using community-developed tools like Kops and the Cluster-API OpenStack Provider. We will also discuss the SIG work in general, including how to get involved with development, testing, and documentation.
https://sched.co/NrrQ
A
Hello,
everybody
and
good
afternoon
welcome
to
the
introduction
to
sig,
openstack
and
community
session
at
cube.
Con
Shanghai
I
want
to
thank
everybody
for
joining
the
session.
So
in
this
talk,
we're
going
to
give
a
brief
overview
of
all
of
the
activities
that
sig
OpenStack
is
engaged
with
right
now
and
how
it
relates
to
the
kubernetes
community
in
general,
but
I'm,
hoping
that
after
we
finish
that
session.
A
The
cig
OpenStack
coordinates
the
cross
community
efforts
of
the
OpenStack
in
the
kubernetes
communities.
This
includes
OpenStack
related
contributions
to
communities,
and
it
can
be,
you
know,
and
you
can
look
at
OpenStack
in
a
number
of
different
ways
in
relationship
to
kubernetes.
The
first
is,
is
you
can
treat
it
like
a
deployment
platform
for
platform
for
kubernetes,
and
so
this
is.
This
would
be
a
typical
scenario
that
you
would
see,
just
as
you
would
run
kubernetes
on
top
of
AWS
or
Azure
or
Google
Cloud.
A
You
can
also
run
kubernetes
on
top
of
a
cloud,
and
actually
kubernetes
really
depends
upon
the
existence
existence
of
a
cloud.
It
doesn't
necessarily
know
about
how
you
handle
storage
or
how
you
handle
ingress
controllers
or
how
you
handle,
how
you
want
to
handle
your
networks,
and
so
it's
dependent
upon
some
sort
of
underlying
infrastructure
that
that
it
builds
upon
through
a
series
of
common
api's.
A
Openstack
can
also
be
a
service
provider
for
kubernetes,
and
this
would
be
the
instance
instance
of
if
you
want
to
have
some
sort
of
say,
authorization,
provider
or
some
sort
of
storage
provider.
Openstack
can
provide
those
things,
and
so
an
example
is
Keystone
has
a
web
hook
that
connects
to
kubernetes
our
back
and
allows
you
to
use
keystone
to
manage
it,
to
manage
your
users
and
your
projects
within
a
kubernetes
cluster.
A
Finally,
it
can
serve
as
a
collection
of
applications
to
run
on
kubernetes,
and
so,
if
you
consider
that
kubernetes
is
an
orchestration
platform
for
micro
services
and
OpenStack
is
a
collection
of
micro
services
that
are
meant
to
deliver
infrastructure,
then
you
can
actually
install
open
stack
on
top
of
kubernetes
and
have
that
be
the
management
platform
for
your
OpenStack
cloud.
Now.
This
leads
to
an
interesting
situation
where
you
might
be
running
an
infrastructure
kubernetes
cluster
with
OpenStack.
A
A
On
top
of
that,
and
so
that's
your
bare
metal
layer,
and
then
you
have
your
infrastructure
layer
where
maybe
you're
installing
you
know
where
you
have
your
OpenStack
installation
there
or
you
could
possibly
have
a
kubernetes
installation.
You
could
possibly
have
both
and
connect
those
with
projects
like
OpenStack
courier.
A
A
A
So
the
cloud
provider
OpenStack
implements
the
cloud
provider
interface
runs
the
cloud
provider,
specific
control,
loops
that
needs
for
services
and
information
from
the
cloud
provider
such
as
zone,
node,
details
and
load,
balancers,
and
so
on.
Cinder
is
the
storage
driver
and
OpenStack.
We
also
have
a
Manila
driver
for
CSI,
also,
which
allows
you
to
treat
shared
file
systems
also
as
CSI
compliant
file
system.
A
A
B
A
A
So
we
a
typical
workflow,
would
be
that
user
issues
a
cubed
control
command
and
then
the
credential
plugin
prompts
the
user
for
Keystone
credentials
and
exchanges
those
credentials
with
the
external
service.
In
this
case,
Keystone
for
token,
the
credential
plugin
returns
a
token
to
client
go
which
then
use
it
as
uses
it
as
a
bearer
token
against
the
API
server.
A
Then
the
API
server
uses
the
webhook
token
authentication
to
submit
the
token
to
the
Keystone
service
provider
and
the
Keystone
service
verifies
the
token
and
returns
the
users,
user,
user
name
and
groups,
and
so
you
can
to
break
this
down
into
a
diagram
where
you
see
that
Keystone
is
sitting
in
the
middle
of
this,
and
you
can
follow
the
entire
flow
cubic.
Encoder
trusts
the
token
and
receives
a
token
back,
and
these
are
these
are
sent
along
with
the
users
credentials.
A
Cubic
control
then
sends
the
token
to
the
cube
API
server.
That
goes
to
the
kubernetes
Keystone
auth,
which
sends
the
token
back
to
Keystone.
So
it's
making
the
round-trip
to
Keystone
and
Keystone
is
saying
yes,
this
is
a
token
that
I
created
and
you
are,
they
are
authorized
for,
for
whatever
this
operation
is
and
responds
with
the
appropriate
user
names
and
groups
that
are
associated
with
it,
then
that
sent
back
to
the
QB
API
server
and
it
either
performs
or
denies
the
operation
based
upon
the
responsible
key
from
from
from
Keystone.
A
We
also
have
the
Barbican
KMS
plugin.
It's
an
API.
The
API
server
requests
the
KS
plug-in
to
encrypt
that
in
recruit
the
secret
data.
It
encrypts
the
data
with
the
key
from
the
Barbican
service
running
in
an
openstack
cloud
and
then
using
envelope
encryption.
The
kubernetes
api
server
request
server
request
to
the
encrypt
decrypt
to
encrypt
decrypt,
the
data
encryption
key,
so
you're,
basically
storing
the
circuit,
the
the
secrets
that
are
allowing
kubernetes
to
encrypt
the
data
that
is
being
stored
in
the
cluster,
and
this
is
stored
in
the
secure
key
service
called
Barbican.
A
Okay,
so
that
was
basically
that
was
a
run-through
of
all
of
the
projects
that
were
managing
that
provide
these.
These
kind
of
low-level,
kubernetes
and
OpenStack
integrations,
but
a
new
project
that
many
of
you
may
have
heard
of
that
is
coming
out
of
the
cluster.
The
cig
cluster
life
cycle
group
is
the
cluster
API
provider
OpenStack,
and
this
is
a
new
project
that
we
have
started
with
in
the
last
year.
A
So
the
cluster
area
is
a
Kerber
Nettie's
project
to
bring
declarative,
kubernetes
style
api's
for
cluster
creation,
configuration
and
management.
It
also
provides
an
optional
additive
functionality.
On
top
of
core
Cooper
Nettie's,
it's
important
to
note
that
the
cluster
API
is
still
in
the
prototype
stages,
although
they
just
started
sending
up
their
alphas
and
I.
Think
they're
out
there
if
they
haven't
published
their
stable,
API
they're
right
on
the
verge
of
stead
of
publishing
their
stable
API,
but
it
should
still
be
considered
a
bit
experimental.
A
You
know,
and
it's
within
its
abilities
and
we're
trying
to
drive
more
technical
feedback
for
the
API,
designed
to
make
sure
that
when
the
API
settles
down,
the
API
is
done
right.
The
first
time
nevertheless
open
the
sig
OpenStack
has
actually
been
collaborating
on
the
creation
of
two
different
cluster
API
providers.
A
A
And
when
the,
when
a
request
is
made
to
that
small
bootstrapping
kubernetes
cluster,
it's
going
to
reach
out
into
your
cloud,
in
this
case
your
OpenStack
cloud,
and
it's
going
to
use
the
custom
resource
types
to
build
out.
It's
going
to
create
the
machines
that
I
wants
to
deploy
kubernetes
on
and
then
it's
going
to
build
out
the
cluster
definitions
and
put
these
in
place
these
into
kubernetes.
A
If
your
workload
is
increasing
your
going
to
be
able
to
have
algorithms
that
are
not
just
applicable
to
the
OpenStack
cloud,
but
to
any
other
cloud
that
will
allow
you
to
scale
your
note
out,
and
so,
as
you
are
looking
at
the
kubernetes
landscape
and
things
that
are
very
important,
that
are
coming
up.
Cluster
api
and
all
of
its
implementations
are
going
to
be
very
important,
because
what
you're
going
to
see
is
an
implementation
of
general
cluster
management,
algorithms
that
don't
that
don't
necessarily
know
anything
about
your
underlying
cloud.
A
Instead,
you're
going
to
have
a
provider
like
the
like
the
cluster
API
OpenStack
provider
that
will
handle
that
will
handle
all
of
the
heavy
lifting
of
creating
your
nodes
and
installing
the
necessary
components
on
top
of
them,
while
well
the
logic
of
what
what
state
is
a
note
in?
Do
we
need
to
grow?
Do
we
need
to
shrink?
It
is
the
is,
is
the
you
knows
is:
is
the
cluster
healthy
will
be
handled
by
cluster
API.
A
So
right
now
this
is
the
case
for
all
of
the
providers.
Is
this
more
of
a
concrete
implement
implementation
than
a
true
pluggable
provider,
and
so
cluster
API?
You
know
kind
of
specifies
an
API
that
you
have
to
an
API
that
you
have
to
code
to.
But
it's
not
it's
not
a
it's,
not
a
pluggable
interface.
A
Again,
it's
still
in
the
prototype
stages.
While
we
get
feedback
on
the
API
types
themselves,
but
it
is
settling
down
and
it's
something
that
you
know
we're
still
looking
for
more
developers
and
more
robust
implementations,
and
so
this
is
something
that
you're
interested
in
contributing
to
there's
a
tremendous
amount
of
effort
behind
it
and
if
you're
using
other
installers
like
cops,
you
should
be.
A
A
A
It's
called
metal
cubed,
which
is
the
bearer,
which
is
a
bare
metal,
cluster,
API
provider
and
so
metal
cubed
exists
to
provide
components
that
allow
you
to
do
bare
metal
host
management
for
kubernetes
metal,
cube
works
as
a
coronating,
app
application,
meaning
it
runs
on
kubernetes
and
is
managed
through
kubernetes
interfaces
and
is
going
to
provide
a
cluster
API
implementation
for
bare
metal.
Now.
How
does
this
relate
to
OpenStack?
A
Well
right
now,
it's
it's!
It's
using
its
using
OpenStack
ironic,
the
logo
of
it
right.
There
is
pixie
boots
who
sees
the
piece
of
bare
metal
drummer
bear,
and
it
ironic
is
the
OpenStack
project
that
allows
you
to
manage
bare
metal,
and
so
it
supports
a
number
of
different
open
and
proprietary
Hardware
types
and
it
you
know,
and
it
it
allows
you
to
manage
the
complete
lifecycle
of
a
bare
metal
system.
So
not
just
how
do
you
provision
the
image
on
it?
A
But
how
do
you
put
machines
into
a
managed
state
if
there's
some
sort
of
hardware
failure
or
how
do
you
deep
revision,
a
machine
when
it's
reached
the
end
of
its
lifecycle?
And
it
gives
you
a
way
to
treat
bare
metal
as
if
it
were
a?
You
know
similar.
Similarly,
to
the
same
way
that
you
would
that
you
would
treat
virtualization.
A
This
even
includes
things
like
connecting
to
the
glance
image
service
so
that
you
are
able
to
upload
images
to
glance
an
ironic
does
all
of
the
work
of
signing
those
images
to
make
sure
that
that
that
they're,
ok
to
load
onto
your
system
and
and
to
provide
a
location
where
those
can
be
downloaded
from
for
your
pixie
server.
So
it's
you
know
it's
a
it's!
A
You
know
pretty
exciting
move
forward
if
you're
interested
in
seeing
more
about
this
ooh
at
the
open
infrastructure
summit
that
we
had
in
Denver
one
of
the
keynotes.
We
had
a
demonstration
of
some
early
stages
of
metal
cube
where
we
were
provisioning,
some
bare
metal
hardware
with
ironic
and
a
custom
resource
definition,
and
we
also
have
a
demonstration
of
this
at
the
from
the
kubernetes
community
meeting
that
was
held
directly
before
Kubik
on
barcelona.
So
that
was
a.
B
A
Okay
and
the
way
it
works
is
that
you
have
you
have
a
beam
you
have
it.
You
have
a
machine
controller
with
a
bare
metal
actuator
built,
that's
built
on
top
of
on
top
of
a
bare
metal
model,
a
bare
metal
operator
which
is
which,
with
CR
DS,
that
represent
the
bare
metal
inventory,
with
the
configuration
needed
by
its
bare
metal
management
workers.
B
A
A
A
A
Christopher
is
the
main
point
of
contact
contact
for
the
OpenStack
cluster
API
provider,
and
a
DD
has
been
one
of
the
primary
developers
on
the
cloud
provider
OpenStack,
and
so
with
that
we
we
have
a
lot
of
time
left
over
and
I
like
to
use
these
sessions.
To
also
talk
about,
you
know
to
answer
any
questions
that
you
might
have,
but
to
also
you
know,
understand
your
usage
and
how
you
know
your
needs
for
the
for
the
cloud
provider.
So
I'm
happy
to
take
questions
now.
A
You
you
no
questions.
Okay,
so
so
I
have
questions
for
all
of
you,
then
so
how
many
of
you
are
running
production,
OpenStack
clouds
right
now,
just
just
for
a
sense
of
so
and
are
you
running
kubernetes
on
top
of
those
clouds
right
now,
some
of
you
so
and
are
you?
What
are
you
using
Magnum
or
you're,
using
some
other
sort
of
system
on
that
to
install
and
maintain
it?
A
C
C
D
B
A
It's
also
very
complex
and
if
you're
interested
in
running
kubernetes
on
OpenStack,
it
may
not
be
the
place
to
start.
If
you
want
to
understand
the
integrations
now
it
is
nice.
So
if
you're
familiar
with
CERN,
which
is
the
the
the
the
the
European
nuclear
research
institution,
were
they
were,
they
discovered
the
Higgs
boson
they're
running
a
large
OpenStack
cluster
and
at
last
count
they
have
over
400
kubernetes
clusters
running
on
top
of
their
OpenStack
cluster
and
they're,
using
Magnum.
To
enable
this,
and
so
Magnum
is
being
used
in
production.
A
Think
that
cops
is
a
good
place
to
start,
because
it
assumes
that
you
have
access
to
an
open
stack
attendant
and
so
rather
being,
rather
than
being
a
service,
a
managed
service
that
installs
kubernetes
for
you.
Instead,
it's
it's
almost
like
a
deployment
tool
that
that
goes
out
and
uses
I
think
uses
terraform
to
go
out
or
to
go
out
and
reach
into
your
cloud
and
manage
the
nodes.
So
you
know
one:
is
you
as
a
user?
D
Chris
we
we
haven't
used
cluster
API
OpenStack
in
catalyst
cloud
because
it's
a
it's
nice,
a
sorry
to
have
a
but
bootstrap
kubernetes
cluster,
but
it's
very
it's
impossible
for
the
card
open
step
for
the
cloud
provider
who
have
deployed
OpenStack.
So
what
do
you
think
of
this?
Because
we
have
deployed
magnum
because
we
have
already
deployed
other
services
like
Nova's
in
their
Neutron
yeah.
A
Yes,
so
so
I
also
think
that's
a
very
good
question.
I
would
I
would
say
that
the
the
cluster
api
provider
OpenStack
is
beta.
Alpha
software,
it's
it's
very
new
Christoph
is
using
it
in
his
his
you
know,
he's
developing
it
for
their
cloud
and
for
the
that
they're
doing,
but
I
wouldn't
be
using
it
in
production
right
now
and
Magnum
is
based
on.
A
You
know
having
a
full
OpenStack
cloud
there
and
there
are
a
number
of
different
tools
that
are
you
know,
built
in
to
take
advantage
of
that,
like
we
have
cluster,
auto
scaling
and
cluster
healing
that
rely
upon
the
existence
of
heat
and
Magnum
to
you
know
to
to
manage
that
so
right
now,
if
you
want
like
the
most
robust
way
to
deploy
kubernetes
and
manage
it
on
top
of
OpenStack,
clouds
is
Magnum
but
I
think
in
within
the
next
two
to
three
years,
which
is
actually
a
very
short
time.
Insight
inside
of
tech.
A
We're
going
to
be
wanting
to
look
at
you
know
as
cluster
API
matures
do
we
I
think
the
appropriate
approach,
and,
of
course,
this
comes
down
to
the
Magnum
team
is,
if
they
want
to
take
advantage
of.
That
would
be
to
keep
the
API
within
Magnum
but
use
cluster
API
is
the
implementation
of
how
they
achieve
that,
and
maybe
in
conjunction
with
heat,
but
that's
a
longer.
That's
a
much
longer
question
for
the
development.
D
C
A
I
mean
to
me
the
the
primary
advantage:
is
there
it
it
comes
down
to
openness
like
Corinne.
Adiz
is
very
attractive
because
it's
an
open
source
platform,
it's
an
open
source
application
platform
and
you
know
the
code
and
you
can
contribute
at
the
code
and
you
can
change
the
code.
Openstack
is
the
primary
open
source
cloud
platform,
that's
out
there,
and
so,
if
you
want
a
free
and
open
cloud
that
you
can
contribute
to
that,
you
can
make
changes
to
that.
You
know
that
you
can
deploy
within
your
data
center
or
you
can
have
managed.
A
Then
there
OpenStack
is
really
the
open,
only
open
source
solution
that
you
have
yeah
and
it's
and
it's
been
proven
in
in
industry.
You
know
throughout
throughout
the
world
to
and
so
and
if
you
don't
want
to
manage
it
on
your
own,
because
it
can
be
daunting
to
do
that.
There
are
any
number
of
vendors
out
there
within
the
OpenStack
ecosystem.
We're
happy
to
help
you
with
that.