►
Description
Foreman is a complete lifecycle management tool for physical and virtual servers. It gives system administrators the power to easily automate repetitive tasks, quickly deploy applications, and proactively manage servers, on-premise or in the cloud.
https://theforeman.org/
Pulp is a platform for managing repositories of software packages and making them available to a large number of consumers. Pulp can locally mirror all or part of a repository, host your own software packages in repositories, and manage many types of content from multiple sources in one place. https://pulpproject.org/
A
Another
open
shift
commons
briefing
today
as
we
like
to
do
on
mondays.
It's
an
ask
me
anything
with
either
a
project
or
an
upstream
project
or
a
product
or
a
new
initiative
someone's
kicking
off,
and
this
week
we
have
a
new
community
manager,
melanie
core
with
us
who's,
getting
the
pleasure
of
managing
and
herding
cats
for
pulp
and
foreman.
So
welcome
melanie,
and
we
have
two
folks
eric
helms
from
the
foreman
project
and
dennis
kilden
from
the
pulp
project.
A
So
I'm
really
psyched
to
have
them
come
here
to
give
us
an
update
on
what's
going
on
in
each
of
these
projects
and
for
melanie
to
take
over
the
reins
of
managing
these.
These
cats,
and
so
melanie,
tell
us
a
little
bit
about
where
you
came
from
in
your
new
role
and
then
let's,
let's
rock
and
roll,
learn
more
about
foreman
and
phelp.
B
Thank
you,
dan,
and
thank
you
very
much
for
having
us
all
here
today.
It's
a
pleasure
to
be
here,
and
so,
first
of
all,
yep,
my
name
is
melanie
core.
I
have
been
with
red
hat
for
just
over
three
years
now,
and
I've
been
working
as
a
community
manager
for
almost
exactly
six
months
and
quite
interesting.
B
So
before
community
management,
I
was
working
with
red
hat
satellites
on
the
documentation
team
leading
that
team
for
about
18
months,
and
so
I
suppose,
the
bit
of
background
and
the
foreman
project
itself
is
11
years
old
and
from
a
lot
of
that
time
they
had
a
dedicated
community
manager.
When
that
community
manager
greg
softkliff
decided
to
start
exploring
a
career
in
data
analysis,
a
lot
of
the
roles
were
divided
amongst
different
people
for
the
community.
B
So
it's
it's
been
it's
been
an
interesting
few
months
and
then,
on
the
other
hand,
there's
pulp,
which
is
also
a
very
interesting
project
and
also
feeds
into
foreman
and
I've
been
working
with
them
to
maybe
grow
the
community.
A
little
bit
more.
So
this
year
has
been
also
extremely
interesting
because
we
haven't
had
any
live
or
in-person
meetings
or
conferences,
so
we're
all
here
together
from
all
different
parts
of
the
world
meeting
in
in
new
ways.
So
that
has
been
particularly
interesting.
B
We
had
our
first
ever
live
our
first
ever
virtual
hub
con
this
year
and
our
first
ever
foreman
birthday
party,
and
so
it
was.
I
was
quite
excited
and
delighted
that
we
got
to
meet
so
many
faces.
We
wouldn't
have
otherwise,
and
I
think,
unless
any
of
any
particular
questions,
I
think
that's
pretty
much
everything
that
I
can
say
to
introduce
myself
at
this
point.
So,
if
not
I'd
be
very
happy
to
hand
over
to
eric
helms
for
his
first
demo
or
peace.
A
All
right
eric,
that's
great,
so
welcome
aboard
and
thank
you
for
taking
on
that
challenge
melanie.
It
definitely
is,
and
popcorn
and
birthday
the
birthday
parties
are
always
fun
for
foreman.
So
eric
tell
us
a
bit
and
about
yourself
and
then
maybe
quickly
dennis
so
you
know
he
doesn't
feel
left
out
and
then
we'll
go
run
into
your
your
presentation
about
what's
going
on
in
foreman
and
where
it's
going.
C
Okay,
so
I've
been
at
red
hat
for
like
nine
and
a
half
years,
and
I
started
as
an
intern
working
on
what
is
now
a
plug-in
to
form.
But
you
can
effectively
say
I've
been
working
on
part
of
foreman
in
its
downstream
product
that
red
hat
makes
called
satellite
for
the
whole
nine
and
a
half
years
that
I've
been
here
and
so
I've
seen
a
lot
through
the
community,
and
you
know
more
recently,
I
moved
into
the
an
architect
role
within
satellite
the
product.
D
D
However,
when
I
joined
we
had
purchased
the
company
to
replace
cloudform,
so
I
had
to
find
another
project
to
work
on
and
I
ended
up
working
on
pulp,
which
was
great
because
I
was
already
friends
with
the
folks
that
worked
on
pulp.
They
sat
near
where
I
sat
so
I
felt
like
I
was
part
of
the
team
before
I
even
joined,
and
so
I've
been
working
on
pulp
for
six
years-
I
guess
maybe
more
and
for
a
lot
of
that
time
we
been
rewriting
pope
and
I'll
talk
about
the
rewrite
of
it.
A
All
right
well
thanks,
and
I'm
really
grateful
that
you're
all
here
today.
So
thanks
very
much
and
it's
wonderful
to
see
faces
from
all
the
teams
too,
so
eric.
Why
don't
you
give
us
your
spiel
and
your
your
talk
about
where
foreman's
at
today,
it's
nice
having
the
historical
perspective
too,
so
take
it
away
and
share
your
screen
and
we'll
rock
and
roll.
C
C
You
know
kind
of
a
lot
of
similar
ways,
at
least
towards
the
end
of
the
story,
becomes
the
same
in
in
both
cases.
It's
just
a
matter
of
kind
of
how
you
start
so
think
of
and
I'll
go
into.
You
know
what
these
things
kind
of
mean
or
how
we
look
at
them
as
the
foreign
project,
but
you
start
by
you
know,
defining
what
it
is
that
you
want
to
what
you're
planning
to
create
you
know.
Is
it
a
web
server?
Is
it
a
database
server?
Is
it?
C
B
C
C
So
you
want
to
start
managing
stuff
from
a
single
place
so
that
you
can
start
to
scale
out.
Maybe
certain
types
of
deployments
that
you
have,
and
in
that
case
you
can
import
the
existing
machines.
You
have
through
a
variety
of
mechanisms,
get
into
those
and
then
once
you've
imported
them.
You
can
start
to
build
out
your
definitions.
Just
like
the
greenfield
case.
C
You
could
even
go
back
sort
of
to
the
green
field
path
and
provision
new
machines
based
on
those
definitions-
and
you
know
end
up
in
sort
of
the
active
management
state
where
you're
monitoring
the
configuration
and
you're
making
changes
and
you're.
Looking
at
reports
and
you're
keeping
an
eye
on
things-
and
you
know
applying
security
changes
and
configuration
changes
and
doing
all
of
the
life
cycle
of
your
posts
and
systems
through
just
you
know
a
single
point
of
view,
which
is
foreman.
C
So
you
know
from
that:
what
is
it,
what
does
kind
of
foreman
look
like?
What
are
you
trying
to
deploy?
You
know
what
are
some
other
like
when
you
think
about
the
aspects
of
it
like
this?
Is
this
is
kind
of
our
old
school?
You
could
say
this
is
very
part
of
the
history
of
foreman.
This
image
has
been
around
for
like
seven
or
eight
years
in
the
architecture
it
has
evolved,
but
it
hasn't
really
changed
from
the
central
concept
that
you
have.
C
You
have
a
central
foreman
server,
that's
receiving
reporting
and
data
and
information
from
various
sources.
You've
got
a
web
ui
you've
got
this
rich
api
and
then
there's
a
piece
of
software
called
the
smart
proxy,
which
is
a
serves
a
number
of
purposes,
so
you
might
install
a
form
and
server,
and
then
you
might
go
install
a
smart
proxy
on
a
different
machine
and
how
you
deploy
that
machine
may
depend
on
your
network
topology
or
what
you're
trying
to
achieve.
C
You
can
deploy
a
smart
proxy
with
the
idea
that
you
want
it
to
sit
at
the
edge
of
your
data
center,
so
you
can
deploy
different
smart
proxies
to
different.
You
know
different
data
centers
at
the
edge
of
those
different
data
centers
or
cloud,
so
you
can
use
it
as
the
sort
of
like
isolated
communication
to
anything
inside
that
network
and
the
smart
products.
You
can
talk
back
to
foreman.
C
It
also
provides
a
sort
of
restful
api
to
things
that
traditionally
don't
have
web-based
apis.
You
know
dnsd
some
dhcp
tftp,
some
providers
that
you
would
typically
have
to
ssh
into
the
box
or
run
or
configure
that
way.
The
smart
proxy
provides
a
wave
do
that
through
a
common
api
for
those
at
all
and
as
well.
It
provides
a
sort
of
like
an
abstracted
api
over
different
providers.
C
So
you
can
really
start
to
build
up
common
patterns
and
api
to
advantage
or
use
it.
You
know
like
for
isolation
for
scale
out
offloading
a
number
of
hosts
that
are
being
managed
or
routing
traffic
through
this
applies
when
we
get
to
some
of
the,
like.
Also
cache
send
out
content
so
like
rpms
files,
debian.
C
Push
out
content
to
those
things
so
they're
much
closer.
If
you
have
networks
that
are
unreliable,
you
can
push
it
out
the
data
out
there,
so
it's
closer
to
the
machines
that
need
to
get
it
rather
than
each
and
every
one
of
them
having
to
reach
all
the
way
back
to
foreman
to
get
that
data,
and
we'll
talk
more
about
that
as
we
come
along.
B
C
C
You
can
define
lots
of
attributes
on
a
host
group.
You
can
define
the
environment
the
content,
what
config
management
provider
you
want
to
use,
whether
it's
ansible
or
puppet
or
salt
or
chef
domain,
subnet,
os
architecture,
all
the
things
that
go
into
how
you
define
what
this
machine
is
or
when
you
provision
it
or
you
can
figure
it.
C
Host
groups
are
nested,
so
you
can
create
different
layers,
different
concepts
and
you
can
organize
it.
How
you
want
to
organize
it.
So
maybe
you
want
to
organize
it
in
a
way
where
you're
creating
what
a
base
level
rel7
host
looks
like
and
then
on
top
of
that
you're
building
out
what
your
web
server
looks
like
what
software
is
on
the
web
server?
C
You
know
the
content,
that's
on
them,
the
layout
on
the
file
system,
the
puppet
modules
I
want
to
apply
to
it
or
the
playbooks.
I
want
to
run
on
it
and
then
you
might
have
small
variations
that
you
want
to
apply.
On
top
of
that,
if
you
happen
to
have
kids,
that's
running
rel
versus
one,
that's
debian,
so
really
host
groups
provide
this
way
to
configure
and
define
what
your
hosts
look
like.
So
that
you
can,
you
know,
provision
multiples
of
them.
You
can
make
updates
and
then
run
updates
across
them.
C
You
can,
you
know,
scale
those
deployment
types
out,
then
there's
other
you
know
so
I
hadn't
mentioned
this,
but
so
you
know
foreman
started
itself
as
a
way
to
manage
a
ui
and
a
way
to
manage
puppets,
and
then
it
brought
a
lot
of
provisioning
capabilities.
On
top
of
it,
then
it
built
out
a
kind
of
plug-in
ecosystem
and
that
plug-in
ecosystem
brings
in
a
lot
of
power
and
functionality.
C
C
Maybe
you
want
to
life
cycle,
you
know
your
your
vagrant
boxes
as
an
example
of
something
we
do
internally
as
part
of
our
development
cycle.
Maybe
you
want
ansible
content.
Maybe
you
want
container
images,
you
can
define
what
those
repositories
are,
what
that
content
is,
and
you
can
use
this
concept
called
content
views
to
further
customize.
It
so
say
you
sink
down
you.
You
want
to
be
a
rail
shop
and
you
want
to
customize
that
rail
or
you
want
to
lock
it
down
to
certain
kernel
modules
or
something
like
that.
That's
you
know.
C
These
are
use
cases
that
people
do
it
and
content
views
in
this
definition.
Allow
you
to
do
that.
Then
you
can
get
into
the
defining
config
management
side
by
choosing
what
provider
and
so
forman
started
is
with
puppet
integration.
But
over
the
years
people
have
added
plugins
that
provide
all
of
the
other
providers
out
there,
so
you
may
define
and
want
to
set
what
puppet
classes
or
ansible
roles
or
chef,
cookbooks
or
salt
states
that
you
want
applied
to
your
system.
C
You
know,
after
you've
defined
what
you
want.
Then
you
can
get
into
the
visioning
space
which
foreman
has
been
doing
for
a
long
time.
You
can
do
bare
metal
virtual
provisioning.
You
can
pixie,
you
can
do
it
through
image
based
provisioning,
there's
a
plug-in,
that's
known
as
discovery
which
provides
this
concept,
the
metal
as
a
service
concept,
which
you
know,
is
kind
of.
C
The
idea
that
you
can
go
plug
in
a
brand
new,
bare
metal
machine
and
it
will
call
out
and
register
itself
back
to
foreman
and
then
based
on
a
set
of
rules
that
you've
set
up.
It
can
automatically
provision
itself,
so
you
plug
it
in
it
boots
up.
It
reaches
out
provisions
itself
based
on
your
set
of
rules,
and
it's
just
ready
to
go.
C
There's
a
number
of
compute
resources
that
we
support
that
come
in
through
plugins.
You
know
the
various
cloud
providers,
various
virtualization
providers.
You
know
there's
plenty
out
there
that
we
support
today
and
and
individuals
teams.
Businesses
can
come
in
and
add
support
for
any
of
the
that
concern
them
if
they're
not
on
their
list
already
by
creating
a
plugin.
C
So
the
other
way
right
in
the
brownfield
ideas
is
say
you
don't
want
to
define
a
provision,
but
you've
got
all
these
machines
that
exist
out
there
in
the
world,
maybe
you're
managing
them
for
through
chef,
maybe
you're,
managing
the
puppet,
maybe
ansible
you
can
import
the
machine.
You
know
the
hosts
out
there
back
into
foreman
to
start
to
get
your
landscape.
Your
inventory,
all
together
through
through
their
kind
of
you,
know,
native
methods.
C
Really
it's
just
about
sending
facts
and
information
about
that
machine
back
to
foreman
and
there's
various
integrations
for
each
of
these
out
there
you
know
puppet
being
foreman's.
You
know
original
use
case
where
puppet
facts
and
reports
would
send
back
and
now
you
can
manage
that
host
through
native
puppet
methods.
C
We
got
the
red
hat
side
with
subscription
manager
and
then
there's
pearl
up
there,
because
I
mentioned
this
when
it's
like.
What's
up
coming
we're
working
on
a
more
generic
way,
if
you
don't
use
one
of
these
providers
configuration
providers
a
more
global
direct
way,
we're
calling
global
registration
to
get
import
a
host
into
foreign
for
active
management.
C
C
You
know
if
you're
wet,
if
you
have
your
web
server
case,
you
can,
you
know,
have
ansible
roles
that
set
up
apache
for
you
or
you
could
have
your
jeff
cookbook.
That
sets
up
say
next
for
you
on
the
machine
and
when
it's
provisioned
or
if
you
assign
it
to
the
host
it'll,
get
run
and
they'll
get
picked
up
and
run
by
that
particular
config
management
solution,
which
will
also
then
send
back.
C
C
C
This
provides
the
ability
to
just
go
run.
You
know
user-defined
bash
scripts
through
the
templating
engine
and
tippling
language,
that's
inside
of
foreman
or
you
can
run
ansible,
playbooks
or
ansible
roles.
This
is
both
of
those
currently
happen
through
ssh,
but
they're,
both
still
backed
by
the
templating
system.
I
haven't
really
mentioned
yet,
but
it
shows
up
in
a
lot
of
places
in
foreman
and
has
a
lot
of
power.
So
provisioning
is
very
template
driven.
C
C
They
get
executed
same
thing
with
the
playbooks
and
the
roles
and
then
also
here
in
the
past
couple
of
releases,
there's
been
some
reporting.
That's
been
present
given
to
the
user,
where
they
can
define,
use
the
same
kind
of
templating
idea
to
generate
reports
of
what
is
within.
You
know,
foreman's
database
within
its
inventory.
C
That,
then,
can
be,
you
know,
exported
and
looked
at,
or
you
know
done
whatever
a
user
needs
to
do
with
that
sort
of
information
of
everything
that's
going
on,
and
then
you
can
also,
through
the
catello
plug-in,
have
there's
this
concept
of
lifecycle
environments,
where
you
can
choose
that
your
hosts
are
in
the
dev
environment
or
the
test
environment,
production,
environment,
and
you
can
push
content
through
those
environments.
You
can
make
choices
based
on
what
environment
the
hosts
live.
In
so
say,
you're
rolling
out
a
new
software
update.
C
You
can
roll
it
out
to
your
dev
environment.
Posts
that
are
in
your
dev
environment
could
get.
You
know
updated
through
save
remote
execution
to
get
that
new
software.
You
could
then
go
out
and
test.
It
look
at
reports
coming
back
foreman
about
what's
happening
in
that
environment
and
when
you
feel
good
about
it,
you
can
roll
that
update
into
maybe
the
qa
environment
or
just
straight
out
to
production
and
then
go
issue
either
updates,
like
I
said,
through
remote
execution
or
say
you're,
using
puppet
by
rolling
it
out
to
production.
C
You
know
your
puppet
and
you
know
puppet
agent
out
there
wakes
up
and
says:
oh
hey,
there's
updates
I'm
going
to
apply
them,
and
now
those
systems
are
up
to
date
and
sending
reports
and
information
back
for
the
you
know
active
management
side
of
things
and
there's
a
lot
that
you
can
do
with
the
active
management
right.
You
can
still
like
that's
what
you
know.
I
mentioned
iterating
through
dev
test
prod.
You
can,
then
you
know
be
thinking
about
inspecting
your
inventory.
C
C
C
C
C
So
that's
that's
sort
of
like
a
pretty,
I
think,
kind
of
high
level
overview
of
trying
to
like
tell
the
story
of
what
you
can
do
with
foreman.
You
know
I
I
like
to
think
of
it
that
you
can
do
a
lot
with
foreman,
but
there's
a
lot
involved
with
you
know,
defining
what
a
system
looks
like
provisioning
it
actively
managing
it,
keeping
on
top
of
security
updates,
keeping
it
from
drifting
with.
C
And
then
I'll
just
kind
of
give
some,
I
think
ecosystem
highlights
for
anybody
curious
at
that
level
about
foreman.
It
does
have
an
api.
I
I
label
it
as
I
like
to
think
of
it
as
ways
that
you
can
help
you
automate
and
scale
out
your
form
and
deployment
your
use
of
foreman.
We
have
there's
the
api
there's
the
cli,
which
is
known
as
hammer
and
then
over
the
past
year.
C
There
is
a
robust
installer
that
is
based
on
a
set
of
puppet
modules,
kind
of
harkening
back
to
foreman's
roots.
The
installer
provides
an
interface
and
an
installation
experience,
but
it's
on
top
of
a
set
of
pipeline
modules,
where
each
one
is
built
to
deploy
the
various
services
that
someone
might
want
there.
The
project
does
provide
rpm
and
debian
based
packages
for
each
of
it
anytime.
There's
a
release
you
can
go
to
the
foreman.org
is
the
main
website.
C
C
You
know.
Sometimes
we
see
these
plugins
show
up
in
the
community
show
up
in
the
open
source.
We
also
know
that
in
some
cases
businesses
build
stuff
for
their
internal
needs
and
they
keep
it.
You
know
closed
source
because
they're
specific
to
their
workflows
that
they're
building
off
of
foreman,
but
you
have
probably
the
biggest
plug-in,
which
is
catello.
C
It
does
content
and
entitlement
management.
It
is
the
main
interface
to
the
pulp
project,
which
is
doing
all
the
heavy
lifting
content
under
the
hood,
which
dennis
will
give
us
lots
of
good
details
about
there's
plugins
for
salt
chef,
ansible
configuration
management
providers.
I
remember
I
mentioned
remote
execution
discovery.
If
you
want
to
do
you
know
provisioning
through
metal
as
a
service,
you
know
plug-in
provision
based
on
rules
open
s-cap
for
open
s-cap
compliance.
There's
a
web
hooks
plug-in
in
the
works.
There's
plug-ins
for
cloud
providers
for
vault
integration.
C
C
We
are
looking
towards
a
foreman
in
the
future
and
say
the
the
biggest
reason
we're
looking
ahead
to
that
is
because,
like
I've
said
part
of
its
foreman's
history,
it's
you
know
has
been
its
puppet
integration
which
was
built
into
foreman
and
so
there's
a
team
working
hard
to
pull
out
the
puppet
to
a
plug-in
which
puts
it
on
the
same
footing
as
the
other
configuration
management
providers.
It
provides
a
little
more.
C
You
know,
cohesive
experience
for
what
your
config
management
provider
is
and
pulls
puts
a
little
more
focus
on
the
main
forman
app
to
be.
You
know
the
place
that
bring
allows
you
to
do
provisioning,
brings
your
inventory
in
and
has
integration
points
for
these
different
import
methods.
These
different,
you
know,
providers
that
can
send
fax
and
tell
you
about
a
host.
C
The
telo
project
is
doing
a
big
migration
to
pulp
three
for
its
content
and
that
make
make
a
lot
more
sense
when
I
hand
it
over
to
dennis
in
just
a
minute
the
global
registration
api
which
is
gonna.
Allow
you
to
not
necessarily
have
to
have
a
you
know:
provider
such
as
ansible
or
puppet
or
subscription
manager
to
import
the
host.
You
can
do
it
through
their
this
new
global
registration
api
and
enables
more
workloads
web
hooks
plug-in
on
the
rise
and
then
a
lot
of
some
look
into
reworking
some.
A
Yeah,
I
think
that
that
was
great.
I
really
appreciate
that
the
insights
and-
and
it's
I've
been
a
long
time
since
I've
looked
at
puppet
stuff
and
ansible
stuff,
and
also
so
it's
really
a
good
refresher
for
me.
So
thank
you
and-
and
I
really
do
like
the
single
pane
of
glass
for
the
monitoring
as
well.
So
sometimes
we're
gonna
have
to
get
you
on
and
do
a
demo
of
all
that
really
really
well
done.
So
dennis
cue
up
pulp
and
tell
us
how
pulp
fits
into
this
puzzle.
D
Thank
you
yeah.
I
don't
have
any
slides.
I
have.
We
have
our
website
that
I
can
hear
in
a
little
bit,
but
I
just
want
to
give
an
overview
of
pulp
and
pulp
is
a
platform
I
think
of
it,
as
actually
as
a
toolbox
for
managing
a
software
repositories,
and
we
are
also
plug
and
based
like
forman
is,
and
each
type
of
content
that
you
want
to
manage
is
managed
by
a
different
plugin.
D
Historically,
the
rpm
plug-in
has
been
like
the
most
robust
and
has
had
the
most
users
I
would
say,
and
it
is
probably
what
drove
for
pulp
to
be
created.
Red
hat
actually
uses
pulp
to
make
all
the
rpms
that
it
publishes
available
to
the
world,
and
many
other
companies
actually
use
pulp
as
the
system
that
they
distribute
their
own
custom
software
through.
D
As
I
mentioned,
we
have
multiple
plugins
and
when
I
first
started
working
on
pulp,
we
were
actively
developing
pulp
2
and
it
had
a
limited
set
of
plug-ins
and
the
architecture
of
pulp.
2
was
such
that
it
was
actually
very
difficult
to
add
support
for
additional
content
types
and
there
wasn't
really
a
defined
plug-in
api.
Every
time
you
had
to
you
wanted
to
add
a
content
type
to
pulp.
D
And
so
we
decided
to
go
on
this
long
journey
to
rewrite
pulp
2
and
create
pulp.
Three-
and
I
say
long
because
it
took
us
about
three
years
to
rewrite
all
of
pulp
and
our
focus
was
on
plug-ins
and
to
make
it
a
lot
easier
to
add
new
plugins
to
pulp,
and
that
has
actually
worked
out
really
well
for
pulp
3.
We
now
have
the
rpm
plugin,
which
you
know,
as
I
said,
is
our
most
important
plug-in,
but
we
also
have
the
file
plug-in
the
container
plug-in
that
lets.
D
D
We
also
have
a
debian
plugin,
which
we
did
have
with
pulp
2.
Also,
we
have
a
python
plug-in,
which
is
about
to
release
a
2-0
generally
available
release
which
will
allow
users
to
create
a
full
mirror
of
pi
pi
and
not
only
create
a
full
mirror.
It
will
let
users
think
multiple
times
and
only
sink
down
like
the
changes
that
were
made
to
pi
p
I
and
pi
p.
I
is
a
very
large
collection
of
python
packages
that
you
would
not
want
to
sync
over
and
over
again
and.
D
D
It
will
go
download
that
package
save
and
serve
it
to
the
client,
but
then
they
will
also
save
it
in
pulp,
so
that
any
subsequent
request
will
be
actually
served
by
pulp
and
for
content
types
like
python.
It
is
definitely
recommended
to
use
the
on-demand
policies
and,
I
believe,
actually
foreman
and
catello
by
default,
create
repositories
with
the
on-demand
policy
unless
the
user
asks
to
do
otherwise,
and
so
we've
been
doing
this
rewrite
and
we
actually
released
pulp
3
back
in
december
of
2019
and
we
released
it.
D
Even
though
we
were
able
to
improve
the
plug-in
api
and
we've
made
for
a
better
rest
api,
we
are
still
missing.
Some
features
that
we're
we
really
want
to.
You
know
get
to,
and
one
of
the
ones
that
we're
actively
working
on
is
role-based
access,
control
and
we've
already
actually
added
the
machinery.
That's
needed
inside
of
core
to
provide
role-based
access,
control
and
now
plugins
are
working
on
adding
that
to
their
feature,
sets
and
we're
hoping
that
that
will
be
done
before
the
end
of
the
year.
D
D
Pulp
does
a
lot
of
asynchronous
work,
so
checking
task
status
is
a
very
important
part
of
the
workflow,
and
so
we've
started
the
work
on
the
pulp.
Cli
and
the
command
is
just
called
pulp,
no
longer
called
pulp
admin,
it's
called
pulp
and
we've
sent
out
a
call
for
feedback
on
our
mailing
list
earlier
today.
D
Another
thing
that
we
are
adding
is
ansible
modules
and
the
ansible
modules
that
we've
created
are
inspired
by
the
forman
ansible
modules
actually,
and
they
are
very
popular.
We've
noticed
that
people
are
downloading
them
a
lot
from
ansible
galaxy
and
I
don't
think
people
are
just
using.
You
know
pulp
out
there
too,
sync
them
all
the
time
which,
if
you
look
at
other
packages
like
rubygems
you'll,
see
that,
oh,
my
god,
my
package
is
so
popular,
but
I
suspect
people
are
just
mirroring
that
content
all
the
time.
D
I
don't
think
it's
quite
the
same
for
the
ansible
module,
the
ansible
collections
quite
yet,
but
another
thing
that
we've
introduced
with
pulp
3
is
our
open
api
schema
and
the
open
api
schema
that
defines
our
rest.
Api
is
what
allows
us
to
generate
client,
libraries
for
python
and
ruby
and
the
big
integration
that
eric
mentioned
between
catello
and
pulp.
3
is
using
this.
These
auto-generated
bindings,
the
client
library
that
is
allowing
catella
may
to
make
great
strides
in
this
integration
with
pulp,
3.
D
and
another
great
thing
about
the
open
api
is
that
it
not
only
lets
us
generate
clients
in
python
and
ruby.
I
believe
it's
40
plus
languages
that
the
open
api
generator
supports.
So
our
next
client
is
going
to
be
actually
a
javascript
client
that
we're
going
to
start
publishing
to
npm
and
that
client
is
going
to
be
used
by
students
from
university
of
massachusetts
at
lowell
to
build
a
ui
for
pulp.
D
A
D
A
D
Yeah-
and
so
I
referred
to
pulp
as
a
toolbox
earlier,
and
that's
because
we
provide
a
lot
of
rest
apis
and
our
project
has
been
consumed
through
the
rest
api
for
a
long
time,
and
you
can
integrate
it
into
your
continuous
integration
systems
or
into
your.
You
know,
continuous
delivery
or
just
in
general
delivery
of
content,
and
there
are
many
different
ways
to
make
the
content
available
and
to
curate
it,
but
we
want
to
make
it
more
than
just
a
toolbox
but
a
tool
also.
That
is
a
little
bit
prescriptive.
D
D
D
D
D
There
are
links
to
the
source
code
to
the
issue
trackers
to
the
packages
on
pi
pi
to
the
documentation
for
them
each
one
of
them
has
its
own
documentation
site.
We
are
in
the
process
of
combining
all
that
into
a
single
site,
so
hopefully
that
will
that
project
will
finish
soon
and
it
will
be
easier
to
navigate
all
of
the
plugins
documentation.
D
D
D
We
are
trying
to
get
back
into
doing
more
youtube
videos.
We
were
doing
them
as
we
were
getting
ready
for
the
pulp,
3
release,
getting
people
excited
about
things
and
then,
over
this
past
year,
that
effort
has
slowed
down
and
when
we
were
having
our
pulp
con,
which
was
virtual
earlier
this
year
we
definitely
had
requests
from
community
members
to
post
more
videos,
and
I
agree
with
those
community
members,
and
we
will
start
doing
that.
A
Well,
pumping
out
the
content
is
really
kind
of
key,
but
then
there's
also.
I
love
that
that
you
have
such
great
strong
docs
as
well.
I
think
we
have
a
tendency,
at
least
in
the
openshift
team,
to
document
by
blogging
or
by
creating
content,
and
that
goes
that
fades
away.
So
don't
feel
too
bad
about
not
having
a
lot
of
video
content,
but
you've
just
created
a
wonderful
one
today,
so
they'll
they'll
be.
A
And
we'll
get
that
out
and
push
push
this
out
in
the
social
channels
as
well.
So
there
we
have
about
two
minutes
left
melanie.
Is
there
anything
that
you
want
to
incite
these
guys
to
talk
about
or
promote
that's
coming
up
on
the
radar?
Next,
like
the
next
pulp
con
or
conference,
or
thing
that
we
need
to
make
sure
that's
on
everybody's
radar.
B
Not
particularly
at
the
moment,
I
suppose,
from
the
pulp
team,
as
dennis
said,
we
have
a
call
for
some
feedback
on
our
pulp,
3
proof
of
concept
for
the
cli,
and
you
know
if
you
do
test
that
there
is
some
swag
on
offer
for
that
and
with
the
foreman
community.
We
have
a
demo
every
three
weeks
and
this
thursday
we
have
a
demo
of
the
latest
and
greatest
changes
in
the
foreman
community,
so
that
is
live
on
a
on
a
thursday.
It's
in
our
calendar
on
the
community.
A
Perfect
well,
I'm
gonna
get
you
to
send
me
the
links
to
all
of
that.
We'll
push
this
video
out
on
the
openshift
commons
playlists
for
the
ama
you're
welcome
to
reuse
it
edit
it
any
way
you
want-
and
I
am
just
really
happy
to
have
all
three
of
you
here
today-
to
share
this.
It's
as
a
great
update,
thanks
eric
and
dennis
and
and
melanie
welcome,
aboard
your
your
welcome
site
to
have
some
community
support
behind
all
of
this
stuff.