►
Description
VanillaStack, an open-source Kubernetes-based cloud-stack, introduces a new approach to set-up and distribute open-source cloud-workloads, abstracting from complexities and providing the foundation for an open-source ecosystem, which is truly open and vendor-agnostic.
In this webinar, the open-source edition of VanillaStack and the underlying ideas are introduced, the idea behind the platform is explained and the future roadmap for integration and roll-out of open-source projects is laid out.
Since VanillaStack will be donated to the community, this webinar will function as an igniter and as a door-opener for all the projects being possibly interested in joining the platform.
Presenter:
Karsten Samaschke, CEO @Cloudical
A
Okay,
let's
get
started,
welcome
everyone
to
today's
cncf
webinar
vanilla
stack
as
a
pro
as
a
platform
for
a
truly
vendored
agnostic,
open
source
ecosystem,
I'm
jerry,
fallon
and
I'll
be
moderating
today's
webinar.
We
would
like
to
welcome
our
presenter
today,
karsten
schamashke,
ceo
at
claudical,
just
a
few
housekeeping
items
before
we
get
started
during
the
webinar.
You
are
not
able
to
talk
as
an
attendee.
There
is
a
q,
a
box
at
the
bottom
of
your
screen,
so
please
feel
free
to
drop
your
questions
in
there
and
we'll
get
to
as
many
as
we
can.
A
A
B
A
B
Perspective
but
more
from
a
community
perspective,
initially
I'm
going
to
give
you
a
little
insight
into
what
vanilla
steak
is
actually
all
about.
Then
I'm
going
to
showcase
you
some
aspects
of
vanilla
steak,
specifically
on
the
installer,
because
we
feel
like
that
is
very
important,
and
then
I'm
going
to
touch
on
why
it
is
important
from
our
perspective
to
the
community,
why
we
and
where
we
position,
that
for
the
community
and
how
we
are
going
to
proceed
with
that.
B
B
In
that
regard,
and
so
to
say
where
we
are
basically
confronted
with
a
lot
of
requirements
from
our
stakeholders
when
we
are
talking
about
and
thinking
about,
I.t,
greater
flexibility
in
infrastructure,
faster
deployments,
faster
reactions,
better
scalability,
247
availability,
automation,
governance
and
so
on
so
forth.
You
know
all
of
that
and
you
know
the
caveat
dot.
B
Nonetheless,
cloud
is
not
per
se
the
answer.
There
are
different
flavors
to
that,
and
let
me
touch
on
them
very
shortly.
I
don't
want
to
bore
you,
but
again
I
feel
like
that
is
pretty
important
there.
So
cloud
is
most
often
perceived
as
something
where
you
do,
some
lift
and
shifting
where
you
basically
set
themselves
infrastructures
and
deploy
things
problem
with,
is,
if
you
do
that.
B
B
B
We
just
ran
over
those,
and
we
just
finished
those
container
wars.
Kubernetes
was
the
winner
and
kubernetes
is
basically
the
container
orchestrator.
Now
it's
an
open
source
project.
You
know
about
that.
It
provides
us
with
the
opportunity
to
have
some
self-healing
services
to
have
automatic
load
management.
B
It's
implemented
with
security
by
design,
it's
100
open
source
and
there
is
a
huge
and
ever
growing
community
behind
it.
That
is
awesome,
and
it's
actually
so
awesome
that,
according
to
a
study
of
451
research
group
just
conducted
some
weeks
ago,
76
of
all
enterprises
plan
to
move
towards
kubernetes
over
the
next
three
years.
B
Problem
is
kubernetes
alone.
Is
then
again
not
the
final
answers,
because
to
that
open
source
ecosystem
based
on
kubernetes,
there
are
again
a
lot
of
challenges
imposed,
because,
basically,
we
are
confronted
with
an
environment
where
proprietary
solutions
are
pushed
with
huge
sums
of
a
huge
amount
of
money,
because
that
is
the
market
of
the
future.
B
And
even
if
you
don't
want
to
hand
over
or
hand
over
your
luck
or
your
future
towards
proprietary
solutions,
which
is
highly
welcome,
you
would
be
confronted
with
a
lot
of
integration
efforts
for
your
open
source
project.
It
is
very,
very
important
to
keep
in
mind
that
kubernetes
alone
is
not
a
solution
to
your
answers.
B
It's
just
a
building
block,
it's
a
very
fundamental
building
block,
but
it
is
just
a
building
block,
so
you
have
to
integrate
a
lot
of
things
onto
your
kubernetes
clusters,
say:
storage,
operational
tools
and
so
on
so
forth,
and
then
you
would
just
have
your
start
and
would
not
even
be
done.
Then
there
is
one
thing
which
troubles
me
personally
a
lot,
and
that
is
the
window
lock.
That
is
even
posed
on
top
of
open
source
solutions.
B
So
if
you
look
on
to
some
of
the
products
provided
by
the
biggest
open
source
windows
in
the
market,
I
don't
want
to
say
the
names
of
those
red
and
green
companies.
They
impose
a
vendor
lock
on
you
as
well,
because
you
just
can
run
their
kubernetes
solutions
on
top
of
their
linuxes,
coupled
with
their
storage
solution.
That
is
the
classical
definition
of
a
window
lock.
B
You
have
a
problem
in
regards
to
an
ecosystem,
because
there
is
no
such
thing
as
a
real
and
true
ecosystem.
It's
just
single
products
that
are
basically
waiting
for
you
to
be
integrated,
so
a
lot
of
work
for
you,
a
lot
of
efforts
for
you
requiring
a
lot
of
knowledge
and,
ultimately
making
it
quite
expensive
to
head
over
to
those
open
source
ecosystems.
B
B
We
basically
try
to
combine
both
things.
We
understand
kubernetes
as
our
operating
system.
This
is
very
important
to
keep
in
mind.
Remember
the
vendor.
Lock.
We
try
to
solve
that
by.
Basically,
not
caring
about
which
linux
you
are
running.
Your
vanilla
steak
upon
vanilla
steak
is
vanilla.
Kubernetes,
we
don't
touch
it,
we
just
roll
it
out.
Vanilla
steak
is
vanilla
cloud
foundry,
we
don't
touch
it.
We
just
wrote
it
out
in
an
opinionated
way.
Vanilla
steak
is
vanilla.
Openstack,
we
don't
touch
it.
We
just
wrote
it
out
in
an
opinionated
way.
B
Vanilla
stack
is
rook,
manila
rook,
we
don't
touch
it.
We
just
wrote
it
out
in
an
opinionated
way
and
we
understand
ourselves
as
an
organization
that
is
able
to
to
make
that
available
as
a
community
project,
and
that
project
is
a
truly
open
source
project,
because
what
we
wrote
out
with
vanilla
stick
and
I'm
going
to
showcase
you
with
another
installer.
In
a
few
seconds
what
we
wrote
out,
there
is
100
open
source
projects
and
it's
not
those
vendor
locked
or
window
locking
projects
you
might
be
seeing
from
other
platforms.
B
It
is
the
vanilla
edition
of
the
project
so
of
the
projects,
so
that
is
actually
where
the
name
came
from.
We
did
not
want
to
alter
kubernetes.
We
do
not
want
to
alter
openstack.
We
do
not
want
to
alter
anything
there,
we
just
take
it,
we
integrate
it
and
we
roll
it
out
in
a
way
that
you
would
be
able
to
run,
for
example,
your
openstack
on
top
of
kubernetes
within
an
hour,
basically,
obviously,
depending
on
the
strength
of
your
ecosystem
and
of
your
infrastructure.
B
But
that
is
basically
what
we
promise
you,
vanilla
stack
is
made
by
the
community
for
the
community,
so
we
position
that
as
something
that
supports
the
community,
I'm
going
to
touch
on
that
in
a
few
seconds
as
well,
and
we
don't
impose
any
vendor
lock,
vanilla
stack,
which
is
currently
available
in
its
very
first
iteration,
will
have
in
its
final
iteration.
Basically,
I
will
present
you
with
an
ecosystem
that
is
giving
you
the
whole
complete
picture.
So
it
is
a
complete
open
source
deck
period.
B
What
you
wrote
out
with
vanilla
stack
with
the
installer
and
with
the
store
is
open
source
we
will
later
on,
have
commercial
products
in
there
as
well,
but
we
will
always
focus
on
the
open
source
versions
of
the
products
we
will
always
make
them
available
and
if
there
is
then
later
on
some
commercial
offerings
on
top
of
that.
Well,
we
need
to
refine
the
project
any
house,
so
it
is
based
on
kubernetes.
We
support
docker
and
creole
istio,
rook
and
self
for
your
storage
purposes.
B
We
have
an
integration
with
neted
trident
currently
running
in
beta,
which
will
be
available
in
the
next
edition
valero
for
your
backup.
I
don't
want
to
touch
all
the
projects
here,
pretty
importantly
openstack
as
infrastructure
as
a
services
layer
with
the
next
iteration
being
available
in
one
month
from
now.
We
will
also
have
a
support
for
cube
word
in
there.
It
is
based
on
ansible
and
terraform.
B
We
provide
you
already
in
the
current
version
with
cloud
foundry
in
the
next
editions.
We
will
also
have
support
for
gitlab
and
jenkins.
We
always
ship
it
with
harbor
for
your
operational
approaches:
prometress
cafana,
the
f
stack
jaeger
will
be
there
and
are
actually
there.
Security
is
done
by
the
likes
of
key
club,
flaco
aquaclear
and
then
vanilla,
installer
in
vanilla,
app
store,
I'm
going
again
to
touch
them
in
a
few
seconds.
They
are
also
part
of
the
stack
and
they
are
also
open
source.
B
B
The
initial
installation
is
done
by
a
vanilla,
installer
and
you
bring
in
additional
functionality
by
the
so-called
vanilla
store,
and
we
promise
you
again
in
the
open
source
version
and
let
me
baby.
Let
me
be
very
clear
on
that.
The
community
edition
does
not
differ
any
kind
from
the
commercial
edition
there
out
of
out
of
the
box
integration
and
out
of
the
box
operability.
B
So,
whenever
you
roll
out
something
with
vanilla,
stick,
you
can
rest
assured,
it
just
works
and
it
is
again
not
any
kind
of
vendor
locked
product.
It
is
not,
I
don't
know
the
kubernetes
running
with
microsoft,
aks
or
the
amazon
version.
It
is
the
kubernetes
we
roll
out,
but
we
want
to
go
a
little
bit
further
than
that.
We
do
not
just
want
to
provide
you
with
a
platform.
We
want
to
set
up
and
start
something
like
an
ecosystem.
B
In
the
end
we
mean
it
in
that
way,
it
should
be
an
open
source
ecosystem,
so
the
ecosystem
and
the
platform
are
open
by
design
and
mindset.
We
support
vanilla
projects.
We
won't
provide
any
kind
of
window
lock,
it
can
be
expanded
with
a
huge
amount
of
open
source
and
commercial
components
and
again
we
understand
it
as
an
ecosystem.
B
So
what
we
will
provide
you
and
what
we
will
provide
the
community
with
is
a
complete,
trustworthy
environment
with
100,
open
source
components
which
is
100
supported
by
us
and
obviously
by
the
community
and
which
is
open
sourced
on
its
own.
You
might
ask
where
vanilla
stack
is
able
to
run
well.
Let
me
be
very
clear
on
that:
it
runs
everywhere.
It
runs
on
everything,
starting
from
bare
metal
environments
or
via
ym's
public
private
clouds
up
to
the
hyperscalers.
B
So
now
my
virtual
machine
should
be
visible.
I
should
have
changed
the
screen
sharing.
Accordingly,
let
me
recheck
that
again
yet
yes,
it
should
be
so
here
you
see.
Basically,
the
starting
screen
of
vanilla,
stick
vanilla,
stick:
installer
is
just
a
docker
image.
It's
available
today,
there's
also
an
iso
image
available,
so
there's
ideally
no
need
for
you
to
install
anything
on
your
local
machine,
perhaps
besides
a
docker
image
or
mounting
the
iso
image
to
your
virtual
machine
software
and
then
basically
start
it
up.
B
B
29.0020.09
and
the
first
selection
you
have
to
do
in
the
first
choice
you
have
to
make
is:
basically
do
you
want
to
have
an
h8
installation
or
not
just
make
your
choice
there?
If
it
is
an
installation,
we
will
set
up
three
masternodes.
If
it
is
a
non-ha
installation,
we
will
just
set
up
one
master
node,
and
then
you
basically
define
your
initial
workloads
keep
in
mind.
You
can
always
change
that
later
on.
You
can
always
add
things
later
on.
We
start
always
with
rook,
as
as
your
storage
solution.
B
Currently
you
cannot
deselect
rook,
that
is
by
intent,
because
we
want
your
kubernetes
installation
always
to
be
in
a
production
grade.
State
claudica,
my
company
is
amongst
the
biggest
root
root
contributors
on
this
planet.
So
we
love
that
project.
We
understand
it
and
we
are
able
to
roll
it
out.
Additionally,
you
can
decide
whether
to
install
openstack
here
as
well
as
where
to
install
cloud
foundry
if
you
like,
and
you
can
then
basically
select
the
amount
of
masternodes
you
want
to
have
a
vanilla
stack.
B
B
I
would
not
recommend
that,
so
we
keep
it
for
the
purpose
of
this
demonstration,
pretty
short
and
just
with
three
worker
notes,
and
now
is
the
only
moment
where
you
would
need
to
touch
a
terminal
during
the
installation,
because
the
installer
creates
an
ssh
key.
It
uses
a
private
key
and
asks
you
to
deploy
the
public
key
onto
your
worker
and
masternodes.
So
once
you
did
that
and
how
it
is
done
is
described
within
the
installer
as
well.
B
You
just
accept,
or
you
just
say
that
you
did
that
press
next
and
then
you
can
basically
go
and
define
your
master
and
your
worker
notes
again,
I'm
just
doing
a
presentation,
so
basically
I
can
use
any
kind
of
random
ip
address.
I
want
to
use
because
in
this
presentation
nothing
is
going
to
be
rolled
out,
so
I
just
add
some
ip
addresses.
B
B
Which
workload
will
be
available
on
which
worker
note,
if
you
have
more
than
three
workers,
it
makes
obviously
sense
to
basically
say
okay
on
which
worker
would
I
want
to
have
my
rook
deployed,
because
you
might
have
fast
ssds
there
here?
In
this
case
you
basically
say:
okay,
I
assign
rook
open
stack
and
cloud
foundry,
whatever
you
want
to
roll
out
to
all
of
the
nodes.
B
Now
the
next
step
is
basically
already
a
step
that
is
working
with
your
infrastructure,
because
now
you
need
to
do
a
node
check,
so
this
node
check
is
basically
connecting
to
your
nodes.
It
is
basically
checking
and
whether
you
have
enough
ram
a
memo
of
two
gigabytes
should
be
there.
That
way
you
have
enough
cpus.
We
would
recommend
a
minimum
of
two
vcpus
and
whether
you
have
enough
storage
or
disk
space
like
20
gigabytes,
should
do
perfectly
fine
and
for
the
root
notes,
whether
you
already
have
a
raw
device
provisioned.
B
And
this
domain
name
is
the
later
on
used
for,
basically
all
the
components
being
exposed
to
the
outside
world
automatically.
So
you
just
have
to
do
the
prefixing
thing
and
we
pre-propellate
that
with
useful
values,
manila
state,
then
again
is
always
is
already
coming
integrated
with.
Let's
encrypt,
you
can
basically
choose
whether
you
want
to
have
let's
encrypt
in
staging
or
non-production
production
mode
or
in
production
mode.
B
You
would
always
recommend
for
any
kind
of
test
clusters,
your
staging
mode,
although
it
might
lead
certificate
issues,
you
need
to
give
a
proper
email
address,
for
let's
encrypt
to
be
able
to
communicate
to
you
and
then
you
would
go
and
do
your
basic
settings
for
your
workloads.
You
want
to
roll
out
so
for
rook,
for
example,
if
you
want
to
have
the
root
dashboard
being
exposed,
well,
just
press
that
option
and
enable
that
option.
The
same
is
true
for
monitoring.
You
can
basically
find
how
many
replica
levels
would
be
there
for
rook.
B
Basically,
how
often
is
the
data
replicated
on
ceph
three
times
is
the
default.
You
can
go
down
to
two
and
you
can
go
up
to
five
according
to
your
needs
and
according
to
the
power
of
your
infrastructure,
the
higher
the
number
the
slower
it
gets.
Then
you
have
to
basically
do
your
openstack
settings.
B
We
support
three
openstack
releases
again
the
open
source
releases
there
not
any
kind
of
vendor
locked
ones,
and
then
you
would
basically
be
able
to
do
some
some
basic
settings
for
your
openstack
components,
so
we
pre-populated,
then
those
settings
again
you
could
just
leave
them
or
you
could
basically
adjust
them
to
your
name.
To
your
needs.
Same
is
true
for
cloud
foundry.
B
We
always
ship
it
with
the
stratos
dashboard,
so
you
always
would
have
some
sort
of
nice
little
web
front
end
and
then
basically
comes
the
additional
two
selection
to
be
rolled
out.
Initially,
however,
is
pretty
important
to
us
because
we
feel
like
it
makes
a
lot
of
sense
to
have
your
own
docker
registry
available.
So
hardware
is
already
pre-selected.
The
same
is
true
for
prometers
and
carfana.
B
A
A
B
Your
selection
here
you
you
are
presented
with
a
summary.
You
can
always
jump
back
to
the
different
sections
here
by
pressing
the
edit
link,
but
once
you're
satisfied
just
press
the
install
button
and
then
the
installation
might
start.
That
is
just
again
not
a
real
installation
now
going
on
here.
It's
just
a
dry
run,
so
we
can
wait
for
a
very
short
time
in
again.
In
reality,
it
takes
like
an
hour
depending
on
your
workloads,
you
roll
out
and
depending
on
your
network
connection
before
your
installation
is
done
here.
B
A
B
B
We
you
can
later
on,
install
it
via
the
app
store
once
that
one
is
available
and
we
checked
it.
It's
able
to
run
to
be
rolled
out
and
operational
within
40
minutes
at
best,
although
my
colleague
basically
claimed
he
can
do
that
in
less
than
30
minutes
with
one
elastic
and
another
or
a
different
use
case
would
be
platform
as
a
services
on
vanilla
stack
where
you
would
basically
roll
out
kubernetes,
harbor,
rook,
gitlab,
jenkins
cloud
funding.
B
Currently
just
cloud
foundry
on
the
environment,
istio
and
gitlab
and
jenkins
will
be
there
with
the
store
again
in
like
two
to
four
weeks.
It
will
be
there.
We
recommend
to
have
a
decent
setup
there.
The
same
is
true
for
ups.
You
can
basically
roll
out
prometress,
kafana,
f
or
x,
stacks
rook
and
cell
for
storage,
and
everything
will
be
rolled
out
and
directly
usable.
The
most
important
aspect
in
that
and
we
are
in
the
cncf
webinar-
is
the
community,
and
that
is
very,
very
important
to
us.
B
B
B
It
is
open
to
community
contributors
now
and
we
are
actually
and
currently
reaching
out
to
many
lux
foundation
and
cloud
native
foundation.
Projects
already
have
some
interesting
conversations
there,
because
we
invite
all
of
you
to
participate
in
that
it
is
a
completely
open
system
and
we
want
to
make
it
even
more
open.
That's
why
we
want
to
hand
it
over
to
a
newly
formed
foundation
in
q1
next
year.
It's
basically
depending
on
some
formal
starving
and
some.
B
Legal
stuff
there,
but
we
don't
want
this
thing.
We
don't
want
vanilla,
stack
to
be
just
something
for
claudical
for
my
company
and
to
be
just
the
next
vendor
locked
kind
of
thing.
We
want
it
to
be
open,
we
will
donate
it
to
the
community
and,
pretty
importantly
to
us,
it
is
available
now
and
it
is
available
today
in
two
versions:
the
community
version
and
the
commercial
version-
and
you
might
ask,
but
the
difference
between
both
of
those
versions
is
there
is
actually
just
one
singular
difference.
The
community.
B
The
community
version,
is
a
rolling
release,
pretty
much
similar
to
fedora,
for
example,
or
to
open
susa
tumbleweed,
whereas
the
commercial
version
is
a
more
stable
version.
In
regards
to
that,
we
basically
have
a
little
that
we
are
a
little
bit
slower
in
publishing
things
there
other
than
that
you
can
do
whatever
you
want
to
do
with
the
community
version.
It
is
again
open
source.
The
same
is
true
for
the
for
the
commercial
version.
B
It
just
uses
a
different
repository
and
ultimately
you
can
basically
use
the
community
version
for
any
kind
of
production-grade
workloads.
We
give.
You
is
a
there's,
a
support
option.
There
called
expert
call.
You
will
find
more
information
on
that
from
tomorrow
on
our
home
page.
That
basically
gives
you
support
for
vanilla
stack
as
well
as
every
workload
you
run
on
top
of
a
community
version
as
well
as
your
linux
installation.
A
B
B
Map
which
might
be
of
interest
to
you
as
well
manila
state
road
map
today
and
I
speak
of
today-
support
fedora
and
ubuntu,
so
you
can
basically
roll
it
out
on
those
platforms.
If
you
would
mind
wait
just
two
more
days,
you
would
be
able
to
roll
it
out
on
deviant,
centers
or
open
suse
as
well.
So
what
we
basically
want
to
achieve-
and
what
is
very
important
to
us
in
that
regard,
is
that
vanilla
stack
is
not
limiting
you
in
every.
B
B
We
will
support
rel
and
slash
in
october
this
year.
There
will
be
a
separate
announcement
and
we
will
provide
another
tool
to
the
community
in
november.
That
is
the
so-called
remote
installer,
which
prevents
you
from
even
having
to
download
an
iso
image
or
a
docker
image,
because
it's
basically
completely
web-based
and
there
will
be
a
so-called
cloud
installer,
which
basically
provisions
your
azure,
aws
or
google
cloud
environments
for
you
and
draws
it
out
there
available
from
december
as
well.
So
I
know
it
was
quite
a
run.
B
That
is
basically
the
home
page
to
the
commercial
edition
the
community
is
on
links
to
the
community
staff
are
available
from
manilastic.org
and
we
would
happily
share
and
spread
the
word
if
you
and
we
would
basically
want
to
do
that
using
the
hashtag
vanillastag
and
I'm
now
stopping
my
presentation,
because
I
need
to
take
a
short
break.
I
just
need
to
brief.
A
A
B
I
can
do
that.
Perhaps
you
want
to
understand
a
little
bit
more.
I
I'm
not
sure
into
which
direction
your
question
is
heading,
but
let
me
first
of
all
give
you
perhaps
an
understanding
of
which
openstack
version
we
support.
We
basically
support
openstack
helm,
so
we
use
the
helmed
version
of
openstack
roll
it
out
on
top
of
vanilla,
stick
on
top
of
kubernetes
and
ultimately
give
you
with
a
vanilla
stack.
B
Then
the
option
to
finally
just
have
your
infrastructure
as
a
services
environment
there
again
it's
a
community
openstack.
So
it's
with
neutron,
it's
with
mischar,
it's
with
all
the
great
openstack
projects.
Although-
and
that
is
a
small
caveat
at
this
moment
since
openstack-
provides
you
with
like
three
quadrillion
different
opportunities
and
setups.
B
We
are
opinionated
in
that
way,
so
the
openstack
installation
is
basically
openstack
helm
again,
three
different
editions
are
currently
available,
starting
with
now,
I
need
to
look
it
up
for
myself.
Thank
you
for
that.
Starting
with
give
me
a
second
train
stein
and
usually
exactly
we
would
recommend
setting
it
up
on
the
stein
release,
because
that's
the
currently
most
stable
version,
but
again
also
the
more
modern
versions
are
available
there
in
regards
to
openstack
in
regards
to
the
other
projects.
B
One
pretty
important
aspect
is:
we
cannot
go
and
provide
you
with
always
the
newest
version
when
they
come
out.
Obviously
we
need
to
basically
adjust
our
installation
scripts.
We
need
to
install,
perhaps
the
installer
on
its
own,
so
we
basically
plan
to
be
with
kubernetes
a
maximum
of
half
a
year
behind
the
major
we
usually
tend
to
do
that
in
one
or
two
months,
but
basically
maximum
half
a
year
later
and
with
openstack
it
could
be
up
to
a
year
depending
on
the
compatibility
depending
on
the
underlying
prerequisites.
B
B
It's
not
about
that,
but
we
have
the
experts
there,
so
we
can
give
you
any
answer
you
like
again.
It's
opens
the
account.
It's
the
open
source
version.
It
prov.
It
requires
a
minimum
of
three
worker
nodes.
You
should
have
plenty
of
ram.
You
should
plenty.
You
should
have
plenty
of
storage.
You
should
have
plenty
of
cpus,
but
yeah.
That's
true
for
every
kind
of
openstack
environment.
It
runs
perfectly
on
top
of
kubernetes.
That
is
what
I
can
say
in
regards
to
openstack.
B
A
A
B
B
We
are
working
on
that
and
we
will
provide
you
with
support
on
that,
but
I
cannot
give
you
an
exact
time
frame
on
that,
because
there's
a
lot
of
challenge
with
that,
but
let
me
put
it
that
way.
We
are
actively
working
on
that
and
we
expect
to
have
a
solution
there
until
the
end
of
this
year.
There's
a
lot
of
challenge
with
that.
B
B
On
that,
the
team,
the
awesome
team
is
working
on
it.
Frankly,
let
me
be
very
clear
on
that.
Vanilla
stack
is,
on
our
end,
a
community
project
as
well,
so
on
our
team.
They
are
all
working
in
their
spare
time
on
vanilla
stack,
we
have
some
full-time
employees
working
on
it,
but
the
other
part
of
the
team
and
the
the
more
enthusiastic.