Puppet users - Jun 2013 - Managing (and pinning) package versions with puppet

I have an installation that I''m trying to manage with puppet. For some
of
the packages we want to have very tight control over the versions. Since 
they are critical to our application, we only upgrade them after testing in 
our test environment, and we schedule upgrades during low traffic times. I 
don''t want puppet to upgrade my database whenever a new package
appears. I
specified the version in my puppet manifest to prevent the package from 
automatically upgrading, however when I went to generate another instance 
using the same config, that version of the package was gone from the Ubuntu 
repo. Only the more recent ones are there.

For some of the packages, I''ve been packing them myself into my own
repo,
however packaging the database (postgresql) has proven too be too much 
overhead.

Any solutions or ideas?

We''re using Ubuntu 12.04.1 LTS.


Thanks,


Andres

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Why not do:

package {''foo'':
    ensure => present
}


This will only ensure that some version of ''foo'' is installed.
Also, I''ve
found that excessive pinning slows down ''apt-cache policy'',
which puppet
appears to run for each package resource.  I''ve improved puppet runs by
an
order of magnitude by removing pins.

-Ken

On Friday, June 14, 2013 3:06:00 PM UTC-7, Andres Olarte
wrote:
>
> I have an installation that I''m trying to manage with puppet. For
some of
> the packages we want to have very tight control over the versions. Since 
> they are critical to our application, we only upgrade them after testing in
> our test environment, and we schedule upgrades during low traffic times. I 
> don''t want puppet to upgrade my database whenever a new package
appears. I
> specified the version in my puppet manifest to prevent the package from 
> automatically upgrading, however when I went to generate another instance 
> using the same config, that version of the package was gone from the Ubuntu
> repo. Only the more recent ones are there.
>
> For some of the packages, I''ve been packing them myself into my
own repo,
> however packaging the database (postgresql) has proven too be too much 
> overhead.
>
> Any solutions or ideas?
>
> We''re using Ubuntu 12.04.1 LTS.
>
>
> Thanks,
>
>
> Andres
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

On 06/15/2013 12:06 AM, Andres Olarte wrote:
> I have an installation that I''m trying to manage with puppet. For
some
> of the packages we want to have very tight control over the versions.
> Since they are critical to our application, we only upgrade them after
> testing in our test environment, and we schedule upgrades during low
> traffic times. I don''t want puppet to upgrade my database whenever
a new
> package appears. I specified the version in my puppet manifest to
> prevent the package from automatically upgrading, however when I went to
> generate another instance using the same config, that version of the
> package was gone from the Ubuntu repo. Only the more recent ones are there.
> 
> For some of the packages, I''ve been packing them myself into my
own
> repo, however packaging the database (postgresql) has proven too be too
> much overhead.
> 
> Any solutions or ideas?
You can keep local copy of ubuntu repos, which you could update only
when you choose to, or you can have your own local repo in which you
will copy only postgresql related pacakges (if it''s only postgresql
which is being a problem).

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

In my opinion the version and/or holdable features should be re-implemented 
as a new variable, such as:

package { ''apache2''
  ensure => installed,
  version => ''2.0.64'',
  hold => true,
}


Rajat

On Saturday, June 15, 2013 3:36:00 AM UTC+5:30, Andres Olarte
wrote:
>
> I have an installation that I''m trying to manage with puppet. For
some of
> the packages we want to have very tight control over the versions. Since 
> they are critical to our application, we only upgrade them after testing in
> our test environment, and we schedule upgrades during low traffic times. I 
> don''t want puppet to upgrade my database whenever a new package
appears. I
> specified the version in my puppet manifest to prevent the package from 
> automatically upgrading, however when I went to generate another instance 
> using the same config, that version of the package was gone from the Ubuntu
> repo. Only the more recent ones are there.
>
> For some of the packages, I''ve been packing them myself into my
own repo,
> however packaging the database (postgresql) has proven too be too much 
> overhead.
>
> Any solutions or ideas?
>
> We''re using Ubuntu 12.04.1 LTS.
>
>
> Thanks,
>
>
> Andres
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

On Monday, June 17, 2013 5:05:41 AM UTC-5, Rajat Patel
wrote:
>
> In my opinion the version and/or holdable features should be 
> re-implemented as a new variable, such as:
>
> package { ''apache2''
>   ensure => installed,
>   version => ''2.0.64'',
>   hold => true,
> }
>
>
>
 
Would you care to comment on why you think that would be better?  A 
specific version number is a special case of ''hold'', which
itself is a
special case of ''installed''.  Splitting them out as separate
parameters
would create the opportunity for them to be inconsistent, and I don''t
see
anything useful to be gained in return.


John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.