►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Taking Bare Metal to the Clouds with Tinkerbell - Mark Coleman, Equinix Metal
The technologies involved in provisioning bare metal machines have remained mostly unchanged since the 1990s. With the recent surge in interest in running cloud native workloads on-prem, this previously underappreciated part of the stack is experiencing a renaissance. Tinkerbell, an open source project for provisioning bare metal using the same API-centric, declarative configuration and automation approach pioneered by the Kubernetes community, helps companies bring cloud native workloads to bare metal. In this talk, Mark Coleman will discuss how the project is built with a focus on openness and transparency, demonstrate how to get from a bunch of servers to a cloud native application, and explain how attendees can get involved with the project.
A
Okay,
welcome
everybody
to
this
talk
at
cubecon
cloudnativecon,
europe,
2021
virtual,
despite
having
been
involved
with
the
cncf
for
four
years.
This
is
actually
the
first
time,
I'm
speaking
here,
so
I'm
very
excited
about
it.
So
the
title
of
today's
talk
is
taking
bare
metal
to
the
clouds
with
tinkerbell
and
let's
jump
into
what
that's
going
to
look
like
so
I'll,
explain
a
little
bit
about
myself.
A
I
think
one
of
the
questions
a
lot
of
people
are
going
to
have
is
why
would
people
be
interested
in
running
their
own
hardware
anyway,
so
I
can
share
something
around
that
assuming
you
do
want
to
do
that.
I
want
to
explain
how
tinkerbell
fits
into
the
picture,
which
is
sometimes
a
little
complex,
I'm
going
to
look
a
little
bit
into
why
we
decided
to
open
source
tinkerbell
from
equinix
metal
in
the
first
place.
A
There's
a
lot
of
new,
exciting
stuff
in
our
zero
five,
zero
release
that
I'm
gonna
go
through
and
then
last
but
not
least
I'll
talk
about
how
people
can
get
involved
if
they
want
to
or
if
they
want
more
information,
all
right.
So,
a
little
bit
about
me,
I'm
the
senior
director
of
developer
relations,
equinix
metal,
some
of
you
may
remember
equinix
metal
as
packet
and
up
in
the
top
right.
A
Now
I
was
involved
in
the
cncf
from
2016
until
december
2020
and
I
put
the
little
wink
there,
because,
when
speaking
with
priyanka,
she
said
I
could
call
myself
the
cncf
marketing
chairperson
emeritus
for
a
little
while
I'm
not
quite
sure
how
long
that
one's
gonna
last
I
live
in
north
london
and
importantly,
for
this
talk
until
I
started
equinix
medal.
I
hadn't
touched
any
hardware
really
since
about
2001
when
I
was
working
on
gaming
pc
and
we're
going
to
look
at
some
of
the
things
that
I've
learned
in
this
talk.
A
So
why
are
people
interested
in
running
their
own
hardware
again?
Well,
actually,
it's
not
again.
People
always
have
been,
but
I
think
there
is
the
perception
in
some
quarters
that
those
companies
still
running
their
own
infrastructure
are
what
the
crossing
the
chasm
model
would
describe
as
laggards,
but
this
may
not
be,
as
it
seems,
public
cloud
adoption
has
accelerated
development
of
many
technologies
that
help
companies
to
change
the
way
that
they
deploy
software
more
easily.
A
Kubernetes,
of
course,
is
an
excellent
example,
but
there
are
actually
many
reasons
why
people
would
be
running
on-prem
hardware
still
and
we're
going
to
look
at
some
of
those.
Now,
as
I
see
here,
despite
the
apparent
hegemony
of
public
clouds,
most
companies
run
their
workloads
across
a
wide
range
of
infrastructure
and
there's
a
few
really
good
reasons.
For
that
one
is
kind
of
obvious
any
company
that's
been
around
for
a
while
will
tend
to
have
infrastructure
of
various
types.
A
Acquisitions
are
a
huge
driver
of
hardware,
heterogeneity
in
that,
if
you
acquire
a
company
you're,
often
faced
with
a
choice
which
is
well,
you
know:
do
we
want
this
company
to
spend
the
next
two
years
using
our
cloud
or
our
way
of
deploying
software,
or
do
we
instead
wants
to
focus
on
making
money?
And
very
often
the
answer
is
the
latter.
A
If
you're
running
on
amazon
and
you
buy
a
company,
that's
gcp
shop
selling,
your
hybrid
cloud
or
multi-cloud,
I
should
say-
and
last
but
not
least,
many
companies
have
requirements
that
aren't
best
suited
to
public
clouds,
whether
that's
around
custom
hardware,
whether
it's
around
compliance
in
their
jurisdictions,
whether
it's
for
performance
reasons,
special
workloads
that
they
have
there
are
lots
of
good
reasons
to
run
your
own
hardware,
but
we'll
see
that
it
does
come
with
some
challenges.
Also
edge
computing
is
something
that
I've
been
watching
for
feels
like
forever.
A
Now
since
2017,
and
often
it
was
conflated
with
5g,
but
I
think
what
we're
starting
to
see
this
year,
in
particular,
is
edge,
really
becoming
a
thing.
Finally,
so
we're
seeing
all
sorts
of
companies
wanting
to
put
hardware
closer
to
their
users,
whether
that's
in
your
office,
whether
that's
in
your
store,
whether
it's
in
your
baseball
stadium.
There
are
many
reasons
why
having
a
data
center
of
type
of
sorts
nearer
to
your
user
would
be
a
good
idea.
A
A
And
what
we're
seeing
is
that
with
some
of
the
developments,
tinkerbell
is
only
just
one
of
them.
There
is
real
opportunity
here
for
those
those
laggards.
If
you
will,
which
I
obviously
don't
agree
with-
to
become
the
early
adopters
of
a
new
wave
of
cloud
native
innovation,
taking
advantage
of
a
lot
of
the
tooling
in
the
cloud
native
ecosystem
to
be
able
to
run
their
own
hardware
at
scale
without
having
to
use
a
public
cloud.
A
And,
of
course,
I'm
not
the
only
person
who's
noticed
this
you'll
notice
that
all
the
public
clouds
and
a
lot
of
the
major
software
vendors
are
creating
their
own
hybrid,
multi-cloud
and
edge
tooling,
so
top
left.
Here
we
have
sap
gardener,
google
and
those
vmware
tanzu
azure
arc
red
hat,
open
shift,
cubamatic
a
smaller
player,
but
an
important
player.
There
are
many
of
those
and
then,
of
course,
the
big
news
from
the
end
of
2020
was
amazon's
eks
anywhere,
which,
as
they
say,
allows
you
to
run
eks
in
your
own
data
center.
A
I
think
in
particular,
if
you
look,
for
example,
the
google
anthos
a
web
page
a
company,
a
project
that
we've
done
a
lot
of
work
with
you'll,
see
that
when
you
look
under
the
requirements
they
list
a
bunch
of
servers
like
go,
buy
these
servers
from
dell
or
supermicro
or
whoever
you
want,
and
then
you
can
run
amphos.
But
as
we'll
see
in
a
moment,
it's
a
little
more
complex
than
just
getting
those
servers
shipped
to
wherever
you
want
them
to
be.
A
If
you're
going
to
go
ahead
and
be
successful
with
this
okay,
so
you
want
to
run
your
own
cloud
now
great.
How
does
tinkerbell
fit
in
well?
First,
let's
start
a
little
bit
further
out.
I
wish
I
could
tell
you
that
tinkerbell
is
a
one-stop
shop.
I
found
that
I
was
googling
one-stop
shop
and
I
found
this
apparently.
This
is
a.
This
is
a
chain
of
stores
in
the
north
of
london,
where
I
live,
I've
never
been
in
one,
it's
a
convenience
store,
but
there
we
go
one
stop
shop.
A
So
I
want
to
first
emphasize
that
this
is
a
massively
oversimplified
view.
There's
a
there's
a
lot
of
stuff
going
on
here,
and
you
can
probably
imagine
that
every
layer
of
this
sort
of
proposed
stack.
There
are
many
different
vendors,
all
sorts
of
options,
and
some
of
the
layers
are
totally
missed
out
just
for
brevity,
but
let's
start
at
the
bottom.
So
one
of
the
things
that's
often
overlooked.
A
You
know
if
you're
using
vms
through
amazon,
for
example,
is
real
estate
like
those
vms
have
to
live
somewhere
and
if
you're
going
to
be
running
your
own
infrastructure,
you're
going
to
need
real
estate
to
put
them
in
now.
That
would
be
fine
if
it
could
be
your
bedroom,
but
if
you're
running
any
kind
of
scale
it's
going
to
need
a
bunch
of
other
things
that
maybe
don't
fit
in
your
bedroom.
So,
for
example,
air
conditioning
becomes
very
important,
and
air
conditioning
is
of
course,
an
entire
data
center.
A
Air
conditioning
is
an
entire
industry
that
is
very
mature.
Has
its
own
vendors
has
its
own
best
practices
and
that's
something
you're
going
to
have
to
get
good
at.
On
top
of
that,
you
need
power,
and
that
can't
necessarily
just
be
the
power
that's
coming
out
the
plug
in
your
bedroom,
but
you're
probably
going
to
need
backup,
generators
and
all
sorts
of
things
again,
depending
on
the
scale
of
your
deployment.
There
can
be
smaller
deployments
that
would
work
perfectly
fine
with
with
normal
house
electricity.
A
A
Networking
is
kind
of
obvious,
both
internal
and
external,
so
your
machines
are
all
going
to
need
to
speak
to
each
other,
which
means
they're
going
to
need
networking.
You
need
switches
and
routers
and
everything
else,
but
also
externally,
you're
going
to
need
to
get
whatever
that
data
center
deployment
is
connected
to
some
sort
of
internet
connection
or
some
sort
of
connections
that
you
can
get
onto
the
internet.
A
Perhaps
most
obviously
you
need
servers
and
server
racks.
Now
all
of
you
will
have
seen
servers
and
all
of
you
will
have
seen
server
racks
either
on
television
or
in
person.
We
don't
have
time
to
go
into
it
today,
but
server
racks,
even
though
they
seem
like
you
know,
pieces
of
metal
that
you
slide
things
into
are
themselves
areas
of
great
disruption,
and
one
of
the
projects
that
we're
very
excited
about
at
the
moment
is
open.
A
19,
equinix
and
a
few
other
companies
have
open
sourced
our
chassis
designs
for
server
racks
and
we've
made
the
open
19
foundation
in
the
linux
foundation,
so
that
others
can
benefit
from
that.
But
we'll
come
back
to
it
once
you
have
a
whole
bunch
of
servers
and
switches
and
racks
and
everything
else
in
there
you're
going
to
need
data
centers
for
infrastructure
management
or
dcim
software.
A
Now
dcim
software
can
be
seen
as
a
sort
of
catalog
of
all
the
things
in
the
data
center
kind
of
metadata
service,
but
they
also
take
care
of
often
monitoring
things
like
heat
utilization
and
other
stuff.
Coming
back
to
the
networking
idea
from
earlier
you're
going
to
need
ip
addresses
and
the
last
time
I
run
a
data
center.
Well,
I
didn't
even
run
it.
I
was
part
of
running
it,
but
it
was
a
long
time
ago
and
we
used
to
track
ip
allocations
in
a
spreadsheet.
A
Now
again,
it's
not
ideal,
but
it
works
a
small
scale
when
you
get
to
larger
scale,
you're
going
to
need
ipam
software
ip
address
management,
software.
That
means
that
you're
not
giving
out
ips
to
the
wrong
people,
and
then
you
can
sort
of
defrag
the
ip
space
and
make
sure
you're
making
the
best
use
of
that.
A
What
this
basically
means
is.
I
need
to
know
how
much
you've
used
of
what
next
up
is
server
provisioning.
So,
when
you
have
all
of
the
below
in
place,
you
now
need
to
take
those
shiny,
new
boxes.
You've
got
in
your
racks
and
you
need
to
make
them
do
something,
and
that
basically
means
taking
essentially
an
inanimate
server
and
getting
it
into
a
state
that
somebody
can
use.
Now
we're
going
to
talk
more
about
this
later,
then
we
get
above
the
border
to
the
bits
that
people
are
typically
familiar
with.
A
Most
people
want
to
put
something
on
top
of
those
servers
on
top
of
the
os.
So
it
could
be.
You
have
a
virtualization
layer.
You
could
have
a
containerization
layer
exposed
through
kubernetes
whatever
it
is.
You
may
also
be
responsible
for
this
part.
Okay,
so
where
did
we
decide
to
focus
would
think
about?
Well,
tinkerbell
is
specifically
around
what
we
call
server
provisioning
internally.
We
often
call
it
bare
metal
provisioning,
but
it's
this
layer
of
the
stack
that
takes
your
servers,
which
are
networked.
They're
in
racks
they've
got
power.
A
Update
tasks
is
very
important,
perhaps
more
interestingly,
for
the
end
user
is
that
those
servers
only
become
interesting
really,
once
you
put
an
operating
system
onto
them,
very
few
people
are
going
to
be
interacting
with
these
before
they
have
an
os,
but
there's
a
few
things
you
have
to
do
before
the
os.
So,
for
example,
you
may
need
to
format
some
disks.
A
You
may
need
to
set
up
some
raid
configurations
and
a
whole
bunch
of
other
things,
then
install
an
operating
system
and
then
present
it
to
the
user
and
we're
going
to
talk
about
why
we
focused
on
that
bit
a
little
bit
later.
But
now
we're
going
to
look
at
exactly
what
tinkerbell
does
so
focused
on
the
idea
of
provisioning
servers.
A
It's
a
little
it's
a
little
bit
too
much
for
for
this
talk,
but
what
I
would
point
you
to
are
two
specific
resources.
First,
on
the
right,
alex
allis
wrote
an
incredible
blog
post
for
the
new
stack
in
2020,
where
he
talks
through
the
actual
net
booting
example
of
taking
a
server
which
doesn't
know
what
it
is
who
it
is
or
what
it's
supposed
to
do
and
get
it
into
a
state
where
we
can
deploy
an
operating
system.
A
A
So
if
you
imagine
that
you
have
a
bunch
of
servers
with
think
about
deployed
somewhere
in
that
network,
and
they
want
to
do
something-
the
first
thing
they're
going
to
do
is
boot
and
when
they
boot
they're
going
to
send
out
a
dhcp
request-
and
this
is
where
tinkerbell
gets
involved.
Tinkerbell
is
going
to
intercept
that
dhcp
request
through
a
service
called
boots,
and
it's
going
to
start
something.
A
A
The
workflows
are
relatively
simple
and
they
all
live
in
tink.
The
element
you
can
see
at
the
top
tink
will
then
say
great.
I
have
a
workflow
for
you,
but
I
need
a
way
to
be
able
to
execute
commands
on
that
machine
to
get
into
the
state
it
needs
to
be
in
which
is
where
oz
comes
into
play.
Oz
is
our
os
install
environment
and
it's
an
in-memory
operating
system
that
we
run
on
the
server
so
that
we
can
run
all
these
other
actions
until
it's
up
to
date.
A
Now
hegel
is
related
to
this,
which
is
it
provides
the
metadata.
We
need
to
understand
what
the
server
is.
What's
its,
what
what
it's
intended
to
do?
Maybe
what
some
of
the
adjacent
factors
are,
but
essentially
what
we're
going
to
do
is
just
run
ozi
on
the
server
controlled
by
tank
to
run
actions
like
I
mentioned
earlier,
which
would
be
you
know,
format
the
disks-
I
don't
know
all
sorts
of
stuff,
but
essentially
probably
install
an
operating
system
so
that
you
can
use
it
once.
A
That's
done
we're
going
to
use
the
service
pbnj
power,
boot
control
service,
to
restart
the
machine,
and
it
will
then
come
up
into
the
fleet
in
the
configuration
that
the
user
wants
it
to
be
in,
and
at
that
point
it
will
be
ready
for
use.
Now
again,
that's
a
massive
over
simplification
of
how
this
works,
but
you
can
check
out
alex
ellis's
blog
post
and
also
go
to
tinkerbell
101,
to
see
this
in
a
little
bit
more
detail.
A
So
everybody
by
now
will
be
familiar
with
the
idea
that
software
is
eating
the
world
by
mark
andreessen.
But
when
I
hear
this,
I
hear
something
else.
What
I
think
is
that
essentially
what's
happening
is
that
the
amount
of
hardware
that
can
be
eaten
by
software
is
expanding
and
then
software
is
extending
to
fill
those
gaps
now.
The
reason
why
we
want
things
in
software
is
obvious.
It
means
we
can
experiment
more
quickly.
It
means
that
we
can
share
our
work.
A
It
means
that
we
can
build
on
the
work
of
others,
but
when
we
were
looking
at
the
stack
for
tinkerbell,
we
specifically
thought
well
a
lot
of
those
other
areas
have
reasonable
solutions
already
or
are
too
far
away
from
the
user
to
be
interesting.
So
how
do
we
open
up
that
next
bit
of
surface
area?
That
people
will
be
interested
in
hacking
on
now?
A
related
question
to
this
is
well,
then,
why
would
we
submit
it
to
the
cncf?
A
Well,
so
we
open
sourced
it
in,
I
believe,
may
of
2020,
and
we
didn't
get
into
the
cncf
sandbox
until
something
like
october
or
september
september
october,
maybe
november.
I
can't
remember
end
of
2020.
the
reason
why
we
wanted
to
do.
This
is
pretty
clear
if
you're
going
to
be
the
piece
of
software.
This
is
that
is
this
critical
to
your
stack.
A
You
need
to
know
that
the
project
you're
relying
on,
has
open
governance
and
you
can
get
a
c
at
the
table
to
influence
the
roadmap.
You
know
I'm
sure
there
are
libraries
out
there,
that
people
use
every
single
day,
they're
open
source,
and
they
don't
really
think
about
the
governance
model
that
much.
A
But
if
it's
the
software,
that's
going
to
turn
your
servers
into
something
your
users
can
use,
then
you're
going
to
care
about
that
a
lot,
and
I
can
talk
later
about
the
incredible
uptick
in
adoption
that
we've
seen
in
the
cncf,
but
broadly,
that's
why
we
wanted
to
make
that
that
decision
all
right,
so
we've
gone
from.
Why
would
anyone
run
their
hardware
in
the
first
place?
We've
seen
how
people
running
their
own
hardware
are
actually
the
beginning
of
a
new
curve
of
adoption.
A
So
you've
heard
me
say
operating
systems
a
lot
of
the
time,
and
that
is
just
one
of
those
key
workloads
that
we
enable
is
getting
a
server
to
the
point
where
you
can
put
an
operating
system
onto
it,
and
we've
done
a
lot
of
work
in
q1
2021
to
make
the
process
for
adding
new
operating
systems
a
lot
easier,
and
what's
that,
what
that's
meant
is
that
we
can
now
install
pretty
much
anything
you
want
now
out
of
the
box.
You'll
see
red
hat
windows,
server,
debian
flat
car
centos
ubuntu
nexus.
A
I
believe
alma
linux
is
in
the
works
and
there
are
a
few
others
as
well.
But
the
reason
why
that's
happened
is
because
of
the
crocodile
project
and
you'll
see
down
there.
The
github
link
for
the
crocodile
project
now
crocodile
is
a
tool
that
makes
it
a
lot
easier
to
package
and
deploy
operating
systems
using
tinkerbell
to
the
point
where,
once
we
get
the
first
few
working,
it's
often
less
than
a
day's
work
to
get
the
next
ones
working.
A
A
Now
as
we're
working
on
tinker
bell
with
the
community.
One
of
the
fantastic
things
we've
seen
is:
the
community
has
allowed
us
to
see
where
the
pain
points
are
both
getting
getting
started,
but
also
with
implementing
extensions
to
think
about
whether
it's
workflows
or
working
with
core
products
itself
hook
is
a
drop-in
replacement
for
ozy.
A
So
you
remember
earlier,
I
spoke
about
oz,
which
is
our
in-memory
operating
system,
where
we
can
run
all
the
actions
that
allow
us
to
run
the
workflows
to
get
the
server
from
the
status
and
to
the
server
it
needs
that
sorry
to
the
state
it
needs
to
be
in,
and
the
results
have
been
incredible.
We've
made
it
so
that
we
can
now
deploy
in
something
like
10
of
the
time
previously.
A
Now
you
remember
earlier,
when
I
spoke
about
workflows,
workflows
in
tinkerbell
are
essentially
the
actions
that
tink
runs
in
ozy
to
get
your
server
from
being
a
server
to
something
that
people
can
actually
use,
and
those
workflows
consist
of
atomic
elements
called
actions
and
each
action
is
essentially
a
docker
container.
That
runs
something
now.
One
of
the
things
that
we
were
very
excited
about
early
on
was
making
it
so
that
these
actions
could
be
contributed
to
in
the
public
and
that's
why
we've
now
have
what
we
call
action
hub.
A
It's
hosted
on
the
cncf
artifact
hub,
and
what
this
allows
people
to
do
is
to
compose
workflows
of
known
public
actions.
They
can
also
extend
them,
they
can
add
their
own,
and
this
is
already
opening
up
a
huge
amount
of
energy
around
building
out
new
actions,
improving
existing
actions,
and
it's
all
very
similar
to
the
docker
hub.
You
know
you
you
can
you
can
use
one
of
our
actions.
You
can
extend
it.
I
think
one
of
the
other
areas.
A
A
It's
been
amazing
to
see
the
difference
between,
let's
say
december,
20,
20
and
now
in
the
sheer
number
of
contributions
we're
getting
from
companies
outside
of
equinix
metal,
and
it
looks
like
if
we
keep
tracking
the
way
we're
tracking
right
now
we're
going
to
hit
parity
with
internal
external
within
about
two
months,
and
we
also
have
some
big
announcements
around
certain
logos,
etc.
That
are
coming
on
board.
So
look
forward
to
that.
Okay,
so
I
realized
that
was
a
bit
of
a
whistle-stop
tour.
A
Let
me
give
you
some
information
on
how
to
learn
more
or
to
get
involved.
So,
first
and
foremost,
we
have
a
community
slack
at
equinix
medal
slack.metal.com
in
the
tinkerbell
channel.
You
can
sign
up,
that's
where
we
have
a
lot
of
our
live
conversations
around
things
we
also
have
community
calls,
I
believe,
they're
bi-weekly,
and
we
have
them
in
u.s
and
eu-friendly
time
zones.
A
If
you
go
to
the
google
group,
that's
listed
there
and
all
of
this
will
be
sent
out
on
the
pdf
slides
afterwards,
so
you
can
get
the
links
without
having
to
screenshot
this
and
type
it
in.
You
can
join
those
github.
Obviously,
tinkerbell
is
the
org.
You
can
find
all
the
microservices
within
their
own
documentation,
twitter,
it's
a
good
place
for
news
youtube
channel.
A
You
will
find
not
only
the
recordings
of
our
previous
community
calls,
but
also
some
of
the
101s
and
other
educational
content
that
we've
got
coming
up
soon
and
then,
if
you
want
to
email
us,
you
can
email,
hello,
tinkerbell.org.
That
goes
to
me,
I
think
dan,
a
couple
of
other
people,
but
you
get
a
response
pretty
quickly
and
on
that
last
one
tinkerbell.org
is
the
main
website.
A
We've
done
a
phenomenal
amount
of
work
on
documentation
in
the
last
few
months
and
it's
really
in
a
state
now
where
people
can
very
easily
get
from
zero
to
hero.
So
to
say
now
a
lot
of
people
don't
have
a
data
center
at
home.
So
one
of
the
other
things
we
did
is
created
a
local
vagrant
installation
that
you
can
run
you're
going
to
need
a
bit
of
ram,
I
think
at
least
16
gig.
But
then
you
can
run
your
own
tinkerbell
setup
where
you
can
have
it.
A
You
know
the
tinkerbell
stack
plus
some
sort
of
example
servers.
You
can
see
how
the
workflows
work,
how
you
can
insert
different
options.
There
configure
some
of
the
way
that
things
are
deployed
and
see
how
you
can
also
take
servers,
in
this
case
virtual
to
being
useful
by
installing
operating
systems
onto
them.
A
Last
but
not
least,
we
also
have
the
sandbox.
So
there
are
a
lot
of
different
different
microservices
within
within
tinkerbell,
and
it
was
a
little
unwieldy
for
people
at
first
to
be
able
to
figure
out
exactly
how
to
get
it
all
working
together.
So
we
introduced
the
sandbox.
The
sandbox
is
a
known
good
state
of
all
the
microservices
that
you
can
run
together
to
make
sure
that
you
know
they're
tested,
and
I
believe
this
is
also
where
the
vagrant
is
pinned
to.
A
So
you
can
try
that
out
locally
easily
without
having
to
crack
out
some
servers
in
your
bedroom,
and
that's
it
like,
I
said,
you've
got
all
the
contact
details.
If
you
want
to
talk
to
me
personally,
it's
mark.holmer
eu.iconics.com,
I'm
a
mr,
mr
coleman
on
twitter
and
if
you
go
into
the
aforementioned
equinix
metal
community
slack-
and
you
can
find
me
on
the
mark.metal.