►
From YouTube: Centaurus Monthly TSC Meeting 04/07/2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Yeah,
so
we're
gonna
get
started
hi
everybody
good
morning,
so
this
is
our
monthly
eps
meeting.
It
was
supposed
to
be
a
week
ago
and
then
we
pushed
it
due
to
some
conflicts.
So
one
of
the
the
the
only
agenda
item
in
this
meeting
is
the
centaurus
dashboard
presentation
and
demo.
Actually
so,
just
to
kind
of
give
you
folks
a
background.
Click
to
cloud
team
is
gonna.
A
Do
the
presentation
and
the
demo-
and
this
is
the
project
we
did
with
our
community
member
click
to
cloud
and
future
way.
Collaboration.
So
essentially,
if
you
folks
are
familiar
with
kubernetes,
kubernetes
upstream
has
a
dashboard.
A
So
what
we
did
was,
as
you
know,
centaurus
we
kind
of
re-architected
a
lot
of
functionality
of
kubernetes
code
base.
So
we
essentially
what
we
did
was
in
this
project.
A
We
enhanced
the
and
kind
of
re-architected
the
dashboard
functionality
so
that
you
can
do
all
the
centaurus
specific
things
using
the
dashboard
as
opposed
to
kind
of
doing
command
line,
a
command
line.
You
know
cube
cuddle
and
all
that,
so
things
such
as
you
know,
in
order
for
us
to
kind
of
enable
the
scalability
we
had
to
do
partitioning
at
every
level,
so
we
have
tenant
partitioning,
we
have
resource
partitioning,
and
then
we
have
this
multi-tenancy.
A
So
in
order
for
us
to
enable
multi-tenancy,
we
have
this
user
management
capability,
which
we
added
as
part
of
centaurus,
and
then
we
have
a
new
workload
types.
You
know
it's
not
just
the
containers,
but
you
can
orchestrate
vms
as
well.
So
essentially
all
of
these
things
have
been
incorporated
as
part
of
centaurus
dashboard.
Actually,
so
that's
pretty
much
high
level.
I
know
roshan
is
going
to
talk
about
a
bit
more
as
well
so
I'll.
Let
you
take
over
russian
or
whoever
wants
to
take
over.
C
D
So
for
today,
as
the
perk
has
already
mentioned,
that
all
the
contribution
that
we
have
gone
through,
so
here's
the
high
level
of
the
you
know
just
a
high
level
recap
of
what
we
have
gone
through
from
the
last
from
the
last
few
months.
So,
firstly,
we
will
be
having
about
regarding
this.
So
here's
we
have
the
recap
and
a
global
model
delivery
where
we
have
we
are.
D
D
Then
if
we
come
for
the
dashboard
portal,
initially
the
dashboard
portal
was
quite
basic
and
then
we,
along
with
the
future
weight
team
with
the
we,
along
with
the
few
soviet
team,
has
tried
to
incorporate
several
functionings
over
there,
like
citrus
cluster,
multiple
tps
and
rp's
functionality
and
authentication
using
username
and
password
in
initially
it
was
based
on
only
on
token.
It
was
initially
only
the
token
base.
D
Then
it
has
been
changed
to
username
and
password,
then
added
the
tenant
management,
user
management
functionalities,
several
cluster
monitoring
quota
management
features
and
various
other
workloads
and
functionalities
to
the
dashboard
and
isolation
based
on
the
user
type
of
the
user
that
we
are
using
either
tenant
in
an
admin
super
admin
or,
you
can
say,
a
general
tenant
user.
D
So
these
were
the
top
goals,
and
for
that
we
have
come
through
what
we
have
come
through
an
dashboard
architecture
where
we
have
yeah,
where
we
had
several
deliverables
and
added
the
various
functionalities
as
already
discussed.
D
So
this
is
the
high
level
dashboard
portal
dashboard
architecture
and
we
can
to
go
through
the
go
through
the
portal
in
detail
after
this
which
russian
will
showcase
and
along
with
this
dashboard
function
or
apart
from
the
dashboard
ui,
we
have
delivered
demo
video
for
this.
For
the
for
the
sake
of
reference
and
now
and
yeah,
and
to
make
it
more
user
friendly,
we
had
edits,
we
had
provided
several
documents
and
source
ports
and
everything
test
plans
test
results,
everything
for
layman
for
a
new
user.
D
It
can
be
to
make
it
more
user
friendly.
D
This
is
just
this
is
just
a
comparison
of
what
we
have.
What
ui
changes
has
been
done
to
the
initial
this
you
can
see.
This
is
the
initial
kubernetes
basic
dashboard,
which
has
been
changed
to
this
now
and
the
functionalities,
and
you
can
see
the
ui
changes
over
there
and
the
parameters
there
are
different.
Parameters
have
been
added
for
for
several
monitoring,
like
cpu
monitoring
and
vm
workload,
management
and
everything.
B
B
B
Can
see
it
russian
go
ahead
yeah.
So
this
was
the
old
architecture
in
which
we
are.
We
had
a
dashboard
service.
We
had
a
front-end
packet
and
one
api
server
it
will
connect
to
so
we
have
modified
the
backend
client
and
added
function
like
it
can
connect
to
multiple
api
servers,
as
in
centaurus,
we
do
have
multiple
api
servers
like
for
each
partition.
We
have
separate
api
server,
so
the
back
end
of
the
center's
dashboard
service
can
connect
to
the
eps
server
of
each
partition
and
get
details
from
that
and
perform
operation
on
tenants.
B
Also,
and
along
with
this,
we
have
added
database
support
into
dashboard
service
because
of
like
we
have
added
user
management
feature
also
in
the
dashboard
which
we
can,
we
will
discuss
it
later
in
next
slides.
B
So
in
dashboard
service
we
have
added
user
management
feature
in
which
we
have
three
types
of
feature:
user,
cluster
admin,
tenant
admin
and
tenant
user.
Cluster
admin
will
manage
all
whole
cluster
centers
faster
and
tenant.
Admin
will
manage
one
tenant
which
which
will
be
assigned
to
that
tenant
and
under
the
tenant
admin
we
will
have
a
tenant
user
which
can
perform
operation
under
some
name.
Space
like
it
will
be
named
space
scope.
B
And
we
can
manage
and
monitor
center
structure
at
various
level
like
the
cluster
admin
can
see
all
the
cluster
resource
details
and
the
tenant
admin
can
see
only
his
tenants
details.
Only
he
can't
be
able
to
see
other
tenants,
retail
and
tenant
user
will
get
details
of
all
resources
which
is
deployed
under
the
specific
namespace
within
our
tenants.
B
Yeah
and
other
features
we
have
added
is
like
their
token
page
mechanism
and
we
have
added
support
for
username
and
password
mechanism,
that
is
our
own
developed
by
cryptoclub
team,
and
we
have
modified
and
developed
a
dashboard
dashboard
back-end
apis,
which
is
around
80
apis.
We
have
modified
to
make
it
to
make
it
work
with
the
multiple
tenants
and
user
can
deploy
workload
on
any
specific
tenant
which
was
not
possible
before,
and
we
have
added
support
for
vm
workload
management
also
in
this
and
cortamini.
B
B
So
this
is
how
tested
admin
will
like
get
an
front
page
in
which
he
can
get
details
of
resource
partition
and
tenant
partition
and
cluster
admin
can
get
details
of
cluster
roles.
Tenants.
He
can
create
tenants
and
manage
it,
and
user
management
can
create
any
type
of
users
like
tenant.
Admin,
supported,
tenant,
admin,
supported
cluster
admin
and
tested,
and
he
can
get
details
of
all
crds
present
in
the
question.
B
Yeah,
so
this
is
the
old
dashboard
how
it
looks
like
before
it
is
given
this
dashboard,
and
this
is
how
it
was.
The
user
interface
was
of
kubernetes
dashboard
and
we
have
like
added
user
management.
So
all
these
tabs
went
under
like
for
tenant,
user
and
tenant
and
for
first
admin
we
have
like
summarize
it
more
in
centers,
dipole.
B
Yeah,
so
that
was
there,
and
this
is
how
cluster
had
been
like
frontier
is,
and
if
you
go
into
the
resource
partition,
we
can
get
details
of
all
nodes
present
in
that
rp
that
it
is
a
detail
of
rp1.
B
B
And
if
you
go
to
this
is
all
for
business
partition
and
for
10
partition
like
we
have
set
up
2tp
and
2rp
cluster.
So
we
have
wrote
a
logic
like.
If
we
have
2
tp,
then
all
tenant
name
started
with
a2m
will
go
to
tp1
and
n2
z
will
go
to
pp2.
B
B
And
if
you
go
inside
the
click
to
cloud
tenant,
we
can
get
details
of
all
resources
for
name
space
created
under
that
electrical
tenant.
B
So
yeah
we
can
go
inside
each
parts
and
get
details
of
that
also
so
that
that
details
you
can
share
if.
B
Yeah,
if
we
like
it,
will
give
the
pods
deployed
in
the
system
tenant
of
tp1
so
like
here,
centers
dashboard
default
node
list
and
this
namespace
are
present
in
system
tenant,
and
these
are
the
deployments
present
in
system
tenant
of
pp1.
B
B
So
all
details
you
can
like,
if
you
want
more
details
it
will,
you
can
click
on
this
link
and
you
can
go
inside
test
and
get
details
of
that.
One.
B
So
it
will
go
and
give
me
detail
of
that
asset
and
for
details
so
yeah.
This
is
this
is
cluster
monitoring
part
of
the
cluster
admin
portal
and
the
cluster
admin
can
manage
all
crystal
rules.
So
here
we
can
create
cluster
role
and
we
can
see
all
customer
created
so
yeah
in
this
part.
Only
cloud
operation
we
can
do
on
cluster
room
and
on
tenants
we
can
create
tenant
and,
along
with
the
tenant
we
can
like
one
tenant.
Admin
will
get
created
like
if
you
click
on
10
create
tenant.
B
B
So
we
will
have
a
demo
tenant
created
here.
It
will
go
to
tp1
as
it
starts
with
d
and
if
you
see
in
user
management
for
the
same
tenant,
the
demo
admin
got
created.
A
E
B
So
if
you
click
on
tenant,
we'll
get
all
details
like
what
all
resources
are
present.
By
default.
Q
public
default
time
cube
system
get
created
in
a
new
tenant
and
this
deployment
will
get
created
automatically
when
we
create
a
training.
B
B
Created
here,
like
suppose,
we
have
created
it
manually,
but
we
want
to
create
a
tenant
admin
for
the
tenant.
You
can
create,
create
a
tenant
admin
using
this
dashboard
like
for
the
click
to
cloud
I
will
the
crypto
club
tenant.
I
will
create
one
more
user,
tenant
admin,
rw
admin.
B
So
now,
click
to
cloud
will
have
two
tenant.
Admin
like
one
is
the
main
which
got
created
by
default
while
creating
a
tenant
and
one
more
supported
tenant
that
we
have
created
admin
that
we
have
created
just
now.
B
Subnet
scaling
policy
disaster
is
a
present
in
central
station,
so
this
is
about
cluster
admin,
port
portfolio
and
let's
go
to
the
tenant
admin
portfolio.
B
So
when
tenant
admin
gets
logged
logged
in
so
he
will
see
interface
like
this,
but
all
the
workflow
details
phone
jobs,
ports
deployments
which
all
are
present
in
the
tenant.
You
can
get
details
of
all
the
resources
present
in
that
and,
along
with
that,
this
is
tenant
monitoring.
Part
like
you
can
see
the
summary
of
that
tenant.
Replica
spots,
stateful
set
ingress
services,
pvc
secrets
all
the
kind
resource
kind.
B
Okay,
tenant
admin
can
create
roles
and
manage
rules
also
so.
B
A
I
see
quite
a
bit
of
functionality
here
I
mean
it's
a
good
job,
so
I
just
wanted
to
understand
from
the
community
perspective
like.
Can
we
deploy
this
along
with
the
centaurus
on
this
on
any
customer
location?
Well,
that's
the
plan.
I
mean
it's
going
to
be
upstream
to
centaurus
repo,
basically
yeah
garten
yeah,
along
with
the
admin
dashboard,
the
whole
higher
skill
scaling
of
the
centros
environment
can
be
done
and.
A
Exactly
exactly
I
mean
that's,
you
can
see
that
you
know
how
complex
the
environment
is,
and
you
know
you
know
we
can
talk
about
it
more
right
now.
It's
kind
of
hardwired
for
two
tps
and
two
rps
like
two
partitions,
but
you
know
imagine
we
need
to
enhance
it
in
future
so
that
you
can
have
n
number
of
rpes
and
number
of
tps
and
all
that
and
then
you
can
have
a
very
complex
user
management
as
well.
So
all
of
those
things,
but
we
have
a
baseline
in
place.
A
A
Up
here,
like
one
after
another
popping
up
so
for
all
the
operations,
which
makes
it
much
more
simpler
for
end
users,
yeah.
A
B
Hey
are
you
okay?
Now
russian
yeah,
oh
yeah,
you
can
continue
good.
A
B
Currently
there
is
tenant
admin
which
one
we
have
created
just
now.
Our
deployment
and
the
c2c
was
the
tenant
admin
created
when
we
created
tenant,
and
I
have
created
one
more
user
solution
user
I
will
create.
I
will
show
you
how
to
create
one
more
tenant
user
like
to
create
a
tenant
user.
We
should
have
a
role
created
here
so
right
now
like
we
have.
I
have
created
demo
role
and
russian
russian
role
will
work
on.
Only
russian
namespace
and
demo
role
will
work
on
default
namespace.
B
B
Like
if
you
want
to
default
in
it,
can
you
default
also-
and
I
will
give
quotient
tenant
here
and
role
already
created?
I
have
is
russian,
so
I
will
assign
that
role
to
that
user,
so
I
have
one
more
user
created
like
will
reflect
in
a
second,
so
yeah.
The
new
user
got
created
here
which
we
can
like
using
which
we
can
log
in
and
deploy
workload
on
the
central
desktop
under
that
tenant.
B
B
So
we
have
a
demo
footer,
like
you,
can
manage
quotas
using
quota
management
like
as
I've
shown
before
and
likewise
we
can.
The
internet
admin
can
see
the
phone
jobs
deployments,
jobs,
name,
spaces
present
in
that
tenant
and
pods,
which
all
are
present
in
the
tenant.
B
So
yeah
in
deployments
also,
we
have
nginx
and
4dns,
and
likewise
we
can
get
all
the
resource,
all
kinds
of
resource
details
in
this,
and
we
have
added
virtual
machines.
Also
so
like
I
have
deployed
one
vm,
uvm
ammo
and
as
it
is
not
working
in
centaurus,
so
it
stuck
in
the
field
when
pending
face.
B
A
A
Yeah,
if
workload
is
a
workload,
in
our
case
it
doesn't
matter
if
it's
a
vm
or
a
container,
it
doesn't
really
matter.
So
what
is
so
cool
everything
is
in
a
part.
Basically
so
vm
is
also
in
a
part.
Two
so
container
is,
in
a
part,
also
so
yeah,
and
then
scaling
can
be
done
from
here
for
any
type
of
workload,
any
workload
to
the
workload.
Yes,
that's
true,
that
is
awesome.
That's
super
cool.
C
F
A
You
may
want
to
just
highlight
the
vm
workload
has
a
different
metadata
displayed
actually
because
the
relevant
one,
because
in
the
case
of
container
you
see
something
else,
but
for
kind
of
for
vm.
This
is
what
it
makes
sense.
You
know
what
what
the
image
is,
what
the.
C
G
C
B
Yeah
so
tenant
admin
can
like
manage
its
workloads
and
config
maps,
secret
storage
class,
persistent
volume,
pvcs
all
these
kinds
of
resources,
the
tenant
admin
can
see
under
that
crypto
club
tenant,
and
this
is
all
for
the
tenant
admin
and,
let's
login,
using
the
tenant
user
portfolio.
So
I
have
created,
like
the
ocean
user.
I
will
take.
B
So
this
is
the
workload
that
is
already
deployed
on
the
russian
workspace
and
pods
and
a
cinder
like
tenant
admin.
You
can
also
see
clone
jobs,
deployment,
jobs,
ports,
duplicate,
stateful,
set
and
virtual
machines
also,
which
is
deployed
in
the
russian
namespace,
the
which
I
have
shown
before
is
deployed
in
default
name
space,
so
it
can't
be
visible
there.
B
So
yeah
I
have
just
now
deployed
one
more
part
and
the
next
two
and
it
got
deployed
here
successfully.
So
similarly
user
can
like
the
cluster
admin,
can
manage
open
cluster
antenna.
Admin
can
manage
whole
tenant
resources
and
deployments,
and
likewise
the
trend
user
can
also
manage
resources
under
that
specific
namespace,
so
yeah.
This
is
all
about
the
centos
dashboard.
A
Yeah,
I
think
just
I
know
stefan
came
a
bit
late
so
so,
essentially
you
know
because
this
centaurus
is
a
pretty
complex
environment.
We
have
different,
so
erosion
showed.
I
know
how
the
dashboard
looked
before
in
a
stream
dashboard,
so
we
have
three
different
personas.
Actually,
so
the
persona
means
cluster
admin
will
see
something
else
and
the
tenant
admin
will
see
something
else
and
then
the
tenant
user
will
see
whatever
is
relevant
to
him.
A
Basically,
so,
in
order
for
us
to
enable
it,
we
had
to
create
a
user
management
functionality
as
part
of
centaurus,
basically
so,
depending
on
the
user
role,
he
will
see
whatever
he's
supposed
to
see
and
do
things
whatever
he's
supposed
to
do.
So
we
created
a
very
basic
rudimentary
user
management,
but
it
can
be
plugged
in
you
know,
with
a
grand
you
know
the
user
management
functionality,
but
what
we
have
is
out
of
the
box
is
very
basic
one.
A
You
know
user
password
and
you
know
that's
pretty
much
it
and
the
corresponding
role
to
it,
and
so
that's
the
kind
of
main
distinction
and
now
for
a
cluster
admin.
All
of
the
functionality
which
roshan
showed
is
all
brand
new,
basically
so
all
the
partitioning
and
the
multi-tenancy,
and
all
that
that's
all
kind
of
gets
displayed
and
as
part
of
the
cluster
admin
and
the
tenant
admin
role
basically
and
the
user
admin
tenant
user
is
pretty
much
the
same
as
before,
except
for
the
fact
that
we
have
added
capability
to
launch
new
workload.
A
B
A
G
A
Yeah
great
I
mean
so.
This
is
a
good
start.
As
I
said,
you
know,
as
prashant
mentioned
the
whole
key.
You
know
the
value
proposition
of
centaurus.
Is
you
can
kind
of
spin
up
resources
and
partitions
on
the
fly
so
currently
that
functionality
is
not
there,
but
you
know,
but
we
do
have
a
scale
out
function.
A
You
know
and
then
you
know
keep
on
changing
tenant
partitions,
depending
on
the
what
the
requirements
are.
So
that's
to
kind
of
go
so
there
a
lot
of
work
still
needs
to
be
done,
but
I
think
the
baseline
looks
good
actually
because
otherwise
you
before
this,
you
are
yeah,
go
go
ahead.
Somebody
was
saying.
A
Okay,
I
think
so
that's
pretty
much
covers
everything,
anything
else,
it's
a
great
job,
I
mean
so.
This
is
good,
that's
a
good
contribution
and
this
will
be
upstream
to
our
centaurus
repo.
So
whoever
wants
to
take
it
and
run
with
it,
you
know
they
can
it's
all
open
source
linux
foundation,
project.
A
Great
great
yeah,
thank
you
deepak.
Can
it
be
experimented
on
any
cloud
by
installing
this
thing,
like
as
an
option,
for
example,
do
you
think
like
we
should
wait
for
some
time
to
bring
it
as
an
offering
or
is
it
in
the
current
state,
with
2
tp
and
2
rp,
it's
a
good
to
start
deploying
some
workload
on
it.
A
I
mean
yeah,
so
just
to
show
the
capability.
If
somebody
wants
to
experiment
the
partitioning,
you
know
to
see
how
it
works,
because
the
the
baseline,
the
upstream
cooperatives,
doesn't
have
all
this
so
try
out
the
scale
out
capability,
so
we
have
multiple
tps,
two
tps
and
two
rps,
so
they
can
start
playing
around.
You
know
with
it.
A
But,
as
you
know,
as
I
mentioned,
we
can
we're
gonna,
extend
all
this
and
make
it
more
dynamic
so
that
you
can
have
multiple,
whatever
rp's
n
number
of
rp's
and
n
number
of
tps
and
then
the
whole
gateway
thing.
You
know.
So
one
of
the
key
thing
is
roshan
mentioned
right.
Now
is
kind
of
a
very
hard
wired
that
any
tenant
name
starting
with
a
to
m,
goes
to
10
and
partition.
A
One
and
and
n
to
z
goes
to
pp2,
so
instead
of
that,
we're
gonna
have
a
gateway
that
will
automatically
do
this
kind
of
a
partitioning
and
rebalancing
and
all
that
that
currently
doesn't
exist.
Actually,
so
that
will
be
that
will
evolve
as
well
as
we
go
along
the
gateway,
so
we
call
it
a
tenant
gateway.
Basically
yeah.
I
was
presenting
in
one
of
the
telcos
conference
recently
and
there
were
their
I.t
staff,
which
were
very
interested
in
seeing
that
how
they
can
use
some
of
this
capability
that
we
have
in
centaurus.
A
At
the
initial
level
and
give
feedback
so
so
sonia
question
sony,
hi
sonia,
so
have
we
upstreamed
that
to
our
code
base?
Yet
are
we
still
doing
doing
some
work.
G
So
far
for
the
actors
upstream.
For
now
we're
not
we're
not
adding
new
features.
A
A
Okay,
anybody
wants
to
chime
in,
I
don't
know.
I
think
this
pretty
much
covers,
I
think
and
ocean
anything
else
you
want
to
cover,
or
we
pretty
much
covered
everything.
D
A
Yeah
yeah
keep
good
yeah
yeah.
We
have.
We
have
few
minutes
yeah,
you
can
yeah,
so
actually
the
the
person
who's
not
there.
Actually
punk
is
not
there.
So
maybe
next
time
yeah
yeah
yeah
we
can.
We
can
do
that.
Actually,
next
time
we
can
have
allocate
some
time
and
have
more
discussion
on
the
edge
side.
Actually
in
the
community
meeting
is
that
okay.
A
Think
that
that
would
be
a
good
thing
to
do.
Yeah,
because
banky
is
not
here
so
yeah.
So
the
folks
who
are
here
in
this
call
they
may
not
even
know
about
that
functionality.
Actually
what
you're
going
to
talk
about?
Okay,
so
I'll
next
time
we
can
have
a
focus
on
the
edge
side,
and
then
you
can
talk
about
the
work
that
you've
done
as
a
community
member
and
a
click
to
cloud
as
a
community
member.
A
A
A
A
A
E
A
G
A
A
Cool
all
right
thanks
guys,
hey
the
other
thing,
so
we
don't
have
actually
a
quorum,
but
next
time
around
I'm
going
to
put
that
in
a
gender
item.
One
of
the
thing
which
we
are
proposing
we've
been
kind
of
internally
discussing,
and
we
want
to
we'll
probably
do
a
vote
and
have
a
discussion
that
we
want
to
open
up
this
meeting
to
not
just
the
tfc
members
but
to
every
anybody
who
ever
wants
to
kind
of
join.
Basically
that
way
we'll
have
more.
A
You
know
people
can
get
visibility
to
what
we
are
doing
as
opposed
to
just
esc
members.
You
know
in
there
so
that
we
can
have
that
discussion.
You
know
next
week
and
then
do
a
vote
and
see
if
it
makes
sense.
If,
if
the
tfc
committee
agrees
to
that
or
not
so
that's
one
other
thing
I
wanted
to
discuss,
but
we
can
do
that
next
time
around
any
any
thoughts
or
anything
gonna
to
expand
the
community
base.
I
think
that's
what
that's
one
of
the
thought
we
have.