[Pulp-list] Using Pulp in a server-only configuration?

[Trey Dockendorf]

Your use case matches exactly how we use Pulp to manage repo contents for a
HPC cluster where a consumer service is not possible.  I've had no issues
and just push out repo files for all pulp managed repos using Puppet.
Since I'm using self signed certs still in Pulp and our network is private
I made sure to serve all repos via http.

- Trey
On Jan 21, 2015 3:06 PM, "Mathew Crane" <mathew.crane at gmail.com> wrote:

> In my environment, it doesn't really make sense to have a single point
> propagating changes to numerous hosts. Instead we'd opt to have the
> consumers pull down from the Pulp server manually. I understand that this
> hides a portion of Pulp's featureset (consumer management and reporting)
> but what I'm more interested in is the ability to manually 'promote'
> packages into different repos with required or updated deps on the server.
> Is there any downside to keeping the consumers 'dumb' and hitting the
> Pulp-managed repositories manually via standard /etc/yum.repos.d/*.conf
> files?
>
> _______________________________________________
> 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/20150125/fac2cc86/attachment.htm>