►
Description
Spinnaker Workshop Part Four - AWS Quick Start - Thomas McGonagle, Armory
Join industry experts who will lead talks focusing on several key and core items that will give you an overview of the breadth of the power of the Spinnaker platform. In this interactive workshop, you will learn about:
How to quickly leverage Spinnaker for a single path from staging to deployment, regardless of whether you are deploying to Amazon EC2, Amazon EKS, Amazon ECS, or AWS Lambda.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
What
is
an
aws
quickstart?
You
might
ask.
Well
it's
an
automated
gold
standard
deployment
in
the
aws
cloud
and
that's
what
we've
crafted
an
armory
recrafted,
an
automated
gold
standard,
spinnaker
deployment
in
the
aws
cloud,
and
now
who
am
I
I'm
thomas
mcgonagall,
I'm
a
cloud
partner
solutions,
architect,
and
if
you
want
to
learn
more
about
me,
you
can
go
to
linktree
mcgonagall.
A
I
have
my
linkedin
if
you
want
to
become
linkedin
buddies,
and
I
have
my
my
own
personal
readme,
it's
all
about
myself
and
who
I
am
and
what
it's
like
to
work
with
me
up
on
my
link
tree.
I
invite
you
to
check
that
out
so
just
to
set
the
stage.
I
wanted
to
talk
about
the
three
industrial,
the
three
industrial
revolutions
and
the
first
one
was
the
the
the
steam
engine
and
the
steam
engine
enabled
the
creation
of
big
factory
towns
and,
as
you
can
see,
the
the
bottom
of
it
is
lol.
A
Mills
and
lol
is
a
place
in
massachusetts.
I'm
based
out
of
massachusetts,
it's
actually
quite
close
to
lowell
and
lowell.
Is
this
old
city
with
all
with,
like
hundreds
of
mills,
these
huge
monstrous
mills
and
these?
What
would
what
powered
these
mills
was?
Water,
power
and
steam
engine
power?
And
this
that
was
the
first
industrial
revolution?
A
And
then
the
second
industrial
evolution
was
automation
and
the
assembly
line
and
the
assembly
line
brought
reliability
and
the
need
for
automation
and
standardized
tooling
brought
together?
What
what?
What
is?
What
we're
trying
talking
about
today?
It's
automation
and
tooling,
and
automation
and
tooling,
enabled
the
second
industrial
revolution-
and
this
is
this.
A
This
picture
is
of
a
factory
churning
out
b24
bombers
and
during
the
the
during
world
war
ii,
these
b-24
bombers
enabled
air
power
to
help
when
the
world
war
ii
and
these
b-24
were
made
up
of
450
000
parts
with
360,
000,
rivets
and
550
sizes
and
weighed
18
tons,
and
the
assembly
line
standardized.
All
these
parts
and
all
these
rivets
and
all
these
components
into
this
one,
cohesive
product
and
I'll,
be
getting
back
to
the
b24
in
just
a
couple
minutes.
A
A
Well,
it's
tools
and
automation,
and
that's
what
we're
talking
about
for
the
remainder
of
this.
This
workshop
we're
talking
about
the
tools
and
automation
that
the
quickstart
provides
and
the
cloud
formation
that
it
utilizes
and
the
infrastructure
has
code
that
it
provides
and
creates
and
makes
so.
Automation,
tooling,
is
how
you
tame
complexity.
A
So
that's
just
something
that's
going
to
keep
coming
up
and
up
and
up
throughout
the
rest
of
this
workshop
is
automation
and
tooling
is
how
you
tame
complexity
and
that's
what
we're
trying
to
do
with
the
quick
start.
We're
trying
to
have
this
quick
start
environment
to
provision
armory
enterprise
in
a
in
as
speedy
and
fast
as
a
way
as
possible,
with
with
a
best
practices
infrastructure
in
aws.
A
So
I
just
wanted
to
to
to
just
mention
that
the
b-24
automation
story
is
an
important
one
to
me.
My
grandfather
was
a
bombardier
captain
and
he
flew
over
54
combat
missions
in
the
termite.
This
is
a
picture
of
him
from
world
war
ii
and
the
the
chance
of
surviving
54
combat
missions
is
one
percent.
So
the
thanks
to
the
automation
and
the
assembly
line
and
the
the
work
that
was
done
in
the
in
the
factories
in
in
michigan
that
were
churning
out
the
b-24s.
A
My
grandfather
survived,
and
I'm
here
to
tell
this
story
today
and
my
grandfather
was
highly
decorated.
He
actually
got
the
flying
cros
the
distinguished
flying
cross
because
he
landed
without
without
landing
gear,
and
that
was
once
again
thanks
to
the
workmanship
and
the
the
incredible
craftsmanship
of
the
factory
workers.
Turning
up
the
b24,
so
aws
quick
start
just
to
recap:
what
are
they
they're,
instead
of
rather
manually
configuring,
all
the
ones
of
a
solution?
A
Customers
can
simply
deploy
a
quick
start
which
uses
infrastructure
as
code
to
automate
the
deployment
so
we're
using
cloudformation
as
the
infrastructure
as
code
to
automate
the
deployment
of
of
a
armory
enterprise
distribution,
and
so
what
is
the
armory
quickstart?
Well,
the
quickstart
helps
you
deploy
popular
technologies
on
aws,
based
on
aws
best
practices
for
security
and
high
availability.
These
accelerators
reduce
hundreds
of
manual
procedures
into
just
a
few
steps
so
that
you
can
build
your
production
environment
in
minutes
and
start
using
it
immediately.
So
it's
this
quick
start.
A
Each
cloud
formation,
each
quickstart,
includes
aws
cloud
formation
templates
that
automate
the
deployment
and
guide
that
describes
the
architecture
and
provides
deployment.
Instructions
quick
starts
give
customers
an
easy
way
to
deploy
complex
software
and
services
on
top
of
aws
infrastructure
and
automation.
A
A
As
a
quick
start,
we
answered
a
few
simple
questions
and
then
we
went
through
the
development
process
of
engineering,
the
cloud
formation
with
our
partners
in
our
in
in
at
aws,
and
then
we
we
are
launching
today
the
quick
start
infrastructure,
so
that
is
available
to
the
entire
spinnaker
summit
audience
so
that
they
can
start
using
the
quick
start.
You
can
contribute
to
the
quick
start
and
can
assist
us
with
it.
You
can
create
something
really
really
grand.
A
A
What
we
are
doing
is
we
are
using
a
vpc,
a
virtual
private
cloud
and
the
vpc
is
made
up
of
of
three
availability
zones.
It
has
elastic
ips,
it
has
not
gateways
and
not
instances
and
has
internet
gateways,
and
it
has
public
shares
public,
subnets
and
private
subnets,
and
this
infrastructure
is
all
captured
because
we're
able
to
reuse
the
vpc
quick
start
in
our
quick
start.
So
so
as
part
of
our
quick
start,
we're
launching
the
vpc
quick
start.
A
Similarly,
there's
an
eks
component
and
so
we're
running
our
armory
enterprise
quickstart
inside
of
an
eks
infrastructure,
an
eks
cluster
and
that
eks
cluster
is
provisioned
very,
very
similarly
to
the
the
the
vpc.
So
the
vpc
gets
provisioned
first
and
the
eks
cluster,
with
its
bastion
hosts
and
snack
gateways
and
three
availability
zones.
Since
kubernetes
infrastructure
get
provisioned
on
top
of
the
vpc
and
then
there's
aurora.
We
have
an
aurora
database
for
back
end
persistence
and
this
aurora
has
a
bastion
host.
A
It
has
aurora
instances
and
so
forth
that
we're
provisioning
and
then
we
have
spinnaker
spinnaker's
microservice
architecture
sits
inside
the
eks
cluster
and
we're
provisioning.
This
eks
cluster
on
top
of
oxygen
refrigeration
spinnaker
on
top
of
the
gts
cluster,
which
just
sits
on
top
of
the
vpc
which
utilizes
aurora.
So
there's
a
tremendous
amount
of
complexity
in
this
infrastructure,
and
then
this
is
a
diagram
from
our
documents,
and
this
is
the
complete
infrastructure.
This
is
the
complete
solution.
A
This
is
the
vpc
with
the
three
availability
zones,
the
bastion
hosts,
the
kubernetes
cluster,
our
armory
operator.
We
are
using
the
armory
operator
to
install
the
into
the
eks
cluster
and
then
and
then
and
so
on.
So
what
so?
I
keep
mentioning
this
cloud
formation
for
anyone
who's
not
familiar
with
it.
It's
an
easy
way
to
create
and
manage
a
collection
of
aws
resources.
It
allows
orderly
and
predictable
provisioning
and
updating
of
resources.
It
allows
you
to
version
control
your
aws
infrastructure.
A
It
allows
you
to
deploy
and
update
stacks
using
console
command
line
or
api,
and
you
only
pay
for
the
resources
you
create,
and
so
just
to
just
summarize,
you
can
provision
using
cloud
information
using
the
aws
console.
You
can
use
provision
using
command
line
or
you
can
use
provision
using
an
api.
We
can
version
control
our
aws
infrastructure.
We
could
have
a
version
one
of
spinnaker.
We
could
have
a
version,
two
of
armory
enterprise.
We
could
have
a
virgin,
3
and
so
forth.
We
have
orderly
and
predictable
provisioning
and
updating
of
resources.
A
And
so
what
are
some
of
the
benefits
of
cloud
formation?
Well,
it
allows
you
to
automate
best
practices.
It
allows
you
to
scale
your
infrastructure
worldwide
and
it
allows
you
to
integrate
with
other
aws
services.
It
allows
you
to
manage
their
party
and
private
resources.
It
allows
you
to
extend
confirmation
within
the
community.
It's
released
as
open
source,
and
so
that's
a
critical
feature
is
that
you
could
take
our
cloud
formation
and
our
quick
start
and
extend
it
for
your
purposes
and
it
provides
a
step-by-step
deployment
guided.
A
It
is
and
I'll
be
digging
into
that
a
little
bit
later,
but
it's
documented.
It's
documentation.
The
cloud
formation
because
of
its
infrastructure
as
code
back
basis,
allows
you
to
document
and
specify
the
the
infrastructure
as
a
deployment
guide.
It's
a
it's
self-documenting.
In
other
words,
this
is
one
of
my
favorite
examples
of
amazon,
eks
quickstart.
A
This
is
a
a
aws
qs
kubernetes
resource
definition
and
then,
as
you
read
from
top
to
bottom,
there's
a
properties
there's
a
cluster
name.
This
is
the
cluster
name
of
the
eks
cluster.
We
have
a
namespace,
we're
defining
it
default.
We
have
a
manifest
definition
and,
in
this
manifest
definition,
we're
defining
a
config
map,
and
so
this
is
something
that
we
use
heavily
in
our
quick
start.
We
use
the
amazon,
aws
qs
kubernetes
resource,
which
provisions
kubernetes
resources
into
an
eks
cluster.
A
This
is
the
aws
qs
kubernetes
helm
resource,
and
this
allows
you
to
define
helm
resources
in
in
one
helm,
chart
against
your
a
against
your
eks
cluster,
using
just
this
cloudformation
defined
template
and
it's
very,
very
powerful.
You
can
package
up
your
your
your
your
software
into
helm,
charts
and
then
you
can
run
them
and
and
install
them
into
an
infrastructure
into
an
eks
infrastructure
in
an
automated
infrastructure
as
code
way.
B
A
A
So
I
keep
talking
about
the
in
the
principles
of
infrastructure
code,
but
I
just
wanted
to
call
these
out.
These
are
the
best
some
of
the
principles
of
cloud
formation
and
you
get
modularity.
The
services
are
small
and
simple.
You
get
cooperation,
so
me
and
my
colleagues
were
able
to
foster
continuous
improvement
through
the
cooperation
of
the
definition
of
these
cloud
formation
templates.
A
You
get
services
are
like
building
blocks,
and
so
we
we
snap
together
the
vpc
and
the
eks,
and
we
snap
together
the
other,
the
other
components
all
together
into
one
big
cloud,
information,
quick
start,
and
that
was
done
through
the
composability
of
cloud
formation.
We
get
a
sensibility,
we
can
modify,
enhance
and
improve,
and
that
is
one
of
our
call
to
actions
is
asking
everyone
here
to
consider,
testing
and
and
submitting
poll
requests
to
our
cloud
formation,
quickstart
and
improving
it.
A
A
We
don't
have
to
really
worry
about
the
implementation
details,
we're
just
working
within
the
cloud
formation,
language,
the
em
mode
of
json
and
defining
these
abstractions
and
then
cloud
formation
takes,
takes
control
and
generates
all
the
different
infrastructure
and
once
again
it's
a
vpc
and
an
eks
cluster
and
an
aurora
database
and
the
spinnaker
installation,
armory
enterprise,
spinnaker
installation,
and
then
we
have
item.
Potence
action
should
only
be
taken
once
and
then
finally,
convergence
over
time.
The
system
tends
towards
correctness,
and
so
what
are
the
benefits
of
this
infrastructure
as
code
with
automation?
A
Well,
it's
repeatable.
We
can.
We
can
provision
a
thousand
ten
thousand
twenty
thousand
of
these
eks
clusters
with
spinnaker
with
armory
enterprise
spinnaker
installed
on
them.
We
get
agility,
we
have
we,
we
allow
engineers
to
move
forward
or
backwards.
We
can
version
control,
we
can
move
and
we
can
have
version
infrastructure
and
we
can
version
control
any
aspect
of
the
infrastructure.
So
we
can
do
the
vpc
or
we
can
do
we
conversion
control
the
eks,
so
we
can
version
control
the
aurora
or
whatever
we
get
scalability
repeatability
plus
automation
makes
scalability.
A
I'm
just
going
to
repeat
that
one
again,
I
think
this
is
my
favorite
one.
Repeatability
plus
automation
makes
for
scalability.
We
have
this
highly
scalable,
repeatable
automated
infrastructure
and
then
once
again
reassurance
documentation
the
cloud
formation
and
the
infrastructure
as
code
confirmation
technology
allows
for
documentation
of
the
of
the
infrastructure
we
have.
A
We
have
the
all
the
different
all
of
the
hundreds
of
components
that
make
up
the
vpc
and
the
eks
and
the
aurora
and
the
in
the
in
the
armory
enterprise
distribution
are
are
documented
and
finally,
we
have
disaster
recovery.
If
we
have
a
problem,
we
can
spin
up
this
infrastructure
again
and
again
and
again
we
can
configure
it
and
install
it
in
different
environments
and
for
different
purposes
and
have
and
and
have
it
in
different
availability
zones
and
so
on.
A
So
what
is
automation's
impact?
Well,
it
improves
speed.
We
can
deploy
workloads
faster,
it
creates
predictability.
We
reduce
risk
of
human
error,
we
provide
management,
we
have
essentially
governed
disparate
workloads.
We
have
increased
responsiveness,
we
can
scale
readily
with
demand.
We
can
foster
collaboration,
communicate
and
collaborate
better.
A
So
once
here's
the
call
one
of
the
calls
of
the
action,
how
do
we
get
involved?
Well,
you
can
contribute
code.
This
is
an
open
source
project.
This
is
an
open
source
attempt
at
infrastructure
as
code
to
spin
up
armory
enterprise,
and
you,
as
a
participant
in
spinnaker
summit,
are
welcome
and
and
encouraged
to
help
out
with
this
project
and
to
to
to
to
participate
as
a
member
of
the
community.
A
What
are
some
of
the
best
practices
for
quick
starts?
So
if
you
do
decide
to
facil
help
out
with
the
quick
start,
you
can
read
the
contributors
guide
you
can
use
id
use
an
ide
with
one
thing.
Visual
studio
code
has
a
great
easy
to
install
cloud
formation.
Linker,
there's
a
workshop
that
you
can
use.
You
can
store
all
assets
in
the
same
repo.
A
A
So
what?
If
you
want
to
log
in
to
an
upgrade
spinnaker?
Well,
this
is
an
example
of
the
output
section
of
our
quickstart
and,
as
you
can
see,
we
have
a
bastion
ip
address.
We
have
a
fashion
security
group,
we
have
an
eks
cluster
name
and
we
have
an
a
node
group
security
group
and
then
a
spinnaker,
extremely
armory
enterprise
connect,
ui
address
and
what
we
can
do
with
this
is
we
can
log
into
the
bastion
host.
A
We
can
connect
up
to
the
bashed
host,
using
a
key
that
we
specify
as
part
of
the
quick
start,
so
a
paint,
a
dot,
pem
file
key.
We
can
specify
that
and
we
can
connect
to
it
and
then
what
we
can
do
is
we
can
go
into
and
download
the
spinnaker
customize
patches
from
armory
and
we
can
edit
the
version
of
the
of
the
patch
version.yaml
core
config
spinner
customize
patches
config
file,
and
we
can
edit
that
and
we
can
configure
the
the
diversion
to
and
change
it.
A
And
then
we
can
run
cube,
cuddle,
apply,
minus
k,
dot
inside
the
spinnaker
customize
patches
directory,
and
then
that
would
re-provision
all
the
microservices
with
a
with
a
newer
version
of
the
of
these
of
the
armory
enterprise
distribution,
and
you
can
then
are
you
are
then
free
to
configure
and
command
and
control
your
spinnaker
instance
using
the
bastion
host.
Just
like
you
would,
if
you
had
provisioned
this
infrastructure,
the
eks
infrastructure,
the
vpncs
in
the
aurora
database.
A
Once
again,
if
you'd
like
to
get
involved,
we
highly
highly
encourage
you
to
get
involved.
The
url
for
the
the
armory
enterprise
quickstart
is
here
down
at
the
bottom.
It's
github.com
aws,
quickstart,
quickstart
armory
spinnaker,
and
we
look
forward
to
your
participation
and
we
thank
you
for
your
time
and
your
energy,
and
we
wish
you
a
very,
very
nice,
finicker
summit.
Thank
you
very
much.
A
To
that
very
controversial
question,
I
just
wanted
to
say
a
huge
thank
you
to
my
my
project
partner
in
the
quick
start,
peter
blinn,
strubus
he's
a
gentleman
and
he's
he's
just
been
a
joy
to
work
with
and
and
and
a
really
wonderful
person.
And
why
was
why
and
then
I'm
going
to
also
thank
our
project
partner
at
aws,
andrew
gargan.
He's
he's
also
a
gentleman
and
a
and
a
tremendous
asset
to
work
with,
but
why
was
it?
Why
is
it
so
important
to
say?
Thank
you.
A
I
at
the
beginning
of
this
project
went
through
probably
the
biggest
crisis
of
my
life.
My
my
son
was
born
three
months
premature
and
I,
when
we
were
able
to
get
this
project
over
the
finish
line
through
through
the
help
of
of
peter
and
through
the
help
of
andrew-
and
I
just
have
been
so
indebted
to
them-
and
I
just
wanted
to
say
thank
you
at
the
beginning,
while
we're
trying
to
figure
out
whether
hot
dog
is
a
sandwich
or
a
taco,
and
so
we
we
have.
A
We
have
some
answers
coming
in.
We
are
seeing
some
answers
around
taco
and
and
and
we're
seeing
some
answers
around
gyros,
which
is
a
great
answer.
Stephen
rachel
believes
it's
a
sandwich,
but
in
all
seriousness
I
I
do
want
do
you
have
some
things
other
things
to
cover?
I'm
gonna,
let
the
the
answers
to
that
controversial
question
keep
coming
in
and
while
I'm
doing
that,
I'm
gonna
answer
vignect's
question
is
the
caching
solution,
the
architecture,
redis
etc.
A
A
If
anyone's
familiar
with
that
design,
where
you,
you
use
basically
the
redis
cache
of
tasks
and
you
use
the
mysql
aurora
database
for
everything
else,
and
we
we
make
we
we
we
tried
to
be
as
prescriptive
as
possible.
But,
as
I
mentioned
at
the
end
of
the
presentation,
you
can
use
the
customize
patches
scripts
to
configure
and
manage
the
spinnaker
installation
once
it's
stood
up
and
it's
trivial.
A
Frankly,
it's
10
minutes
worth
of
work
to
set
up
to
you
to
if
you,
if
you're,
very,
very
prescriptive
about
redis-
and
you
only
want
to
use
redis
and
you
want
to
use
redis
in
cluster
you're.
More
than
welcome
to
do
that
or
if
you
want
to
use
redis
outside
of
the
cluster
and
use
the
the
aws
redis
product,
you
can
do
that
or
you
can
use
mysql
for
everything
and
you
can
use
aurora
for
everything.
So
so
we
give
you
those
options.
A
A
Let's
see
if
there's
any
chat,
so
so
we're
getting
a
lot
of
sandwiches,
I
I
tend
to
agree
with
the,
but
I
do
believe
it's
a
sandwich.
You
know
a
couple
pieces,
it's
a
piece
of
meat
with
some
bread.
On
the
other
side,
I
I
do
tend
to
kind
of
agree
with
that.
One
or
a
year
right
then
nate
nada,
they
read
corrected
me,
it's
actually
a
gyro
and
I
call
it
a
gyro.
That's
like
a
northeast
thing.
A
I
think
nate
is
based
out
of
michigan
and
so
that
offended
his-
I
guess
greek
ancestry-
maybe
or
something-
and
so
you
know,
do
we
have
any
other
questions
and
answers,
if
not
I'm
going
to
cover
some
kind
of
housekeeping
and
I'm
going
to
keep
an
eye
out.
Oh
so
here
here
comes
a
question
from
vignect
again
is
a
horizontal
pod
scaling
using
hpa
supported
for
spinnaker
pods,
and
so
that's
a
that's.
A
great
question
and
my
understanding
is
is
is
hpa,
is
not
supported
for
spinnaker
pods.
B
A
Going
to
just
quickly
jump
into
some
housekeeping,
you
know,
in
addition
to
this
talk,
I'm
giving
a
talk
on
something
called
compliance
operations,
comp
pops
and
that's
on
thursday.
That's
a
lightning
talk,
and
then
we
have
our
birds
of
us
of
a
feather
spinnaker
at
scale
and
we
have
industry.
We
have
aws
personnel
that
are
going
to
be
there.
That's
on
thursday
june
24th
at
255
edt,
and
then
I
did
want
to
call
everyone's
attention
to
that.
A
We
have
a
fireside
chat
with
jeff
barr
and
cody
powell
from
snap
and
jeff
is
from
aws
he's
the
he's
kind
of
a
big
shot
he's
their
their
chief
evangelist
and
and
then
cody's
a
big
shot
in
his
in
his
own
right
and
he's
the
the
infrastructure
engineer,
senior
infrastructure,
engineer
manager
at
at
snap
and
we're
gonna.
Have
this
really
really
outstanding
conversation?
I'm
gonna
be
to
be
perfectly
blunt,
I'm
I'm
very,
very
excited
about
it.
A
I'm
going
to
be
asking
them
questions
like
is
devops
dead
and
I'm
going
to
be
asking
them
questions
like
you
know.
If
you
could
have
a
sandwich,
what
would
it
be
stuff
like
that?
Just
very
important
questions
for
for
the
for
our
participants
in
our
firestar
chat,
and
that
is
on
july
1st
and
that's
at
11
a.m.
Edt
and
then
I'm
just
looking
over
my
notes.
A
We,
we
also
have
a
workshop,
an
aws
workshop,
where
you
can
do
things
like
blue
green
deployments
and
scale
up
and
roll
back,
and
I
will
we'll
be
making
that
available.
You'll
have
to
come
by
our
our
booth,
that's
the
armory
booth,
I'm
a
I'm
wearing
my
armory
shirt.
If
anyone
doesn't
doesn't
notice
well,
we
have
our
armory
booth
and
we
have
information
the
slick
sheet
or
this
glossy.
A
You
know
two-sided
marketing,
slick
sheet
that
we
can
hand
out
to
you
with
other
information
on
what
we're
doing
and
why,
why
we're
doing
it
and
how
we're
working
with
aws
and
all
the
kind
of
cool
things
that
we're
doing-
and
I
just
wanted
to
say
thank
you
very
much
and
then
so.
There
is
an
anonymous
question
and
it's
our
albs
supported
in
spinnaker
and
they
sure
are
so
we
we
are
leveraging
eks,
and
so
you
can
use
an
elb.
A
You
can
use
an
alb
in
in
the
eks
cluster
and
wire
that
up
to
the
eks
cluster,
that's
part
of
the
kind
of
secret
sauce
that
the
elastic
kubernetes
service
provides
provides
to.
You
is
the
ability
to
use
the
the
I
guess.
How
would
you
describe
it,
the
the
load
balancers
from
amazon
and
if,
if
you
have
any
other
follow-up
questions
anonymous,
please
let
please
let
us
know
it's
been
a
tremendous
pleasure
being
here.
A
Everyone
and
I
think
I
can
just
get
cut
off
in
like
a
minute-
I'm
not
really
sure
what
happens
like.
So
I'm
just
saying
my
goodbyes
and-
and
it
please
please
and
I'll,
put
in
my
my
my
my
my
link
tree
again
so
that
if
you
want
to
get
in
touch
with
me
you're
more
than
welcome
to
I
love
making
from
new
friends-
and
I
love-
I
love
people,
and
so,
if
you
want
to
become
linkedin
friends,
please
please
reach
out
to
me
and
we
can
have
a
comment.