Hi, There is no downside other than losing the parts of Pulp that are tied to the consumer (applicability, pushing out updates). If all you are looking for is to mirror/promote content in repos this works great.
-Barnaby ----- Original Message ----- From: "Mathew Crane" <[email protected]> To: [email protected] Sent: Wednesday, January 21, 2015 4:04:01 PM Subject: [Pulp-list] Using Pulp in a server-only configuration? 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 [email protected] https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
