<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> We update several hundred. We typically do them in batches of anywhere between 5-50 depending on the group. <o:p></o:p> <o:p> </o:p> I have several mco actions written that do things like "yum clean cache," etc. I haven't had problems with rpmdb corruption. Usually I always run a 'yum clean cache' before doing anything.<o:p></o:p> <o:p> </o:p> Josh<o:p></o:p> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> From: Andrea Giardini [mailto:contact@andreagiardini.com] Sent: Tuesday, January 27, 2015 5:45 PM To: Baird, Josh Cc: pulp-list@redhat.com; Trey Dockendorf; Mathew Crane Subject: Re: [Pulp-list] Using Pulp in a server-only configuration?<o:p></o:p> </div> </div> <o:p> </o:p> @Josh How many machine do you update with this method? I use mco as well it's not always efficient with high number of machine (expecially if they have high load) How do you deal with rpmdb corruption/ stuck transactions and all the other errors that can prevent a machine from updating correctly? Cheers Andrea<o:p></o:p> <div> On 01/25/2015 06:29 PM, Baird, Josh wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> We also use Pulp in this exact way. Puppet drops down repo definitions to each host which are associated with the host's Puppet environment (dev, qa, prod). The repo definitions point to "snapshot" repositories in Pulp. We promote packages up through the environments as you are describing.<o:p></o:p> <o:p></o:p> We do not use the pulp-consumer client. Instead we trigger "yum updates" using mCollective on groups of hosts.<o:p></o:p> <o:p></o:p> Josh<o:p></o:p> <o:p></o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> From: <a href="mailto:pulp-list-bounces@redhat.com">pulp-list-bounces@redhat.com</a> [<a href="mailto:pulp-list-bounces@redhat.com">mailto:pulp-list-bounces@redhat.com</a>] On Behalf Of Trey Dockendorf Sent: Sunday, January 25, 2015 12:22 PM To: Mathew Crane Cc: <a href="mailto:pulp-list@redhat.com">pulp-list@redhat.com</a> Subject: Re: [Pulp-list] Using Pulp in a server-only configuration?<o:p></o:p> </div> </div> <o:p></o:p> 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.<o:p></o:p> - Trey<o:p></o:p> <div> On Jan 21, 2015 3:06 PM, "Mathew Crane" <<a href="mailto:mathew.crane@gmail.com">mathew.crane@gmail.com</a>> wrote:<o:p></o:p> <div> 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?<o:p></o:p> </div> _______________________________________________ Pulp-list mailing list <a href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/pulp-list" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a><o:p></o:p> </div> </div> <o:p></o:p> <pre>_______________________________________________<o:p></o:p></pre> <pre>Pulp-list mailing list<o:p></o:p></pre> <pre><a href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a><o:p></o:p></pre> <pre><a href="https://www.redhat.com/mailman/listinfo/pulp-list">https://www.redhat.com/mailman/listinfo/pulp-list</a><o:p></o:p></pre> </blockquote> <o:p> </o:p> </div> </div> </body> </html>