Hi folks, I''m about to propose to my current company that we use puppet to manage releases of home grown software. The environment is a mix of Solaris 8/9/10 and RHEL 5&6. I''ve got a handle on how to create recipes to release software into the RHEL environment. The unknown for me is how to manipulate the pkgadd provider to load the locally grown package stream. Can someone guide me in the right direction. -- Peter L. Berghold Owner, Shark River Technical Solutions LLC Custom hosting provider. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
You need to use the adminfile and source parameters - once you have done that the provider works just fine. On Dec 28, 4:19 pm, Peter Berghold <salty.cowd...@gmail.com> wrote:> Hi folks, > > I''m about to propose to my current company that we use puppet to manage > releases of home grown software. The environment is a mix of Solaris > 8/9/10 and RHEL 5&6. > > I''ve got a handle on how to create recipes to release software into the > RHEL environment. The unknown for me is how to manipulate the pkgadd > provider to load the locally grown package stream. Can someone guide me in > the right direction. > > -- > Peter L. Berghold > Owner, Shark River Technical Solutions LLC > Custom hosting provider.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
We decided to distribute the pkg files the same way we do Linux
packages - via http. This define has been very useful to us:
define pkg_http($version,$source, $adminfile, $responsefile=undef){
exec {"/usr/sfw/bin/wget $source -O
/var/tmp/$name-$version.pkg":
unless => "/usr/bin/test -f
/var/tmp/$name-$version.pkg",
alias => "wget_$name",
} # exec
package { "$name":
ensure => ''installed'',
provider => ''sun'',
source => "/var/tmp/$name-$version.pkg",
adminfile => "$adminfile",
responsefile => $responsefile,
require => Exec["wget_$name"],
} # package
} # define pkg_http
Our typical admin file looks like this:
mailinstance=unique
partial=nocheck
runlevel=nocheck
idepend=nocheck
rdepend=nocheck
space=nocheck
setuid=nocheck
conflict=nocheck
action=nocheck
networktimeout=60
networkretries=3
authentication=quit
keystore=/var/sadm/security
proxybasedir=default
On Wed, Dec 28, 2011 at 8:55 AM, Bill Proud <billproud@yahoo.com>
wrote:> You need to use the adminfile and source parameters - once you have
> done that the provider works just fine.
>
> On Dec 28, 4:19 pm, Peter Berghold <salty.cowd...@gmail.com> wrote:
>> Hi folks,
>>
>> I''m about to propose to my current company that we use puppet
to manage
>> releases of home grown software. The environment is a mix of Solaris
>> 8/9/10 and RHEL 5&6.
>>
>> I''ve got a handle on how to create recipes to release software
into the
>> RHEL environment. The unknown for me is how to manipulate the pkgadd
>> provider to load the locally grown package stream. Can someone guide
me in
>> the right direction.
>>
>> --
>> Peter L. Berghold
>> Owner, Shark River Technical Solutions LLC
>> Custom hosting provider.
>
> --
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
We use virtual package declarations and realize the packages in the class they
are needed. We push a standard adminfile to all the Solaris hosts. The packages
are on an NFS share that is exported to all our servers:
file { "noask_pkgadd":
path => "/var/sadm/install/admin/noask_pkgadd",
ensure => present,
owner => root,
group => sys,
mode => 644,
source => "puppet://$server/files/$operatingsystem/noask_pkgadd"
}
@package{"mcollective":
ensure => installed,
name => "DUKmcoll",
source => "/net/nas-server/pkgs/DUKmcoll.pkg",
adminfile => "/var/sadm/install/admin/noask_pkgadd",
require => File["noask_pkgadd"]
}
realize(Package[''mcollective'']
On Dec 28, 2011, at 12:08 PM, Aaron Grewell wrote:
> We decided to distribute the pkg files the same way we do Linux
> packages - via http. This define has been very useful to us:
>
> define pkg_http($version,$source, $adminfile, $responsefile=undef){
> exec {"/usr/sfw/bin/wget $source -O
/var/tmp/$name-$version.pkg":
> unless => "/usr/bin/test -f
/var/tmp/$name-$version.pkg",
> alias => "wget_$name",
> } # exec
>
> package { "$name":
> ensure => ''installed'',
> provider => ''sun'',
> source => "/var/tmp/$name-$version.pkg",
> adminfile => "$adminfile",
> responsefile => $responsefile,
> require => Exec["wget_$name"],
> } # package
> } # define pkg_http
>
> Our typical admin file looks like this:
> mail> instance=unique
> partial=nocheck
> runlevel=nocheck
> idepend=nocheck
> rdepend=nocheck
> space=nocheck
> setuid=nocheck
> conflict=nocheck
> action=nocheck
> networktimeout=60
> networkretries=3
> authentication=quit
> keystore=/var/sadm/security
> proxy> basedir=default
>
> On Wed, Dec 28, 2011 at 8:55 AM, Bill Proud <billproud@yahoo.com>
wrote:
>> You need to use the adminfile and source parameters - once you have
>> done that the provider works just fine.
>>
>> On Dec 28, 4:19 pm, Peter Berghold <salty.cowd...@gmail.com>
wrote:
>>> Hi folks,
>>>
>>> I''m about to propose to my current company that we use
puppet to manage
>>> releases of home grown software. The environment is a mix of
Solaris
>>> 8/9/10 and RHEL 5&6.
>>>
>>> I''ve got a handle on how to create recipes to release
software into the
>>> RHEL environment. The unknown for me is how to manipulate the
pkgadd
>>> provider to load the locally grown package stream. Can someone
guide me in
>>> the right direction.
>>>
>>> --
>>> Peter L. Berghold
>>> Owner, Shark River Technical Solutions LLC
>>> Custom hosting provider.
>>
>> --
>> You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.