►
From YouTube: Alliances Solution Index
Description
The Alliance Solution Index is intended to serve as a catalog of joint solutions (GitLab + XYZ platform/tool/framework/etc) that have been vetted by GitLab SA's. The goal is to have a specific location to store informative and useable technical content thats related to our alliance and ecosystem partners
A
Hi
everyone
welcome
to
another
episode
of
cs
skills
exchange.
We
have
a
very
interesting
topic,
I'm
very
curious
about
this
topic
as
well
about
alliance's
solution
index
and
kurt,
and
darwin
are
going
to
leave
the
conversation
with
us
among
a
few
other
panelists,
so
kurt
I'll,
let
you
get
started
and
take
it
away.
B
Great
wonderful
thanks,
everyone
for
coming
out
and
attending
this
session
today.
My
name
is
kurt
tusak,
I'm
a
solutions
architect
on
the
alliances
team.
I'm
gonna
go
ahead
and
start
my
screen
share
and
we'll
get
right
into
the
session
this
morning
or
this
afternoon,
depending
on
where
you're
located.
So
again,
today's
session
is
going
to
be
about
the
alliance
solution
index
and
so
just
to
give
an
overview,
we're
going
to
talk
about
who
are
alliance
essays.
What's
the
solution
index,
what
we're
doing?
B
You
know
that
there's
many
different
places
of
finding
information
so,
whether
that's
youtube,
google
drive
slide
decks
all
sorts
of
different
popping
projects.
Things
like
guided
explorations,
which
is
a
big
repository
of
solutions
that
darwin
has
put
together.
We
in
the
alliance's
team,
we
made
our
own
attempt
at
creating
kind
of
a
card,
catalog
of
solutions,
and
so
there's
you
know
with
all
these
different
formats
of
data
and
levels
of
accessibility
and-
and
you
know,
disparate
systems.
B
The
alliance's
essays
I
showed
on
the
previous
page,
where
each
one
of
us,
with
our
respective
scope,
is
responsible
for
curating
the
links
and
content
and
managing
the
tagging
and
categorization
of
that
content,
so
that
it
ends
up
in
high
spot
so
that
it
ends
up
under
this
alliance's
essay
collateral
page
and
then
is
ultimately
available
to
be
consumed
by.
You
know
the
our
broader
peers,
both
solution,
architects,
customer
success
and
then
the
broader
overall
sales
organization.
B
So
if
we
ask
why
a
high
spot,
I
know
it's,
it
probably
seems
like
another
tool.
We
have
to
consume
and
there's
lots
of
these
that
are
being
added
but
high
spot
added
value
in
several
specific
instances.
First
and
foremost,
we
get
traffic
metrics,
so
we
have
a
very
clear
understanding
of
what
people
like
to
see
what
generates
the
most
activity,
what's
the
the
highest
interest
and
that
allows
us
to
basically
create
a
feedback
loop
and
that
informs
our
future
solutions.
B
B
B
If
we
have,
you
know,
gitlab
unfiltered
and
you
know
various
issue
boards
I
mean
if
you
try
and
do
a
keyword
search
across
get
lab
issues,
it's
more
or
less,
not
super
effective
or
you
get
an
avalanche
of
data
across
again
literally
hundreds
of
thousands
of
issues
that
you're
searching
and
a
lot
of
that
stuff
is
not
really
relevant
for
your
use
case.
So
the
idea
is
that
we
want
to
create
a
first
place
to
look
for
customer
success.
B
So
hey
do
we
have
a
integration
with
xyz
platform
or
do
we
have
any
relationship
with
abc
company?
Usually
those
questions
are
floated
in
the
alliance's
channel
or
in
a
customer
success
channel
and
that's
okay,
but
just
the
async
nature
of
our
company.
You
know
even
somebody
asked
today.
Somebody
in
apac
asked
about
openshift
at
4am
like
well.
Hopefully
somebody
can
answer
that.
I
think
vladimir.
B
You
responded
to
that
question,
which
is
great
for
somebody
who's
in
another
region,
but
if
somebody's
say
waiting
on
a
response
from
me
or
waiting
on
a
response
from
a
tiff,
it
may
be
hours
or
in
some
cases
days
before
the
right
person
would
see
that
information
so
again
having
a
unified
place
to
just
say.
Well,
let
me
punch
in
the
keyword
of
the
thing
I'm
looking
for,
and
at
least
I'll
have
a
general
understanding
of
if
something
like
that
exists
and
and
what
we
might
have.
B
B
So
as
our
alliance's
team
grows,
as
we
add
additional
alliances
as
we
get
decent
coverage
on
the
alliance
as
we
have
now,
and
we
expand
into
new
technology
partners
and
as
our
ecosystem
footprint
expands,
we're
going
to
keep
curating
this
right.
That's
kind
of
the
purview
of
the
alliance's
essay
team
is
to
kind
of
keep
a
curated
and
well-managed
list
of
solutions
that
either
have
expiration
dates
on
content
or
has
been
freshly
loaded
in
has
been
vetted
by
us
and
again
is
being
backed
by
our
specific
alliance
agreement.
B
So
you
know
that
if
something
is
in
there
that
it's
well
supported,
you
know
there's
an
agreement
behind
it.
So
there's
some
kind
of
co-selling
or
oem
agreement,
or
whatever
the
nature
of
the
the
alliance
is,
is,
is
backing
that
content.
So
you
know
it's
something
somewhat
official
and
then
going
forward
we're
opening
this
to
internal
and
customer
contributions.
B
So
again,
if,
if
those
of
you
all
in
the
customer,
success
organization
or
working
with
customers
and
say
oh
xyz
customer
they
built
this
really
cool
integration
with
you
know,
vmware,
where
they've
come
up
with
a
really
neat
fix
for
getting
over
some
hurdle
or
challenge
that
we
weren't
quite
aware
of.
Let's
consume
that
and
recycle
that
back.
So
it
again
un
unblocks
or
helps
us
get
over
hurdles
with
other
customers
right.
We
want
to
be
able
to
recirculate
something
that
you
know
one
customer
did
or
one
solution.
B
B
So
again,
just
to
give
a
quick
demo
of
of
where
we're
at
here
and
I'll
put
this
page
in
the
chat
here
just
in
case
everyone
wants
to
see
it.
One
thing
I
found-
and
maybe
this
is
something
that
high
spot
is
getting
better
at-
is
sometimes
it's
a
little
hard
to
find
these
individual
pages.
If
you
do
a
search
for
a
spot
or
a
document
it'll
pop
right
up,
this
is
an
individual
page,
and
so
sometimes
it's
a
little.
B
At
least
for
me,
it
was
a
little
tricky
to
find
some
of
these
things
so
either
way.
This
is
a
page
and
it's
you
know
you
there's
basically
kind
of
like
a
wysiwyg.
What
you
see
is
what
you
get
html
editor,
where
you
can
drag
and
drop
these
various
components,
and
so
we've
done
a
little
bit
of
that
we've
styled
kind
of
an
overview
page.
B
We
have
individual
contact
information,
then
we
have
kind
of
just
a
roll
up
of
of
all
the
content
we
have
here
and
again.
All
this
content
is
basically
determined
by
the
property
of
let's
see
here,
I'll
show
you
in
high
spots.
So
we
have
all
these
categories
and
tags
here.
So
this
alliance
essay
tag
is
what
we
monitor.
That's
what
our
responsibility
is.
B
So
when
we
tick
something
with
alliance's
essay,
that's
going
to
cause
it
to
roll
up
under
this
alliances,
that's
the
collateral
page,
and
so
that's
the
checkbox
that
we,
you
know
once
we
give
it
that,
then
we
say:
okay,
we're
gonna
own
this!
It's
gonna
live
here
and
we're
gonna.
You
know
again
make
sure
that
it's
something
that
aligns
with
our
current
alliance
arrangements,
I'll
throw
it
to
darwin
just
to
see
if
you
have
anything
that
you
want
to
add
to
our
presentation
today,.
C
Yeah
sure
having
some
laggy
machine
problems,
so
maybe
I'll
have
you
kurt
click
through
for
me,
so
I
I
just
wanted
to
show
the
all
alliances
content
section.
So
if
you
click
that
all
alliances
content-
and
this
will
take
you
th
these
pages
in
high
spot-
are
kind
of
fun
landing
pages.
They
can
have
some
tracking,
but
this
is
the
real
index
that
you
can
see.
C
You
should
know
that
items
can
be
internal
only
or
they
can
be
for
customer
facing
and
that
all
of
our
non-technical
roles
within
cs
and
beyond
in
sales
will
be
using
these
content
items
to
send
out
promotions
to
customers.
So
it's
a
great
place
to
have
your
content
in,
but
if
you
click
so
so
once
you
click
into
this,
all
of
these
categories
on
the
left
are
now
only
the
only
categories
being
shown
are
ones
that
apply
that
have
been
checked
somewhere
in
the
alliance's
content.
C
C
So
like
multiple
categories,
so
we
have
some
stuff
that
we'll
probably
be
putting
up
about
aws
and.net,
so
that
would
have
both
microsoft
and
aws
clicked
as
partners
and
then
a
couple
of
things
that
we
have
added
kurt
if
you
could
expand
delivery
mode
right
now.
Everything
here
is
user
self-service,
but
if
we
there
is
another
delivery
mode
called
get
lab
assisted,
which
means
that
technically,
this
is
not
free
to
send
directly
to
a
customer.
You
you'd
want
to
ask
you'd
either
want
to.
C
If
it's
got
enablement
built
in
you,
either
want
to
learn
how
to
deliver
it
yourself
and
when
we
have
those
kind
of
things
we'll
try
to
have
a
video
too
that
if
you
want
to
deliver
it
to
your
market
or
your
area,
but
user
self-service
is
something
you
can
send
directly
to
the
customer
and
then
content
level
current.
If
you
could
expand
that.
C
Next,
one
right
under
delivery
mode.
Sorry,
we've.
We
also
added
this
concept
to
the
overall
tags,
and
so
the
idea
is
just
that,
especially
if
it's
user
self-service
kind
of
what
level
are
we
hitting
them
at
and
then
I
think
we
had
if
you
want
to
expand
asset
type
under
here,
we
added
the
asset
type
of
working
code,
so
there's
videos
also
some
of
them
are
multi-attributed
in
this
way
too.
C
So
there
might
be
a
video
that
shows
a
customer,
a
certain
thing,
and
that
thing
it's
showing
is
a
working
code
example.
So,
a
lot
of
times
we'll
link
that
example-
and
we
won't
put
two
separate
items
in
for
the
working
code
and
the
the
explainer
video.
That
explains
it
just
a
couple.
Other
things
I
wanted
to
mention
just
find
my
notes
here:
apologies,
my
machine's
been
moving
so
slow
this
morning
that
I
I
was
having
a
hard
time
even
clicking
on
different
windows.
C
C
C
One
of
the
problems
right
now
in
the
whole
ecosystem
is,
if
you
make
a
piece
of
content
and
it's
highly
reused
for
six
months
or
a
year,
there's
no
real
way
for
you
to
know
that
and
show
that
that
content
was
valuable
and
especially,
if
you
do
purposely
develop,
develop
content
to
be
broadly
usable,
it
can
be
really
helpful
to
have
that
and
then
finally
occurred
at
the
top.
If
you
could
click
into
customer
success
on
top
left
nav
bar,
I
think
it
might
be.
C
Maybe
that
works
too.
Okay,
so
then
well,
actually
yeah
click
recent
spots.
So
this
is
the
customer
6x
landing
page
and
that
recent
spots
we
put
all
of
our
content
underneath
the
customer
success
sections
and
what
this
helps
is.
If
you're
searching
the
customer
success
spot-
and
you
happen
to
use
a
keyword
like
aws
or
google
cloud,
that
is
also
in
our
content-
it
will
come
up.
Things
that
are
isolated
by
spot
are
a
little
harder
to
search
across
all
spots.
C
The
way
you
can
tell
the
content
that
we
are
providing
is
kurt
if
you
could
select
alliance's
essay
under
providing
maintaining
group,
so
we're
just
trying
to
map
here
that
if
you
have
a
challenge
with
the
content,
give
us
a
shout
there
is
an
ability
for
customers
to
also
rate
the
freshness
and
the
applicability
and
I'll
just
give
you
want
to
go
down
in
the
list.
A
bit
kurt.
C
I
may
not
have
this
on
here,
but
I'll.
Give
you
an
example
of
one
piece
of
content.
Is
a
five
video
series
on
how
to
use
something
called
an
aws
quick
start.
So
that's
an
example
of
almost
like
a
small
bit
of
lms
enablement
as
a
youtube
playlist,
and
so
that's
an
example
of
something
that
you
could
send
out
for
the
customer
to
be
enabled
on
something.
C
We
during
this
meeting
we're
wide
open
to
your
questions
about
this
content
index,
but
also
just
about
alliance's
essays
how
we
can
help,
or
even,
if
you're
unclear,
on
how
alliances
can
help
you
with
getting
your
deals
across
the
line.
So
I
guess
that's
all
I
have
occurred
if
you
want
to
open
up
the
questions.
D
B
B
I
think
it
has
like
tracking
on
delivery
and
all
that
sort
of
stuff
right
or
you
can
create
basically
just
a
pass-through
link,
and
so
that
will
tell
you,
hey
this
person,
clicked
the
link
10
other
people
click
the
link
right
like
it'll,
give
you
an
idea
of
how
deep
did
this
attempt
to
pitch
penetrate
right?
If
we
send
the
link
to
one
person-
and
we
say
well,
nobody
clicked
it-
we
know-
maybe
it
kind
of
didn't
land
or
maybe
they
didn't
receive
it.
But
if
we
send
something
like
wow,
this
got
20
clicks.
B
D
B
C
If
you
can
go
back
to
the
customer
success
spot,
you
can
also
pitch
multiple
items,
even
with
links.
So
if
you
click
back
through
to
the
whole
list
overall
list,
there's
another
place
where
they
can
activate
a
pitch
and
send
multiple
items
so
that
I
think
the
triple
dots
by
lynn's
name
is
that
nope?
Okay?
So,
let's
see
all
customer
success
spot,
maybe
oh.
C
To
share
things
yeah,
so
you
can.
You
can
also
send
multiple
items,
even
if
you're
sending
a
link.
So
that's
another
way
to
do
it.
If
you,
you
know,
it
would
be
a
great
way
to
use
your
customer
follow-up
emails
as
well
just
say:
hey,
here's,
a
follow-up,
email,
some
content,
I
thought,
would
be
helpful
compared
to
our
meeting
today
and
ship
that
out
and
if
they're
forwarding
it.
You
should
see
the
those
click-throughs
as
well.
E
C
C
And
if
you
haven't
gotten
a
chance
to
take
the
training,
it
is
the
videos.
Are
there
if
you're
a
content
provider,
it's
a
great
way
to
provide
content,
but
even
you
know,
essays
and
tams
generally.
Do
both
roles
provide
content
and
share
content,
so
it's
great
to
get
familiar
with
both
sides
of
its
features.
If
you
haven't
had
the
opportunity
and
there's
a
channel
two
channels
in
slack
and
one
of
them
has
an
employee
from
high
spot.
C
F
C
D
F
F
C
It's
a
little
bit
of
both.
So
when
you
go
into
high
spot
to
author
the
high
spot
index
item,
you
probably
should
be
ready
to
share
at
that
point.
So
if
you're
collaborating
on
actually
building
it,
you
might
you
might
want
to
turn
off
my
video.
It
looks
like
they've
having
and
with
problems.
You
might
want
to
do
that
beforehand.
C
It
also
helps
us
deal
if
any
of
you
have
done
youtube
videos
and
you
redo.
You
update
the
video
and
then
the
old
links
are
still
there,
and
if
you
delete
the
video
you
know,
no
one
can
find
the
forward
links.
So
this
is
really
cool.
If
you're
updating
like
youtube
content
to
provide
the
forward
link.
C
B
Yeah,
I
think
it's
you
know,
there's
again
it's
like
another
tool
right
there's.
It
seems
like
there's
always
kind
of
some
new
toy
or
thing
to
log
into
or
utilize
in
some
way.
So
I
I
definitely
understand
there's
kind
of
like
okay.
What's
the
point
of
this
thing
or
how
is
it
going
to
help
me
be
successful,
so
I
think
part
of
it
is
it's
a
little
bit
chicken
or
the
egg
right?
We
have
the
tool,
then
we
have
to
populate
it.
B
So
I
think
this
is
kind
of
our
attempt
to
not
only
just
solve
one
of
our
own
problems
that
we
had
in
alliances,
which
is
you
know,
keeping
all
of
our
information
together,
but
you
know
driving
adoption
of
something
like
this,
like,
I
know,
there's
a
decent
amount
of
reps
that
you
know.
Maybe
they
make
their
own
personal
slide
decks,
but
they
don't
make
a
lot
of
maybe
decks
that
are
available
for
just
general
consumption.
B
You
know,
hopefully
this
maybe
changes
that,
if
someone's
a
subject
matter
expert
in
something
and
they
put
together
a
great
deck
on
some
particular
use
case,
really
making
that
easy
for
other
people
to
you,
know
utilize
and
and
share
in
right
again.
If
we
have
a
good
solution,
if
we
have
a
good
tool,
if
we
have
a
sharp
a
sharp
sword,
we
should
be
sharing
it
around
right.
If
it's
something
that's
effective
and
so
that's
kind
of
our
intent
here
is:
how
do
we
have
a
group?
B
C
Also
to
build
on
what
kurt
was
saying
as
a
content
provider,
you
can
set
a
reminder
date
to
check
the
content,
freshness
kind
of
an
age
out
date
where
it
will
be
retired
from
being
able
to
be
selected,
and
that
helps
you
know
how,
when
you
generate
something,
sometimes
you
can
forget
about
it
and
it's
a
couple.
You
know
a
year's
worth
of
get
lab
releases
behind
this
can
help
remind
you
could
also
help
your
team
to
understand
how
much
content
do
we
have
under
management.
C
E
Darwin
this
is
samir.
I
think
people
are
maybe
coming
off
mute
soon,
but
I
just
kind
of
want
to
interject
real
quick.
I
think,
from
a
perspective
of
the
content
that
you
all
are
creating
and
putting
out
there
publishing
out
there
I'm
keeping
track.
There
is
quite
a
lot,
so
sometimes
it's
hard
for
us
to
remember.
E
What's
where
and
seeing
what?
What
what
you
just
showed
in
high
spot,
I
think,
is
very
valuable,
so
keep
keep
up
the
good
work.
This
is
awesome.
Thank
you
for
delivering
all
the
stuff
from
a
perspective
when
to
engage
the
alliance
essays,
that's
a
little
bit
murky.
So
if
there
is
some
place
where
we
can
go,
read
up
on
it,
a
handbook
page
or
if
you
can
describe
it
now,
that
would
be.
That
would
be
great.
C
We
do
have
a
channel
for
aws
and
I
think
maybe
we
don't
have
a
channel
for
google,
but
one
thought
is
just
if
you
have
very
highly
cloud
specific
questions
to
either
copy
the
relevant
alliance
essay
on
the
question
wherever
you
post
it.
If
you
want
to
make
it
very
broad,
that's
one
thing:
that's
helpful.
C
Also,
I
think
the
deal
components
have
been
articulated
quite
well,
but
in
case
anyone's
not
familiar.
Alliances
also
has
the
ability
to
coordinate
on
the
customer
side
for
making
the
building
go
through
the
particular
cloud
provider,
which
can
have
a
lot
of
advantages
to
the
cut
the
companies
you're
selling
to
and
sometimes
maybe
new
sales.
C
So
that's
something
too
that
we
can
speak
to
you
know.
Everyone
should
know
that
you
can
deploy
into
the
cloud's
deployment
services
and
I
would
generally
say
that's
better
practice
than
trying
to
you
know.
So.
Some
some
organizations
mistake
the
runner
to
be
an
endpoint
management
agent,
one
install
it
on
all
the
end
points
and
it's
just
better
to
shove
it
into
the
cloud's
deployment
mechanism.
So
those
are
some
of
the
some
of
the
areas
where
that
might
be
helpful
to
pull
us
in.
E
C
E
If
I
may
follow
up
real
quick
with
regards
to
the
engagement,
you
mentioned
cloud
providers
as
being
sort
of
the
the
big
big
ticket
items
here,
but
alliances
has
a
slightly
broader
definition,
correct
like,
for
example,
if
somebody
built
an
integration
with
git
lab
that
would
fall
under
alliances,
or
would
that
not
fall
on
their
alliances?
What's
the
scope.
C
Yeah
we
we've
defined
a
new
sub
team
just
recently
it
has.
It
is
traditionally
followed
under
alliances,
but
I
guess
it's
somehow
now
more
formalized
as
of
two
weeks
ago,
but
we
have
mike
lebeau
who
works
with
that,
and
you
there's
also
in
guided
explorations
a
subsection
called
plug-in
extensions
which
can
actually
a
lot
of
them
can
self-service,
build
their
own
extension
generally,
any
any
technology
partner,
who's
plugging
into
ci.
C
If
someone
has
security
dashboards
and
if
it
does,
it
can
output
our
json
file
format
and
if
they
don't
have
security
dashboards,
it
can
put
out
junit
xmls
because
from
a
technology
partner
perspective,
they
want
the
best
visualization
of
results
for
their
customers,
whether
or
not
they
have
ultimate,
and
so
that's
another
little
nuance-
that
for
anyone
who
plugs
into
security
scanning
or
quality
scanning
that
they
might
want
to
pay
attention
to.
But-
and
so
I
think,
we're
you
know-
we're
trying
to
get
more
sa
staffing
around
that.
H
Also
add
one
more
point
to
that:
samir
you're
right
from
an
alliance's
broader
alliance's
perspective,
we
categorize
our
alliances
partnerships
into
three
categories,
the
leading
cloud
partners.
Then
we
have
the
platform
partners,
the
likes
of
red
hat
and
vmware,
and
then
we
also
have
the
isv
ecosystem
partners,
which
is
what
you
are
alluding
to.
So,
while
these
are
the
sub
categories
of
alliances,
the
alliance's
essay
team
is
primarily
more
focused
on
the
first
two,
even
though
this
team
has
traditionally
helped
on
the
isv
ecosystem
related
work
as
well.
H
There
is
a
plan
to
actually
staff
an
engineering
team
which
is
specifically
focused
on
all
the
integration
work
with
our
isv
ecosystem
partners.
More
often
than
not
it's
the
first
two
sub-categories
where
more
of
field-facing
work
and
expertise
is
needed,
like
in
pre-sales
motions
and
the
likes
when
it
comes
to
the
isv
ecosystem.
Work
like
even
if
you
are
in
the
field
and
if
you're
needing
help
more
often
than
not
it's
engineering
level,
work
that
is
actually
needed
help
for
and
there
is
a
plan
to
actually
staff
an
engineering
team.
C
Also
previously,
I
worked
with
mike
to
try
to
define
partner
levels
at
that
level
and
encourage
that
for
low
touch
partners
that
we
can't
afford
to
like.
We
couldn't
staff
an
engineering
staff
of
30
and
they
all
become
familiar
with
the
partner,
and
we
also
talked
with
datadog,
and
they
do
it
this
way,
as
well
as
the
partner
who
wants
to
integrate
with
us.
C
So
they're
used
to
getting
to
becoming
familiar
with
the
ci
framework
and
being
given
sort
of
a
a
structure
that
makes
them
successful
within
that
and
engineering
that
and
that
that
should
always
be
the
first
default
motion,
because
the
only
they
know
when
they
have
a
major
release
of
their
software
and
that
glue
code
might
have
to
change.
There's
not
a
really
good
way
for
us
to
be
the
owners
on
code,
which
is
except
essentially
gluing
their
system,
including
their
new
releases
into
gitlab.
H
Cool-
and
let
me
do
one
more
point
to
add
to
your
previous
question
as
far
as
the
engagement
model
goes.
Yes,
there
is
a
handbook
page,
it's
very
limited
as
of
right
now,
but
it
provides
you
pointers
as
to
you
know
how
you
can
reach
out
to
the
alliance's
sav
or
the
triage
board,
and
there
is
also
a
slack
channel
called
channel
solution,
architects,
which
is
a
public
like
within
git
lab.
H
C
Can
anyone
share
times
when
you
have
engaged
alliance's
essays
that
have
really
helped
you
out?
Maybe
that
would
help
the
others
in
the
room
too
to
understand
times
to
engage,
because
we
can't
necessarily
define
every
time
to
engage
very
formally,
and
some
of
you
are
very
instinctual
about
good
times
to
reach
out
and
it
works
out
well,
so
anyone
has
any
stories.
I
want
to
share
that'd
be
great
too.
G
C
I
I
Right,
okay,
yeah!
Well,
it's
it's
a
sort
of
a
a
decent
use
case.
A
partner
was
bid
in
to
an
end
customer
where
they
needed
to
provide
a
reference
market
to
architecture
deployments,
but
they
wanted
to
understand
not
not
just
technical.
You
know.
Okay,
this
is
this
is
how
you
deploy
a
reference
architecture,
all
the
different
nodes,
but
they
were
looking
at
the
costing
elements
because,
as
a
managed
service
provider,
that
was
important
for
them.
I
If
nobody
else
has
got
a
question
there,
can
I
roll
onto
my
next
question
that
I
put
in
in
the
dock,
which
sort
of
curtis
sort
of
answered,
but
so
it's
going
back
to
high
spot.
So
I
just
noticed
that
under
channel
partners,
there
are
a
list
of
about
six
or
seven
partners
where
I
is
that
a
tag
kurt
excuse,
my
lack
of
correct
terminal
terminology.
I
So
so,
as
I
say
like
under
alliance
and
partners,
yes,
you've
got
aws
and
ibm.
Google
and
you've
got
content
there,
which
obviously
relates
to
you
know
what
you
know,
what
what
we
do
with
with
them
or
capabilities
that
they
have.
I'm
not
quite
sure
what
the
use
case
would
be
for
content
tagged
against
specific
partners.
I
I
sort
of
envisaged
that
high
spot
was
more
generic
content
that
we
could,
then
you
know
send
out
to
whoever.
I
So
you
know,
because
by
extrapolation,
if
we've
got
a
list
of
partners
there,
would
that
mean
that
we
could
end
up
with
individual
customers
tagged?
I
would
say
that
that
would
you
know
significantly
change
the
you
know
the
the
ease
of
maybe
navigating
searching.
If
you've
suddenly
got
you
know,
500
customers
or
500
partners
listed.
B
B
At
that
point,
we're
doing
like
marketing
analytics
for
our
partner
channel
partner
companies
right-
that's,
probably
not
not
the
best
use
of
channel
essays
time,
because
right
I
mean
the
point
of
this
is
at
least
a
big
point
of
it
is
to
track
usage
of
things
right.
So
if
we
did
have
something
that
was,
I
don't
know
some
accenture
solution
that
people
wanted
to
send
out.
B
It
seems
like
it's
kind
of
a
strange
use
case
to
me.
I
don't
know
who
created
the
the
tags
there,
if
that
was
just
somebody
trying
to
again
pre-populate
some
data
in
a
best
effort
type
way,
but
maybe
not
didn't,
consider
what,
like
the
actual
use
case,
is
but
yeah
to
your
point
I
would
say
yeah
what
what
under
what
instance,
would
we
tag?
Something
is
like
hey.
This
is
a
c
prime
asset
be
like
well,
it
would
be
their
marketing
material.
B
You
know,
unless
one
instance
I
could
think
of
is
if
some
partner
came
up
with
some
widget
or
application
shim,
or
something
like
that.
That
was
incredible
and
amazing,
and
it
was
so
amazing
that
our
channel
sales
people
are
our
our
sellers.
Were
like
recommending
some
something
that
some
partner
had
made.
You
know
hey.
This
is
the
auto
dev
op,
the
super
auto
devops
tool,
kit
right,
it'll
do
even
more
than
auto
devops
or
something
like
that
or
it's
some
extension
of
our
product.
C
I
I
don't
think
I
don't
think
the
platform
is
meant
for
us
to
help
partners
manage
collateral,
that
they
basically
own
and
maintain
on
the
system,
if
only
if
it
was
something
that's
completely
co-developed,
and
there
was
someone
on
our
side
brokering
that
and
willing
to
be
long-term
responsible
for
it.
The
tags,
too,
have
been
kind
of
mvc'd.
C
Anyone
can
create
a
tag
in
their
own
spot.
I've
created
tags
that
are
spot
wide,
but
you
have
to
ask
an
admin
of
the
system
to
make
them
cross
spot
so
available
and
they're
called
lists,
but
it's
the
same
thing
as
tags
like
what
we're
talking
about
here
in
sub
lists
are
like
values
within
that
tag
so
or
within
that
category
yeah.
So
it's
probably
pretty
free
form.
C
I've
been
asking
them
to
change
a
few
of
them
because
their
intent
is
not
clear
simply
by
the
name.
So
one
was
market
and
I
was
unclear
about
okay.
If
all
my
content
that
I'm
providing
applies
to
every
market,
do
I
check
every
market
and
they
were
they
said.
No,
that's.
If
it's
targeted
at
certain
markets,
I
said:
could
you
change
the
name
of
that
to
target
target
market
so
that
I
know
that
I
only
pick
it
if
it's
exclusive
to
a
region,
not
that
I
go
in
and
pick
every
region
for
something
that's
non-exclusive.
A
H
B
No,
I
mean
that
was
that
was
actually.
It
is
just
really
a
call
for
call
for
contributions
if
you
have
something
that
you
feel
is
valuable
or
is
been
reused
again,
especially
at
the
integration
and
the
scope
of
integrating
git
lab
plus
something
else
right
feel
free
to
reach
out
and
even
if
you're,
not
sure
of
where
the
exact
place
to
put
it
in.
You
know
we'll
get
it
in
the
right
spot.
So
thanks.