►
From YouTube: CDF - SIG Interoperability Meeting 2020-11-12
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
C
Yeah
yeah,
we
had
a.
We
had
the
issue
in
on
monday
that
cameron
joined
when
we
were
ending
the
meeting,
so
he
had
missed
it
by
one
hour.
Yeah
I'll
see
james
coming
in
uploads.
D
Hello,
I
almost
got.
I
missed
almost
missed
the
time,
but
manchester
just
then.
B
D
D
B
So
why
we
wait
tracy,
you
know,
as
you
mentioned,
on
slack,
to
meet
and
go
through
this
missing
chapters
in
white
paper
like
maybe,
if
more
people
join
us,
we
can
ask
anyone
who
wants
to
join
to
that.
You
know
meeting
so
we
work
on
it
with
more
people,
because
oliver
commented
on
one
of
the
sections
today
which
got
me
interested
okay.
There
are
probably
more
people
who
want
to
who
may
prefer
focused
time
on
this,
like
nr
until
the
end
of
november,
so
I
will
propose
that.
B
So
hi
james,
oh,
I
already
said
james
jeremy,
sorry,
I
am
tired
hi
there.
So
if
you
can
add
your
name
to
the
md
document,
while
we
wait
two
three
more
minutes,
we
use
the
time.
B
B
G
B
B
Well,
they
may
join
on
the
way,
okay,
so
action
item
review.
First
action
item
was
on
me
to
create
a
hack
and
the
document
for
the
metadata
work.
Let
me
share
my
screen.
B
Sorry,
you
can
see
the
screen
now:
yeah
yep
yeah,
so
the
document
is
there
and
let
me
open
the
page
and
it's
just
basically,
I
put
the
names
of
volunteers
like
tracy
miranda,
steve
taylor
and
james
strachan
and
the
other
like
introduction,
scope,
tbd,
and
I
tried
to
capture
the
things
people
mentioned
like
what
ramen
mentioned
about
what
they
have
in
ebay.
This
ebay
metadata,
I
think,
trace
reagan
mentioned
ortilli's
use,
hermetic,
manifest
helm,
chart
and
techton
chains
christie.
B
I
think
she
mentioned
this
together
with
in
total,
although
these
were
the
existing
efforts
before
during
that
discussion.
So
this
is
the
document.
If
you
want
to
use
this
feel
free
to
do
that,
we
can
connect
this
back
to
see
grepo
as
well,
so
we
version
control
it
in
the
repository
tool
and
yeah.
That's
the
action
item.
B
Simply
I
close
that
one.
We
will
talk
about
this
topic
again
and
the
next
action
item
is
on
me
to
sync
with
oliver
on
case
study
for
white
paper,
which
we
did
and
then
we
will
talk
about
that
when
we
come
to
the
white
paper
topic.
B
So
I
close
that
one
and
the
other
action
item
is
on
ramen
and
I
check
with
ramen,
or
I
mean
ask
this
internally
like
trying
to
get
permission
like
that
type
of
you
know
official
permission
stuff,
so
it
will
happen,
but
it
may
take
three
weeks
until
we
see
the
example
manifest
from
ebay
for
metadata
topics.
So
we
keep
that
open.
B
Trace
recognize
steve
taylor
to
do
ortelius
presentation
demo.
I
still
don't
see
them,
so
we
keep
that
action.
Item
open
and
finally,
storing
james
struchan's,
tacton
jenkins
x
lies
on
presentations
repository,
which
is
done
as
well.
So
closing
this
one
too.
F
Just
before
we
get
into
that,
I
want
to
just
bring
up
the
the
meeting
timing
again
yeah,
just
because,
like
I
think,
by
keeping
it
on
utc,
we've
effectively
moved
it
an
hour
earlier
for
everyone,
but
I
have
concerns
that
that
makes
it
difficult
for
our
friends
on
pacific
time
to
attend,
given
it's
7
a.m,
and
I
know
it's
already
challenging
for
ramen
to
to
make
the
previous
time
so
yeah
I
mean
we
can
see
how
it
goes,
but
I
like
to
suggest
we
go
back
to
the
like
yeah
the
problem
at
utc.
F
Is
it
it
changes
half
half
the
time
of
the
year,
and
it's
not
like
relative
to
everyone
else.
We've
all
shifted
the
meeting
an
hour
earlier,
but
I
propose
we
go
back
to
the
original
time.
B
Well,
given
that
the
majority
of
people
in
this
meeting
are
from
europe,
I
think
we
can
quickly
take
a
vote
here
and
say:
yeah,
it's
it's
okay
or
not,
okay,
for
people
from
europe
and
then
we
can
just
send
them
notification
to
everyone
and
update
the
invitation,
but
I
think
we
could
stick
to
utc
again
still
yeah
one
hour
later.
Yeah
four
p.m:
youtube.
B
So
anyone
has
any
objection
to
moving
the
meeting
one
hour
later,
so
it
will
become
5
p.m,
for
european
and
4
p.m,
or
5
p.m.
Central
european
4
p.m.
Uk,
I
think,
or
gmt
and
4
pm
utc
in
winter
and
in
summer
it
will
be
6
p.m.
Central
european
summer
time,
5
pm,
uk
gmt
and
4pm
utc.
H
Just
a
comment
there
from
from
me
emilia,
I'm
thinking
of
when,
when
this
daylight
savings
time
occurs
and
when
the
switch
is,
I
believe
now
that
this
last
time
it
happened
now
to
the
winter
time.
It
was
not
that
the
same
weekend,
both
in
u.s
and
europe,
so
that
could
be
maybe
a
little
confusing.
When
should
we
then
switch
back
to
the
other
time
again
to.
B
D
B
Happy
with
it
yeah,
maybe
it
would
be
good
to
remind
remind
the
survey
outcome.
Actually,
when
we
decide
this
time
zone,
it
was
actually
a
tie
between
3
pm,
utc
and
4
pm
utc
and
I
simply
said,
let's
start
with
3pm
utc
in
case.
If
we
have
people
from
asia
pacific,
because
if
we
make
it
4
p.m,
it
is
very
difficult
for
them.
It's
like
middle
of
night
or
something,
but
I
don't
remember
having
anyone
from
asia
pacific
joining
the
sig
meetings
we
can.
B
B
So,
okay,
aside
from
emil,
is
there
any
other
person
who
prefers
the
earlier
time
slot.
F
Yeah
and
I
don't
think
we
need
to
have
set
it
in
stone
like
I
think
we
can
relook
at
it
in
summertime,
but
I
I
think
the
problem
we
need
to
solve
now
is
you
know:
we've
got
folks
who
are
involved
in
the
discussions
and
it's
now,
we've
now
effectively
moved
the
meeting
to
a
place.
They
can't
easily
join
and
we
should
fix
that.
B
B
B
B
I
I
From
our
end,
it's
it's
a
big
diversity
in
the
company,
since
we
have
a
pretty
long
history,
half
a
century
right
and
that's
basically,
our
main
driving
factor
that
that
we
have
people
who
just
came
out
of
university
and
on
the
other
side,
we
had
people
30
years
with
the
company,
and
you
can
do
the
math
and
see
how
acquainted
are
the
people
30
years
with
a
company
with
maybe
all
the
cloud
native
paradigms,
whereas
the
others
freshly
joining
may
have
a
harder
time
to
understand
what
what
the
what
the
older
people
in
the
company
do
right
and
therefore
we
I
believe
we
are
one
of
the
biggest
drankin
shops
in
the
world,
but
there's
other
things
than
jenkins.
I
Therefore,
interoperability
is
a
big
topic
and
we
also
brought
quickly
up
this
open
source
project.
We
we
open
sourced,
I
believe
in
2017,
which
is
one
one
thing
which
helps
us
in
company
internally
also
with
our
partners,
customers
to
bring
some
abstraction
layer
into
the
game,
and
I
suggested
to
to
give
some
some
more
insight
into
the
project
in
in
one
of
the
upcoming
meetings.
F
Yeah,
I
think
that's
great,
I'm
really
happy
that
you
could
contribute
it.
One
question
I
was
wondering
whether
it's
possible
to
specify,
but
is
there
a
way
to
quantify
even
in
victims
like
how
many
different
teams
you're
dealing
with
or
that
are
doing
kind
of
different
things
in
sap
like
is
it
dozens?
Is
it
hundreds?
Is
it
20?
F
My
mind
springs
back
to
a
talk.
Salesforce
once
did
where
they
sort
of
talked
about
having
20
different
ci
cd
systems
and
that
kind
of
give
an
instant
picture
of
complexity
such
as
wondering
whether
there's
a
way
to
not
too
specific
but
give
some
indication
of
the
scale
of
the
problem
from
sap
side.
I
I
And
for
ci
cd
system
systems
or
cd
orchestrators,
I
would
need
to
see
right.
I
know
we
with
one
central
jenkins,
offering
we
we
provision
essentially
jenkins
with
a
click
of
the
button,
and
we
have
roundup
between
1500
and
2000
jenkins
instances
like
up
and
running
there
and
that's
just
one
infrastructure.
I
F
Yeah,
if,
if
there
is
something
you
can
share
to
qualify
it,
it's
just
a
lot
of
the
conversations
we
have.
I
think
people
are
keen
to
be
able
to
set
things
in
context,
so
they
know
like
okay.
Is
this
a
solution
like
you
know,
fidelity
will
come
and
say:
okay,
we're
looking
for
a
solution
for
40
000
developers
is
something
sap
are
doing
in
the
same
ballpark.
So
we
can
compare
approaches.
Yeah.
F
E
I
F
I
F
F
And
I
guess
jenkins
instances
is
one
way.
I
I
don't
know
for
cloud
native
like
with
tecton
and
jenkins
x.
How
do
people
typically
qualify
the
scale
they're
running
at
any
comments
and
andreas
enjoy
our
dreams.
D
You're
good
to
think
about
when
we
from
from
the
jegger's
ex
point
of
view,
because
it's
an
episode
of
projects,
it's
hard
to
know,
even
just
how
many
people
are
actually
using
jenkins
x.
I
know
that
we've
seen
that
there's
studies
before
on
the
jenkins
project-
and
there
are
some
astronomical
numbers,
but
you
don't
know
it's
very
hard
to
then
quantify
it's,
not
your
organization
that
you
can
kind
of
keep
tabs
on
use
one
in
the
software,
so
yeah.
F
E
I
I
do
have
numbers
for
certain
aspects
right
like
this.
This
centrally
provisioned
jenkins
infrastructure.
I
B
Maybe
jeremy
because
zul
is
used
within
open
infrastructure,
open,
dev
community,
maybe,
as
part
of
your
case
study,
you
can
perhaps
mention
number
of
jobs
or
number
of
instances.
Rule
managers
for
the
community,
like
with
thousands
of
developers
and
so
on.
G
Yeah,
I
mean
that's,
that's
a
probably
a
different
case
study.
In
that
case,
I
was
actually
hoping
to
to
use
the
volvo
motors
case
study,
but.
A
G
I
guess
I
could
mention
other
google
users
too.
I
didn't
know
how
how
much
information
you
really
wanted
about
specific
deployments,
because
I
I
thought
that
the
scope
of
this
white
paper
was
going
to
be
around
interoperability,
so.
G
Entirely
sure
what
the
size
of
the
deployments
necessarily
has
to
do
with
interoperability
features,
whereas
the
the
reason
I
was
going
to
pick
the
volvo
motors
use
case
was
because
they've
got
multiple
different
code
hosting
systems
that
they
want
to
be
able
to
to
have
dependencies
between
changes
in
garrett
and
get
lab
and
be
able
to
to
cross
test
between
those
in
the
same
ci
system.
So
that
was
that
that
I
could
make
a
bit
more
of
a
interoperability
case,
for
I'm
not
sure.
A
B
It
be
something
like
this
jeremy
since
like
well.
Okay
study
would
be
great
because
demonstrating
interpretability
between
different
acm
to
support
by
the
cicd
to
zoo
is
great.
I
think
we
should
have
that,
but,
as
part
of
that
case
study,
I
suppose
you
will
have
some
intro
information
about
what
is
rule.
Maybe
you
can
add
a
sentence
or
two
there.
While
talking
about
what
is
zul,
maybe.
G
Yeah-
and
I
mean
we-
we
do
have
the
same
sort
of
paradigm
going
on
in
open
dev.
That
volvo
is
using.
We've
got.
You
know,
projects
that
are
hosted
in
our
garrett
instance
in
open
dev,
but
they
also
have
dependencies
that
are
managed
by
other
groups
of
people
in
github,
and
so
we
have
some.
You
know
ci
jobs
that
we
can
basically
say.
G
I
want
to
test
this
new
feature
in
my
project
in
garrett,
against
this
pull
request
that
I've
proposed
in
this
github
project,
and
you
know,
be
able
to
to
confirm
that
that
if
that
pull
request
lands,
then
my
feature
in
my
project
will
will
work
the
way
that
I've
designed
it
and
all
the
sky
jobs
will
pass
and
everything,
and
also
to
not
merge
my
change
in
my
project
until
the
pull
request
and
my
dependency
and
github
lands.
So
I
I
can
definitely
use
that
same
paradigm
in
the
open,
dev
use
case.
G
I
just
I
was
trying
to
steer
clear
of
open
dev
because
there's
already
a
somewhat
incestuous
relationship
between
the
open,
dev
hosting
environment
and
zuul,
since
the
zuul
project
is
itself
hosted
in
open
dev
and
that
muddies
the
waters
of
the
use
case
a
bit
compared
to
somebody
like
volvo
who
is
while
they
are.
You
know
developing
contributors
to
the
zul
project.
They
aren't
necessarily
also
having,
as
close
a
tie
to
the
the
ci
software
development
as
the
open,
dev
environment,
maintainers,.
F
I
would
plus
one
to
the
the
volvo
use
case
and
particularly
the
focus
on
code
hosting
systems,
because
I
think
it's
important
when
we
talk
about
interoperability.
It's
it's
not
narrowly
focused
on
pipeline
orchestration,
but
it
is
everything
to
do
with
software
delivery.
So
yeah,
I
think
that's
that's
a
great
case
study
and
I
think,
with
the
earlier
conversation,
I
was
just
trying
to
put
into
context
the
company,
so
I
I
think
you
can
steer
clear
from
the
the
open
dev
if
that
makes
life
easier.
B
Okay,
so
volvo
got
more
votes,
so
yeah
jeremy,
as
I
mentioned
on
irc
I
think
end
of
november,
is
what
we
are
targeting
for.
Creative
team.
B
B
Thanks
a
lot
okay
and
I
see
either
james
or
cara
you
put
this
is
in
progress
here.
So
I'm
not
asking
you
again
because
I
asked
it
yesterday
during
talk
meeting.
So
that's.
B
So
we
have
jenkins
extect
on
captain
ghost
spot
check,
erickson
sap
and
volvo
on
its
way
and
thanks
trace
for
getting
us
in
touch.
I've
forgotten
the
name
from
another.
What.
B
Yeah,
I
will
follow
up
with
him.
I
haven't
heard
him
back
yet,
but
I
will
ping
him
again
and
book
time
with
him.
So
if
you
get
fintech,
that
would
make
it
even
more
interesting.
F
Yeah,
no,
I
I
think,
they're
really
great
a
nice
variety
of
companies
and
open
source
projects
and
all
kind
of
bringing
something
new.
Was
there
a
spot
for
the
like
the
the
jenkins
and
tekton
integration?
One
did
vincent.
B
Oh
or
yes,.
D
It
was
a
bit
of
a
brief
dm.
We
had
car
was
on
there
as
well,
where
we
kind
of,
I
think
there
was
there's
no,
as
tracy
said
on
that
thread,
there's
not
too
much
overlap,
so
it
was
the
case
of
that
he
can
have.
They
can
have
their
own
use
case.
I
know
they
were,
they
did
say,
they're
going
to
work
on
it,
but
haven't
heard
since
offered
some
help
if
they
wanted
anything.
So
if
they
wanted
anything
so,
okay.
B
B
So
I
will
let
me
action
myself,
so
I
will
ping
vibhal
on
slack.
A
A
B
B
B
Okay
and
the
other
chapters-
okay,
this
chapter
we
already
agreed-
we
will
take
something
from
one
of
these
links,
so
we
can
do
this
offline.
We
don't
need
to
talk
about
it
and
then
review
it
after
we
choose
which
one
to
take.
I
think
this
chapter
is
tricky
like
and
oliver.
Thanks
for
your
comment
there
like
we
need
to.
B
As
I
noted
here,
we
need
to
clarify
integration
versus
interoperability
and
what
we
are
actually
working
with,
and
then
these
are
the
the
points
here
is
actually
taken
from
the
pull
request
we
proposed.
I
seek
interoperability
november
last
year
and
these
were
the
items
people
brought
up
under
the
proposal
like
pipeline
standardization,
pipeline
integration,
pipeline
data
and
metadata
is
related
to
this
as
well,
and
events
in
ci
cd
is
one
of
the
work
streams
we
have.
B
So
these
are
the
topics
of
interest
for
the
people
who
to
who
is
taking
part
in
this
seek
so
oliver
you
want
to
talk
about
this.
What
you
put
here
is
comment.
I
Yeah
I
saw
the
pipeline
standardization
and
languages
and
I
I
personally
believe
it's
an
important
aspect.
What
that's
something
we
we
also
see
within
the
company
right
since,
due
to
the
high
amount
of
teams.
Also,
it's
it's
difficult
to
for
teams
to
get
into
the
nitty-gritty
details
of
every
single
orchestrator,
orchestrator,
dsl,
right
and
there's
what
what
we've
been
doing
is
we've
been
hiding
some
complexity
of
the
dsl,
making
it
easier
to
reuse,
mainly
in
the
jenkins
case,
right
things
which
have
been
discussed
with
shared
libraries
and
so
on
right.
I
That's
that
it's
that
the
teams
have
it
much
easier
to
get
started
right,
but
but
there's
a
might
be
a
project
company
specific
solution
for
jenkins,
but
for
other
projects.
I
believe
we
don't.
We
are
still
further
behind
for
having
certain
things
right
and
having
something
at
least,
maybe
just
a
minimum
language
minimal.
I
Minimum
dsl,
which
suits
certain
use
cases
could
already
already
beneficial,
because
I
don't
think
that
from
what
I
see
within
our
companies
that
not
every
team
needs
all
the
nitty
gritty
details
of
the
individual
orchestrators.
It's
rather
task
flow
executing
this
that
right,
without
going
into
a
specific
container
definitions
and
so
on.
D
Yeah
we
really
like
what
the
tecton
projects
has
been
doing
around
this
from
having
the
standardizing
around
the
dsl.
But
then
people
can
build
use
that
and
have
reusable
tasks,
and
particularly
the
catalog.
The
tecton
catalog
is
really
nice
way
to
be
able
to
share
those
kind
of
there's
those
pieces.
Those
chunks
almost
have
a
pipeline
that
you
don't
want
to
get
into,
but
somebody
else
may
maintain
it,
but
you
it
just
does
what
it
says
on
the
tin
and
then
you
you
put
that
in.
D
Yeah
yeah
exactly
but
then
well
what
with
the,
what
we've
done
with
jenkins
x
is
actually
combining
those
and
having
actual
full-on
pipelines
within
the
catalog.
So
using
exactly
the
same,
catalog
approaches
is
just
using
tecton
all
the
way,
all
the
way
down.
Yeah.
I
From
from
james
as
well,
but
there's
a
few
aspects,
we
I
really
like
about
it
and
what
we've
been
doing,
also
on
with
on
jenkins,
classic
right,
because
having
a
simple
way
of
overriding,
a
stage,
adding
a
task
to
a
stage
or
a
step
to
a
stage.
D
I
don't
know
if
you
managed
to
do.
I
don't
know
if
you're
on
the
call
sorry,
but
there
was
james
strachan
did
a
bit
of
a
last
week.
I
was
there
yeah
cool
yeah.
D
So
that's
really
I
mean
that's
coming
up
the
the
the
two
jx2
but
sorry
the
gx3
is
almost
beaten
within
the
next
two
weeks,
probably,
but
it
might
be
the
guides
that
we've
got
in
the
walkthroughs
of
that
are
going
to
be
a
lot
clearer.
So
I'm
hoping
I
mean
I've
been
using
it
myself
using
just
vanilla
tecton
and
it's
actually
a
lot
easier
to
be
able
to
extend
and
override
those
those
steps
using
the
tecton
principles
and
dsl
we're,
certainly
finding
that.
D
D
It
seems,
and
standardization
seems
a
lot
better
because
I
think
we
got
it
wrong
if
I'm
honest,
with
the
trying
to
put
a
dsl
on
top
of
over
above
tectonic,
it's
it's,
it's
legally
abstraction,
we're
gonna,
it's
really
hard
to
maintain,
and
so
standardizing
just
on
tact
on
it's
just
from
the
like
an
api
is,
I
think,
is
a
lot
cleaner.
I
I
D
F
Yeah,
this
interesting
set
of
different
approaches
in
this
space
it'll
be
good
to
bring
folks
together
and
like
stephen
turana
and
and
the
templating
engine
and
jenkins.
They
were
having
some
talks
with
simon
keaghy
and
the
techton
folks
and
I
think
it'd
be
great
to
start
to
drive
all
these
efforts
closer
and
closer
together.
So
we
have
a
some
form
of
yeah,
integrated
or
interoperable
solution.
I
B
So
this
chapter
is
kind
of
yeah.
We
need
to
recommend
like
write
down
what
we
mean
when
we
say
interval,
then,
when
I
was
looking
for
like
if
there
are
other
you
know,
industries
or
communities.
Talking
about
like
integration
versus
interoperability,
I
found
lots
of
articles
from
health
industry.
It
seems
there
is
this
heart
transformation
happening
in
us
or
somewhere,
and
they
are
talking
a
lot
about
interoperability
in
that
context,
and
actually
it
is
funny
that
they
are
saying
exact,
same
things
as
we
have
been
discussing
here
for
health
industry.
B
B
Yeah
yeah,
so
I
will
put
few
of
the
links
there,
so
we
can
look
at
what
how
they
are
differentiating
between
integration
and
interoperability,
which
we
can
you
know
somehow
get
their
like
thoughts
and
combine
that
with
ci
cd
stuff
to
come
up
with
our
perspective
there,
and
the
next
chapter
is
key
consideration,
constraints
and
concerns.
I
think
this,
like
the
bullet
points
here,
actually
could
fit
well
under
considerations
as
well,
because
like
depending
on
who
you
are
talking
to
those
people,
consider
interoperability
for
pipeline
standardization
or
pipeline
integration
or
events
and
so
on.
B
So
this
could
either
end
up
here
or
stay
where
it
is
these
bullet
points,
and
in
addition
to
that,
the
constraints
and
concerns
is
one
of
the
like
lack
of
internality
is
one
of
the
constraints.
You
know
why
we
can't
achieve
what
we
want
to
achieve
with
different
tools
and
technology,
so
that
type
of
stuff,
and
if
we
can't
fill
the
chapter,
we
can't
think
of
not
including
it
to
be
honest
like
because
there
is
nothing
under
it.
B
Okay,
so
reusable
libraries
yeah.
I
think
you
also
mentioned
this
like
reusable
libraries
just
five
minutes
ago
or
something
such
things
can
go
under
this
without
like
exact
pointer,
but
we
have
examples.
So,
let's
go
sem
or
tecton
client
which
james
brought
into
cdf.
We
can
use
those
as
examples
here
and
the
need
to
somehow
make
those
libraries
visible
for
everyone's
use.
B
I
am
thinking
if
we
should
have
metadata
here
as
well
because
like
since
we
start
talking
about
metadata-
and
it's
not
the
first
time
we
are
talking
about
this.
As
many
mentioned
during
before
previous
meeting
metadata
topic
comes
up
regularly
in
different
contexts
across
different
communities,
so
we
can
highlight
that
and
since
in
white
paper
we
are
not
talking
about
what
we
did.
We
are
talking
about
what
we
can
do
and
come
and
help
us,
so
that
could
be
some
thing
to
get
interest.
I
Yeah,
another
aspect
might
be
in
in
other
already
within
other
areas,
but
configure
pipeline
configuration
right
and
because,
in
the
end,
what
what
we
see
is
you
on
the
one
side,
have
a
pipeline
flow
on
the
answer.
On
the
other
side,
you
have
the
configuration
for
individual
steps,
for
example,
and
quite
often
this
is
mixed
within
the
same
dsl
right.
Then
the
question
is
what
we
do
is
we
we
have
the
configuration
separate.
I
We
have.
We
keep
flow
in
on
one
side,
configuration
like
which
images
to
use
for
for
certain
step,
execution
and
so
on
separate,
which
makes
the
flow
easier,
reusable.
D
The
two
class
secrets
is
that
as
well,
would
you
class
secrets
something
different.
I
How
we
started
dealing
with
secrets
is
that
we
as
typical,
are
typically
done
either
injected
as
environment
variables,
or
we
now
within
the
the
pipeline
library,
which
we
have
in
in
this
piper
project.
We
directly
access
wall
from
within
the
steps.
That
means,
if
we
have
a
step
interacting
with
some
security
system,
some
security
tool
system
to
upload
a
report.
This
step
will
access
directly
vault
retrieve
the
secrets
without
the
without
having
the
orchestrator
system
involved.
D
I
wonder
how
much
I
wonder
if
it's
a
relevant
subject
for
a
paragraph
or
something
around
how
how
pipelines
deal
with
secrets.
I
know
cara's
got
lots
of
thoughts
around
this
one
as
well.
It
might
be
quite
it
might
be
useful
to
have
something
a
paragraph
or
something.
D
E
K
I'm
happy
to
add
to
that
section
very
much.
Can
I
ask
him
it
may
or
may
not
be
irrelevant
relevant
to
this
discussion,
but
should
we
have
any
any
any
sort
of
indication
on
or
or
discussion
in,
the
white
paper
on
looking
at
the
role
like
standards,
but
open
standards
and
apis,
and
just
looking
at
maybe
something
around
how
different
definitions
of
how
data
is
transferred?
How
that
affects?
K
F
K
Data
flows
through
yeah
how
the
data
is
flowing.
So,
if
you
think
of
say
standards
or
open
standards,
you
know
versus
private
standards
and
then
how
apis
are
developed
and
the
choices
that
are
made
and
how
different
apis
are
developed.
Do
we
want
to
have
any
discussion
on
the
importance
of
open
standards
or.
F
Yeah,
I
think,
like
for
open
standards
for
this
white
paper.
It's
almost,
I
think,
it's
enough
to
say
that
they
don't
exist
and
that's
why
we
have
this
whole
white
paper
moving
in
that
direction,
but
yeah,
okay,
but
then
there's
lots
of
trends
like
these
things.
Standardized
metadata,
shared
libraries
are
kind
of
the
steps
the
industry
needs
to
take
before
we
can
even
get
to
the
super
formalized
kind
of
standards.
H
Yeah
and
adding
and
adding
to
that,
I
will
also
say
that
we
already
have
that
in
the
event
submit
in
csv
section
in
the
document
for
the
for
the
events
part.
So
that's
one
one
way
of
dealing
with
the
data.
If
I
understand
your
reflection
right
cara,
but
of
course
there
are
other
ways
to
hand
it
as
well.
F
Yeah
and
the
api
point
I
think,
that's
worth
calling
out
like
we
talked
about
standardized
metadata,
but
are
we
covering
api
in
the
library
section,
or
should
we
separate
that
out?
That's
been
a
a
pretty
good
way
for
lots
of
software
to
to
drive
better
interoperability
by
having
a
kind
of
de
facto
apis
that
people
use.
I
mean
effectively,
that's
what
kubernetes
is
so
I
don't
know
if
we're
explicitly
calling
that
out
or
we
need
to.
F
B
But
we
can
yeah
can
if
we
can
comment
on
it
like
here
somewhere,
so
we
don't
drop
it
because.
J
B
F
F
And
related
to
that,
I
was
gonna
james
and
cara
like
something
like
lighthouse
in
jenkins
x,
which
is
you
know,
that's
an
approach
to
standardize
across
sem
providers
which
header
do
you
think
that
would
best
fit
under
if
we
were
going
to
pull
it
in
as
an
example
of
new
approaches
and
trends
that
need
to
happen.
D
D
D
B
Okay,
so
let's
move,
I
think,
if
you
get
all
these
things
in
this
will
be
and
also
write
paper
so
case
studies
where
I
talked
about
it,
the
future.
The
intention
was
like
to
talk
about
what
we
intend
to
achieve
and
also
taking
parts
from
roadmap,
because
we
have
some
future
looking
statements
within
the
roadmap
so
include
some
of
those
things
from
there
and
conclusion
is
simply
yeah.
Come
join
us
call
for
action.
F
B
So
now
we
have
names
on
most
of
chapters,
so
I
can
take
this
one
because
I
already
mentioned
few
references
there.
B
The
idea
tracy,
you
brought
up,
I'm
wondering
if
anyone
is
interested
to
have
in
our
next
week
or
week
after
next
to
just
you
know,
work
on
these
chapters
together,
like
we
can
perhaps
say,
give
one
week
to
everyone
to
fill
some
text
into
these
chapters
and
week
after
next
during
the
sig
meeting
week,
we
can
have
a
separate
meeting
from
segmenting
if
it's
with
everyone
just
to
get
this
done.
F
B
Okay,
let
me
suggest
this:
we
can
send
a
mail
to
a
mail
list
and
invite
anyone
who
wants
to
join
and
then,
if
anyone
wants
to
join,
they
can
respond
to
the
mail
and
they
can
join.
F
B
F
That
week
for
me
for
a
working
session,
oh
we
could
even
use
the
the
normal
session
if
it's
going
to
be
quieter
and
we
don't
have
folks
to
present
working
session.
Okay.
B
Okay,
I
think
we
are
getting
somewhere
for
the
white
paper,
which
is
great
and
if
you
can
make
this
happen
before
christmas
vacations,
like
mid
latest
mid
december,
perhaps
so
people
can
read
the
white
paper
during
their
holidays
if
they
get
bored.
B
Wishful
thinking,
so
that
was
the
white
paper
and
if
no
one
has
any
other
comments
going
to
the
next
topic,
so
standardized
metadata,
we
don't
have
james.
We
don't
have
tracy
reagan
here.
So
anyone
wants
to
talk
about
this
topic
or
should
we
park
it
until
we
meet
next
time,
and
I.
K
K
I
have
a
question
too:
have
the
standardized
metadata
meetings
been
kicked
off.
B
B
So,
apart
from
those
people
listed
there,
it's
not
limited
tony
tracy,
steve
and
james.
You
know,
if
others
have
any
thoughts
on
this,
just
go
in
and
put
your
toes
there.
You
know
it
doesn't
mean
it's
only
these
people
who
work
on
this,
because
when
we
discuss
this
last
meeting,
many
people
were
talking
about
this
and
the
page
is
empty.
It's
surprising.
B
B
I
K
F
B
Okay,
so
this
makes
oliver
your
presentation
will
probably
need
to
wait
until
new
year
until
after
new
year,
or
I
can
check
with
you
again
before
this
10th
of
december
meeting-
to
see
if
they
can't
make
it.
I
can
shake
with
you
to
see
if
you
can
make
it
the
presentation,
and
then
we
shuffle
things
around.
F
Just
a
quick
one,
I
just
want
to
do
an
additional
shout
out
for
a
a
new
special
interest
group
city
of
spinning,
which
is
around
best
practices
and
maurizio
salatino
is
heading
that
up
as
chair
and
there's
going
to
be
a
kickoff
meeting
on
monday
at
11
a.m.
Eastern,
and
so
this
is
kind
of
taking
the
accelerate
book
as
a
starting
point
and
and
sort
of
saying.
F
How
can
we
help
people
figure
out
where
they
are
compared
to
the
industry
and
what
are
most
people
doing
versus
what
other
leading
edge
people
doing
and
and
just
mapping
that
all
out?
So
it's
it's
much
more
structured
for
the
industry.
So
if
you
do
want
to
get
involved
with
those
conversations,
yeah
join
in
the
the
sick
meeting
on
monday.
B
It's
on
public
calendar,
yeah.
J
B
B
B
B
So
anything
else.
B
Okay,
then,
I
think
today
was
good,
like
we
spent
good
time
on
the
white
paper,
because
we
haven't
been
able
to
do
that
last
few
meetings.
So
that's
good
to
have
and
if
no
one
has
any
other
topic
to
bring
up,
then
I
suggest
we
have
the
next
meeting
as
usual
with
whoever
can
join.
B
And
you
know
it
gets
completely
complicated
if
we
delay
it
later,
yeah
at
least
that's
exciting.
Okay,
thanks
out
everyone
and
have
a
nice
day
evening
and
talk
to
you
in
two
weeks
or
in
four
weeks.
Okay,
thank
you.