Katello: Do capsules replace foreman-proxy?

Support
1

I am at a loss as to whether I install a foreman-proxy or capsule on my
remote DHCP server. I have a recently installed Katello 2.2 server that
will be managing it.

2

> I am at a loss as to whether I install a foreman-proxy or capsule on my
> remote DHCP server. I have a recently installed Katello 2.2 server that
> will be managing it.

Capsules are smart-proxies with more features. So a capsule will work
as a smart-proxy, and you should add it as a new Smart proxy in Foreman.

See http://www.katello.org/docs/2.2/user_guide/capsules/index.html for
reference.

··· On 05/19, lawre wrote: > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

–
Daniel Lobato Garcia

@eLobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato

3

> Capsules are smart-proxies with more features. So a capsule will work
> as a smart-proxy, and you should add it as a new Smart proxy in Foreman.

I like to say that Capsules are downstream deployments and contains
several components: Pulp, Puppet Master and Smart Proxy. It's a
different point of view, less confusing for Capsule users who sometimes
need to restart "foreman-proxy" service (not "capsule-service" because
there is no such a thing).

> See http://www.katello.org/docs/2.2/user_guide/capsules/index.html for
> reference.

What folks think? Should we re-word the docs above?

··· -- Later, Lukas #lzap Zapletal
4

Lukas is correct, downstream there is a naming collision around
smart-proxy with other products. So, you can think of a capsule as a
smart proxy.

– bk

··· On 06/02/2015 05:00 AM, Lukas Zapletal wrote: >> Capsules *are* smart-proxies with more features. So a capsule will work >> as a smart-proxy, and you should add it as a new Smart proxy in Foreman. > > I like to say that Capsules are downstream deployments and contains > several components: Pulp, Puppet Master and Smart Proxy. It's a > different point of view, less confusing for Capsule users who sometimes > need to restart "foreman-proxy" service (not "capsule-service" because > there is no such a thing). > >> See http://www.katello.org/docs/2.2/user_guide/capsules/index.html for >> reference. > > What folks think? Should we re-word the docs above? >
5

Having said this… i am sure that the PM folks downstream would love for
the term capsule to be adopted upstream.

– bk

··· On 06/02/2015 10:54 AM, Bryan Kearney wrote: > Lukas is correct, downstream there is a naming collision around > smart-proxy with other products. So, you can think of a capsule as a > smart proxy. > > -- bk > > > On 06/02/2015 05:00 AM, Lukas Zapletal wrote: >>> Capsules *are* smart-proxies with more features. So a capsule will work >>> as a smart-proxy, and you should add it as a new Smart proxy in Foreman. >> >> I like to say that Capsules are downstream deployments and contains >> several components: Pulp, Puppet Master and Smart Proxy. It's a >> different point of view, less confusing for Capsule users who sometimes >> need to restart "foreman-proxy" service (not "capsule-service" because >> there is no such a thing). >> >>> See http://www.katello.org/docs/2.2/user_guide/capsules/index.html for >>> reference. >> >> What folks think? Should we re-word the docs above? >>