►
From YouTube: CDS G/H (Day 2) - Calamari Localization
Description
https://wiki.ceph.com/Planning/CDS/CDS_Giant_and_Hammer_(Jun_2014)
25 June 2014
Ceph Developer Summit G/H
Day 2
Calamari Localization
B
Right
so
here
we
are,
I
guess
we're
going
to
pick
up
with
the
first
session
as
the
calamari
localization
discussion.
Xi'an
is
here
to
to
lead
that
discussion
and
I
think
lee
may
be
joining
us
in
a
little
bit.
But
jen
did
you
want
to
tell
us
a
little
bit
about
your
blueprint.
A
Hello,
everyone,
my
blueprint
is
about
the
localization
of
calamari
and
after
calamari
openings
those
code.
I
will
try
to
deploy
the
culinary
and
ubuntu
process
so
currently
calamari
can
provide
provide,
monitor
view,
osd
management
for
management
and
information,
and
so
and
so
on,
other
functions
and
but
it
looks
very
in
the
server
I
deployed
is
empty.
So
I'm
not
sure
what
kind
of
the
information
it
looks
so,
maybe
later
I
can,
I
can
see
it.
A
This
shift
is
more
and
more
step,
step
stable.
It
will
be
widely
used.
I
think,
though,
there
will
be
more
and
more
people
to
participate
in
china.
Calamari
has
had
as
a
monitor
with
the
nice
square
cluster
of
sleep.
It
has.
It
has
a
significant
every
effect
I
think,
but
localization
by
localization
of
country.
A
C
C
Oh,
I
mean
there's,
there's,
naturally
the
kind
of
best
choice
that,
for
that
is
git
text.
C
A
D
Yeah,
I
think
I
mean
from
my
perspective,
I
think
the
only
the
only
thing
I
would
want
to
make
sure
that
we
do
is
that
any
localization
effort
is
done
in
a
in
an
easily
replicated
generalized
way
so
that
we
can
slot
in
all
the
different
languages
right.
So
it's
a
one-time
effort
to
sort
of
modify
the
code.
I
assume
that's
what
get
text
does,
but
I've
never
right.
E
D
C
E
C
C
F
It's
a
default
yeah.
If
it
can't
look
up
in
the
po
file,
then
it's
always
falling
back
to
the
english
version.
C
All
right,
so
I
guess
from
a
standpoint
of
how
we'd
want
to
go
forward
with
doing
this
would
be.
You
know,
we'd
have
to
cut
the
tickets
to
actually
choose
which
pieces
that
we're
going
to
be
translating
and
then
after
sorry
and
then
and
then
after
we
have
that
structure
in
place
of
the
pieces
that
make
sense
to
translate.
C
Then
we
have
to
engage
the
community
to
provide
the
actual
mappings,
but
the
community
could
also
do
the
work
to
provide
the
translation,
but
that's
a
larger
discussion
of
which
parts
make
sense,
because
traditionally,
when
you're
taking
stuff,
you
know
from
kind
of
a
deep
technical
domain
like
ceph,
you
can
lose
some
of
the
meaning
of
the
domain
specific
language.
You
know,
for
example,
osd's
pools
pgs.
When
you're
talking
about
the
relationships
of
those
you
can,
you
can
lose
some
of
the
meaning
by
translating.
F
C
E
It's
one
of
the
one
of
those
things
where
we
could
use
help
from
from
someone
who's
done
this
before,
because
it's
it's
a
little
bit
of
an
art
choosing
which
messages
really
should
be
in
which
we
shouldn't
dana.
Do
you
have
any
experience
in
this
area?
Being
a
non-english
speaker,
I
assume
you
ever
dealt
with
the
translation
stuff
at
all.
F
Yeah,
but
not
python,
related
code.
E
F
E
F
I
I
also
guess
if
the
tool
is
coming
up
into,
for
example,
a
red
hat
towards
user.
They
also
will
translate
it
if
it's
important
enough,
so
they
also
have
teams
to
technical
teams
to
translate
technical
terms
in
the
correct
translation.
So
I
would
say
they
may
can
help
if
the
community
is
not
able
to
do
it.
C
B
Yeah
is
it
possible,
with
git
text,
to
leave
certain
key
things
behind
as
well
like
translate?
B
You
know,
meaning
for
osd,
monitor
whatever,
but
leave
it
parenthetically
cited,
so
that
you
can
match
it
in
the
low
level
messages
so
that
when
you
see
like
a
pg
dump,
you
can
see
the
literal
pg
to
pg
match
between
english
and
the
the
low
level
message,
but
still
have
a
meaningfully
translated
thing
of
what
this
is
next
to
it.
C
D
C
A
B
Xi'an,
do
you
follow
along
with
this?
Do
you
agree
with
the
idea
of
using
get
text?
B
E
E
C
A
E
D
Are
there
I
mean,
are
there
other
projects
that
are
relatively
narrow
in
scope?
That
are
just
easy
examples
of.
A
D
F
C
So
yeah
I
mean,
I
think
we,
the
the
canonical
location
could
be
just
you
know.
It
gets
usually
a
pretty
bad
place
to
store
large
screen
shots,
so
we
probably
wouldn't
want
to
put
them
there
if
it
wasn't
actually
code.
C
Yeah
I
mean
we
could
use
google
drive
for
screenshots
or
something
like
that.
Do
you
have
anything
community-facing
that
solves
that
problem.
C
E
B
Maybe
jion,
maybe
gregory
can
go
through
the
ui
first
identify
the
things
that
should
be
translated
first
and
that
should
get
you
started.
Does
that
sound
good.
B
I
was
thinking
more
from
the
point
of
view
of
of
the
calamari
guys
know
what
is
sacrosanct,
given
what
kinds
of
things
can
be
manipulated.
B
Yeah
yeah
so
all
right,
but
I
think
the
as
long
as
we
keep
it
on
the
blueprint
or
linked
from
the
blueprint
that
way
it's
kind
of
a
canonical
resource,
regardless
of
where
we
point
things
at
that,
probably
is
key.
D
B
C
D
C
So
I
mean
dozens
of
images,
you
know
the
calamari's
got
more
main
screens
and
then
there's
a
couple
of
modals,
so
I
don't
expect
it
to
be
large
at
first
and
we
can
okay
iterate
that
as
we
go,
you
know
it's
the
first
step,
yeah
yeah.
B
I'm
asking
now
in
chat,
but
obviously
the
problem
with
google
drive
is
the
firewall,
so
we
should
make
sure
that
jian
is
actually
able
to
get
to
google
drive
and
access
google
draw.
If
that's
what
we're
implementing.
E
B
Dan,
just
pasted
a
test
link
to
make
sure
that
you
be
able
to
get
to
it,
but
it
sounds
like
he
has.
Access
to
google
drive
so.
F
A
B
D
Mean
I
think,
the
the
high
level
goal,
for
me
at
least,
was
to
to
have
some
sort
of
hierarchical
view.
So
I
mean
ideally
something
based
on
the
crush
map
or
some
things
like
that,
so
you
can
see
like.
Oh
everything
in
that
rack
is
down
or
a
whole
row
is
down
or
just
you
know,
an
outlier
ost.
Something
like
that.
So
you
can
drill
in
that
way.
B
Use
the
google
earth
again.
D
B
Jen,
did
you
have
other
concerns
or
things
that
you
wanted
to
touch
on,
so
we
we
will
be
scaling
beyond
256
nodes
in
1.3,
but
we
aren't
sure
how
it's
going
to
happen
yet
that
that's
still
being
designed.
B
But
beyond
that,
do
you
have
other
questions
for
calamari.
A
B
C
So
the
answer
for
1.2
about
say
more
osd
stats
was
we
didn't
bring
a
whole
lot
of
them
across
because
there
that's
just
a
really
a
lot
of
data
to
be
sending
to
one
small
calamari
node
and
we
prioritize
the
decision
that
you
know
we
haven't.
You
know
waited
through
the
sea
of
osd
stats,
the
kind
of
sentiment
we
have
or
thinking
our
plan
is
we're
gonna,
whitelist,
specific
ones
in
the
future.
C
B
C
Yeah,
absolutely
I'll
put
my
name
on
it
and
put
the
task
of
sharing
the
screenshots
with
the
date.
Okay,.
B
Cool
all
right
well,
thank
you
very
much
jian.
This
was
good
and
it
looks
like
we're
just
about
ready
to
start
the
next
one.
So
did
anyone
else
have
any
other
things,
any
questions
in
the
channel
or
anything
before
we
shut
this
one
off.
A
B
All
right:
well,
I'm
gonna
kill
the
video
on
this
one
because
I
think
it's
pretty
much
wrapped
and
then
we
could
skip
to
the
rgw
bucket
stuff
if
we
need
to
yeah
all
right
well,
thank
you.
Jen.