►
From YouTube: Community Stream #5 - v0.3.1, Collections, and Community
Description
Broadcasted live on Twitch -- Watch live at https://www.twitch.tv/nrelabs
A
A
B
Well,
you
and
I
have
talked
about
the
idea
of
doing
something
funny
for
April
1st
I
did
not
get
around
to
it,
because
my
ambition
was
fairly
high.
I
have
a
really
good
idea
for
something
that
I
want
to
do
with
respect
to
NRI
labs,
but
I'm
gonna
have
to
save
it
until
next
year,
because
it
is
a
it
is
a
large
undertaking.
So
it's
gonna
seem
like
we
run.
Were
that
we're
not
festive,
but
the
reality
is
that
we
just
got
too
busy
yeah.
We
wish
we
we
want.
A
B
B
B
A
B
A
B
A
Me
photos,
like
you
know
like,
like
legendary
places.
A
tree
apparently
were
Zeus
was
either
born
or
I.
Don't
know,
Wow
was
awesome,
yeah,
something
like
that.
Okay,
oh
no,
he
was
born
in
the
cave,
that's
right
and
under
the
trees,
I
don't
know
something
he
had.
He
had
had
relations
with
another
another
God
under
a
tree
somewhere,
and
she
sent
me
that
message
like
I
want
to
be
there
eating
that
cheese.
Reading
going
around
Crete
creative.
It's.
B
For
those
that
don't
know,
Lisa
is
a
colleague
of
ours.
She
but
she's,
well-known
in
the
networking
community
short
for
a
long
time
for
brocade
a
while
back
in
the
melodic
sound
ation.
Now
juniper
she's
just
awesome
like
she
just
works
her
butt
off
for
this
kind
of
stuff
community
stuff,
which
is
very
helpful.
Yeah
her
and
Vicky
pursuer.
A
Are
are
we
have
my
goodness,
we
I
think
we
would
be
lost
without
the
two
of
them
they've
they're
there
I'm
the
I'm
supposed
to
be
the
community
in
the
manager,
but
I
think
the
way
this
is
evolving.
I'm
gonna
I'm
going
to
be
a
puppet
and
they're
going
to
be
the
community
managers,
but
it
is,
this
is
all
done
which
is
fine.
I
can
you
know,
be
a
puppet
with
strings
that
was
my
marionette
impression.
B
A
B
A
B
Yeah
there's
a
few
things:
let's
talk
about.
First,
the
the
new
release
which
I
Iran
the
release
workflow
late
last
week,
so
it's
been
out
for
a
little
bit,
but
we
only
what
we
usually
do
is
we
is
we
run
through
I.
Have
a
I
have
a
stack
storm
workflow
that
goes
through,
like
tagging,
all
the
repos,
and
all
that
just
to
make
our
release
happen
and
compiling
syringe
and
all
of
the
stuff
that's
necessary
to
make
a
release
happen.
What
I
usually
do
is
I.
B
Do
that,
like
a
few
days
early,
so
I'll
cut
the
release
and
then
I'll
immediately
deploy
that
to
our
PTR
site,
which
is
basically
like
a
test
site.
It's
meant
to
be
like
a
staging
ground
for
for
production,
so,
rather
than
push
things
immediately
to
production,
we
just
push
it
to
this
PTR
site
first
and
then
that
way
we
have
the
ability
to
do
some
last
minute,
like
checks
just
to
go
over.
Some
lessons
make
sure
everything
still
works.
Funston.
B
We
do
have
a
good
amount
of
automated
testing,
but
it's
it's
we're
still
working
on
it,
so
it's
good
to
have
the
ability
to
to
run
through.
You
know
some
lessons
before
you
know
pushing
out
to
the
main
site
in
that
way,
the
user
experience
that
makes
it
out
to
the
to
the
just
regular
learners
is
as
good
as
it
can
be.
So
anyway,
the
the
release
has
been
out
for
a
few
days,
but
just
last
night,
or
yesterday
morning
or
two
nights
ago,
Saturday
Saturday
night
I
deployed
it
to
production.
B
B
Hopefully,
I'll
be
ready
to
talk
about
it,
not
maybe
not
on
the
next
livestream,
but
on
the
one
after
that,
for
what
one
dunno
is
eventually
going
to
look
like
and
so
I
have
an
idea
of
someone
like
the
really
big
features
that
need
to
be
worked
on,
and
you
know
they're.
Obviously
there
will
be
little
things
in
in
various
releases
as
well,
but
some
of
the
big
things
like
you
know
the
upcoming
feature
of
doing
collections.
That's
that's
a
pretty
important
one,
we'll
be
doing
pretty
soon.
B
A
B
B
Could
just
show
up
to
one
of
the
streams
with
it
like
braided,
like
a
Viking
and
and
just
have
the
hat
on
that'd,
be
kind
of
cool
I.
Don't
have
the
facial
hair
for
that.
If
I
tried
to
grow
my
facial
hair
even
close
to
that
like
I've,
recently
trimmed
it,
but
if
but
if
I
try
to
grow
it
out
it
just
kind
of
like
curls
in
on
itself,
it's
not
curly
but
I
feel
like
it
just
like
re-enters
my
face,
so
it
doesn't
grow
like
ever.
It
just
becomes
like
it
just
becomes
matted.
A
A
My
plan,
but
concurrent
to
this,
we
are
working
on
less
less
code,
related
things
and
more
we're
working
again
with
Vicky
and
Lisa,
and
we're
gonna
be
producing
all
of
the
requisites
sort
of
collateral
that
goes
with
an
open
source
community
things
like
a
governance,
stock
and
code
of
conduct
and
all
that
stuff
and
I
was
hoping.
We'd
have
that
around
100,
but
it
doesn't
sound.
Like
that's
gonna
happen.
It'd
take
a
little
while
to
get
all
that
stuff
yeah
vetted,
but
you.
B
Want
to
talk
about
a
little
bit
just
to
let
people
know
like
what
you
can
it
back,
because
it
I
think
from
one
of
the
things
that
Vicky
said
when
we
were
talking
to
her
on
the
call
a
few
days
ago
was
probably
probably
what
other
people
are.
Thinking
is
like
why
you
know
this
is
such
a
small
project
still
like?
Why
are
we
thinking
about
governance
like
what
some
of
the
driving
horses
behind
that
yeah.
A
Sure
well
part
of
the
well.
The
I
mean
a
big
reason.
Is
it's
good,
it's
great
to
have
individual
contributors,
but
it's
unfolding
with
enemy
labs
like
it
does
with
many
open
source
projects
that
the
contributors
will
are
largely
working
for
organizations
that
would
that
would
like
to
leverage
you
know
the
platform
they
would
like
to
gain
value
out
of
the
platform
they're
actually
going
to
be
having
at
least
part
time,
some
of
their
own
people,
you
know,
could
contribute
in
a
relapse
which
you
know
that
that's
very
common
for
open
source
communities.
A
A
So
with
that
kind
we
have
a
lot
of
interest
actually
from
a
whole
whole
variety
of
people
from
sort
of
hubs
for
network
engineers
like
I,
don't
I,
think
I,
don't
think
I
want
to
mention
any
names
yet,
but
you
know
we
have
a
couple
well-known
sites
where
people
get
a
lot
of
their
information
about.
What's
going
on
the
network
engineering
community
who
are
wanting
to
contribute
and
then
a
variety
of
organizations,
both
all
kinds
of
engine
would
actually
tech
companies
and
then,
as
well
as
like
tech
practice
companies
that
come.
A
You
know,
people
who
provide
services
and
stuff
like
that
to
to
customers
that
aren't,
strictly
speaking,
you
know
a
Silicon
Valley
company
and
they
and
they've
expressed
like
a
like
a
very
strong
interest.
It's
it's
exciting
for
both
of
us
Matt's
been
and
some
of
those
meetings
to
hear
the
feedback
we're
getting
they.
They
really
want.
You
know
to
to
ramp
it
up
and
and
and
start
putting
lessons
in
here
for
all
different
kinds
of
lessons.
But
in
order
to
do
that,
we
sort
of
have
to
have
this.
You
you
need,
you
need.
A
You
know
contributors
guides
and
and
governance
Doc's
like
what
does
the
contribution
model
look
like,
and
you
know
what
what
are
the
do's,
then?
What
are
the
don'ts?
That
kind
of
thing
from
you
know
what
what
format
should
these
files
be
and
stuff
like
that?
You
know
that's
a
great
idea.
Matt
actually
come
to
think
of
it.
You
might
want
to
put
something
like
some
kind
of
vim
configuration
file
out
there.
A
B
Working
on
I
have
been
working
on
like
a
spellcheck
kind
of
thing.
For
the
lesson
curriculum
just
to
add
my
the
developer
portion
of
my
brain
is
like
anything
I
could
put
into
the
CI
pipeline.
I
will
yeah
so
the
reviews,
so
the
reviews
take
less
time.
That's
the
whole
point
right.
Lay
up
the
reason
we
have
like
peph
eight
linters
is
not
is
so
that
when
you
review
python
code,
you
don't
have
to
like
be
like
well,
this
needs
to
be
R
is
over
sixty
characters
and
we
have
to
respect
the
you
know.
A
A
B
B
A
Pack,
your
ferret
Thank
You,
PAC
Fair
for
for
staying.
He
says
many
of
us
had
Network
to
code,
would
love
to
know
how
to
contribute
and
what
curriculum
would
be
appropriate.
Yeah
dad
is
actually
yeah.
That's
a
good
point.
What
what
do
you
contribute?
Well,
you
know,
let's
we'll
cover
that
a
little
bit
after
we
get
through
some
of
this
here.
What
you
can
do
right
now,
if
you're
interested
in
learning,
how
to
contribute
network
to
code
by
the
way
for
those
of
you
that
are
watching.
A
Is
it's
Google
it
it's
it's
an
awesome
community
of
people
who
are
networkers,
who
are
trying
to
learn
how
to
automate
or
who
do
automate
and
they're,
trying
to
teach
other
people
how
to
automate
that
there
are
tips
and
tricks
and
tools,
and
so
on
check
them
out
and
yeah
I
I
definitely
would
love
to
see
some
contributions
from
that
community.
I
know,
I-I've
seen
a
lot
of
cool
things
come
out
on
my
Twitter
feed
different
things
projects
people
have
worked
on
and
and
yeah.
That
would
be
awesome.
A
B
Like
the
whole
reason,
we
we
built
this
platform
wasn't
to
be
rah-rah.
Us
like
there
are
a
bunch
of
lessons
that
we
explicitly
didn't
write
because
we
wanted
to
provide
space
for
people
that
we
know
could
could
provide
them
like,
like
I,
wrote
a
little
bit
of
a
napalm
lesson,
but
it
could
use
some
work
and
then,
like
the
whole,
nor
near
thing
that
David
Grosso,
also
created
and
and
a
few
other
folks,
Patrick
I,
believe
ogen.
B
B
So
I'll
admit
that
that's
part
of
it,
but
like
that's,
not
the
only
reason
like
there's
all
kinds
of
content,
we've
explicitly
said:
no
we're
not
gonna
write
that
we're
gonna
we're
gonna,
we're
gonna,
do
our
we're
gonna,
do
the
hard
work
of
making
this
community
project
first
and
foremost,
and
and
one
of
those
things
is
like
the
team
at
network
to
code.
They
they
they
literally
their
whole
business,
is
predicated
on
helping
customers
adopt
automation,
so
they
have
the
expertise.
B
We
know
they
have
the
expertise
and
so
like
the
work
that
we're
doing
right
now
is
aimed
at
making
it
more
accessible
for
people
to
share
their
knowledge
and
share
their
expertise.
We,
this
would
not
be
an
interesting
site
if
it
was
just
a
here's,
a
bunch
of
automation,
lessons
that
Matt
and
Derek
created,
because
they
are
awesome.
That
would
not
be
interesting.
Yeah.
A
B
Of
my
effort
is
these
days,
especially,
is
going
into
how
can
I
make
it
as
easy
as
possible
for
others
to
contribute
regardless
of
company?
I
think
this
goes
back
to
the
governance
discussion
that
we're
talking
about
earlier,
one
of
the
things
that
we
want
to
do
when
we
create
these.
These
government
governance
Docs
is
like
what
is
it
that
every
lab
stands
for
or
the
antidote
project?
What
does
it
stand
for
and
I
think
one
of
the
things
is
like?
B
A
Yeah,
that's
yeah,
so
I
hope
that
I
hope
that
answers.
Oh
well,
we'll
talk
about
that.
We'll
talk
about
what
to
contribute
a
little
bit,
let's
but
but
yeah.
So
we
are
working
on
that.
Like
the
governance,
the
code
of
conduct,
there
was
a
couple
things.
We
even
had
some
interest
from
a
couple
of
parties
about
co-sponsoring,
which
is
which
is
really
awesome-
that
that's
really
awesome.
But
you
know
that's
this
whole
separate
document
right
and
how
that's
structured
and
made,
and
everything
else
is
that
stuff
always
takes
a
long
time
to
iron
out
yeah.
A
B
So
yeah
0.3
that
one
was
real
late
last
week.
It's
live
now
so
feel
free
to
test
the
site
there.
There
are
a
few
interesting
changes.
The
one
you'll
probably
notice
above
all
of
them,
is
that
the
navbar
on
the
top
has
changed
they're
using
icons
instead
of
just
texts.
Like
click
me
kind
of
thing,
so
it
looks.
A
little
better
looks
a
little
sleeker.
B
Mostly
I
will
say
like
if
I
were
to
think
of
all
the
changes.
I
was
a
project.
The
vast
majority
of
the
changes
are
actually
on
the
syringe
side,
and
most
of
them
are
bug,
fixes
and
kind
of
performance
things.
So
this
is
again
I'm
trying
to
save
a
lot
of
the
really
big
features,
for
you
know
major,
or
at
least
like
according
December,
like
minor
versions,
so
you're
not
four
will
be
the
next
like
big
version
yeah.
B
So
this
one,
this
one
is
a
little
bit
on
the
like,
not
necessarily
underwhelming
stuff,
we're
good
fixes,
but
not
a
lot
of
like
big
features
in
this
version.
The
one
thing
I
do
want
to
call
attention
to
is
is
because
we
well
we
currently.
What
we're
currently
doing
is
we're.
Actually,
when
we
do
releases,
we
release
the
curriculum
for
energy
labs.
In
the
same,
we
keep
them
and
we
keep
that
in
lockstep
with
the
version
of
the
platform
itself.
B
One
of
the
things
they'll
talk
about
here
in
a
little
bit
is
a
separation
of
repositories
that
makes
it
so
that
we
don't
have
to
do
that.
We're
gonna
still
do
that
for
a
little
bit,
but
I
want
to
be
I
want
to
I
want
to
run
this
a
little
bit
more
clearly
about
the
difference
between
NRA
labs,
the
curriculum
and
antidote.
The
platform
we're
going
to
be
making
sure
that
those
are
the
difference
between
those
things
is
a
lot
more
clear
going
forward.
B
But
the
big
thing
in
this
release
is
like
I
said
every
time
we
we
do
a
release.
We
we
also
do
a
release
in
the
same
way
of
curriculum,
and
we
have
a
new
lesson
in
this
version
contributed
by
David
G,
who
you
saw
in
the
last
live
stream,
so
everything
you
saw
in
the
last
live
stream
is
now
live.
If
you
didn't
look
at
the
last,
live
stream,
I
encourage
you
to
go
back
and
look
at
it,
but
a
quick
synopsis.
B
Basically,
it's
an
introduction
to
terraform
and
terraform
is
a
really
cool,
open
source
tool
that
allows
you
to
make
to
manage
infrastructure
as
code.
In
a
very
declarative
way,
if
you
contrast
that
to
something
like
an
ansible
or
even
like
a
Python
script,
those
those
tools
are
useful,
but
they
they're
very
much
like
a
you
know.
Do
this.
Do
that
it's
very
algorithmic
thinking
or
me
what
that
means
is
like
you
have
to.
Actually
you
have
to
properly
like
enunciate
the
steps
of
what
is
required
to
it.
To
accomplish
a
task.
B
Terraform
is
much
more
declarative.
I
want
this
to
exist,
I,
don't
care
how
you
do
it
just
I
want
this
to
exist,
and-
and
so
it's
really
cool
if
you're
thinking
about
things
like
cloud
resources
like
I
need
these
three
VMs
and
they
need
to
be
running
this
image.
They
need
to
be
networked
this
way
and
they
need
to
be
connected
to
this
firewall.
B
So
that's
life
I
encourage
you
to
look
at
it.
It's
live
now.
I
can
remember
the
lesson
ID,
but
if
you
go
to
the,
if
you
go
to
the
advisor
it
just
typed
terraform
a
little
pop-up.
That
is
by
far
the
big
thing
for
this
release.
It
one
more
thing:
I
want
to
talk
about
on
the
curriculum
side
of
things.
There
were
actually
three
lessons
two
plans
to
go,
live
on
this
release.
B
So
what
we're
hoping
to
do
is
figure
that
out
in
the
next
like
week
and
then
follow
up
this
release
with
another
release
like
again
within
like
a
week
like
that's
the
goal
at
most
two
weeks,
so
this
isn't
gonna
be
like
another
months
between
releases,
because
the
content
is
there.
Those
two
lessons
are
finished:
there
they're
ready
to
go.
It's
just.
We
need
to
make
make
sure
that
the
image
that
they
use
for
their
for
their
lesson
is
is
as
functional
as
it
needs,
but
I
don't
expect
that
that's
gonna
take
a
long
time.
B
A
B
You
want
it
to
be
made
known
to
the
world,
so
you
want
to
create
a
new
lesson.
That's
totally
awesome.
We
appreciate
that
that's
cool,
but
that's
not
the
only
way
you
can
contribute
you
can
and
and
should
consider
contributing
new
labs
or
even
editing
existing
lessons
for
existing
content.
So
the
content,
that's
there.
You
shouldn't
view
that,
as
like
finished,
especially
the
lessons
that
I
created
initially,
you
know
before
launch
because
mostly
I
created
those
is
like
a
proof
of
concept.
B
So
there
are
plenty
of
places
in
existing
content
that
could
use
either
additional
labs
or
just
simple
edits,
all
kinds
of
stuff.
Don't
view
the
existing
curriculum
is
set
in
stone
cuz,
it's
totally
not.
It
is
as
contributed
as
anything
else
as
new
content
is
so
just
I
just
want
to
say
that
so
that
people
feel
don't
feel
like
they
have
to
like
come
to
the
table
with
something
groundbreaking
and
new.
In
order
to
contribute
to
this
thing,
there's
there's
there's
all
kinds
of
things
you
can
get.
You.
A
Know
well
so
we'll
talk
about
that
right
now.
Actually,
if
you
go,
if
you
go
to
the
website
and
you'll,
see
that
there's
like
a
little
there's
like
a
lesson
on
yeah
mole
and
it
talks
about
gamma
lists
and
if
you're
familiar
with
llamó,
you
know
that
there's
there's
other
things
in
yeah
all
right,
there's
more
there's
other!
You
know,
there's
like
dictionaries
in
UML.
If
you
will
and
other
things
and
will
actually
besides
and
you
you
could
be
writing.
You
could
write
a
lesson
on
any
of
those
things
in
yeah
mole.
A
A
lab
actually
excuse
me,
I'm
and
and
add
it
to
the
existing
lesson
on
yeah
mole
right,
there's
like
the
first
ones
on
list.
The
second
one
is
on
whatever
and
let's
say,
you're
contributing
the
third
one.
You
can
add
additional.
You
can
add
additional
labs
to
existing
lessons.
That's
a
in
fact!
That's
a
great
bite-size
way
to
contribute
your
first
time
around
I
would
I
would
recommend
that
is
instead
of
making
a
whole
left
like
a
lesson.
Is
it's
like
a
whole
new
topic?
B
A
So
what's
appropriate
for
contributions,
though
in
general.
Well,
you
know,
following
what
I
just
said,
anything
that's
generally
consumable
by
everybody.
You
know
lessons
on
Yemen
lessons
on
you
know
and
literally
anything
that
a
network
engineer
would
commonly
encounter
if
they're
automating
things
in
it
and
it
doesn't
have
to
be
restricted
to
anything
juniper
related
right.
It
We
certainly
have
lessons
on
Juno's
related
to
automation
tools,
but
if
you're
doing
something
awesome
with
cumulus
or
or
literally
anything
Aristo,
who
knows
just
you,
you
know
feel
free
to.
A
If
what
you're
doing
is
something
that
someone
else
could
learn
and
apply
to
their
environment.
You
know
by
all
means
you
can
you
can
contribute
that
you
can
literally
anything
to
do
with
network.
Automation
is
something
you
can,
you
can
contribute
and
it
and
it
again
it
doesn't
have
to
be
specifically
about
something
network
related.
It
can
also
be
you
know.
Foundational
sort
of
topics
like
like
I
said
ya,
know
and
and
so
on,
that
are
obviously
widely
applicable
to
things
not
in
networking
butter,
which
you'll
run
across
a
lot
inside
of
networking
tools.
A
A
B
That's
perfect,
yeah,
I
I,
just
that's
been
on
my
mind
lately
is
is
no,
but
nobody
has
said
anything
explicitly
to
me,
but
every
time
I
see
a
contribution.
It's
it's
in
the
form
of
a
new
lesson
which
again
totally
fine
I,
just
want
to
make
sure
that
we
are
being
as
clear
as
possible.
That's
not
by
far
that's
not
the
only
way
ya
contribute.
It
is
and.
A
It
is
actually
sort
of
suboptimal
a
method
of
contributing,
because
a
whole
lesson
with
multiple
labs
is
actually
can
be,
is
a
lot
more
work
than
just
adding
one
little
lab
to
an
existing
lesson
on
a
smaller
topic.
So
if
sure,
if
you
are,
should
be
the
first
time,
I
would
recommend
doing
it
that
way.
A
Okay,
so
you
could
also
contribute
by
the
way
to
the
to
the
platform
itself,
antidote
and
there's.
You
know
Matt's
about
to
go
into
what's
new
in
the
in
the
new
release.
That's
not
content
related
for
the
in
a
new
platform,
but
if
you're,
if
you
already
have
some
coding
chops
and
there's
you
know,
there's
there,
there
are
there's
issues
and
bugs
that
exists.
Now
that
you
could
pick
up
in
and
you
know
and
fix,
and
and
then
you
know,
start
getting
your
feet
wet
and
how
the
actual
platform
works.
A
That
you
know
please
do
if,
if
that's
something
you're
inclined
to
do,
there's
also
documentation
that
that's
and
the
web
front-end
that's
out
there
that
you
know
if
you
have,
if
you've
done
some
JavaScript
things,
I,
don't
see,
assess
things,
I,
don't
know
anything
about
the
web.
I
try
I
extract
every
time.
I
have
a
project
where
that
exists.
I
have
to
relearn
it
from
scratch,
because
I
jettison
that
from
my
brain
as
quickly
as
possible,
but
there's
there's
a
web
front-end
piece
and
there's
and
there's
is
it?
What
read
the
docs?
A
B
Yeah
well
I
mean
it
like
I
was
kind
of
what
I
was
saying,
there's
in
in
the
in
in
this
for
simple
fixes
that
can
outline
them
a
little
bit
like
I
said
the
biggest.
The
biggest
change
you'll,
probably
notice
is
on
the
front
end.
The
web
front
end.
There
was
a
change
to
to
convert
the
links
on
the
top
navbar
to
font
awesome
icons.
So
it
looks
a
little
better,
there's,
also
a
link
on
by
the
way
on
the
main
site
to
this
to
our
twitch
or
not
twitch.
B
Well,
there
is
twitch
as
well,
but
there's
also
a
link
to
our
discord
chat,
which
is
where
we're
doing
a
lot
of
the
you
know
community
folks
chatting
about
issues
and
things
like
that.
That's
what
we're
moving
towards
that's
like
the
most,
that's,
probably
the
most
visible
change.
There
were
some
things
on
the
on
the
on
the
back
end
so
syringes
these
sort
of
the
orchestrator
on
the
back
end
in
this
release,
I
on
a
lot
of
a
lot
of
you
know,
adding
adding
long
needed
like
testing
like
unit
tests
for
syringe.
B
You
know
some
some
minor
bug
fixes
there
was.
There
was
also
some
some
changes
made
to
the
way
that
we
could
figure
network
devices
in
syringe.
So
it
used
to
be
that
what
we
would
do
in
syringe
is
whenever
you
went
to
a
new
lab
inside
of
a
lesson,
so
you
go
for
like
lab
1
to
lab
two.
What
it
would
do
is
it'll
spit
up
some
containers
that
run
napalm
directly
so
literally
like
the
napalm
CLI
napalm
space
host
equals
IP
address
and
username
and
password
that
kind
of
stuff.
B
We've
changed
that
to
actually
we
we
created
a
new
container,
that's
called
configurator
and
it
still
runs
napalm
because
we
want
to
make
sure
we
continue
to
use
napalm
so
that
we
can
configure
any
vendor
network
device,
not
just
Juno's,
but
you
know
iOS
or
US,
or
things
like
that.
So
that's
that's
not
changed,
but
instead
of
running
the
napalm
CLI,
what
we're
doing
is
we're
running
Python
script.
B
This
actually
is
is
in
support
of
some
of
the
image
work
that
I
was
talking
about
earlier,
that's
necessary
for
the
jet
and
the
open
config
lesson.
The
new
image
for
VQ
effects,
actually,
doesn't
you
the
current
the
current
image
that
we
that
we've
been
using
in
most
lessons
uses
Matt
to
expose
the
management
IP
address
to
the
outside
world?
Pretty
common
example:
cuz
it's
running
Cleo
is
a
VM
within
the
container.
So
what
it
does
is
it
says?
B
Otherwise,
it
won't
work
because
the
the
way
that
the
container
networking
works
is
you
have
to
make
sure
that
you're
not
like
randomly
using
a
different
IP
address,
sometimes
so,
in
order
to
do
in
order
to
do
that,
we
we
have
to
make
sure
that
whenever
we
reconfigure
that
the
Junos
devices
we
don't
overwrite,
you
know
the
the
IP
address
was
something
that
doesn't
work.
We
need
to
be
able
to
dynamically
set
the
management
IP
address
as
opposed
to
using
a
static
one,
which
is
what
we
were
doing
before
so
anyway.
B
All
of
these
changes
are.
None
of
these
changes
are
visible
to
the
outside
world.
You
don't
see
this
if
you're
a
user,
hopefully
ever,
but
it's
a
necessary
change-
that
we're
doing
to
continue
to
reinforce
the
notion
that
you
know
so
that
we
continue
to
reinforce
the
notion
that
we're
not
you
know
explicitly
building
this
for
one
particular
image
type.
The
whole
purpose
of
the
platform
is
to
be
totally
agnostic
to
what
it's
running.
We
have
some
strong
opinions
on
what
we
run
within
NRA
labs
posting
that
consus
we
have
to
make.
B
We
have
to
make
some
rules
about
things
like
security,
but
the
platform
itself.
We
we
don't
want
the
platform
itself
to
be
restrictive
in
terms
of
like
oh,
you
know,
you
know
like,
for
instance,
we
could
have
used
PI
Z
to
configure
these
devices
just
straight
up.
We
could
have
totally
done
that.
We
didn't
do
that
because
we
don't
want
it
to
be
just
a
Juno's,
only
thing
so
we're
using
napalm
things
like
that.
B
A
B
That
that
that
got
into
the
weeds
quickly,
but
just
suffice
it
to
say
that
there
was
a
lot
of
fixes
like
that
in
this
release.
The
release
notes
are
there
and
I'm
gonna
write
a
blog
post
here
in
a
little
bit
to
publish
tomorrow
to
talk
about
the
release
in
earnest
but
other
than
the
new
lesson.
It's
mostly
minor,
not
necessarily
minor,
but
behind-the-scenes
fixes
like
that
sweet.
B
Well,
yeah
I
mean
that's
one
thing:
I
have
to
figure
out
one
one,
one
feature
that
we've
want,
that
we
becoming
more
and
more
the
days
go
by.
Is
this
idea
of
collections
where
we
have
a
home
for
lessons
that
are
written
that
are
they're
part
of
a
collection
like
for,
like
we
have
a
bunch
of
use
case.
B
That's
driving
this
like
we,
as
in
juniper,
do
contribute
some
lessons
that
are
a
little
bit
more
juniper
specific,
even
though
they're
open-source,
it's
important
for
us
to
be
upfront
about
when
or
when
you
can
and
can't
use
certain
technologies
like
the
J
snappy
lesson.
For
instance,
J
Snap
is
an
awesome
tool
and
it's
open
source,
but
it
is
juniper
specific
and
we
don't
want
to
like
get
in
the
habit
of
proposing
these
things
and
be
like.
Oh,
you
totally
use
this
everywhere.
Then
let
you
figure
out
later
after
you
like.
B
Do
your
research
to
try
to
figure
out.
Oh
I
guess
this
only
runs
on
juniper
devices
like
we
don't
want
that.
We
want
people
to
know
from
the
very
beginning
when,
when
certain
technologies
are
applicable
and
then
and
then
a
totally
seemingly
different
use,
can
we've
got
folks
like
channel
partners
and
then
groups
like
network
to
code,
all
kinds
of
groups
that
are
like
hey
I
want
to
contribute
to
energy
labs
and
what
we
want
to
do
provide
a
home
for
that
content.
Not
just
like.
B
Please,
please,
let
us
assimilate
your
content
into
the
Borg
of
the
NRA
labs
curriculum.
We
want
there
to
be
a
highlight
there.
That
says:
hey
this
lesson
was
contribute
by
networks
of
code
and
oh
by
the
way,
you
know
click
this
little
badge
at
the
top
of
this
lesson
that
says
NTC
where
you
click
it
and
it
goes
to
a
page
within
Emory
labs
that
explains
who
network
Takota
is
why
they've
contributed
and
what?
What
they're?
Why
they're
awesome
and
maybe
some
links
to
additional
resources
to
follow
up
with
them.
You
know,
externally.
B
We
want
to
be
able
to
provide
that
kind
of
context.
Just
like
the
kind
of
context
we
want
to
provide
for
Juneau
specific
things
that
are
only
applicable
juniper.
We
want
to
be
able
to
sort
of
collect
similar
content
together
and
provide
at
that
additional
context.
Whatever
that
context
is
and
for
us,
that's
that's
something
that
we
want
to
do
very
soon
and
we're
playing
with
the
way
that
we
want
to
actually
implement
that
before
tentatively
calling
it
collections
more
than
likely
it's
going
to
be
a
new
resource
type,
so
it'll
be
in
git.
B
Nice
ceptin,
that's
like
the
the
elevator
pitch
verbal
layout.
We're
still
playing
with
the
idea,
but
that's
the
that's
the
vision
we
want
to
there's
so
many
use
cases
that
we've
come
across
where
this
will
help.
So,
if
not
at
the
very
next
version,
it'll
be
very
soon
after
I,
just
gotta
figure
out
is
the
next
version.
B
A
B
B
A
A
little
care
package
as
a
sticker
in
it
we're
also
I've
also
previously
put
out
there.
Therefore,
some
contributors
will
be
not
all
of
them,
because
it's
cost
prohibitive,
but
some
I'll
be.
We
have
a
little
stock
of
enemy
lab
shirts,
but
nice
button
shirts,
with
the
with
the
logo
embroidered
on
them,
so
some
people
will
be
getting
those
if
you,
if
you
contribute
you're
eligible
for
these
things,
we
should
in
theme
in
along
with
the
theme.
A
Much
we
have
too
many
things
going
on
discord
and
int,
which
we
do
it.
We
do
have
some
important
things
happening
with
this
big
things
happening
with
this
project,
probably
version
2.0
kind
of
things
that
will
be
officially
announcing
sometime
later
this
year.
That
will
explain
why
that
we're
using
discordant
which,
for
this
you
know
for
the
for
the
social
home
of
this
community,
so
in
in
line
with
that,
we
maybe
we
should
put
together
a
loot
box
and
enter
no.
B
A
A
A
B
A
A
B
B
Let
me
make
sure
everything
on
my
screen
is
legit.
Yeah,
okay,
cool
I.
Do
that
before
I
start,
the
stream
I
close
out
all
the
windows
and
like
yeah,
so
so
this
is
the
this
is
the
plan
like
I
I,
think
I
talked
about
this
a
few
streams
ago.
Every
time
I
create
a
new
plant
or
every
time
I'm
in
the
middle
of
building
release.
B
I
have
a
second
plan
that
I
create
for
basically
the
next
release,
whatever
it
is,
and
so,
if
I
feel
like
something
needs
to
wait,
a
release,
I'd
bump
it
to
the
next
one,
and
so
since
we
just
came
out
with
zero
to
three
dot,
103.2
is
here.
Most
of
these
still
need
to
get
categorized,
but,
to
be
honest,
there's
not
a
lot
of
issues
here,
usually
a
release
when
I
start
a
release,
there's
usually
a
lot
more
in
this
column,
you
could
you'll
notice.
The
dark.
B
Are
that
there's
a
lot
of
documentation
badges
here
there?
There
will
be
a
lot
of
documentation
updates
for
this
release.
I
realized
over
the
last
few
releases
that
the
docs
are
still
very,
very
outdated
and
they
just
need
to
be
updated.
So
that's
one
thing,
I'm
gonna
be
doing.
The
other
thing
is
and
I'm
targeting
this.
This
is
probably
a
more
significant
change
that
people
should
be
aware
of.
B
B
What
I've
had
on
my
mind
for
a
while
is
and
I'm
gonna
be
doing
this
in
the
next
release
is
restructuring
the
repos
to
make
a
little
bit
more
sense,
and
so
some
of
the
specific
repos
like
antidote
web
and
syringe
those
are
fine,
as
is
they'll
stayed
the
way
they
are
mostly.
This
is
about
the
antidote
repo.
B
So
if
you
look
at
the
antidote
repo
right
now,
you'll
see
that
there
is
a
that
there's
a
bunch
of
stuff
with
respect
to
how
we,
as
in
juniper,
are
actually
running
this
stuff
in
production,
most
of
which
is
really
just
not
relevant
to
most
people,
it's
cooled,
I
mean
obviously
it's
cool
that
we
open
sourced
it.
So
if
you
do
want
to
run
a
version
of
this
in
the
cloud
using
our
tools,
you
know
power
to
you,
I
we're
not
gonna.
You
know
we're
not
going
to
be
taking
this
off
of
github
entirely.
B
The
problem
is
that
having
this
alongside,
the
curriculum
doesn't
make
a
whole
lot
of
sense
and
similarly,
the
same
thing
with
the
platform
really
czar.
Really
all
of
our
kubernetes
manifests
for
deploying
the
platform
that
is
antidote
into
into
kubernetes
and
actually
running
it.
So
this
is
much
more
of
an
operational.
Both
of
these
directories
are
much
more
operationally
focused.
They
have
nothing
at
all
to
do
with
the
curriculum
I
mean
so
more
than
likely
we're
gonna
be
moving
them
to
another
repo,
probably
antidote,
ops,
I!
B
Don't
talk
about
this
a
lot
because
it's
not
really
useful
to
most
people,
but
this
is
a
repo
that
we
have
it's
right
now,
it's
pretty
much
just
a
stack
storm
pack.
So
it's
if
you're
not
familiar
with
stacks
storm,
it's
automation,
platform
for
doing
event,
driven
automation,
I
think
it's
pretty
awesome,
but
that's
because
they
paid
my
bills
for
a
year
and
a
half.
So
that's
not
the
only
reason
I
think
they're
awesome,
but
that's
a
good
one
anyway.
B
This
is
a
stack
storm
pack
for
for
doing
things
like
running
releases,
but
there's
a
bunch
of
workflows
in
here
to
actually
run
releases.
So
that's
pretty
cool
anyway.
It
makes
a
lot
of
sense
for
the
infrastructure
and
platform
things
for
actually,
you
know
running
antidote.
The
platform
as
NRE
labs,
the
site.
It
makes
a
lot
of
sense
for
that
to
live
here
so
more
than
likely
that's
where
it's
gonna
get
moved
and
then,
similarly
the
so-so
docks.
B
This
is
actually
a
pretty
good
place
for
this
to
live,
but
we're
going
to
be
doing
a
little
bit
of
shut
work.
We're
gonna
be
shuffling
things
around,
so
the
the
the
the
order
of
operations.
If
you
look
at
the
issue
that
I
was
looking
to
earlier,
I
have
I
have
an
order
of
steps
that
I'm
gonna
be
taking.
B
The
first
thing
I'm
gonna,
do
is
actually
I'm
gonna
rename
this
repo,
this
antidote,
repo
and
rename
it
to
something
like
NRE,
labs
and
I'll,
be
effectively
I'll,
be
removing
everything,
except
for
the
lessons
directory
I
want
to
preserve
the
history,
because
there's
been
a
lot
of
work
from
a
bunch
of
different
contributors
like
15
contributors,
contributing
to
this
thing,
I
don't
want
to
wipe
out
their
history,
so
I
want
to
preserve
that.
So
the
first
thing
is
I'm,
going
to
be
renaming
this
to
something
specific
to
the
NRI
labs
curriculum.
B
So
this
repo
is
only
about
hosting
that
curriculum
content,
but
we
have
every.
You
know
we
have
a
lot
of
links
all
over
the
internet,
pointing
to
the
antidote
repoed.
So
we
want
to
make
sure
that
that
stays
there
so
I'll
be
creating
a
new
repo
with
this
named
antidote,
the
new
reef,
the
new
antidote
repo,
will
really
just
be
this
Doc's
folder
that'll
really
be
the
only
thing
in
that
repo
and
then
I'll
be
creating
get
sub
modules
to
point
to
all
of
the
other
repos
like
the
NRI
labs
curriculum
the
the
antidote
web.
B
Syringe
all
that
stuff.
That
way
you
can
see
when
you
go
to
this
repo,
you
can
see
what
it
actually
is
and
that
it
is
it's
an
umbrella
sort
of
umbrella
term.
For
all
of
these
other
teeny
projects
and
I
think
that
that
change
will
make
things
lay
out
a
little
bit
more
logically,
whereas
the
curriculum
is
a
sort
of
a
separate
thing.
B
It
also
opens
up
the
door
by
the
way
or
for
us
to
be
able
to
maintain
releases
for
the
curriculum
separately
so
that
we
don't
have
to
do
a
new
version
of
the
curriculum
every
single
time
we
want
to.
You
know
to
a
release
event
or
any
of
the
antidote
platform
and
vice-versa
we
don't
have
to
like
build
a
new
version
of
antidote
in
order
to
release
the
curriculum
so
having
those
things
logically
separate
I
think
makes
a
lot
of
sense.
B
But
of
course
you
know,
we
want
to
make
sure
that
the
antidote
repo
stays
a
thing
we
wanna
make
sure
it
continues
to
be
a
thing.
So
if
you
have
any
questions
or
comments,
the
issue
you
want
to
keep
track
of.
Is
this
one
antidote
issues?
187
so
I
open
that
yesterday
and
I
tweeted
it
out
this
morning
nice.
This
will
be
something
that,
like
I,
said
most
of
this.
B
You
know
if
you're,
the
only
the
only
people
that
are
really
being
for
people
that
are
contributing
and,
like
I
said,
the
get
history
is
going
to
be
preserved
in
the
NRA.
The
new
nru
labs
repo,
so
you'll
you'll
need
to
update
your
git
remote,
but
otherwise
you'll
you'll
be
fine.
You
won't
have
to
like
reclone
anything
you'll,
just
change
the
remote
location,
so
heads
up
on
that
I,
you
know
I.
Will
you
know,
update
update
this
issue
as
things
I
would
expect
this
to
happen
either
right
before
or
during
the
the
next
release.
B
So
yeah
I
would
say:
that's
probably
it
for
the
plan
for
the
next
release
and,
of
course,
if
you
want
to
see
the
other
issues
that
we're
planning
there's
a
few
other
minor
things
that
we
have
planned
for
the
next
release.
So
as
you
as
always
peruse
the
org,
the
org
projects
we
have
one
for
0.32,
looks
like
I
created
one
for
3.3
as
well.
Don't
think
there's
anything
in
there
yet
but
yeah.
This
is
the
current
one.
So
take
a
peek
at
that.
If
you
want
updates
thanks.
A
B
A
Right
Wow,
we
covered
a
lot
in
that
was
a
good
stream
for
50
minutes,
50
51
50,
no
50.
We
started
at
12:01.
Yes,
all
right,
it's
important
to
be
precise.
You
know
we'll
try
to
get
guests
on
here
next
time.
Yeah
I
think
David
G
is
actually
might
start.
Co-Hosting
is
the
third
third
co-host,
so
you
don't
always
see
the
same
two
faces
or
hear
the
same
two
voices
and
we'll
get
and.
B
A
Stay
I've,
it's
so
hard
to
make
look
and
I'm
watching,
like
a
recording
of
this
dream
or
any
of
my
presentations.
I've
ever
done,
they've
been
Horta,
tight,
I
struggle
to
watch
them,
and
especially
once
where
I
know
it
didn't
go
as
well
as
as
it
could
I
can
see.
All
all
of
my
nervous,
ticks
and
stuff
am
I
like
a
change
in
my
voice.
Oh
my.
B
B
B
Now,
it's
like
you
are
aware
that
your
voice,
like
can,
can
go
up
and
down
and
all
these
different
things
in
like,
but
if
you're
in
the
middle
of
it,
you
don't
think
about
that
you're
just
like
and
then
syringe
is
the
orchestrator
behind
the
scenes.
And
then
we
like
to
talk
about
HTML
and
JavaScript
and
stuff,
and
that's
like
well,
it's
so
hard
to
listen
to
yeah
yeah.
B
A
Yeah,
you
know,
maybe
we
should
get
some
Network
to
code.
People
on
here
come
to
think
of
it.
If
you're
watching
you,
you
need
only
ask
yeah
I,
think
that's
a
great
idea.
There's
got
to
be
at
least
one
or
two
that
could
come
on
here
and
talk
a
little
bit
about
what
they're
doing
and
how
they
could
intersect
with
us
totally.
B
I,
honestly,
this
is
one
of
the
one
of
the
reasons
I
got
on
that
on
that
soapbox.
Earlier
about
about
the
the
like,
the
the
governance,
talk
that
we're
thinking
about,
creating
and
and
the
fact
that
people
can
contribute
small
things
in
addition
to
big
things
like
most
of
my
social
energy,
for
this
project
is
being
devoted
to
the
to
making
sure
it's
to
making
sure
that
the
collaborative
nature
of
this
project
is
is
as
obvious
as
possible.
B
I
I
think
we
in
this
industry
still
just
are
so
cynical
about
anything
attached,
II
or
even
remotely
attached
to
some
corporate
entity,
even
like
big
open-source
projects
like
oh
there's,
so
many
vendors
involved.
So
clearly
the
the
project
itself
is
just
being
influenced
by
the
you
know,
the
big
companies
and
I
I,
don't
think
people
yet
realize.
Just
how
collaborative
this
project
is
right
now
like
how
not
corporate
it
is
right.
A
A
A
Doesn't
work
like
that,
but
you
take
it
they're
more
than
welcome
to
contribute
lessons
yeah
and
some
of
them
do
actually.
So
that's
nice.
We
have
it's
cool
to
hear
from
engineers
that
are
like
really
excited
about
something
they're
working
on
it's
one
of
my
I
mean
I,
told
her
the
longer
I've
been
intact,
the
more
even
if
it's
something
I,
don't
know
anything
about
I,
really
like
watching
someone
intact
present
about
something
that
they
like
excited
about.
A
You
know
later,
like
that,
just
yeah
you
tell
their
brain
is
like
just
churning
about
this
thing
and
I
I,
just
like
that
in
general
it
could
be
about
a
project
or
attack.
I
know
nothing
about
night,
but
my
neighbor
is
a
control
systems,
materials,
engineer
/.
He
does
a
couple
different
things
and
he
gets
really
excited
and
he
comes
over
my
house
and
he's
telling
me
about
like
these
different
things.
B
B
A
B
Arrange
it
yeah
will
do
will
do
us
like
we
usually
do
this
well
the
end.
This
applies
to
anybody.
This
probably
won't
scale
for
like
a
year
but
for
the
initial
phase
of
the
project.
If
you
just
want
to
schedule
some
time
with
us,
we
can
overview
the
project
and
what,
where
it's
currently
at
and
like
how
you
could
contribute
what
it
looks
like
that
kind
of
thing,
happy
to
happy
to
do
that.
We
don't
have
to
like
just
like
stream
it
we
can.
B
A
I'm
gonna
call
it
death
because
I
haven't
eaten
lunch
and
I
have
endless
meetings.
Now
this
afternoon,
I'm
gonna
I
I
have
15
minutes
to
go,
eat
and,
and
then
and
so
on,
and
then
start
my
my
afternoon
of
non-stop
talking
so
meet
a
meeting
phone
yeah.
So
things
were
thanks
for
joining
everyone
and
again
I'm
cloud
totes,
elo,
UDT
OAD,
and
this
is
Miren
mi
ER
di
n
and
thanks
for
for
joining
us,
please
follow
us
on
Twitter
enter
at
NRI
labs.
Please
follow
that.