►
Description
Broadcasted live on Twitch -- Watch live at https://www.twitch.tv/nrelabs
C
A
A
A
D
C
C
A
B
C
C
A
We've
with
the
next
big
version
is
Oh
dot,
4
dot.
Oh
and
there's
a
bunch
to
talk
about
there.
One
of
the
things
that
we've
we've
had
to
deal
with
a
little
bit
is
a
lot
of
folks
contributing,
aren't
super
familiar
with
either
get
or
and
or
github
I
wondered
Eric
if
you
might
be
interested
in
just
walking
through.
We
have
Doc's
on
this,
but
it'd
be
nice
to
I.
Think
do
like
a
visual
walkthrough
on
like
like
what
just
starting
out
like
if
you
just
are
looking
at
the
curriculum.
A
A
C
Ok,
so
let's
start
by
just
going
over
what
the
github
repository
looks
like.
C
C
Well,
that's,
that's
the
get
of
account!
That's
the
spot,
we're
all
the
NRI
labs
stuff
is
and
you'll
see
that
there
are
25
repositories,
but
it's
really
five
of
them.
That
sort
of
are
the
main
repositories
for
the
project
and
we'll
kind
of
go
over
these
right
now
by
scrolling
down.
So
first
we
have
any
doe
web.
This
is
our
web
front-end.
So
when
you
go
to
actually
when
you
go
to
any
labs
labs
that
network
reliability,
data
engineering,
all
of
that
front
end
is
inside
this
antidote
web
repository.
C
So
it's
kind
of
it's
separated
out
from
the
back
end,
which
is
good
and
from
from
the
actual
course,
the
lessons
themselves,
which
is
good
any
labs
curriculum.
This
is
where
all
the
actual
public
lessons
are
for
that
website.
Let's
go
here!
Actually
we
can
click
on
lessons
and
then
you
see
they're
broken
up
into
categories,
fundamentals,
tools
and
workflows.
You
go
to
fundamentals
and
you'll,
see
numbered
or
descriptions
of
the
lessons
in
the
directory.
I
won't
get
into
too
much
detail.
I
guess
about
that
now
or
maybe
I
should
I,
don't
know.
A
C
So
this
is
okay.
I'll
go
over
what
a
lesson
looks
like
in
the
github
repository
you'll,
see
a
lat
in
you
know,
underneath
the
lesson
category
underneath
the
actual
lesson
you'll
see
a
yam
we'll
file
here
in
that's
in
every
single
one
of
these
lessons-
and
this
is
actually
a
description
of
the
lesson,
including
a
description
of
the
sandbox
environment,
that
the
lesson
uses
to
illustrate
whatever
it
is.
You
know
whatever
concepts
are
trying
to
get
across
in
the
lesson
and
among
it
this
is
well
this
one's
just
about
yamo.
So
it's
not
that
interesting.
C
Let's,
let's
pick
a
different
one
will
pick
lessons
tools,
J
snappy,
we'll
see
we
have
the
mo
file
here.
Of
course,
there's
the
lesson
name,
the
lesson,
a
unique
number
identifying
the
lesson.
There's
a
lesson
diagram
to
go
with
the
lesson.
You
know
that
kind
of
thing
description,
some
other
metadata,
but
what's
really
interesting
here-
is.
C
Where
it
says
utilities
and
devices
I'll
start
with
devices,
these
are
the
actual
network,
the
virtual
network
devices
that
are
in
the
lesson.
So
in
this
case
you
know
we
have
three
vqf
X's
in
the
lesson,
so
we
have
a
name
forum
and
we
have
a
source
image.
This
is
the
container
image
and,
of
course,
there's
three
of
them
and
you'll
see
that
there's
actually
one
two
three
different
source
images
and
there's
a
reason
for
that.
C
If
these
are
acted
in
order
to
make
them
boot
in
a
reasonable
time,
each
of
these
is
actually
a
snapshot
and
we
can't
use
the
snap
same
snapshot
over
and
over
again,
because
then
all
the
nodes
would
have
the
same
Mac
dresses
and
that
doesn't,
as
we
learned,
doesn't
actually
doesn't
work
so
great.
So
you
need
to
have
three
different.
C
We
made
three
different
ones
and
snapshot
at
each
of
them,
so
these
are
like
nodes
on
a
graph
right
and
then
we
have
connections
which
are
edges
on
the
graph
and
they
describe
how
the
nodes
on
the
graph
are
interconnected.
We
can
see,
there's
three
connections
here
and
there's
an
a
N
and
a
bien
so
Q
FX,
1,
&,
2,
2,
&,
3,
&,
3,
&
1,
so
we're
making
a
triangle
out
of
these
three
vqf
X's
you'll
notice,
there's
no
interface
names
here
and
the
reason
in
this
case.
C
Why
that's
true
is
because
you
can
actually
guess
what
the
interface
names
will
be
by
looking
at
this
list.
This
is
an
ordered
list
right,
so
this
connection
will
be
made
first,
this
one
we
made.
Second,
this
will
be
made
third
every
single
time.
This
lesson
is
spun
up
and
we
know
from
from
how
these
work
that
this
will
be
GE,
0,
0,
1
right
the
first
time
a
node
is
mentioned
in
the
in
a
connection
that
interface
will
be
GE,
0,
0
1
in
the
case
of
EQ
effects.
C
So
this
is
GE
0,
0,
1,
2,
GE,
0,
0,
1,
then
you'll
see
vq
of
x2
is
mentioned
a
second
time
we
can.
That
means
that
this
will
be
GE,
0,
0,
2,
connected
to
GE,
0,
0
1
on
V
Q
of
X
3,
and
then
here's
3
mention
the
second
time
that'll
be
G,
0,
0,
2,
connected
to
V
Q
of
X
1
GE,
0,
0
2.
Since
it's
the
second
time
V
Q
of
X
1
is
mentioned,
you
can
sort
of.
C
You
can
read
them
that
way
and
there's
actually
a
number
of
appliances,
regardless
of
vendor.
That
kind
of
worked
that
way.
So
we're
making
this
this
triangle
topology
of
these
vqf
X's,
then
we
have
a
a
utility
know
called
Linux
1,
and
this
node
is
is
a
it's.
It's
a
Linux
host
that
you
can
access
the
management
interface
via
Netcom
4
or
you
can
even
get
to
see
a
lie
if
you
wanted
into
each
of
these
devices.
C
C
C
If
you
use
energy
labs,
then
you'll
know
that
each
lesson
is
a
set
of
stages
and
each
stage
is
like
a
mini
lesson
right.
So
you
can
have
will
have
a
lesson.
We
have
a
lesson
on
yeah
Milland,
there's
multiple
stages
in
that.
In
that
lesson
that
teach
different
aspects
of
gamal
like
one
on
Yamma
list
and
one
on
llamo.
A
So
well,
we
have.
There
are
some
there's,
a
common
beer
clock
also
points
out.
There's
there's
some
contributing
documentation.
There's
also
references
to
a
lot
of
this
stuff
so
like.
If
you
want
to
know
like
what
the
different
fields
are
in
a
in
a
metadata
file
for
less,
for
instance,
or
any
metadata
file,
you'll
see
we're
gonna
be
coming
out
with
a
few
different
types
of
resources
and
antidotes.
A
So
any
metadata
file
that
the
full
reference
of
what
field
does
what
that's
gonna
be
in
the
docs
one
thing:
that's
pretty
common
for
people
to
get
tripped
up
on,
especially
if
you
know
we're
talking
about
like
network
engineers
who
aren't
used
to
doing
anything
at
github
Derrick.
Do
you
mind
over
viewing
like
the
the
process
of
like
okay,
you,
basically
at
the
beginning,
you're
considering
contributing
a
lesson?
A
What's
the
kind
of
stuff
you
need
to
start
doing,
and
then
you
know
we
can
sort
of
skip
over
the
reference
part
of
actually
grinding
out
the
lesson
because,
like
I
said,
I,
think
there's
Doc's
for
that
and
then
ending
with
a
pull
request,
or
you
know,
forking
the
repo
and
ending
with
a
pull
request.
What's
like
the
full
lifecycle,
there.
C
Well,
the
okay,
so
if
the
first
thing
is
obviously
you
need
a
get
up
account
with
the
key
and
all
that
stuff
right
and
what
we
recommend
I'm
gonna.
Actually,
let
me
finish:
I'm
not
gonna,
go
deep
into
each
of
these,
but
there's
a
I'm
gonna
mention
all
of
these.
So
I'm
gonna
cover
that
real,
quick
before
we
before
we
touch
on
that
man,
the
other
the
other
three
I'll
say
the
other
two
really
important
directories
are
the
syringe
directory.
That's
the
scheduler
for
antidote.
That's
the
component
that
reads
in
that
yamo
file.
C
We
were
just
talking
about
and
then
there's
added
antidote
which
at
this
point
is
really
a
Doc's
reply,
repository
and
I,
and
the
last
thing
is-
and
this
is
this
whole
gateway
into
what
Matt
asked
about
just
now-
the
antidote
self
medicate
repository,
which
is
actually
one
of
the
first
things
you
ought
to
do.
If
you
want
to
consider
doing
a
lesson,
you're
going
and
any
note
self
medicate
is
actually
a
way
that
you
can
run
the
entire
website,
local
on
your
computer
and
if
you're
going
to
be
contributing
lessons.
That's
what
you
that's!
C
It's
really
recommended
that
you
use
any
to
self-medicate
to
build
your
lessons.
It's
it's
designed
to
be
easy
to
use
and
to
make
it
easy
to
to
spin
up
a
local
copy
and
make
changes
to
your
lesson
and
then
quickly,
refresh
and
and
see
how
they
look
and
work
and
all
that
stuff.
So
once
you
download
self-medicate
that
first
thing
your
and
it's
everything's
Val,
you
know-
and
you
know
that
mini
cube-
is
working
as
well
as
virtual
box
for
KVM
you're
going
to
want
to
clone
this
enemy,
Labs
curriculum
directory.
C
That
has
all
the
lessons
in
it
onto
your
computer
and
you
know
actually,
no,
that's
not
true,
I'm
jumping
ahead.
What
you
want
to
do
is
you
want
to
fork
this
directory
to
your
own
account
and
if
we
go
to
my
repositories,
you'll
see
I
have
a
fourth
copy
right
here.
Once
you
fork
this,
then
you're
going
to
want
to
clone
this
directory
into
the
same
parent
directory
that
you
cloned
self-medicate
into
when
you,
when
you
install
self-medicate
once
you
do
that.
A
A
Basically,
what
it's
doing
is
it's
creating
a
copy
at
the
point
where
that
repository
currently
is
so
it
doesn't,
it
doesn't
keep
your
fork
in
sync
automatically,
there's
ways
to
do
that
yourself,
but
it
doesn't
do
it
for
you
just
wanted
to
call
that
out
before
the
Fort
button
over
to
the
top
right.
Does
that
for
you,
yep.
C
At
that
point,
you
can
load
self-medicate
and-
and
you
should
be
able
to
see
all
those
lessons
and
everything
working
on
your
local
development
in
your
local
development,
whether
it's
on
your
laptop
or
your,
you
know
some.
You
know
PC
or
server
that
your
that
you're
doing
this
on
its
kind
of
recommended.
It's
my
recommendation
that
you
have
the
depending
what
you're
doing
enough
RAM
to
support
that
lesson.
If
you're
gonna
load
up
three
qfx
images
and
and
other
components,
you're
gonna
want
16
gigs
of
ram
or
more
to
do
that.
A
Yeah,
this
is
good.
It's
gonna
wildly
depend
on
the
lessons
that
you're
loading,
in
fact
in
the
very
very
near
future.
What
we're
finding
is
some
of
the
lessons
require
actually
not
not
not
just
a
lot
of
resources
in
terms
of
like
you
know,
RAM
and
CPU,
but
just
by
virtue
of
using
nested
virtualization,
which
we
often
have
to
do
even
in
the
cloud,
even
in
the
production
instance,
because
we're
running
inside
of
GP
VMS,
just
the
fact
that
we're
using
nested,
virtualization
and
there's
just
not
enough,
there's
no
amount
of
RAM
or
CPU.
A
We
can
throw
at
the
problem
to
make
it
faster.
It's
still
gonna
be
super
slow,
so
one
of
the
things
we're
gonna
be
doing
in
the
in
the
near
future
is
is
because
of
only
you
know.
Only.
This
is
only
true
for
a
few
of
the
lessons,
but
some
of
the
lessons
are
using
what
we'll
call
full
versions
of
a
network
device.
We've
actually
done
a
lot
of
tricks
with
most
of
the
lessons
existing
that
that
really
lightens
them
and
doesn't
make
it
as
much
of
a
problem
that
we're
running
in
nested
virtualization.
A
But
it's
that
only
goes
so
far.
So
what
we're
so
in
the
near
future,
we're
gonna
be
moving
the
the
production
cluster
to
a
sort
of
a
bare-metal
as
a
service
provider,
to
get
better
much
much
much
better
performance
on
that
side
of
things
as
a
result,
if
you
want
to,
if
you
want
to
be
able
to
develop
those
kind
of
lessons
with
those
full-featured
Network
Devices,
and
it's
not
just
Juno's
by
the
way,
there's
a
lot
of
other
devices
that'll
require
this
I'd.
A
Imagine
then
more
than
likely
you're
gonna
want
to
run
self-medicate
on
bare
metal.
Maybe
you
have
us
a
big
server
that
you
that
you
want
to
dedicate
to
developing
lessons
so
one
one
cool
thing:
the
self-medicate
does,
or
rather
mini
cube,
which
is
the
sort
of
miniature
kubernetes
installer
that
we
use
underneath
self-medicate.
You
can
actually
provide
a
flag
there
that
says:
hey,
don't
use
any
VM
at
all,
just
spin
up
kubernetes
in
containers
locally.
A
C
Yep,
so
so,
when
so
after
you've
cloned
it
and
you
verified
that
you
can
actually
see
the
lessons
that
you've
cloned
on
your
laptop
you're
going
to
want
to
open
up
an
issue
back
actually
back
at
the
original
enery
learning.
Any
labs
curriculum
repository
in
this
case,
one
of
actually
one
of
our
co-workers,
opened
up
a
an
issue
to
do
an
EVP
n
lesson
and
attained
it
curriculum,
which
is
what
your
is.
What
you
want
to
do
in
this
case,
and
here
you're
just
more
or
less
to
clear
your
intention
to
do.
C
A
A
In
anyways,
the
one
one
thing
to
note
is
the
the
curriculum
label
is
is
useful,
but
one
of
the
reasons
we
had
that
there
is
because
we
used
to,
for
those
that
have
been
around
for
a
little
bit,
the
the
lessons
used
to
be
in
the
antidote
repo
which
housed
a
lot
of
stuff,
which
is
why
you
see
the
curriculum
label
on
everything.
It
was
a
way
that
we,
it
was
a
way
that
we
were
able
to
keep
issues
about
the
curriculum,
separate
from
issues
about,
say
the
infrastructure
anyways.
Since
then,
we've
split
things
out.
A
C
C
At
that
point,
you're
gonna
go
through
the
process
which
I'm
not
going
to
lose.
It
detail,
hero
of
actually
iterating
over
building
your
lesson
iterating
over
and
refining
it,
and
then
at
some
point,
you're
gonna
be
happy
with
what
you
did,
in
which
case
you
can
do
a
pull
request.
Let
me
go
back
to
my
repository.
C
Which
I
have
nothing
here
to
actually
show,
but
that
that's
what
you're
gonna
do
you're
gonna
do
a
pull
request.
Here's
some
examples
of
some
pull
requests,
so
we'll
go
with
final
adjustments,
and
promotion
of
this
is
one
of
them.
So
Matt
made
some
changes
to
Jett
and
open
config
lessons
and
as
a
result
of
his
refinements,
he
was
based
on
that
commit.
There
was
five
commits.
C
There's
some
discussion
about
the
actual
lesson
here
and
then
you
know
the
whole
idea
here
is
once
you
open
the
pull
request
with
what
you're
wanting
to
contribute
there'll
be
some
kind
of
discussion
around
your
contribution,
both
from
you
know
from
various
people.
Here
we
have
three
or
four
different
people
chiming
in
on
on
this
lesson
and
you'll
continue
to
make
adjustments
etc,
and
then,
at
some
point
you
know
that
pull
requests
will
be
merged.
A
So
I'm
very
very
briefly:
could
you
go
back
to
the
NRI?
Labs
curriculum
cite
the
repo
rather
yeah.
So
if
you
actually
go
to
your
fork,
I'll
give
people
a
little
little
hint.
A
Sorry
I
have
to
watch
the
stream
to
see
your
screen
and
it's
like
five
seconds
too
late.
Go
to
yeah,
go
to
the
good
of
your
fork
for
the
repo,
that's
great
cool,
so
so
yeah.
So
basically
you
can
see
right
here
where
it
says
this
branch
is
for
commits
behind
NRA
learning
master.
That's
the
reason.
It
says
that
is
because,
as
I
mentioned
toad
when
he
forked
this,
it
was
probably
as
some
time
ago
either.
A
A
It
kind
of
depends
on
what
changed
he
might
be
able
to
continue
working
on
his
copy
and
not
affect
anything
if,
for
some
reason,
the
commits
that
were
applied
to
the
route,
repo
kind
of
overlap
with
the
ones
that
he
makes
and
his
branch
here
if
they
conflict
that
will
result
in
something
called
a
merge
conflict
which
sounds
scary.
But
we
have
ways
of
fixing
that
so
you
know
basically
just
try
your
best
to
keep
your
fork
up
to
date
and
there's
ways
to
do
that.
A
If
you,
if
you
just
read
through
how
to
use
git
the
main
the
main
the
reason
I
pulled,
this
up
is
because,
if
you
have
made
commits
toad,
hasn't
he's
just
he's
just
four
commits
behind,
but
it
might
also
say
four
commits
behind
and
say
maybe,
like
two
commits
ahead.
What
that
means
is
you
have
commits
in
your
in
your
local
fork
here
the
fork
that
you
made
you've
pushed
commits
here
that
the
root
the
root
repository,
the
fort
from
doesn't
have
and
the
reason
we
call
it.
A
A
pull
request
is
because
what
you're
doing
is
you're
requesting
that
the
upstream
repository
owner
pulls
the
changes
that
you've
made
in
your
fork
into
their
root
repository.
So
you're,
basically
saying
look
I
diverged
from
your
history
back.
You
know
two
commits
ago
and
I've
made
these
changes.
Can
you
make
these
changes
now
part
of
your
history?
That's
why
the
term
pull
request
exists
and
a
lot
of
other
sites,
like
git
lab,
for
instance,
use
similar
terminology.
They
use
the
term,
merge,
request,
kind
of
kind
of
the
same
thing.
A
It'll
also
pop
up
it.
You
can't
see
it
on
the
screen
right
now,
but
there
will
be
a
pop
up
near
the
top
of
the
screen.
It
says
recently
pushed
branches
and
it'll
have
a
big
old,
green
button
that
says
open
pull
request.
That's
also
a
very
useful
way
of
opening
a
pull
request.
I
find
that
that's
much
more
useful
to
open
a
pour
request
because
it
just
it
takes
you
right
where
you
need
to
go,
you
can
open
a
pull
request
by
going
to
the
pull
request,
tab
and
clicking.
A
You
know
new
pull
request,
but
this
I
find
what
I
just
said
to
be
a
lot
easier
to
just
open
it
right
after
you
push
and
by
the
way
you
don't
have
to
open
a
portal
quest
only
when
you're
ready
to
to
have
something
reviewed,
it's
totally
acceptable,
in
fact,
usually
preferred.
Certainly
within
the
realm
of
software
development.
I
know,
a
lot
of
teams
have
worked
this
way.
A
Just
opening
this,
you
can
see
what
I'm
working
on
it's
a
it's
a
manner
of
providing
visibility
into
where
you
work
and
it
and
it
helps
both
parties
to
it,
helps
you
know
the
reviewers
get
up
to
speed
with
what
they're
gonna
have
to
review
in
the
near
future.
Even
if
it's
not
right
now,
and
it
also
helps
the
person-
that's
creating
the
content,
because
it
gives
others
an
opportunity
to
say
hey
by
the
way.
Did
you
know
that
this
other
thing
exists?
You're,
you
know
you're,
writing
it
you're
right,
you're,
creating
a
lesson.
A
For
instance
you,
you
know
you
might
be
using
the
snippet,
the
snippet
buttons
for
for
the
for
your
lesson
guides
and
you
might
be
using
the
old
index
format
and
somebody
can
come
in
and
say
hey.
Did
you
know
that
you
don't
have
to
provide
that
anymore?
You
just
provide
the
keyword
this
and
it
does
it
for
you,
so
things
like
that.
It's
it's!
It's
totally!
Okay,
to
open
a
pull
request
at
any
time
just
be
be,
you
know,
be
explicit
and
letting
people
know
if
it's
ready
or
not
ready
to
be
reviewed
or
not.
C
A
The
main
site
miss
it's
it's
the
main
site,
but
just
with
PT
r
dot.
At
the
beginning,.
A
C
C
That
is
again
there
could
be
things
that
go
wonky
in
the
reason
why
we
have
PTR's,
because
there's
still
things
that
could
go
wonky
before
we
gets
pushed
out
and
PTR
is
a
mirror
of
the
actual
deployment
in
that
we
have
in
production
in
Google
Cloud.
But
you
know
this
is
stored.
The
last
gate,
if
you
will
to
make
sure
everything,
looks
good
in
that
it's
not
going
to
blow
up
plus
other
people
can,
you
know,
can
go
and
interact
with
your
lesson
and
give
feedback.
You
know
on
the
PTR
website,
yeah.
A
Yeah,
actually
that's
one
of
the.
What
that's
to
be
honest,
that's
one
of
the
easiest
way
sure
the
object
is
whenever
we're
gonna
be
doing
this
going
forward.
Now
that
we
have
our
community
site
up
and
running
anytime
we're
about
to
do
a
new
release.
What
we'll
do
is
I
have
a
few
days
ahead
of
time
at
the
very
least
a
few
days
ahead
of
time.
A
What
we'll
do
is
we'll
publish
a
post
there
in
the
community
site
that
says
hey
the
next
version
of
NRI
labs
has
been,
has
been
cut
and
we've
we've
we've
we've
made.
We
basically
put
it
onto
the
PTR
site,
meaning
the
PTR
site
is
now
running
the
specific
version
of
the
project
and
of
the
curriculum
that
we're
planning
to
push
into
production
in
a
few
days.
If
you
go
to
the
PTR
site
now,
it
should
look
exactly
like
what
the
main
site
will
look
like
in
a
few
days.
A
Can
you
please,
you
know,
go
through
and
run
some
lessons
and
just
provide
us
with
any
feedback
view
that
you
run
into
any
any
problems.
You
run
it
to.
Let
us
know
that's
one
of
the
easiest
ways
to
get
involved
in
the
project,
because
you
don't
need
to
know
how
anything
works.
You
just
need
to
be
able
to
use
the
site
and
that's
it
and
and
be
able
to
open
github
issues
to
let
us
know
about
problems,
that's
it
I.
C
A
This
is
pretty
informal.
I
think
it
would
be
good
to
have
like
a
like
a
you
know,
not
necessarily
like
scripted
like
robotic,
but
it'd
be
good
to
have
that
as
a
reference.
Not
a
lot
of
people
want,
especially
considering
you
know
it's
not
in
our
best
interest
to
spend
time
reinventing
like
github
documentation,
it's
good
to
just
be
able
to
focus
on
what
we
what
we
do,
uniquely
alright,
let's.
C
A
C
A
A
A
C
B
A
C
C
So
if
you're
just
joining
us,
because
I
see
somebody
had
just
joined
us,
Matt
and
I
are
about
to
talk
about
version
0.4
out
of
Oh,
which
is
coming
up.
It's
one
of
it's
a
major
step
that
we're
taking
to
his
version
1.0,
which
will
be
coming
soon.
This
quarter,
I,
think
and
Matt
is
currently
disconnecting
his
second
monitor
so
that
it
works
right.
C
A
A
What's
worse
is
that
there
are
like
eight
year
old
kids
that
make
three
million
dollars
a
year
doing
that
and
they
do
it
so
much
better
anyway,
so
so
yeah
as
Derek
was
saying,
0.4
natto
is
kind
of
the
next
big
thing.
There's
there's
actually
there's
actually
some
story
here,
we've
been
lately
thinking
about
so
in
the
background,
obviously
one
of
the
things
that
we
want
to
do
just
because
this
is
a
project
that's
near
and
dear
to
our
heart.
We
want
to.
A
A
We
need
the
project
to
do
when
it
gets
to
like
a
1
dot,
Oh
kind
of
thing
and
a
lot
of
those
concerns
are
about
features
and
functionality,
but
also
in
terms
of
like
scale,
even
security
to
a
degree,
there's
a
lot
of
things
that
need
to
be
considered,
and
so
what
we've
been
doing?
The
past
really
few
months
is
really
starting
to
tangibly
think
about
what
one
meadow
looks
like
and
I.
A
This
is
still
something
we're
working
on,
and
so
we
haven't
really
published
anything
there
yet
just
because
it's
still
so
much
in
flux,
but
0.4
Dino
is
the
first
main.
It's
I
mean,
if
you're
being
pedantic
about
it
in
cember
terminology,
it's
a
minor
release,
but
the
first
big
release
that
that
puts
us
on
the
path
to
one
dot
o
because
0
for
da
is
gonna
include
a
lot
of
features
that
are
pretty
significant,
one
of
which
is,
and
you
can
see
it.
A
A
Somehow
I
can't
remember
the
relationship
there,
but
they're
they're
very
closely
aligned
with
CNC
F,
which
is
you
know
the
the
folks
that
that
how's,
the
kubernetes
project
and
a
lot
of
other
cloud
native
kind
of
things
that
we
that
we
actually
use
within
the
project,
not
every
one
of
these
issues
in
the
plan
by
the
way.
If
you,
if
you
want
to
look
at
this,
you
can
look.
It's.
D
A
Learning
slash
project,
slash
9,
as
I
have
done,
with
every
single
release,
since
we
launched
in
October
of
2018,
every
single
release
gets
a
github
project.
So
if
you
have
any
doubts
or
questions
as
to
what's
being
worked
on,
this
is
the
place
to
go.
I
have
been
religious
about
making
sure
that
anything
is
in
here
a
if
only
for
my
own
sanity,
because
it
helps
keep
things
you
know
collected
for
myself,
but
also
its
public.
So
you
can
see
it
not.
A
Every
one
of
these
issues
is
groundbreaking
lead
if,
for
instance,
there's
always
gonna
be
some
bug,
fixes
and
small
feature
enhancements,
and
things
like
that.
There's
always
gonna
be
new
lessons
so
intermingled
with
the
plan.
You're
gonna
see
things
like.
You
know,
new
problems
with
existing
lessons
or
new
lessons
or
additions
to
lessons.
All
that's
still
gonna
be
in
play
here.
This
isn't
just
about
the
platform
itself,
but
this
is
there's
there's
also
big
features
like,
for
instance,
in
the
sy,
our
CTL
tool.
A
What
we
want
to
do
is
have
to
interact
with
for
building
a
new
lesson
so
that
you
don't
have
to
start
from
scratch
and
just
copy
somebody
else's
directory,
and
you
know
reverse
engineer
it
and
try
to
figure
out
how
to
get
your
lesson
working
we
want
to.
We
want
to
help
with
that.
We
want
to
help
make
that
a
little
better.
A
So
that's
one
of
the
things
we're
gonna
work
on
there's
other
things
like
you
know
being
able
to
like
click
a
button
in
the
web
UI
that
goes
straight
to
the
source
of
that
lesson
in
in
github,
I
think
that'd
be
pretty
cool.
A
lot
of
a
lot
of
like
statically
generated
websites
that
use
github
pages.
Have
that
I
think
we
can
say,
like
you
know,
view
the
source
for
this
in
github.
A
A
So,
there's
a
lot
of
stuff
like
that
in
this
lesson,
what
I'm
doing
or
at
the
moment
there
are
some
sort
of
quote
breaking
changes
to
syringe,
just
because
of
some
of
the
terminology
that
we're
switching
around.
You
know
what
I'm
gonna,
I'm
gonna
spoil
a
little
bit
of
the
plan.
I'm
not
gonna,
go
crazy
about
it,
but
one
of
the
things
one
of
the
things
that
we
we've
done
up
until
now
is
antidote,
as
a
project
has
been
pretty
centered
around
lesson
and
and
that's
for
good
reason.
A
You
know
lessons
are
a
big
part
of
what
we've
done.
You
know
and
by
lessons
I
mean
the
when
you
go
to
when
you
go
to
a
page
and
you
learn
something
ya
know
Jinja
or
j
snap,
your
nape
all
like
those.
Those
are
all
individual
lessons
that
you
learn
something
about,
and
certainly
we're
gonna
continue
using
that
that's
a
that's
like
the
the
keystone
for
a
lot
of
what
we're
building.
A
But
what
we're
finding
is
that
if
they're,
not
they're,
not
they're,
not
as
compelling
as
they
could
be
just
but
on
their
own,
what
we?
What
we've?
What
we've
thought
about
is
adding
other
things
into
the
project
that
helps
either
people
find
content
more
easily,
for
instance,
or
maybe,
or
maybe
helping
people.
You
know
sort
of
work
their
way
through
a
set
of
lessons.
Maybe
there
is
a
bunch
of
lessons
that
sort
of
have
something
in
common
with
each
other,
and
you
just
want
to
be
able
to
find
those
lessons
more
quickly.
A
There
might
be
things
like
you
know
like
the
interactive
labs
that
provide.
You
know
the
lab
experience
that
a
lesson
provides
is
cool,
but
maybe
you
want
to
be
able
to
do
some
really
quick,
like
knowledge
based
learning,
so
maybe
having
something
like
a
multiple-choice
quiz
in
conjunction
with
a
practical
lab.
You
know,
instance,
maybe
those
two
things
together
will
really
really
help
enhance
the
learning
experience.
So
we
there's
there's
just
a
whole
bunch
of
resource
types,
different
resource
types.
A
In
addition
to
simply
lessons
that
we've
thought
of
and
what
we're
doing
is
we're
centering
everything
around
this
new
model.
That's
correct
eccentric.
So
when
you're,
when
you're
looking
at
say
the
NRI
Labs
curriculum
that
repository
and
github,
we
used
that
terminology.
When
we
moved
it
very
intentionally,
because
we
sort
of
saw
the
writing
on
the
wall
and
we
knew
that
we
were
gonna
have
to
Center
everything
around
a
curriculum.
A
So
what
when
you,
when
you
stand
up,
for
instance,
your
own
version
of
antidote
or
when
we
stand
it
up
in
the
cloud
in
production
for
the
main
energy
lab
site,
what
we're
doing
is
we're
centering
everything
around
a
curriculum
in
that
NRA
labs
curriculum
repo
is
the
main
curriculum
for
us.
It's
not.
Obviously
it's
not
the
only
curriculum
that
you
can
use.
A
You
can
create
your
own,
but
it's
the
one
that
we're
creating
and
we're
we're
collaborating
on
for
the
for
the
community
and
everything
is
nested
as
sort
of
children
resources
underneath
this
curriculum
and
so
you'll
see
in
the
in
the
curriculum
in
that
drain,
that
repo
you'll
see
a
directory.
That
says
lessons,
obviously
we're
still.
We
still
have
lessons,
that's
like
the
main
thing
in
and
re
labs
and
in
antidote,
but
we
have
other
resource
types
that
we're
thinking.
For
instance,
collections.
A
That's
gonna
be
something
that
we're
gonna
be
coming
out
with
in
Cortado
and
I
sort
of
breezed
over
it
in
the
last
screen,
but
it's
there
in
the
plan.
That's
one
way
that
we're
thinking
about
grouping
certain
lessons
together,
maybe
not
necessarily
by
category
but
maybe
perhaps
by
lesson
author,
for
instance,
you
know,
maybe
maybe
maybe
a
vault.
The
cellar
comes
in
and
says,
look
I.
A
You
know,
I
want
to
contribute
a
lot
of
a
lot
of
our
knowledge
to
the
community,
but
I'd
like
for
people
to
understand
where,
where
all
of
that
came
from,
and
maybe
get
some
credit
for
that
and
and
for
people
to
learn,
you
know
where
they
can
find
out
more
some
of
this
information.
So
we've
thought
about
this,
and
one
of
the
things
we're
gonna
be
doing
is
introducing
a
concept
called
collections
that
group
those
kind
of
lessons
together.
It's
not
it's,
not
a
it's.
A
Not
a
recategorize
ation
will
still
have
categories
for
things
like
you
know
what
kind
of
tools
or
fundamentals
or
workflows
are
being
discussed.
That's
still
going
to
exist.
This
is
more
like
another
axis
of
categorization,
so
more
on
that
in
in
the
near
future,
we'll
show
you
that
will
say
that
feature
in
action
at
near
near
the
end
of
the
ODOT
Fordo
cycle.
Another
thing
is,
you
know:
quizzes
I
mention
this
before
multiple
choice,
questions
that
might
be
pretty
cool
to
a
couple
with
you
know
a
set
of
lessons
where
you
know.
A
Maybe
the
lesson
does
like
a
practical
walkthrough
of
a
concept,
but
before
you
get
there,
maybe
you
want
to
take
a
quiz
seeing
where
your
knowledge
is
so
you
can
see
where,
like
maybe
you
need
to
fill
in
some
gaps
or
maybe
you're
rolling
out
a
curriculum
to
somebody
or
a
group
of
people,
and
you
want
them
to
you
want
that.
You
want
to
quote
like
certify
that
they
know
what
they're
doing
you
can
you
can
sort
of
join
quizzes
with
the
lessons
for
a
full
like
knowledge,
plus
interactive
experience
that
might
be
pretty
cool.
A
There's
also
courses
we're
thinking
about
creating,
for
instance,
you
know
it's
nice,
that
these
lessons
are
grouped
in
a
sort
of
a
technical
way
like
what
what
lessons
are
about
tools
or
fundamentals
or
whatnot,
but
there
might
be
there
might
be
another
way
of
thinking
about
it.
For
instance,
I
want
to
learn.
Let's
say
I
want
to
learn
everything
there
is
to
know
about
network
testing.
A
I
want
to
know
I
want
to
know,
I
want
to
know
everything
that
you
have
to
offer
in
in
the
energy
lab
curriculum
that
has
to
do
with
network
testing
and
I
want
to
be.
You
know,
quote
certified
we'll
use
that
term
for
now
loosely
on
network
testing,
I've
seen
I've
seen
everything
that
energy
Labs
offers.
What
we
can
do
is
we
can
create
a
course
that
sort
of
navigates
through
all
of
the
other
stuff
and
and
and
just
focuses
only
on
the
lessons
and
the
quizzes
that
are
relevant
to
accomplishing
that
end
goal.
A
So
we
want
to
provide
some
guidance
through
the
through
the
noise
so
to
speak
and
and
if
you
only
want
to
focus
on
one
specific
outcome,
we'll
help
we'll
help
guide
you
through
that
and
then
finally
there's
another
resource
type
or
thinking
about,
and
so
for
instance,
if
you've
gone
through
a
course,
for
instance,
let's
say
you
went
through
the
network
testing
course
it'd
be
nice.
If
you
could
you,
you
could
point
to
either
sort
of
a
badge
or
some
kind
of
indication
that
you've
done
that
and
we're
gonna.
A
A
They
can
go
to
the
community
site
and
search
for
people
with
that
sort
of
badge
or
that
award,
and
we
think
that
that's
gonna
be
really
really
useful
in
helping
people
sort
of
understand
each
other
specialties,
because
this
is
a
very
diverse
field.
It's
becoming
a
kind
of
a
complicated
set
of
skills.
So
it's
nice
to
have
some
some
some
guidance
around.
You
know
who's.
Who
knows
what?
So,
anyway,
that's
a
big
change.
This
isn't
gonna
happen,
Oh,
tough,
no,
as
I
mentioned.
Really.
A
Yeah
and
and
I
the
the
one
no
plan
isn't
quite
yet
because
we
haven't
finished
it,
but
the
ODA
four
plan
is
obviously
it's
in
the
github
project
there.
So
please
feel
free
to
look
at
that
if
you
have
any
questions
just
reach
out
either
via
Twitter
the
community
site.
If
you
don't
know
about
that,
this
is
what
I
was
mentioning
earlier:
community
dot
network
reliability,
not
engineering,
it's
free
to
sign
up,
so
just
sign
up
for
an
account
you
can.
You
can
go
to
any
one
of
these
we're
playing
with
the
categories
as
well.
C
B
A
That'd
be
great,
this
is
pretty
wet
way
better.
Honestly,
the
stream
went
way
better
than
the
lab
and
half
of
the
half
of
the
stream
was
over
here
about
whiteboarding
were
actually
was
over
there.
The
whiteboard
was
on
my
futon
and
and
my
I
had
used.
I
had
I,
don't
have
a
good
like
distance
mic,
so
I
had
to
use
my
webcam
mic
and
it
was
horrible
horrible.
C
C
I,
don't
do
we
have
any
questions.
Yeah
we'll
give
everyone
a
second
here
to
ask
questions.
Now,
just
go
over
some,
what
we
say
every
time:
I'm
Derek
winkworth,
you
can
follow
me
at
cloud.
Toed
Cielo,
you
DTO
ad,
on
Twitter,
and
this
is
matt
oswald.
You
can
follow
him
at
near
Dhin,
m,
IE,
r
di
n
on
twitter.
You
can
also
follow
any
labs
on
twitter
at
NRI
labs.
Please
follow
all
of
those
things.
Please
join.
If
you
go
to
our.
C
So
please
join
those
and
participate
in
the
in
the
discussion.
If
you
have
any
questions,
of
course,
you
can
ask
on
discourse
or
discord
or
shoot
Matt
or
I,
or
the
energy
labs
account
on
Twitter
a
message:
I,
don't
think
we
have
any
questions
so
I
think
we'll
wrap
it
up.
Go
okay!
So
next
time,
though,
we
are
getting
on
this,
we're
getting
on
the
horn
at
like
20
minutes
out,
resolve
all
audio
and
video
issues.
20
minutes
out
from
like
4:00
a.m.
A
C
Be
I
don't
like
to
rush
I
like
to
be
at
the
airport
with
enough
time
to
sit
down
and
relax
before
we
get
on
the
plane,
because
I
dislike
flying
immensely
and
I
don't
want
to
be
rushed
into
the
airport
trying
to
trying
to
I
like
to
stroll
casually.
You
know
down
the
terminal
hallway
and
they
have
a
have
a
sit
and
think-
and
maybe
you
know,
eat
a
breakfast
sandwich
before
I
before
I
get
on
my
plane.
I.