►
From YouTube: Community Stream #1 - NRE Labs Selfmedicate
Description
Broadcasted live on Twitch -- Watch live at https://www.twitch.tv/nrelabs
A
If
you
want
and
we're
gonna
be
talking
about
some
significant
changes,
we
made
to
a
piece
of
energy
labs,
a
tool
that
that
makes
it
very
easy
to
write
lessons
for
any
labs,
so
go
to
go
through
the
process
of
creating
lessons
for
any
labs
called
self
Medicaid
I
just
want
to
say
sorry
for
the
lighting
I'm
in
a
quiet
room
in
a
building
somewhere.
So
I
don't
have
the
best
lighting
he's
being
interrogated
by
the
KGB
yeah
right
now.
Their
other
side
of
my
laptop
right
now
telling
me
what
to
say.
A
That
would
be.
That
would
be
the
not
the
worse
and
it's
happened
to
me
in
the
last
month.
So
if
so
so,
having
kicked
that
off,
I
I
guess
we'll
do
some
boilerplate
I
guess
enery
Labs
is
a
is
an
open
source
project
sponsored
by
Juniper
Networks,
but
it's
it's
not
a
product
of
Juniper
Networks.
It's
a
way
for
its
for
network
engineers
to
get
familiar
with
automation,
concepts
that
they're
gonna
run
into.
If
they
start
using.
A
You
know
popular
automation,
related
tooling
out
on
the
on
the
interweb
so
that
they
can
download
and
and
get
familiar
with
it's
completely.
What
is
that
marketing
wall
free?
You
don't
have
to
register
it
at
all
on
the
website.
You
can
just
go.
There,
click
on
a
lesson
and
it
instantly
launches
a
sandbox
just
for
you
without
knowing
anything
about
you
so
that
you
could
start
learning
without
worrying
about
you
know
being
being
targeted
in
some
kind
of
nefarious
marketing
plan.
So
so
I
highly
recommend
going
there.
A
B
Cool
so
yeah
kind
of
like
what
Derek
was
saying
we.
The
purpose
of
this
is
not
to
you
know
to
to
go
rah,
rah
juniper,
it's
it's
really
like
the
disconnect
we
saw
in
the
industry
was
that
there
was
all
you
know
the
this
small
group
of
folks
that
were
automating,
and
they
knew
a
lot
about
bits,
various
tools
and
processes.
And
then
you
thought
you
have.
You
have
folks
that
you
know
don't
really
know
much
about
automation
and
the
the
way
that
those
two
groups,
like
shared
information,
just
wasn't
super
great
like
at
the.
B
In
the
best
case
scenario,
you'd
have
some
of
the
automation,
savvy
folks,
writing
blog
posts
and
github
URLs,
and
things
like
that.
But
the
people
that
didn't
know
anything
about
automation
wouldn't
really
feel
like
they
had
the
skills
to
even
consume.
The
tutorials,
like
there's
just
a
huge,
huge
disconnect
there,
and
so
we
wanted
to
build
a
platform
that
allowed
folks
who
already
have
some
expertise,
and
that's
said,
of
course
that's
gonna
come
in
varying
degrees.
B
But
in
in
most
cases
you
have
to
actually
kind
of
know
a
lot
about
automation
already
in
order
to
consume
that.
So
we
have
this
balancing
act
that
we
want
to
play
between
interactivity.
A
lot
of
us
like
to
learn
by
doing
and
then
I
on
the
other
side
of
the
fence.
We
have
the
ease-of-use
that
comes
intuitively
with
a
blog
post.
You
don't
need
to
know
anything
to
read
a
blog
post
so
with
NRE
labs.
B
What
we
wanted
to
do
is
build
a
platform
that
took
the
strengths
of
both,
and
so
we've
constructed
the
way
we've
constructed.
The
software
is
such
that
you
can
contribute
to
this
curriculum
in
a
way
that
when
that
curriculum
is
consumed,
the
person
that's
using.
It
doesn't
need
to
know
anything,
and
so
our
goal
for
this
for
this
particular
community
episode
is
actually
to
show
how
you
can
do
exactly
that.
We've
developed
a
sort
of
a
child
project
or
a
sister
project
to
some
of
the
other
software
we've
created,
and
we
call
it
self
medicate.
B
What
self
medicate
really
is
is
a
it's
a
it's
a
it's
a
way
of
running
the
same
software
that
we
run
the
production
site.
All
on
your
laptop.
The
benefit
of
that
is,
you
can
create
curricula
locally
on
your
laptop
in
your
own
text,
editor
and
test
it
all
on
your
laptop
again
fully
in
the
browser,
but
the
actual
content
is
running
on
your
laptop
and
not
anywhere
else
like
not
in
our
cloud
or
anything
like
that.
B
The
cool
thing
about
that
is,
you
can
use
that
as
sort
of
your
development
environment,
if
you
even
regardless
of
whether
or
not
you
want
to
contribute
that
content
eventually
to
NRE
labs,
you
have
this
local
environment
to
test
that
content
out
in
and
then
you
know
once
you've
gotten
it
to
a
certain
point.
Maybe
you
think
about
contributing
it,
and
so
this
is
one
of
the
things
that
we
really
wanted
to
do
to
make
sure
people
felt
like
their
path
to
being
able
to
contribute
their
automation.
B
Expertise
was
as
it
had
as
low
a
barrier
to
entry
as
possible.
So
that
is
the
motivation
behind
this.
Like
I
said
all
self
medicate
is,
is
a
set
of
scripts
that
allows
that
that
allows
you
to
run
the
exact
same
software
on
your
laptop
in
a
smaller
scale
that
we
do
in
production
to
power.
The
full
and
re
labs
experience.
B
So
my
what
I'd
like
to
do
in
the
next
you
know,
maybe
five
to
ten
minutes,
is
outline
what
we've
built
to
enable
that
now,
if
you've
been
around
for
a
while
self-medicate,
you
probably
actually
have
heard
that
for
a
while.
We
actually
released
self-medicate
alongside
the
original
release
of
venery
labs,
but
there
there
were
a
few
problems
with
it
and,
as
the
software
moved
forward
with
a
whole
bunch
of
different
features,
it
was.
B
It
was
difficult
to
keep
the
two
in
sync,
and
so
one
of
the
things
that
we've
done
recently
was
invest
a
lot
of
time
into
making
the
self-medicate
experience
a
lot
more
intuitive.
For
instance,
if
you
didn't
know
anything
about
kubernetes
you,
then
you
you,
wouldn't
really
have
the
tools
to
know
how
to
troubleshoot.
What's
going
wrong
on
the
self-medicate
experience,
and
sometimes
things
would
go
wrong
or
even
not
necessarily
things
go
wrong.
B
B
What's
going
on
behind
the
scenes,
is
it
just
looked
like
nothing
was
working,
even
though
there
was
a
download
taking
place
so
one
of
the
things
that
we
did
was
we
built
logic
into
the
self
Medicaid
experience
that
made
that
a
lot
more
obvious.
So
two
things
we
added
visibility
into
that
process.
So
you
know
a
lot
more
about.
What's
going
on
behind
the
scenes
from
self
medicate,
when
you
execute
self
medicate
it'll
tell
you
much
more
about
what's
going
on
and
in
addition,
it'll
also
preemptively
download
some
of
those
large
those
large
images.
B
For
instance,
the
VQ
effects
images
are
fairly
large
and
they're
pretty
much
needed
by
any
lesson
at
least
the
lessons
that
are
there
right
now,
so
the
self
medicate
script
will
actually
download
those
ahead
of
time
and
again,
it'll
tell
you
what
it's
doing
and
it'll
tell
you
how
long
it's
taking
the
benefit
to
that
is.
Once
you
have
the
once,
you
have
the
environment
spun
up
and
all
of
that's
finished.
When
you
start
a
lesson,
it'll
happen
much
more
quickly
because
it
doesn't
have
to
download
the
images
at
that
point.
B
B
So
if
we
go
to
so
I
just
have
a
terminal
open
and,
as
you
can
see,
we
have
the
self
medicate
SH
script.
This
is
just
in
the
antidote
self
medicate
repository
we'll
put
a
link
to
that
in
the
chat
that
way
you
can
see
where
that's
at,
but
it's
it
it's
at
Emory
learning,
/
antidote
self
medicate.
So
if
you,
if
you
go
to
that
repo
and
you
clone
it,
you'll
see
that
there's
really
just
script
in
the
directory.
B
In
fact,
I'll
just
navigate
to
that
right
now
you
can
see
that
we've
we've
also
reorganized
things
a
little
bit
better,
every
all
of
the
kubernetes
esque
things
that
you
saw
maybe
before.
If
you,
if
you've
seen
this
in
the
past,
those
are
all
now
in
a
subdirectory,
and
you
really
don't
have
to
met
you
really
don't
have
to
mess
with
them.
It
used
to
be.
This
is
another
change
we
made
recently
and
self-medicate.
B
It
used
to
be
that
you'd
have
to
actually
manually
edit
the
coop,
the
the
kubernetes
manifests
in
order
to
get
your
code
placed
or
your
lessons
placed
within
the
environment,
and
you
actually
don't
have
to
do
that
at
all
anymore
because
of
some
of
the
changes
we
made.
So
the
all
of
the
kubernetes
stuff
that
you
might
have
seen
before
is
all
in
this
manifest
directory,
and
you
really
just
don't
have
to
mess
with
it
every
you
know
you.
B
B
This
so
the
shell
is
zsh
I've
been
using
it
for
about
six
years
and
I
love.
It
I
can't
remember
what
the
name
of
the
theme
is
it
some
sort
of
solarized
theme.
A
B
Yeah,
so
there's
a
few
things,
the
the
prompt.
It
shows
you
where
you
are
in
the
CSH
sort
of
abbreviated
format.
So
you
know
these
are
sub
directories
that
are
abbreviated
for
for
brevity
and
then,
in
addition
to
that,
this
is
my.
This
is
the
git
plug-in,
so
you
can
see
what
directory
you're
in
what
branch
you're
in
Mac
changes
is
the
original
name
of
the
branch
and
then
I
kind
of
know
what
some
of
these
logos
mean,
but
basically
these
logos,
the
status
of
the
git
repository.
B
So
if
you
can
get
status
pretty
sure
it
just
means
that
there's
been
a
few
changes.
If
I
were
to
stage
one-
let's
see,
add
self-medicate
yeah,
it
looks
like
there's
there's
a
plus
sign
now
for
anything,
that's
been
staged
anyway.
Yeah
this
zsh
I
use
a
I
used
to
use.
Oh
my
zsh,
but
I
knew
I
moved
to
Z
presto.
So
that's
that's
a
framework
for
automatically
configuring
zsh
and
my
dog
files
are
public.
I
could
send
a
link
in
the
chat
for
the
if
you'd
like
to
poke
around
at
that
yeah.
B
Mm-Hmm
and
my
desktop
environment
is
i3
in
case
you're,
wondering
about
that
too.
Okay,
so
oh
yeah,
right!
So
the
the
okay
right,
the
the
repository
itself,
and
let
me
actually
just
show
the
github.com
NRI
learning
antidote
self
medicate.
So
this
is
the
repository
in
order
to
get
this.
You
just
clone
it.
So
if
you
probably
use
HTTP
and
I
just
copy
this
URL
and
do
a
git
clone
on
your
local
file
system
and
you'll
get
everything
that
we
have
now.
You
might
also
notice
that
this
branch
master
this
doesn't
show
the
manifest
directory.
B
B
You
can
check
out
the
branch
map
changes
like
you
saw
on
my
terminal
if
you
want
to
get
this
stuff
right
right
now,
but
it's
not
quite
merged
yet
into
master.
So
if
you
clone
the
repo
right
now,
you
won't
get
it.
You'll
have
to
manually
check
out
this
branch,
but
if
you
just
wait
a
day
or
two,
you
won't
have
to
do
any
of
that
you'll,
just
you
can
use
master,
will
be
merging
this
very
soon.
B
So
if
you
go
to
the
terminal,
so
self,
medicate,
SH
and
actually
I
can
just
show
some
of
the
code.
You
can
see
that
there
is
a
whole
bunch
of
new
sub
commands
that
didn't
exist
before
and
actually
they
said,
the
script
itself
has
been
renamed.
It
used
to
be
called
ante
up,
I
renamed
it
to
self-medicate.
I
thought
ante
up
was
cool,
but
it
ended
up
being
a
little
bit
confusing.
So
self
medicate
is
the
name
of
script
in
keeping
with
the
name
of
the
repository,
and
we
have
a
few
sub
commands.
B
So
you'll
notice
in
the
output
that
I
saw
that
I
showed
before
I
ran
the
sub
command
start.
So
if
you're
starting
out
you
just
let's
say
you
initially
clone
the
repo
and
you
haven't
done
anything
yet
start
is
the
first
command
that
you're
gonna
want
to
run
this.
What
this
will
do
is
it'll
spin
up
a
whole
bunch
of
stuff
behind
the
scenes.
B
This
is
okay.
We're
ready
to
go
here
is
the
URL
to
access
the
local
environment,
so
I'll
scroll
back
up
and
show
you
that
output.
The
very
first
thing
that
you
see
is
this
self
medicate
SH
and
then
again
the
sub
commands
start
and
then
you'll
notice
that
I'm
passing
in
a
third
parameter.
A
second
second
parameter
to
the
script
anyway,
and
this
looks
like
a
directory,
so
so
dot
dot
slash
antidote.
Now
this
is
up
a
directory,
the
dot
dot
and
then
the
antidote
directory.
B
On
top
of
that,
so
it's
a
sister
directory
to
where
we're
at
right
now
and
you
might
ask
well,
why
are
we
doing
that?
Why
are
we
passing
that
in
so
this
is
another
change
that
we
recently
made.
It
used
to
be
with
self
medicate
that,
in
order
to
use
any
changes
that
you
may
let's
say
you
make
curriculum
changes
to
you
know
you,
maybe
you
add
a
lesson
or
you
modify
an
existing
lesson.
The
way
that
you
would
have
to
see
those
changes
locally
is
after
starting
self-medicate.
B
B
Which
are
here
so
you'd
have
to
go
into
the
syringe
dye.
Yml
file
and
you'd
have
to
change
a
two
lines.
Actually,
you'd
have
to
change
this
line
to
indicate
your
repo
instead
of
the
NRI
learning
org
and
similarly,
you'd
have
to
do
the
same
thing
with
this
line.
So
a
few
things
there
first
off
it
had
it.
B
It
required
people
to
edit
kubernetes
manifest,
which
is
a
pain,
especially
if
you
don't
know
kubernetes
at
all,
you're,
just
sort
of
poking
through
a
bunch
of
random
UML
and
in
addition,
it's
a
pain
because
you
had
to
act
mint
and
push
your
changes
before
you
could
even
see
them
manifested
in
the
local
environment
which
you,
which
is
annoying.
So
you
know
people
want
to
be
able
to
just
try
things
and
save
them
and
reload
them
instead
of
deal
with.
B
B
If
you
look
at
the
script,
what
it's
actually
doing
is
it's
mounting
the
lesson
directory
that
you
pass
in,
so
that
dot,
dot,
slash
antidote,
we're
passing
that
in
at
run
time
that
gets
set
to
this
variable
lesson
directory
and
when
we
start
mini
cube.
We're
passing
that
in
so
that
directory,
whatever
you
state
gets
mapped
to
slash
antidote
inside
of
the
mini
cube
VM,
and
then,
on
top
of
that,
whenever
we
spin
up
things
like
syringe
those
pod
definitions
are
actually
using
that
slash
antidote
to
create
host
only
volumes.
B
So
again
you
don't
have
to
deal
with
any
of
that.
The
reason
I
call
out
is
because
the
end
result
of
all
of
that
configuration
is
that
anything
that
you
have
local
on
your
filesystem
and
I
mean
like,
for
instance,
here's
the
antidote
repo.
If
I
make
a
lesson
change
here,
let's
say
I
edit,
the
the
je
snappy
lesson,
one
guide,
let's
say:
I
type-
something
here
and
I-
save
that
the
way
that
you
can
actually
make
that
change
represented
in
your
local
environment
is
by
using
the
reload
command.
B
So
if
we
go
to
self-medicate
again,
you
can
see
that
there's
a
second
command
reload,
and
this
is
really
cool.
What
this
does
is
it
really
just
restarts
syringe?
That's
the
only
thing
it
really
does.
For
those
that
know
some
a
little
bit
about
the
architecture.
Syringe
is
our
back-end
component
that
does
orchestration
and
one
of
the
things
that
it
does
when
it
starts
initially
is
it
looks
at
the
local
file
system
and
says:
okay,
here's
all
the
lessons.
Let
me
load
them
all
into
memory
now
again.
B
Normally
what
what
happens-
and
this
is
true
in
production-
is
it
actually
goes
out
and
it
clones
a
git
repo
that
it's
configured
to
clone
and
then
it
loads
the
content?
That's
that's
that
gets
pulled
locally,
but
again,
dealing
with
get
when
you're.
Just
developing
content
can
be
a
pain,
so
so
we've
so.
A
Bana
yeah
I
mean
erupt.
This
is
very
cool.
I
used
an
e
dote.
You
know
when
before
you
could
do
a
local
local
directory
right.
So
now
you
can
just
take
now.
I,
don't
not
like
you
said:
I
don't
have
to
commit
to
github
or
anything.
I
can
make
all
my
changes
test
everything
out
locally
and
then
do
the
commit
into
a
repository.
So
there's
two
things
here:
I
was
curious
about
one.
Is
you
said
that
this
whole
thing
runs
inside
of
a
VM?
Do
you
have
to
have
VirtualBox
installed
before
they?
B
Actually,
let
me
bring
up
the
it's,
not
it's
not
actually
published
yet
because
this
is
also
in
another
pull
request.
But
if
you
go
to
antidote
project,
dot,
RTF
d,
io
or
read
the
docs
io
and
you
go
to
building
antidote
and
you
say,
build
and
run
antidote
locally.
This
is
the
old
version
of
the
docs.
Like
I
said
this
is
being
modified
in
a
pull
request
as
well,
but
the
URL
will
be
the
same.
B
So
if
you
go
to
the
docs
after
we've
merged
these
changes,
you'll
be
able
to
see
there's
a
section
that
talks
about
dependencies
and
there
actually
is
already
one
here.
It
just
I,
don't
think
it
talks
about
VirtualBox,
so
yeah
you
do
need
a
hypervisor
installed.
I
use,
VirtualBox,
it's
a
pretty
common
open
source,
hypervisor
so
use
that
Oracle.
A
B
A
Okay,
so
earlier
you
said
you
added
a
feature
where
it
would
pre
download,
common
or
large
images.
You
are
talking
about
container
images
for
the
platform
itself
running
within
kubernetes
yep,
when,
when
you're
developing
locally
and
you're
introducing
a
new
container
image,
how
does
that
work?
Yeah.
B
That's
a
good
call,
so
so
not
all
the
images
are
only
the
one,
only
the
really
common
one,
it's
not
really
possible
for
us
to
preemptively
download.
You
know
any
image
that
you
might
want
unless
you
feel
in
one
of
the
things.
One
of
the
reasons
why
I
wanted
to
show
the
script
is.
You
certainly
could
go
to
the
self-medicates
script
and
add
that
image
yourself.
If
you
wanted
to
do
that,
we
can't
remember
right
where
it
was
it's
yeah
here.
B
So
here's
the
list
of
images
that
we
download
and
like
I
mentioned
before,
all
of
the
like
the
vqx
images.
Those
are
extremely
common,
pretty
much
every
lesson
uses
those,
so
it
makes
sense
to
download
those
ahead
of
time
same
thing
with
utility.
It's
not
that
big,
but
it's
again
used
by
nearly
every
lesson.
So
that's
the
reason
we
pre
download
those.
B
Well,
we
don't
pre
download
everything,
and
so
to
your
point,
if
you,
if
you
create
a
new
lesson
and
you
want
it
to
be
shown
it's
in
self
Medicaid,
do
you
need
to
manually
download
that
image?
No!
Actually,
that's
not
the
case.
We're
just
pre
downloading
these
to
make
the
user
experience
better
at
runtime.
B
However,
when
you
start
a
lesson,
if
the
image
isn't
pulled
yet
it
will
still
automatically
pull
it
it'll
just
do
it
sort
of
just
in
time,
as
opposed
to
ahead
of
time,
so
that
stuff
still
works,
that
the
ability
to
automatically
pull
images
that
are
referenced
in
the
syringe
file.
All
of
that
still
there
we
just
added
some.
We
just
pulled
these
images
ahead
of
time
in
the
self
medicate
script,
to
make
the
user
experience
a
little
better
at
the
at
the
you
know,
at
runtime,
okay,.
B
B
It
says,
like
hey,
I'm,
installing
some
basic
infrastructure
now
I'm
installing
the
antidote
platform,
and
then
these
four
are
the
images
that
we
just
saw:
it'll
download
those
in
sequence
and
then,
once
it's
all
finished,
it'll
say:
hey
I'm,
all
done,
you
should
be
able
to
access
the
web
UI.
Now
and
again,
this
was
a
big
problem
before
where
again
people
you
know
the
you
know,
internet
connections
can
be
kind
of
slow,
and
so
even
small
images
that
are
required
for
an
antidote
might
still
be
downloading.
B
At
the
end
of
this
script,
getting
run
because
again
the
self-medicates
script
before
all
it
really
did
is
run
a
custom.
You
know
sort
of
mini
cue
command
and
then
upload
a
bunch
of
definitions
and
immediately
after
that
stuff
got
uploaded.
It
would
present
you
with
this
URL
and
so
when
people
would
go
to
that
URL
right
away
like
if
they
did
eat
it
all
and
they
went.
You
are
right
away.
It
actually
wouldn't
work
because
things
were
still
being
downloaded
literally
the
images
for
running
the
web
UI
and
for
the
backend
Orchestrator.
B
Those
would
still
be,
you
know,
sort
of
being
downloaded.
So
what
one
of
the
reasons
why
we
did
all
of
this
stuff?
First,
where
you
say
like
look
we're
installing
the
platform.
It's
not
ready
yet
is
so
the
fee
is
so
that
when
we
do
finally
present
this
URL,
it
should
actually
be
working,
because
we've
verified
that
everything
has
has
been
downloaded
correctly.
It's
part
of
what
the
script
does.
B
So,
like
I
said,
if
you
copy
that
URL,
you
should
be
able
to
see
the
web
UI
here
so
again.
This
is
exactly
the
same
thing
that
we
see
in
the
production
version
of
the
site.
It's
just
running
locally.
You
can
see
antidote,
local,
that's
a
that's!
A
an
entry,
that's
been
placed
in
the
Etsy
hosts
file
for
us
by
the
way
the
self-medicates
script.
Does
that
also
automatically,
and
then
port
30,000
won.
So
if
we
do
search
lessons,
let's
go
to
the
introduction
Tem
a
lesson.
B
A
B
Like
a
VQ
effects
or
anything
like
that,
so
it
should
take
very
little
time
to
spin
up,
looks
like
we're
there.
Okay,
perfect!
So,
like
I
said
you
have
a
in
here
and
that's
pretty
cool.
Now,
let's
say
you
wanted
to
make
a
change.
Let's
say
you
wanted
to
say
like
okay,
let's
say
we
just
some
random
change.
Let's
say
hello
before
welcome,
let's
go
to
that
directory.
So
let's
go
to
antidote
and
lessons
and
lesson
14.
Yes,
I
have
the
lessons
memorized,
don't
judge
me.
B
Hello
and
welcome
okay,
so
we've
made
a
change
now.
This
could
be
a
change
to
an
existing,
less
be
a
new
less.
It
really
doesn't
matter
any
change
inside
the
curriculum
that
we've
been
that
we
passed
into
the
self
medicate
script
is
in
play
here.
So
if
we
do
a
reload
you'll
see
again,
we
have
a
reload
sub
command
in
the
self
medicate
script,
where
we
say
reload,
antidote
components.
B
This
isn't
just
to
reload
the
components
again
when,
when
syringe
starts
up,
it
actually
looks
at
the
content
fresh,
whether
or
not
that
contents
been
pulled
via
git
or
whether
it's
just
already
on
the
file
system
and,
like
I,
said
the
way
that
we've
installed
syringe
within
the
self
medicate
environment
is
the
latter.
It
uses
it
doesn't
Chloe,
it
doesn't
try
to
clone
it
in
real
time.
It
just
expects
that
it's
going
to
be
there
on
the
file
system
and
then
what
self
medicate
does?
Is
it
Maps
the
directory
appropriately,
so
that
it's
there?
B
What
that
means
is
if
we
want
to
show
our
changes
in
the
in
the
environment.
We
really
don't
have
to
do
anything
other
than
hit
this
reload
command,
and
if
you
see
the
the
code
behind
the
scenes
that
reload
command
all
it
does,
is
it
just
deletes
the
syringe,
pod
and
kubernetes
will
start
a
new
one.
So
it's
actually
really
simple.
That's
all
it
does,
and
it
also
waits
by
the
way
to
make
sure
that
any
existing
lessons
are
terminated
and
then
it
shows
you
reload
complete.
B
So
if
we
do
a
self
medicate,
reload
and
I'll
load
another
terminal
window
actually,
so
we
can
ground.
Well,
wait
wait
to
pick
so
if
we
do
a
coop
cuddle
get
pods
there
we
go
so
so
syringe
has
been
restarted.
You
can
see
it's
only
13
seconds
old
and
we
do
a
coop
cuddle
get
a
namespace.
You
can
see
that
the
old,
less
name
space
that
we
were
running
is
being
terminated.
That's
what
we
rating
on
over
here
in
this
in
this
pain,
the
self
medicate
scripts
waiting
to
that
looks
like
it's
been
finished.
B
Yep
there
we
go,
the
namespace
is
gone.
So
now,
when
we
refresh
this
page,
it
will
then
reload
a
new
copy.
The
lesson
not
only
this
doesn't
happen,
normally
the
stays
around
for
30
seconds,
if
you
haven't
used
it,
but
because
we've
deleted
the
syringe
pod,
its
killed
any
existing
lessons,
and
so
that's
why
we're
reloading
it
here,
but
once
it's
reloaded
you
can
see
that
our
changes
are
here.
B
You'll
notice
that
I
didn't
do
anything
with
get
like
I
have
yet
to
run
a
git
command
like
all
so
the
whole
workflow
before
of
having
to
add
files
to
a
git
repository,
commit
them
and
and
push
them
and
then
and
then
before
you
even
get
started
having
to
deal
with
like
making
sure
that
your
kubernetes
manifests
are
edited
so
that
they're,
pointing
to
your
repos
instead
of
you,
know
the
NRI
learning
organization,
like
none
of
that
applies
anymore.
It's
all
done
with
the
local
file
system.
B
So
you
just
simply
edit
the
files
in
your
text,
editor
of
choice,
as
we
did
just
now
with
this
and
your
run
reload
and
self
medicate
handles
the
rest.
So
that's
really
cool.
That
saves
a
lot
of
time
and
a
lot
of
complain
about
it's,
not
super
new,
but
again
we've
sort
of
made
enhancements
across
the
board
if,
let's
say
you're.
Obviously
this
is
running
a
little
hot,
because
the
lessons
can
take
a
few
quite
a
few
resources.
B
B
You
got
to
be
careful
about
this
because
again,
if
you
do
MIT,
if
you
do,
if
you
actually
delete
the
environment-
and
you
can
do
this-
if
you
run,
if
you
know
mini
cube-
which
I
would
advise-
that
you
learn
enough
about
mini
cube,
because
it's
always
useful
to
be
able
to
troubleshoot
when
things
do
go
wrong.
But
if
you
were
to
go
behind
the
scenes
and
say
like
mini
cubed,
that
will
actually
delete
the
entire
kubernetes
installation.
Now
you
could
absolutely
recreate
it
very
seamlessly.
B
In
the
same
way,
you
did
initially
by
running
self-medicate
that
sh
space
start,
but
it
would
then
it
would
obviously
then
redownload
everything,
so
it
would
take
actually
quite
a
bit
depending.
Obviously,
this
totally
depends
on
your
internet
connection,
but
this
can
take.
You
know
upwards
of
like
half
hour.
Even
so,
what
would
be
awesome
is,
if
you
could
just
have.
You
know
only
do
this
once
and
don't
you
know,
don't
don't
delete
the
mini
cube
environment
just
just
stop
it.
So
that's
what
the
sub
commands
stop
and
resume
allow
us
to
do
so.
B
The
stop
command
is
actually
really
easy.
If
we
just
go
to
the
stop
function
here,
all
it
does
is
it
runs.
Mini
cube
stops
so
not
not
nothing
too
complicated
there,
but
the
resume
the
resume
command.
We
added,
because
again,
every
time
we
start
mini
cube,
we
want
to
make
sure
that
all
of
these,
these
parameters
that
mini
cube
that
are
optional
for
many
cube.
We
actually
want
these
to
be
set.
We
want
to
make
sure
we
have
a
decent
amount
of
CPU
allocated.
We
have
a
decent
amount
of
RAM
allocated.
B
We
absolutely
must
have
CNI
enabled
because
that's
actually
that's
actually
how
lesson
networking
works
today
and
then,
of
course,
we
want
our
directory
mounting.
So
all
of
that
stuff
we
want
to
make
sure
we
have
whenever
we
start
mini
cube,
and
so,
if
you
use
the
resume
sub
command,
meaning
if
you,
if
you
literally
type
oops,
if
you
literally
type
self-medicate
resume,
then
it
will
automatically
pass
that
in
so
you
don't
have
to
worry
about
those
parameters
yourself,
you
just
type
resume.
That's.
A
B
So
that's
it
like
I
said
there
are
two
floor
requests
they'll
all
end
with
this.
If
you
want
to
monitor
and
make
sure
the
see
when
the
changes
are
actually
going
to
get
merged,
the
two
pull
requests
that
you
want
to
monitor
are:
is
this
one?
This
is
the
main
one.
This
is
where
these
self-medicate
changes
actually
take
place.
So
this
is
where
the
script
is
actually
getting
modified
to
support
everything
we've
talked
about
today.
B
B
A
B
Take
these
barriers
out
of
the
equation,
just
like
we
took
barriers
out
of
the
equation
for
people
that
are
learning
Network
automation,
like
the
platform
itself,
does
that
we
also
have
to
start
reducing
the
barriers
for
folks
that
are
actually
bringing
content
in.
So
that's
that's
why
we
did
this.
We
wanted
to
make
sure
that
everybody,
you
know,
has
the
ability
to
contribute
with
as
few
barriers
as
possible.
B
A
Like
it
so
so
we
anyone
that's
watching,
you
know
the
best
way
to
get
started
with.
This
is
just
it's
just
go
to
the
website
and
download
it.
You
do
have
to
put
Virtual
Box
in
place.
First
I
recommend
a
laptop
with.
You
know,
16
gigs
of
ram.
If
that's,
if
you
have
that,
if
it's,
you
can
run
it
on
a
gigs
of
ram,
some
of
the
lessons
lots
of
lessons
can
be
created
in
the
gigs
ram
or
less.
A
But
if
you
want
to
use
the
virtual
cue
FX's
that
we
have
in
our
repository
now,
those
those
are
not
memory
friendly,
container
images.
So
you
know
it's
definitely
recommended
16
gigs
of
ram,
and
you
know
four
cores
would
be
good
on
your
on
your
laptop
as
well.
That
would
help
if
you
intend
on
using
those
particular
images
anyway
and
and
just
get
started,
you
know
just
download
it
try
to
run
it.
You
know
try
to
just
use
one
of
the
existing
lessons.
A
Is
it
sort
of
template
and,
and
you
in
hack
your
way
through
it?
It's
it's
actually
very
easy
to
do.
I
would
say
the
most
tedious
part
is
actually
making
docker
container
images
if
you
plan
to
do
that
from
from
scratch.
For
your
lesson,
that
can
be.
That
can
be
somewhat
somewhat
tedious,
and
you
know
what
we'll
do
a
Tristram
on
that
in
the
future.
Actually,
yeah.
B
Yeah
so
yeah,
sometimes
you
need
to
be
able
to
do
that.
Sometimes
you
know
like
product
it.
We
have
a
utility
image
that
has
a
lot
of
stuff
installed
sort
of
our
junk
drawer
image.
If
you
will
so,
if
you
just
want
to
run
a
script,
usually
everything
you
need
is
gonna
be
in
there,
so
you
might
have
to
create
an
image
you
might
not.
B
I
got
some
traveling
to
do
this
week,
but
next
week
I
will
be
I
will
be
unencumbered
by
by
obligations,
and
so
my
hope
is
that
next
week
we'll
be
able
to
do
the
very
next
release
for
energy
labs
and
I'm
really
excited
about
that.
For
a
few
reasons,
the
main
reason
of
which
I
just
finished
reviewing
a
new
lesson
by
our
good
friend,
David
G.
Those
in
the
network,
Automation
community,
have
undoubtedly
seen
his
work.
B
He
works
for
us
for
Juniper,
not
for
us
like
he
would
like
we're,
not
his
like,
like
boss
or
anything
but
like
he
works
for
juniper
over
a
tamiya,
and
he
has
built
this
amazing
lesson
on
using
T.
It's
not
just
so
actually
for
those
that
don't
know
terraform
it's
an
infrastructure
as
code
tool,
I
won't
go
down
that
rabbit
hole,
it's
an
infrastructures,
code
tool
and,
generally
speaking,
it's
mostly
used
for
being
able
to
configure
cloud
environment.
B
B
It's
all
done
using
the
HCL
language
with
with
terraform,
which
means
you
can
integrate
that
with
a
whole
bunch
of
other
tools
that
already
integrate
with
terraform
and
I'm.
Pretty
excited
about
that
I'm
not
gonna
lie
it's
a
it's
a
really
cool
lesson:
we're
gonna
get
the
the
Hoshi
Corp
folks
to
take
a
look
at
it.
Maybe
that
maybe
they'll
contribute
I,
don't
speak
for
them,
but
we're
gonna
get
them
taking
a
peek
at
this
very
excited
about
that
and
then.
In
addition,
we
also
have
two
other
lessons.
B
I
need
ice
till
need
to
review.
I
feel
about
I
haven't
gotten
around
to
it,
but
we
have
some
awesome,
juniper
specific
stuff
from
Raymond
Lam
to
lessons
actually
one
on
our
Juniper
extension,
extensibility
toolkit
and
then
another
one
on.
What's
the
other
one,
he
wrote
I
told
him
totally
blanking
on
that.
He
just
he
just
submitted
a
new
lesson.
B
I
I'm
blanking
on
the
on
the
I,
know
this,
but
he's
cranking
out
content,
which
is
all
that's
gonna,
get
I'm
sure
into
the
next
release.
Cuz
I,
don't
have
a
ton
of
huge
platform
related
things
that
I
absolutely
must
get
done
right
now
and
and
right
now
the
curriculum
is
more
importance.
I'm
gonna
get
those
merged.
B
The
only
the
only
other
thing
that
I'd
like
to
bring
up
is
one
big
feature:
I've
been
thinking
about
integrating
with
the
platform
and
now
that
I
have
had
I've
had
several
meetings
over
the
past
two
weeks
that
have
just
totally
reinforced
the
urgency
of
this
is
the
idea
of
having
lesson
collections.
So
we
have
categories
where
we
categorize
lessons
into
things
like
well.
This
lesson
talks
a
lot
more
about
fundamentals.
This
lesson
talks
a
little
bit
more
about
tools,
or
maybe
this
lesson
talks
about
like
workflows
that
integrate
tools
in
a
specific
way.
B
B
So
we
have
like
types
of
lessons,
but
then,
if
you
could
like
think
of
a
horizontal
category
across
those
that
allowed
you
to
organize
lessons
into
things
like
like,
basically
like
a
collection
of
lessons
that
are
maybe
attributed
to
a
certain
author,
so
maybe,
for
instance,
one
of
our
one
of
junipers
channel
partners
just
cranks
out
a
bunch
of
lessons
that
highlights
their
own
expertise.
It
would
be
really
cool
to
attribute
those
lessons
to
them
and
provide
a
little
bit
more
information.
So
folks
can
learn
more
about
that
company.
B
If
you're
looking
at
automation-
and
you
want
to
know-
and
you
see
a
company-
that's
doing
it-
you
probably
want
to
get
in
touch
with
them
yeah,
and
so
we
want
to
be
able
to
highlight
that
and
the
same
thing
by
the
way
you
know
problems.
We
have
you
know
we
again:
enemy
Labs
isn't
meant
to
be
a
product
pitch,
but
inevitably
just
because
of
the
way
the
networking
industry
is
we're.
Gonna
have
to
highlight
certain
things
that
are
a
little
more
vendor
specific
than
others.
B
Now
we're
gonna
take
on
the
burden
of
making
sure
that
it's
not
a
sales
pitch
like
that's
sort
of
a
content,
curation
task
on
our
part,
but
we
also
at
the
same
time,
want
to
be
very
upfront
about
who
created
this
content
and,
for
instance,
the
Jason
app.
You
lesson
is
a
great
example:
it's
open
source
and
we
don't
make
money
off
that.
So
there's
no
there's
no
real,
like
monetary
incentive
for
us
to
promote
it.
B
B
These
use
cases
have
actually
come
up
in
a
few
weeks
and
what
we're
gonna
be
doing
is
rolling
out
a
new
feature
with
a
form
that
makes
all
of
that
very
explicit,
work-in-progress
title
we're
calling
it
collections,
don't
know
if
that's
gonna
be
the
long
term
name,
but
basically
we
just
need
some
sort
of
metadata.
They'll
describe
that
and
I
think
I
think
that'll
be
useful.
I
think
that'll
useful
for
people.
You
know
that
aren't
necessarily
like
individual
contributors.
B
A
So
you
know
what
will
we
have
I'll
save
a
more
detailed
review
of
the
changes
that
are
upcoming
in
in
NRE
labs,
because
there
is
gonna
be
something
significant
about
the
next
announcement
that
that
we,
the
next
time
we
talk
about
the
updates,
because
there's
there's
a
you
know.
Major
milestones
are
gonna
be
reached
very
soon
here
for
the
project
and
we'll
we'll
do
a
separate,
Twitter
stream
on
that
upcoming.
Soon,
maybe
again
this
week,
we'll
announce
it
on
Twitter.
It
could
be
next
week
who
knows.
B
B
To
figure
out
the
cadence
I
think
we
want
to
do
two
weeks,
but
we're
not
we're
not
gonna.
Do
like
a
you
know,
we're
not
gonna,
like
only
do
once
a
week
if
we
feel
like
there's
something
you
need
to
know
about,
or
the
community
wants
involved
with
wool
we'll
spin
that
up
and
if
you,
if
you
have
an
idea,
just
you
know,
send
us
a
note
on
Twitter
yeah.
A
Yep
and
by
the
way,
this
will
be
sort
of
the
format
going
forward.
I'm
gonna,
host
the
event
and
usually
and
we'll
have
guests
on
today
was
Matt.
That
was
an
easy
guess
to
have
he's
he's
the
main
coder
behind
the
project.
Schmuck
schmuck,
but
we
will
have
we'll
have
people
from
on
scible
coming
on
as
guests
in
the
upcoming
weeks
and
yeah.
A
Another
thing,
so
it's
not
just
you
know,
do
not
just
gene
over
folks,
but
there
will
certainly
be
a
number
of
junior
folks
who
will
have
as
guests,
but
if
you
have
any
ideas
of
as
a
viewer
on
what
kind
of
guests
you'd
like
to
see
or
what
kind
of
content
we'd
like
us
to
cover
around
any
labs
or
network
automation,
please,
you
know
just
send
us
a
message.
You
can
message
us
on
Twitter.
A
A
Anyone
who
wants
to
join
in
that'll
be
the
official
chat
channel
for
enery
labs
going
forward
and
we're
doing
this
video
conference
using
their
video
conferencing
tools
actually,
as
a
matter
of
fact,
right
now
so
and
there's
a
reason
why
we
chose
social
media
outlets
for
gamers
to
do
this
to
host
this
event
and
stuff
and
and
that'll
become
that'll
unfold
throughout
the
year,
but
you'll
see
something
very
cool.
There's
a
reason
why
we're
on
discordant,
which
yes
it's
for
gamers
and
then
and
yes,
something
very
cool,
is
gonna
happen
with
any
lab.
So.
A
Know
I
mean
I've
been
using
Skype.
My
whole
life
and
I
haven't
latched
on
to
it
yet
either
so
it's
yeah,
it's
I.
Much
prefer
this
platform,
it's
sort
of
optimized
to
do
exactly
this
kind
of
thing,
so
I
think
we're
gonna
wrap
up.
Then
it's
been
almost
an
hour
for
us
this
time.
Around
some
streams
will
be
longer.
Some
streams
will
be
shorter,
but
yeah
I
think
that's.
It
check
out
self-medicate
check
out
energy
labs.
Tell
your
friends
about
it
and
follow
us
on
Twitter,
a
denturri
labs,
fighting.