►
From YouTube: SIG Azure 1 10 planning
Description
A
List
of
features
and
work
that
we
want
to
finish
before
full
110.
That
means
we
to
finish
by
end
of
February.
Okay
I
go
through
there.
The
most
important
requirement
from
everybody
using
copper
nets
right
now
on
Azure
or
any
other
cloud
is
support
for
kms.
The
idea
has
to
encrypt
eight
CD
objects
like
openness,
objects,
safety
need
city
using
an
external
key.
There
was
a
bit
of
contentious
on
this
feature,
garage
an
implementation
removed
and
now
replaced
with
the
gr
PC
external
service
running
where
you
can
just
talk
to
it.
A
To
get
the
key
and
encrypt
and
so
forth,
has
a
very
crisp
and
clear
interface
and
were
ready
to
implement.
I
have
Rita
she's,
not
on
the
call
but
Rita
promised
to
take
over
this
one.
All
right,
then
we
have
the
agile
gateway
and
a
store
at
Gateway.
So
it
seems
this
is
the
agile
application
gateway.
Has
an
English
control
controller
right,
that's
what
is
currently
stalled
and
you're.
A
Looking
for
somebody
for
this
feature,
the
idea
is
to
use
ingress
mechanism,
companies,
ingress
mechanism
and
Link
it
to
Azure
application
gateway,
because
chain
gateway
has
some
sort
of
some
set
of
features
that
people
really
like
around
that
it's
throttling
and
handling
of
incoming
data
to
your
cluster
and
people
are
interested
to
use
that.
Okay,
this,
the
third
one,
is
the
v1
of
out
of
three
provider,
and
by
v1
I
mean
it
will
look
exactly
like
what
you
have
an
entry
provider.
A
As
a
matter
of
fact,
what
we
have
right
now
is
a
private
variable
on
hazard
user,
all
right
that
has
exactly
the
same
code.
That's
in
entry
Batra
at
an
annex
you
to
the
team
that
this
is
again
the
tempo
in
China
and
they
are
asleep
now.
But
what
they
have
is
a
very
simple
job
that
keeps
things
in
sync
all
right
and
allow
this
cloud
provider
to
be.
In
always
home
bar
with,
with
the
the
entry
provider.
A
Over
the
next
over
the
next
couple
of
weeks,
this,
this
previous
three
will
go
public
right
and
then
we
need
to
make
the
decision
of
when
should
we
switch
off
the
old
provider
into
the
new
provider?
This
decision
is
a
bit
complex
to
me
because
it
has
implications
on
how
it
can
be
updated
at
existing
clusters
so
forth
and
we're
looking
in
so
that
I
might
be
bringing
some
input
to
this
and
look
at
for
input
over
the
next
four
over
the
next
called
sinkhole.
A
The
rest
is
pretty
easy
to
see
to
to
go
through
a
few
just
driver
for
the
new
agile
storage
fuse
driver
for
plop
storage.
I,
don't
know
if
you
guys
looked
at
it,
but
there's
a
fuse
driver
right
now
for
blobs
and
I
don't
mean
beige.
Blobs
I
mean
blobs,
like
the
traditional
block,
blobs
encryption
for
the
volumes
people
are
interested,
especially
especially
highly
regulated
environments.
They
are
interested
in
like
encrypting
the
disk
itself,
the
entire
the
data
of
the
disk
is
encrypted.
A
This
will
be
easier
once
we
have
the
kms
integration,
because
it's
also
depends
on
the
key
vault.
So
the
way
as
it
works
is
the
keys
are
said
in
key
book.
So
once
we
have
the
kms
integration,
that
will
be
a
closet,
a
keyboard
proficient
in
the
user
user
resource
group
and
that
can
be
used
for
the
pink
version
as
well.
A
Oh
nice
integration
people
are
asking
like
there
is
requirement
for
it,
but
nobody
came
up
so
far
was
here
is
the
use
case
we
want,
and
accordingly
this
is
being
stolen.
Installing
and
I'm
I'm,
probably
gonna,
take
it
out
of
the
one.
If
you
want
then
release,
because
if
people
want,
if
somebody
came
with
requirements,
the
most
important
thing
is
to
come
with
a
use
case
that
scribes.
How
can
we
say
that
this
requirement
is
delivered?
Because
now
we
have
people
saying
oh,
a
mass
integration,
but
ok.
What
does
this
mean.
A
Some
monitoring
and
analytics
platform
on
top
of
Hydra
that
provides
like
alerting,
graphing
and
dashboarding
and
all
that
stuff
so
and
it's
lightly
fighting
the
greeted
with
agile
own
feature
set.
So
it
makes
sense
as
somebody
using
Azure
and
Coronets
on
desert.
Then
you
can
look
at
everything
in
one
platform,
all
right,
then,
in
the
autoscaler
go
to
scale
your
feature
right
now,
it's
a
it's
an
a
question
mark
this
progress
spot
again.
The
people
who
are
working
out
are
not
exactly
people
I
know
so
I
don't
have
a
lot
of
input
there.
A
All
I
know
it's
progressing.
I
should
have
some
input
this
week
on
this.
Alright,
the
idea
is
autoscaler
for
within
the
cluster
itself,
it's
not
external
to
scale,
it
lives
on
the
cluster,
and
then
people
can
scale
and
scale
up
the
cluster
and
down
automatically
alright,
it's
based
on
one
of
the
incubation
projects
on
copper
nets,
and
then
you
have
the
the
most.
This
is
probably
again
very
important,
see
there
is
a
big
move
on
dropping
you
think
service
principle
for
continual
for
copper,
Netta's.
A
There
is
an
endpoint
on
the
note
rest
endpoint,
where
you
can
connect
get
a
token
and
go
with
this
token
in
to
all
the
resources
that
you
lost
or
may
need
to
talk.
This
includes,
but
not
limited
to
Active,
Directory
or
sequel.
Server
storage
is
going
to
support
this
as
well.
So
there
is
a
lot
of
work
on
this
area.
A
Now
the
v1
implementation
I
think
called
Dead
supported
the
MSI
MSI
was
every
node
who
gets
it
my
identity
right
now,
as
you
can
tell,
this
is
kinda
the
optic
because
you
will
end
up
with,
is
under
the
50
notes
on
a
50
nodes,
each
one
with
own
identity,
and
then
the
team
realized
this
and
quickly
have
the
explicit
homicide.
Explicit
MSI
is
deed.
Coupling
the
identity
from
the
north,
so
I
can
give
a
bunch
of
notes
from
identity.
I
can
give
a
bunch
of
things.
One
identity.
A
That
means
my
cluster
can
be
represented
with
one
identity.
That
means
I
can
do
stuff
like
I,
can
grant
this
single
identity
to
give
all
keys
I
can
give
it
to
pour
it
right
in
give
it
to
Active
Directory.
That
means
better
security
and
better
management
and
apply
less
operational
overhead
on
the
the
the
cluster
itself.
This
is
a
big
deal,
and
it's
one
of
those
things
that
everybody's
talking
about
and
everybody's
keeping
track.
A
The
reason
Windows
this
VT
110
feature,
which
is
the
CRI.
When
you
see
all
my
configuration
windows,
is
trying
to
move
away
from
like
explicit
kinetically
vision
and
so
on
and
and
talks
directly
to
CRI
again,
I.
Don't
have
a
lot
of
input
on
this
because
I'm
not
keeping
track
of
Windows
but
I,
know
that
people
are
working
on
this
again
and
actually
my
team
Microsoft
I
was
working
on
actively
on
this
right.
A
All
right
side
by
side
there
is
another
PR
Google
is
working
on
it,
which
is
added
like
dynamically
deciding
on
the
number
of
resistive
discs
pair
or
persist
volumes
will
not,
and
this
will
be
configuration
driven
so
side
by
side.
When
we
deliver
both
of
them.
We
shouldn't
we
shall
no
longer
get
problems
like,
but
your
game
is
nombre
meme
and
you're,
trying
to
slim
starch.
A
So
this
is
all
happening
over
there
and
then
the
there
are
three
buttons
were
tracking
four
four
four
v110
there
will
be
more
bugs
to
track
the
first
one
is
agile.
The
agile
file
resize
feature
like
I,
have
an
azure
file.
Pv
and
I
want
to
resize
it
mount
options
for
a
DD
like
mount
mount
read-only
or
like
the
the
bind
mount
option
that
we
have
right.
Now
we
don't
have.
A
We
have
basic
support,
but
the
idea
is
to
support
more
there
then
Andy
from
such
a
native
is
actively
working
this
one,
and
then
there
is
the
flex
volumes
of
booting
windows
that
allows
to
support
funky,
B,
behaviors
and
funky
behaviors,
that's
window
specific,
mainly
the
think
of.
As
your
story.
Sorry
windows,
culture,
species
which
is
similar
to
Linux
volley
measures.
You
can
stitch
a
disk
out
of
disks,
so
Felix
volume
support
will
allow
store,
but
by
PowerShell
scripts
to
allow
people
to
actually
do
these
things
all
right.
A
There
was
a
request.
Last
time
we
talked
around
release,
notes
for
that.
Behavior
changes
with
that
for
energy,
Network,
load,
balancers
and
so
forth.
Sits
there
on
one
line,
release,
notes
right
now
and
you
go
ahead
and
read
it
well.
It
has
a
lot
of
features
for
people
to
use
and
will
not
try
it
so
hard
not
to
change
the
behavior
but
extended
meaning.
If
users,
don't
change,
don't
say
change
the
config.
A
Everything
will
remain
as
if
they
turned
on
a
conflict,
then
you
can
use
in
features
that
allow
them
to
not
forget
that
surprise
of
oh
I
expected
this
to
happen,
but
all
right.
The
last
thing
to
talk
about
is
the
announcements
for
anybody:
who's,
not
who's,
not
there.
Over
the
past
few
talks,
we
are
going
to
fork
Copernicus
or
nasha,
meaning
people
in
NASA
will
run
as
with
specific
boundaries,
not
the
mystery.
However,
the
this
binaries
are
almost
100%
of
upstream.
A
Our
job
is
going
to
be
again
pushing
upstream
as
fast
as
we
can,
but
this
allows
for
emergency
fixes.
Let's
say
how
to
ban
patches
for
agile,
specific
stuff
that
cannot
go
as
fast
on
the
out
trim
or
mainline.
We
will
apply
them
on
our
our
fork
and
then
quickly.
Push
for
upstream.
Anything
that
doesn't
make
a
stream
will
be
reverse
it
back.
So
what
you
will
get
when
you
run-
and
this
this
fork
is
everything
upstream
plus
plus
yes,.
A
So
during
one
night
we
were
lucky
what
we
were
any
at
the
edge
of
our
seats.
The
changes
we
did
for
the
network
load
balancer.
The
energy
was
seriously
affecting
customers
using
copper,
netizen
measures,
specifically
large
clusters,
as
in
the
cloth,
because
the
cluster
doesn't
work
because
issues
in
the
cloud
provider-
yes,
we
were
very
lucky,
pushing
them
in
building
them
and
pushing
them
in
20
days.
B
C
B
D
A
B
E
A
Is
public?
The
images
is
public,
so
the
binary
is
that
the
head,
the
hypercube
image
itself,
is
going
to
be
public.
All
of
this
is
going
to
be
public
all
right.
That
piece
is
missing
right
now
and
we
have
people
I.
Think
we
have
a
good
call.
Chauncey
is
responsible
for
building
like
the
CIC
PD
for
this
environment,
and
once
we
have
this
tightened
up
with
East,
we
will
be
using
this
fork.
E
A
One
of
the
things
that
will
we
wouldn't
have
here
is
a
very
wide
set
of
CICE
jobs
for
testing
right
on
on
had
there
any
specific
hazard
tests
will
be
there
in
addition
to
be
upstream
as
well
the
whole
point
of
doing
this
is
not
too
distant
herself
of
midline.
Actually,
we
want
to
be
close
to
me
as
as
much
as
we
can
it
has.
It
has
always
been
a
part
of
what
we're
trying
to
do,
however,
due
to
just
emergency
out-of-band
batches.
A
Basically,
this
is
this
is
where
this
fork
will
get
it
first,
but
I
internally,
when
we
talked
about
this
I
was
very
clear.
If
it
doesn't
make
it
upstream
in
X
and
XS
currently
being
defined
X
weeks,
it
will
give
it
it
will
have
to
be
revert.
We
cannot
have
for
or
thrown
away
from
inland
that
something
that
you
need
to
understand.
A
Nope
so
the
best
guy
to
talk
about
and
probably
bet,
a
lot
better
better
explanation
than
me
has
Jase,
sadly,
won't
happen
today,
but
he
should
be
here
like
the
next
next
next
iteration
and
he
can
talk
more
about
the
reasoning
and
how
it
would
work
and
so
forth
right
now
nobody's
using
that
fork.
As
far
as
I
can
tell
like
you,
when
you
run
a
CS
engine
and
all
that
you're
actually
owning
the
hyper
hyper,
keep
images
formula
and
not
yet
all
right.
A
B
A
A
F
B
A
So
the
last
thing
because
throws
shatter
yesterday
only
the
agile
said,
the
channel
on
Copernicus
slack
about
disk
by
schists.
Right
now
is
a
standalone
project.
That's
not
formally
a
part
of
agile
right.
However,
we
were
working
actively
on
making
this
a
reality.
We
want
some
people
to
be
able
to
use
large
number
of
disks
quickly
attached
and
attach
them,
and
actually
there
is
a
flex
volume
if
you're
keeping
an
eye
on
what
I'm
planting
about.
A
C
Sorry
sorry
I
couldn't
be
here
for
the
meeting
of
dealing
with
personal
stuff,
but
yeah.
If
you
haven't
covered
I,
just
want
to
make
sure
that
people
look
through
the
issues
NPR's
that
are
serve
out.
There
was
some
need
a
little
attention,
but
doesn't
that
it
looks
like
you
guys.
Did
a
great
job
planning
and
I
sincerely
appreciate
a
cup.
A
A
B
A
Okay,
so
there
is
not
a
smooth
meeting
between
folks,
like
gentian,
you
have
jesse,
Frizzell
and
Brandon
working
on
getting
windows,
coping
and
support
like
better
windows,
coconuts
and
so
forth.
This
V
team
extends
networking,
storage
and
kernel
one's
criminal
as
well.
The
idea
has
always
been.
We
want
Windows
to
be
like
a
first-class
citizen
to
copper,
nitrate.
A
The
most
important
thing
for
me
now
is
actually
to
talk
about
the
CNI,
because
see
no
I
eventually
will
become
the
default.
I
think
it's
currently
now
on
ACS
engine
right,
so
we've
actually
seen
I
would
be
turned
on
on
all
the
clusters.
You
we
see
on
hand,
that's
huge,
because
there
is
a
lot
of
limitation
and
the
existing
route
table
approach
for
networking
and
all
that
and
we
want
to
drop
them.
So
this
is
not
tracked
here,
because
it's
happening
Millie.
A
It's
really
our
side
components,
it's
a
plug-in
for
network,
but
Jack
Jack
from
Jack
Francis
I've
seen
him
here.
You
can
talk
more
about
that,
but
that's
in
terms
of
like
teams
working
for
Microsoft
of
this.
This
is
where
I
would
like
say.
First,
networking
team
is
working
heavily
on
enabling
this
and
there
is
a
Windows
V
team
working
across
multiple
groups.
You
have
guys
like
Patrick,
Lang
and
and
he's
a
colleague
whenever
working
heavily
on
this.
Ok,
all.
E
A
E
E
A
E
C
Yeah
Thank
You
Cal
for
any
meeting
and
and
if
anybody
has
any
questions
just
to
them
and
the
Siderius
like
general
eternities
there,
but
it
looks
like
we've
got
a
good
thing:
I'll
be
working
on
the
PM
side
of
this
so
I
under
facing
with
the
features
process
to
make
sure
this
is
documented
and
that
we
track
these
through
and
do
the
documentation.
So
again,
thanks
everybody
for
all
your
help,.