I wasn't clear enough in describing the problem -
What I'm trying to achieve is that if the package is installed, don't
execute the file statement and download the rpm.
If I leave the file in /tmp, it does not download again, if I delete
the file and the package is installed, it still downloads the rpm. I
don't want to have to keep the rpm on the system after the package
install.
Seems an NFS mount for the rpm's might be the solution?
Thanks
On Jul 30, 2:53 am, quicksilver03 <sebasti...@mailworks.org> wrote:
> I'm using 0.25.5 and I do it in pretty much the same way:
>
> file { "oratoolkit_rpm":
> require => [ Group["oinstall"],
> Group["dba"],
> User["oracle"],
> ],
> path => "/home/admin/install/oratoolkit-1.0.2.1.4-1.noarch.rpm",
> source => "puppet:///oracle/oratoolkit-1.0.2.1.4-1.noarch.rpm",
> owner => admin,
> group => admin,
> ensure => present,
> }
>
> # installs the oratoolkit package
> package { "oratoolkit":
> require => File[oratoolkit_rpm],
> source => "/home/admin/install/oratoolkit-1.0.2.1.4-1.noarch.rpm",
> provider => "rpm",
> ensure => installed,
> }
>
> Try adding an ensure => present to your File resource and see if it
> avoids downloading the RPM file over and over again.
>
> On Jul 29, 10:40 pm, Rustler <coltsixshoo...@gmail.com> wrote:
>
> > I am using version 2.6 and it would be nice if you could use a puppet
> > url for the package source, but that does not appear to work (docs say
> > it has to be a local file).
>
> > My other choices seem to be an nfs mount, or a local repo server.
>
> > Thanks
>
> > On Jul 29, 11:23 am, Patrick Mohr <kc7...@gmail.com> wrote:
>
> > > On Jul 29, 2010, at 9:45 AM, Rustler wrote:
>
> > > > This code is working - but due to the file declaration it keeps
> > > > downloading the rpm even after the package gets installed.
>
> > > > 1. How do I stop the rpm from downloading after the package is
> > > > installed?
>
> > > Best method:
> > > *) If at all possible you should just replace this with a real package
> > > repository.
>
> > > Should also work:
> > > *) Put the rpm files on a webserver and download them as needed. I think
> > > rpm can take URLs instead of local paths.
> > > or
> > > *)Install from a network drive like nfs
>
> > > Not recommended:
> > > *) Just put the rpms into a folder you create. It will keep growing
> > > forever, but it probably won't ever get very big unless you release a lot
> > > of packages. Trust me on this, pushing out big files with puppet is
> > > probably a mistake. It will put a large load on the puppetmaster, and if
> > > you are using a version of puppet less than 2.6.0, the RAM requirements
> > > on the client and serve will be horrendous.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
