[Pulp-list] pulp without consumer agents

[Michael Hrivnak]

Thanks for asking.

Pulp is moving away from consumer management. We think the best path for
everyone is to focus on making pulp a great repository management tool, and
leave system management to other projects that are dedicated to that
purpose. Lots of our users already use ansible and puppet, so those are
great starting points if you are looking to replace pulp-agent.

The current thinking is to remove pulp-agent and related features in 3.0.
We will keep consumer tracking features though; you'll be able to use the
API to report to pulp what machines exist in your infrastructure, what
packages they have installed, what repositories they are using, and then
pulp will tell you what updates are needed. All of this functionality
exists today; it just won't be integrated with an agent anymore.

I'll send out more detail on the roadmap soon, but we hope to begin work on
3.0 relatively soon. We are already doing technical planning and
preparation.

And of course, we want feedback and participation from everyone who is
interested. As the core team, it can be challenging to identify what the
best ways are to keep the whole community engaged, and to offer
opportunities for participation. If you have thoughts about whether we
should or should not keep pulp-agent, or anything else related to long-term
planning, please share those thoughts!

Michael

On Thu, Mar 31, 2016 at 11:26 AM, Ashby, Jason (IMS) <AshbyJ at imsweb.com>
wrote:

> Hmm, I’m interested in hearing more about the agentless consumer proposal
> as well.
>
>
>
> I recently removed pulp from of all my consumers completely and instead
> have only the Pulp server. I use puppet to deploy the yum.repos.d files and
> sslcacert that needs to present on the consumers. I use good old-fashioned
> ssh to do the yum updates.
>
>
>
> I’ve been using pulp for about 2+ years, and I’ve always battled with SSL
> cert issues (we have a root CA so I was dealing with an intermediary cert
> for the pulp server which was tricky) as well as message queues (qpid and
> rabbitmq) always going down either from the messaging server or the
> consumer/agent itself.  This is not to say it was pulp’s fault, but I felt
> like it was overkill for only 300ish servers we need to manage.  This new
> setup we’re using is way simpler and less for me to manage…just a server
> serving pulp repos.
>
>
>
> *From:* pulp-list-bounces at redhat.com [mailto:pulp-list-bounces at redhat.com]
> *On Behalf Of *Elizabeth Jones
> *Sent:* Thursday, March 31, 2016 10:57 AM
> *To:* pulp-list at redhat.com
> *Subject:* [Pulp-list] pulp without consumer agents
>
>
>
> I recently saw a youtube pulp video that I think was dated Jan 2016, the
> speaker was from redhat and mentioned in passing that pulp was going to be
> phasing out consumer agents.  Does anyone know anything more about this?
> We are running into problems being allowed to install anything on our
> servers and it would be handy if we could manage server patching from the
> pulp server without having to install a consumer agent on the consumers.
>
>
>
> thanks,
>
> EJ
>
> ------------------------------
>
> Information in this e-mail may be confidential. It is intended only for
> the addressee(s) identified above. If you are not the addressee(s), or an
> employee or agent of the addressee(s), please note that any dissemination,
> distribution, or copying of this communication is strictly prohibited. If
> you have received this e-mail in error, please notify the sender of the
> error.
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160331/410a6a04/attachment.htm>