Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-14 Thread warron.french
Hi James, I am working in an environment that uses RH Satellite; based on everyone's input though I will get the RPMs added into a 3rd party repository. Thanks for the inputs everyone. I have deployed the module already, but I will redesign it with this separate report as suggested. \\Warron Fre

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-06 Thread John Gelnaw
On Monday, March 6, 2017 at 9:16:45 AM UTC-5, jcbollinger wrote: > > > On Sunday, March 5, 2017 at 6:56:11 PM UTC-6, John Gelnaw wrote: > >> I created a second "mount point" in puppet via fileserver.conf, pointing >> to a location outside the puppet git tree, so I could use >> "puppet:///download

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-06 Thread jcbollinger
On Sunday, March 5, 2017 at 6:56:11 PM UTC-6, John Gelnaw wrote: > I created a second "mount point" in puppet via fileserver.conf, pointing > to a location outside the puppet git tree, so I could use > "puppet:///downloads/" as a source, synchronized that directory > to a local directory on t

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-05 Thread John Gelnaw
On Friday, March 3, 2017 at 8:31:00 AM UTC-5, Michael Watters wrote: > > This would be the ideal but you *can* use the rpm provider when needed. > For example: > > package { 'jdk': > ensure => installed, > provider => 'rpm', > source => '/pub/oracle/jdk-8-linux-x64.rpm', > } > > >

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-03 Thread Michael Watters
This would be the ideal but you *can* use the rpm provider when needed. For example: package { 'jdk': ensure => installed, provider => 'rpm', source => '/pub/oracle/jdk-8-linux-x64.rpm', } This will install the rpm using the defined source path. In our environment the /pub dire

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread Dan White
+1 To manage an RPM not in yum, put it into yum. > On Mar 2, 2017, at 11:02 AM, Garrett Honeycutt > wrote: > >> On 3/2/17 9:58 AM, warron.french wrote: >> Hello all, >> can someone please advise me on a proper set of syntax (a file to look >> at) for an example to follow to solve the following

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread Rob Nelson
We should note that yumrepo is a native type in puppet that you can use to manage the remote repo information on nodes, and there's a (from memory) palli/createrepo module to create and maintain the yum repo itself. It's not that difficult to add createrepo to a role and set up a node as your inter

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread Rob Nelson
For clarity, because I had to reread this twice to get the context: VERSION CONTROL repositories should never contain binary objects. Just want to differentiate that from yum repositories. On Thu, Mar 2, 2017 at 2:11 PM Andrew Grimberg wrote: > Repositories should _never_ contain binary objects

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread Rich Burroughs
There are a number of reasons it's not a great idea to put them in the module, but one is that if you start sticking binary artifacts into your Puppet code, the size of the repos(s) will grow a lot and it will be much slower to clone them. Also it's just not how people expect things to work. Say y

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread James Pryor
Warron, And if my previous email solves #1 & #2, then #3 is an addition of an exec resource, then adding it at the end of the dependency chain: [root@localhost myinstallmodule]# cat manifests/init.pp class myinstallmodule { exec { 'dothething': command => 'echo "look it works!"; logger look

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread James Pryor
Warron, Correct. Garret is right. It is not best to deliver RPMs as part of the payload-contents of the Puppet Module, and do not store RPMs in a git repo (or whatever version control system you might be using). Yes, "yum localinstall" exists and but RPMs are best delivered via the OS's native pac

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread Andrew Grimberg
Repositories should _never_ contain binary objects. The only exception I ever allow my developers is graphical assets related to websites. On 03/02/2017 08:48 AM, warron.french wrote: > Garrett, thanks. > > So, to clarify for myself in terms of a BEST practice are you declaring > "don't deliver R

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread warron.french
Garrett, thanks. So, to clarify for myself in terms of a BEST practice are you declaring "don't deliver RPMs as part of the payload of the Puppet Module?" *I just got that part working. :-/* I don't mind correction, but I don't want to go down the rabbit hole. Secondly, using an exec resource

Re: [Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread Garrett Honeycutt
On 3/2/17 9:58 AM, warron.french wrote: > Hello all, > can someone please advise me on a proper set of syntax (a file to look > at) for an example to follow to solve the following challenge: > > 1. I have 2 deliver 2 *.rpm files that are not in a YUM repository, so > I dropped them into the f

[Puppet Users] Manage delivery and execution of RPMs not in YUM

2017-03-02 Thread warron.french
Hello all, can someone please advise me on a proper set of syntax (a file to look at) for an example to follow to solve the following challenge: 1. I have 2 deliver 2 *.rpm files that are not in a YUM repository, so I dropped them into the files directory of my module path. 2. I need to