►
From YouTube: Geo Kickoff 12.7
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
A
So,
let's
begin
the
first
thing
to
make
note
of
was
we
were
planning
to
release
the
support
for
design
repositories
in
12.6,
but
we
will
be
continuing
work
for
this
in
12.7,
we
have
three
more
mode
requests
that
need
to
go
through
the
final
review
and
have
unfortunately
missed
the
cutoff
for
this
release,
but
that
will
be
included
in
12.7.
So
we
will
be
wrapping
that
up
and
shipping
that
as
part
of
the
next
milestone,
the
next
thing
that
we
are
continuing
to
work
on
is
getting
geo
rolled
out
to
the
staging
environment.
A
The
next
set
of
work.
We're
planning
to
look
at
is
improving,
planned,
fail
overs.
At
the
moment,
it
can
be
quite
cumbersome
to
follow
a
series
of
steps
in
order
to
get
the
failover
to
be
successful
so
recur.
We
are
currently
discovering
exactly
what
the
system
is
capable
of
now
and
what
improvements
would
make
sense
to
do
as
a
first
iteration.
The
things
that
we
have
planned
for
12.7
are
to
go
through
some
demonstrations
in
detail
for
both
single
nodes
and
hae
installations.
A
Ultimately,
if
people
are
doing
or
using
geo
for
disaster
recovery,
they
should
be
practicing
using
planned,
fail,
overs
on
a
regular
basis,
and
we
want
to
make
sure
that
that
is
as
easy
as
possible
for
them.
So
this
is
going
to
be
a
fantastic
effort
once
we
get
to
the
implementation
of
this
now,
as
I
said
at
the
moment,
we're
still
in
discovery
determining
once
they're
in
what
steps
we
need
to
be
taking
next
following
on,
will
be
we're
continuing
to
look
at
the
self-service
framework.
A
A
We
still
need
to
confirm
some
aspects
of
the
verification
side
of
that
framework
that
weren't
addressed
in
the
proof
of
concept,
but
we're
pretty
confident
they
will
be
able
to
get
the
first
data
type
moved
over
using
the
new
framework
and
we'll
be
able
to
put
a
demonstration
together
of
that
of
how
they
can
be
used.
Our
plan
further
than
that
is
to
do
another
data
type
ourselves
before
we
start
to
ask
other
teams
to
use
the
framework
themselves
to
add
any
new
tate's
types
on
ticket
lab.
A
You
know
for
further
information
about
that.
You
can
take
a
look
at
the
proof
of
concept
here.
Another
proof
of
concept
that
is
also
linked
to
this
work
is
making
the
repository
tables
the
single
source
of
truth,
so
that
we
can
keep
the
back
fill
process
quite
simple
and
straightforward.
This
proof
of
concept
is
also
moving
along
and
we
hope
to
conclude
that
in
12.7
as
well,
which
will
support
the
self
service
framework
quite
nicely.
A
Other
things
we're
taking
a
look
at
us
and
doing
is
continuing
to
look
at
improving
the
usability
of
the
administrator
interface.
This
is
also
in
discovery
at
the
moment.
Essendon
continues
to
develop
out
the
scorecards
for
the
front
end,
we're
hoping
that
this
will
advance
into
issues
into
concrete
issues
for
further
for
further
investigation
and,
ultimately
for
implementation
in
the
new
year.
A
Alongside
that,
we
have
also
found
from
the
distribution
team
that
they've
moved
further
along
with
their
work
on
the
provisioner
tool
and
we're
looking
forward
to
giving
them
feedback
on
how
their
provisioner
tool
is.
M
is
working.
The
provision
is
going
to
make
it
much
easier
for
us
to
set
up
a
che
installations
of
Geo
so
that
we
can
get
through
testing
issues
specifically
for
that
plan.
Failover.
That
I
mentioned
earlier
on
having
a
faster
way
to
set
up
machines
in
order
to
do
tests
will
be
a
significant
help
to
us.