►
From YouTube: OpenStack SIG Intro – Chris Hoge, OpenStack Foundation, & David Lyle, Intel (Any Skill Level)
Description
Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (http://bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (http://bit.ly/kccncchina18).
OpenStack SIG Intro – Chris Hoge, OpenStack Foundation, & David Lyle, Intel (Any Skill Level)
SIG OpenStack coordinates the cross-community efforts of the OpenStack and Kubernetes communities. This includes coordinating improvements to and documentation of the OpenStack cloud provider implementation in Kubernetes as well as supporting efforts to deploy OpenStack itself using Kubernetes. Attend this session to learn more about the SIG's mission, recent accomplishments, and future plans.
About Chris
Chris Hoge is a Strategic Program Manager for the OpenStack Foundation. He's been an active contributor to the Interop Working Group (formerly DefCore), and helps run the trademark program for the OpenStack Foundation. He also works on collaborations between the OpenStack and Kubernetes communities. Previously he worked as an OpenStack community manager and developer at Puppet Labs, and operated a research cloud for the College of Arts and Sciences at The University of Oregon. When not cloud computing, he enjoys long-distance running, dancing, and throwing a ball for his Border Collie.
About David
David Lyle works on cloud technologies as a Cloud Software Architect in Intel's Open Source Technology Center. David is primarily focused on Kubernetes and OpenStack.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
B
A
A
So
the
mission
of
cig
OpenStack
is
really
to
coordinate
the
cross
community
efforts
between
OpenStack
kubernetes.
It's
really
a
love
story
right,
but
they're,
complementary
software
solutions
and
there's
many
ways
that
they
can
integrate.
So
OpenStack
can
be
run
on
top
of
kubernetes,
so
we
can
use
it
to
provide
a
scalable
control
and
data
plane.
B
You
know
you
know
traditionally,
within
the
kubernetes
community
there's
you
know,
sic
has
ownership
and
ownership
of
code
and
a
mission,
and
that's
certainly
true
of
what
we're
doing
here
but
there's
this
is
also
the
kubernetes
and
OpenStack
are
two
very
large
open-source
communities
and
on
the
OpenStack
side
of
things
we
also
have
a
cig
kubernetes,
which
is
the
exact
same
organization,
the
idea
being
that
by
but
by
having
a
special
interest
group,
that's
big!
That's
recognized
by
both
communities.
We're
able
to
take
advantage
of
the
resources
that
are
available.
B
You
know
be
able
to
engage
the
both
of
the
communities
in
a
more
direct
way
and
act.
You
know,
and
the
and
the
members
of
that
sick
act
as
a
you
know
is
kind
of
you
know,
ambassadors
between
the
two
communities,
and
so
you
know
you
might
hear
if
you
come
to
some
OpenStack
events,
you
might
hear
talking
about
you
know
in
static
state
communities,
and
you
know
these
are
the
you
know
by
design.
These
are
the
same
organizations
and
you
know
we
welcome
anybody
from
either
community
compart
to
come
and
participate.
A
B
A
B
You
know
you
know
looking
at
current
work
items
talking
about
future
work
items,
and
you
know
just
kind
of
like
a
face
to
face
working
session
for
all
of
us
to
get
together
and
and
work
through
some
of
the
issues,
and
so
I
really
encourage
everybody
to
come
to
that
session.
If
you're
interested
in
participating
or
if
you're
currently
participating
and
you
kind
of
want
to
meet
your
co-collaborators,
you
know
face
to
face.
B
The
other
thing
that's
happening
is
we're
doing
some
kubernetes
and
OpenStack
leadership
story
trading
over
over
this
week
is
kind
of
a
hallway
track.
The
first
one
is
going
to
be
directly
after
this
session.
So
again,
if
that's
something
you're
interested
in
participating
in
you
know,
please
come
and
talk
to
me
afterwards
and
you
know
that's
some
exciting
things
that
are
happening
there.
We
have
over
60
sessions
that
are
happening
at
the
OpenStack,
some
of
and
Coover
that
are
devoted
to
container
technology.
B
A
lot
of
that
is
going
to
be
focused
on
kubernetes,
and
so
you
know
that's
a
that's.
That's
a
fantastic
event.
It's
going
to
be
co-located
with
the
open,
dev
comp,
which
is
focused
on
CI
and
CD
I'll,
be
at
docker
Con
in
the
middle
of
June,
and
then
we'll
probably
have
something
going
on
and
with
open
in
four
days
in
China
we
have
a
bunch
of
contributors
who
are
you
know
who
originate
from
China
and
so
I
expected
we're
gonna
have
a
lot
of
participation
from
from
community
members
there.
A
Okay,
so
now
we're
we're
going
to
talk
to
about
the
actual
code,
part
of
this,
what
we
accomplished
in
110,
so
there
is
a
cloud
provider
in
the
kubernetes
kubernetes
repository
right
now,
during
this
cycle
we
created
a
external
repository.
You
can
see
the
link
for
it
there,
so
this
is
part
of
the
grander
effort
to
move
all
the
integrated
cloud
providers
into
their
own
repositories.
So
they
can
better
manage
the
code
and
have
it
a
little
bit
more
pluggable
and
reduce
the
size
of
the
overall
kubernetes
repo.
A
So
currently
we
have
it
the
down
the
cloud
provider,
repo
that
we
have
now
attracts
the
tracks,
the
upstream
kubernetes
provider
code.
So
any
changes
that
happen
there
we
pull
down.
In
addition
to
that,
we
can
land
new
features
into
the
new
repository,
so
things
those
don't
get
back
synced
into
kubernetes
kubernetes,
but
we
can
still
add
new
features.
And
then
then
we
have
a
deprecation
and
removal
plan
plan.
B
At
least,
and
one
of
the
exciting
things
about
so
you'll
notice
that
the
location
of
this
repository
is
still
within
the
kubernetes
organization
and
you
can
actually
go
and
find
all
of
the
other
providers
at
similar
addresses
cloud
provider
as
your
cloud
provider.
Gc
P-
and
this
is
by
design,
there's
there's
the
there's
working
group
cloud
provider
which
is
working
to
create
and
kind
of
enforce
standards
across
all
of
the
providers,
and
so
not
only
just
behavior
across
the
the
the
the
provider
plugins
themselves,
but
also
what
are
the
expectations
of
documentation?
B
What
are
the
expectations
of
testing?
You
know,
you
know
what
are
the
you
know
and
what?
What
are
ways
that
we
can
collaborate
so
that
the
cloud
providers
aren't
working
in
a
silo
and
providing
a
different
experience
for
everybody,
but
instead
are
working
together
to
so.
It
makes
it
easier
for
you
to
transition
your
workloads
from
from
one
cloud
to
another,
regardless
of
the
provider.
That's
underneath
it,
and
so
that's
another.
B
Pretty
big
focus
of
our
efforts
is
to
make
sure
that
we
remain
active
with
the
working
group
cloud
provider
as
well
as
testing
and
sick,
Doc's
and
I
think
stick
architecture.
You
know
for
the
for
the
you
know,
for
the
for
the
for
the
provider
code
itself
to
you
know,
make
sure
that
we're
providing
the
best
experience
that
we
can
for
the
entire
community.
A
Now
you
can
actually
use
ipv4
ipv6
before
couldn't
and
then
the
we
also.
There
was
also
an
issue
with
ipv6
support.
So
we
fixed
that
as
well,
and
then
there
used
to
be
an
experimental
way
to
use
Keystone
authentication
in
kubernetes.
That
was
part
of
the
main,
the
the
kubernetes
repo,
and
that
was
excised
from
the
repo
and
in
favor
of
using
the
now
preferred
stander
of
web
hooks
for
authentication
providers.
A
B
One
of
the
one
of
the
other
big
things
that
we
are
our
initial
work
was
focused
on,
so
we
moving
the
provider,
you
know
creating
an
external
repository
and
having
that
hosted
within
the
kubernetes
organization.
That
was
a
big
task
and
that's
done,
but
once
you
have
that
you
want
to
ensure
that
the
code
you're
writing
actually
works.
This
has
been
a
problem
with
the
provider
for
some
time
where
we
actually
didn't
have
dedicated
tests
running
on
top
of
an
OpenStack
cloud.
B
So
the
first
step
that
we
took
to
solving
that
problem
is
we,
the
CN,
CFC
ICD
cross
cloud
repository
that
URL
may
have
changed,
so
you
should
be,
should
be
careful
at
looking
at
it.
You
know
looking
it
up,
but
they're
they're
pretty
easy
to
find.
They
have
a
they
have
a
they
have
a
project
which
is
essentially
a
kubernetes
installer,
and
it
will.
A
So
efforts
for
the
upcoming
cycle
and
most
likely
beyond
that
as
well,
but
his
continued
worked
on
the
testing
front
again
with
open
lab
and
making
sure
that
the
that
we
can
test
the
external
provider
and,
in
addition
to
the
entry
provider,
the
doc
documentation
changes
in
conjunction
with
cig
doc,
Doc's
about
where
cloud
provider
documentation
should
live.
We
also
could
use
a
great
improvement,
not
documentation,
so
always
an
ongoing
effort.
Another
effort
that
we're
trying
to
get
off
the
ground
is
cluster
auto-scaling
support.
A
B
B
So
it's
something
that
you
know.
If
you
should,
you
should
definitely
check
it
out.
If
you
have
a
project
that
you
know
you
want
to
run
tests
on,
but
you
don't
have
the
resources
to
test
they'll
be
able
to
provide
it
for
you,
and
not
only
has
that
testing
work.
You
know
that
testing
work,
the
end-to-end
testing
work
came
out
of
you
know.
We
started
that
by
by
creating
an
an
end-to-end
test
it
with
an
upstream
kubernetes
to
test
mini
cube.
B
Once
that
test
was
in
place,
it
was
possible
for
it's
possible
for
the
OpenStack
provider,
but
all
of
the
other
providers
also
to
use
that,
as
as
an
example
of
how
to
set
that
test
up
and
the
main
differences.
Is
you
add
the
configuration
option
to
to
enable
your
provider-
and
you
know
you
have
you
know,
run
it
on
run
on
your
cloud
and
you
have
your
end-to-end
test
running,
and
so
that's
that's.
That's
pretty
exciting.
B
If
you
want
to
get
involved,
refactoring
and
improving
the
documentation
is
a
great
place
to
start.
There's
we
have
a.
We
have
a
patch
up
a
getting
started
patch
and
you
know
if
you
went
and
reviewed
that-
and
you
shared
your
own
experiences,
they
would
be
greatly
appreciated
so
that
we
can
provide
the
best
documentation
possible.
I
know
that
you've
been
working
on
some
of
the
cluster
auto-scaling
and
yeah.
B
You're
you're
interested
in
contributing
to
the
to
the
codebase.
It's
an
interesting
problem
to
solve,
especially
on
our
open
OpenStack
clouds,
where
you
have
such
a
wide
variety
of
different
clouds
and
different
capabilities
that
may
be
available
to
you
and
the
containers
white
paper,
we're
looking
at
releasing
that
and
then
at
the
Vancouver
OpenStack
summit.
We
are
also
actively
looking
for
contributions
there.
Our
next
major
content
revision
is
due
this
Thursday
and
then
we're
gonna
be
spending
the
next
few
weeks
polishing
it.
B
A
Ok
and
so
now,
we're
gonna
slip
into
a
little
bit
more
on
the
OpenStack
side
of
things
again
just
kind
of
the
coordination
between,
but
just
a
brief
update.
So
we
talked
about
OpenStack
on
kubernetes
in
the
OpenStack
project,
our
OpenStack
namespace,
there's
a
OpenStack
helm
which,
which
is
a
solution
for
this,
has
low
key
base
image.
The
lightweight
OCI
base
images
and
they've
done
a
lot
of
work
around
ironic
chart
integration.
So
a
new
way
to
do
your
cluster
deployments
using
cube
ADM
as
well
as
some
major
third-party
integrations.
A
Magnum
mango
is
a
service
that
allows
you
to
run
cluster
orchestration
engines
on
top
of
OpenStack,
so
it
not
only
supports
kubernetes
but
swarm,
but
obviously
the
focus
here
is
kubernetes,
so
they've
had
a
lot
of
improvements
as
well.
Additional
network
providers
support
upgrading
the
version
of
kubernetes
that
they
support
as
well.
Our
back
and.
B
It's
I
think
it's
I
think
so
for
those
of
you
who
saw
the
keynote
this
morning
when
CERN
was
talking
about,
they
had
their
OpenStack
cloud
and
they
were
running
kubernetes
on
top
of
it.
Magnum
is
the
way
that
they're
running
kubernetes
on
it
and
and
that
115
clusters
that
was
X
and
n
number
is
from
actually
a
couple
months
ago.
I
actually
think
that's
up
above
200
now,
there's
hg.
B
I
mean
managed
kubernetes
there,
a
number
of
public
OpenStack
clouds
that
you
can
take
advantage
of
that
with
so
that
you
can
get
up
and
running
with
the
kubernetes
cluster
right
away,
and
one
more
thing
to
mention
about
Magnum
I
just
came
from
the
if
you're
familiar
with
the
kubernetes
conformance
program,
it's
a
it's
a
trademark
program
where,
if
you
can
demonstrate
that
your
product
can
deliver
kubernetes
in
a
conformant
way,
where
conformance
as
measured
by
passing
a
set
of
specific
end-to-end
tests,
then
you
can
be.
You
have
a
certified
kubernetes.
B
You
know
trademark
that
you
can
apply
to
your
project,
and
so
one
of
the
things
we're
going
to
be
working
on
for
for
the
one
for
the
111
cycle
is
to
is
to
work
with
the
Magnum
team
to
run
the
conformance
tests
and
to
make
sure
that
we
have
continuous
conformance
testing
so
that
Magnum
will
permanently
qualify
for
that
kubernetes
certified
trademark.
So
that
you
can
be
assured
that
if
you
use
Magnum
to
install
kubernetes
you're
getting
a
conformant
version
of
it,.
A
Also,
a
Zune
Zune
is
a
is
a
more
direct
way
to
communicate
with,
can
hurich
manage
containers
inside
of
OpenStack
and
there's
some
improvements
there
I
want
to
near
and
dear
to
my
heart
is
support
for
clear
containers
that
was
before
the
announcement
of
cotta
containers.
So
a
kadhai
container
support
will
will
soon
follow,
but
also
some
PCI
pass-through
for
GPUs
and
NYX.
A
Container
networking
courier,
so
courier
is
a
project
that
allows
you
to
use
OpenStack
Neutron
based
networking
in
a
container
environment,
perhaps
across
across
kubernetes,
OpenStack
or
and
so
trying
to
simplify
it's.
Basically,
it's
just
a
bridge
between
the
networking
so
but
again
a
lot
of
a
lot
of
great
work.
Just
to
add
support
of.
B
Basically,
if
you
have
a
Neutron
network
running,
you
can
use
courier
to
create
a
network.
It's
a
it's
a
network
plug
into
your
container
runtime.
You
know
your
is
essentially
your
docker
runtime,
so
that
the
networks
you
create
a
neutron
are
transparently
available
to
whatever,
whatever
your
container
infrastructure
is
and
so
started
with.
You
know.
A
So
we're
continuing
to
want
to
grow
the
community
and
get
people
you
know
participation
from
both
the
OpenStack
side,
as
well
as
the
kubernetes
side,
as
Chris
mentioned
earlier,
we
do
have
the
deep
dive
session,
which
is
really
meant
to
be
a
collaborative
working
session.
There's
not
there's
not
going
to
be
a
formal
presentation,
but
there's
is
an
ether
pad
where
you
can
add
your
topics
that
you
want
to
discuss
and
we
can.
A
We
can
work
through
that,
but
a
lot
of
times
it's
just
building
some
building
support
and
in
consensus
around
the
directions
we
want
to
take
and
just
getting
people
involved.
You
can
also
reach
us
on
slack
and
and
the
Google
group
as
well,
and
we
do
have
bi-weekly
meetings
on
zoom',
every
other
Wednesday
so
feel
free
to
join,
and
we
would
love
to
have
your
participation.
A
B
You
know,
like
you
know,
could
have
been
joined
for
examples,
a
way
that
some
people
do
that
and
in
you
can
take
advantage
of
the
storage
that's
available
at
the
bare
metal
cluster
you
can
and
it
kind
of
behaves
transparently
and,
and
so
there
are
a
few.
There
are
a
few
caveats
with
that,
like
you
may
not
want
to
run
octavia
load
balancer
because
lock
table,
you
will
want
to
bring
up
its
own
machine,
which
means
that
you're
devoting
an
entire
bare
metal
machine
to
load,
balancing
which
you
may
or
may
not
want
to
do.
B
A
B
A
B
Are
you
thinking?
Is
this
something
like
Manila
where
it's
yeah
I,
don't
know
what
the
status
of
Manila
support
is.
I.
Think
that
the
the
people
that
you
would
want
to
talk
to
is
one
of
the
engineers
from
CERN,
because
because
they
are
because
they're
an
academic
institution,
they
rely
heavily
on.
You
know,
you
know
things
like
shared
file,
storage
file
stores
and.