►
From YouTube: Argo Workflows and Events Community Meeting 15 June 2022
Description
00:25 Announcements
03:50 Hera Python SDK for Argo Workflows - update from creator & maintainer, Flaviu Vadan @ Dyno Therapeutics
https://github.com/argoproj-labs/hera-workflows
See the October 2021 community meeting for more info about Hera: https://www.youtube.com/watch?v=QETfzfVV-GY
Community Meeting agenda, notes, and schedule: http://bit.ly/argo-wf-cmty-mtng
A
B
A
We're
just
getting
started,
I
think
everybody
here
probably
knows
this
is
being
recorded
so
thumbs
up
to
that
and
we'll
post
this
in
the
channel
after
we're
done
so
yeah.
I
guess
a
few
announcements
and
then
we'll
have
one
presentation
today
by
flav,
so
so
the
first
announcement
here,
I'm
kalyn,
kaylin
or
cart
so
I'll-
be
helping
out
running
this
meeting
going
forward.
A
A
A
Cool
other
announcements,
the
contributors
meeting,
we're
still
holding
that
it's
now
every
other
tuesday
at
10
a.m,
with
terry
hosting
that,
but
several
of
us
are
joining
that
every
other
week.
So
we
encourage
people
to
stop
by
there
and
in
that
process
we
are
updating
the
argo
workflows
roadmap.
So
just
a
reminder
to
vote
any
issues
and
comment
on
that
document,
so
we
can
keep
prioritizing
issues
and
or
new
feature
requests.
A
A
C
A
C
A
B
D
Hi
everyone,
my
name
is
fabio,
I'm
a
software
engineer
at
dino
therapeutics
and
I'm
one
of
the
main
maintainers
of
hera
workflows.
I'm
here
today
to
give
an
update
on
the
progress
of
hera
since
its
initial
release
in
the
argo
project,
labs
organization
last
october,
and
chat
about
some
of
the
next
steps
the
project
might
take
in
the
next
few
months.
D
What
is
herahera's?
Argo
workflows,
python,
sdk
that
was
written
and
released
by
dino
therapeutics
in
collaboration
with
the
argo
maintainers
last
october.
At
that
time,
argo
workflow
specifically
was
slightly
challenging
to
access
via
python
for
scientific
computing
purposes,
because
existing
sdks
were
not
very
accessible
to
users,
who
are
not
very
familiar
with
argo
concepts
in
the
first
place,
and
that's
what
motivated
dyno
to
create
a
client
for
argo,
that
abstracts
away
the
argo
core
concepts
and
exposes
a
light
interface
that
gives
users
the
ability
to
focus
on
easy
creation
and
submission
of
workflows.
D
At
the
core
of
harris
design,
the
idea
of
simplicity
will
always
be
central.
In
addition,
there
was
a
set
of
initial
requirements
that
hero
aimed
to
solve
upon
initial
release
it
aimed
to
simplify
dependency
setup,
which
it
did
via
either
bit
shift
operators
or
a
method
called
next
directly
on
tasks.
D
It
also
needed
easy
parallelism
set
up,
which
it
achieved
via
simply
passing
multiple
structure,
parameters
to
one's
python
function
that
is
executed
on
argo,
easy
submissions
by
a
single,
create
call
and
elements
such
as
maintaining
some
parallels
between
the
naming
conventions
of
argo
and
hera
to
facilitate
users.
Understanding
of
how
hera
concepts
relate
to
elements
of
the
argo
ui,
for
example,
and
support
for
multiple
types
such
as
identic
schemas,
that
give
you
validation,
serialization
and
things
of
that
kind,
so
that
are
passed
between
tasks.
D
So
where
are
we
at
today
since
last
october,
so
heroes?
Currently
on
version
350?
There
were
a
few
breaking
changes
that
I
would
say,
were
pretty
minor,
but
they
were
impactful,
such
as
the
introduction
of
a
differently
structured
host
and
token
representation
for
workflow
submission,
and
we've
introduced
these
things,
because
they
are
a
more
accurate
reflection
of
how
the
community
wanted
wanted
to
perform
submissions
to
argo
through
era
harrah's
currently
sitting
at
127
stars
with
32
forks
and
it
was
featured.
D
I'd
say
there
were
primarily
three
impactful
bugs
that
affected
hera
so
far,
which
have
been
solved
in
in
past
releases.
Of
course,
through
issue
submissions.
Some
users
have
a
very
positive
feedback
due
to
the
description,
such
as
awesome,
great
work
and
amazing,
which
I
was
super
grateful
for,
and,
lastly,
hera
recently
added
a
users.md
file,
which
now
includes
four
official
companies,
specifically
reverie
labs,
infinite,
lambda,
pipe
kit
and
dyno
therapeutics
in
the
next
four
to
six
months.
The
primary
goal
is
to,
of
course,
keep
delivering
on
feature,
requests
that
come
from
the
community.
D
One
question
I
noticed
in
the
cncf
slack
workspace
is
whether
there's
an
argo
cd
client
that
is
similar
to
design
in
indesign
to
hera,
and
there
wasn't
one
at
the
time.
So
there
are
some
thoughts
floating
around
on
the
topic
of
making
here
a
facilitator,
a
facilitator
of
access,
targo,
cd,
the
same
way,
facilities
access,
the
article
workflows.
D
The
idea
of
spinning
up
local
clusters
for
testing
hero
is
also
something
that
might
empower
user
adoption,
in
addition
to
the
creation
of
blogs
that
showcase
different
application
types
for
hera.
In
the
realm
of
machine
learning,
data
processing,
etl,
similar
to
the
topics
outlined
on
the
argo
workflows,
readme,
for
example.
D
D
Lastly,
it
would
be
valuable
for
some
users
to
have
access
to
more
contextual
types
for
different
cloud
providers
such
as
tolerations
and
node
selectors,
for
example,
that
are
very
contextual
to
what
you
see
in
the
google
kubernetes
engine
azure
and
aws
in
the
last
minute.
I'd
like
to
briefly
cover
some
thoughts
and
contributions.
There
are
currently
24
unique
contributors.
The
hereafter
whom
I
want
to
extend.
Thank
you
for
donating
your
time
and
effort
to
making
hero
better
a
better
product.
D
Hair
is
also
looking
for
retainers,
which
would
help
enable
the
path
to
feature
parity
with
argo
workflows
and
potentially
argo
cd,
which
might
enable
wider
community
adoption
by
supporting
more
features
of
argo
and
enabling
and
enable
the
integration
of
argo
with
other
tools
such
as
desk
and
apache.
Apache
spark.
B
B
E
One
quick
question:
what
would
like
the
plan
dash
or
like
spark
integrations?
Look
like
I
mean,
would
it
be
like
hey
we're,
invoking
some
sort
of
like
workflow
template
that
we
are
baptizing
as
like
canon
for
each
of
these
integrations,
or
is
this
like
a
dedicated
like
spark
or
desk
task?
That
would
become
like
a
primitive
within
hera
itself?.
D
A
Awesome
yeah
thanks
again
flav
for
the
update
and
I
think
that's
going
to
be
a
wrap
for
this
meeting.
We
were
going
to
have
another
presentation,
but
unfortunately
the
presenter
had
an
unexpected
health
issue,
come
up
so
we'll
slot
that
for
july's
presentation
and
like
I
said
at
the
beginning,
if
anybody
has
any
interest
in
demoing
we're
giving
a
longer
presentation,
please
don't
hesitate
to
slack
me
on
in
the
cncf
chat
or
or
send
me
an
email.