[Puppet Users] 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+unsubscr...@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.
Re: [Puppet Users] creating directories
Yes,
Just use the file type, and set ensure to directory:
file { "/etc/myapp":
ensure => directory
}
On Tue, Jan 12, 2010 at 4:34 PM, Christopher Johnston
wrote:
> What is the best way to have puppet create (mkdir) directories? I am
> currently using exec types, but is it possible to use a file type for this?
> -Chris
> --
> 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.
>
>
--
Andres Olarte
dotCMS
Main: 305.858.1422
Direct: 786.594.5285
Fax: 305.397.1719
www.dotCMS.org
"Packt Publishing's 2009 Best Non PHP Open Source CMS Finalist"
--
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.
[Puppet Users] Re: Puppet / EC2 noob question
What I do is this: Delete the certs for hostname X from the puppetmaster. Start the instance from the puppet master machine. Passing a script (that get's ran at startup). This script does the following: Set the hostname to X. Install puppet on the client (I use bare ubuntu images) Connect to the puppetmaster instance. Mean while the script on the puppet master is waiting for the signing request from X, and as soon as it gets it, it signs it. Hope that helps. On Fri, Sep 11, 2009 at 8:07 AM, Chris wrote: > > Hi all, > > I'm starting to use EC2, and I'm after some examples of best practices/ > tips and tricks from folk with more experience of the Puppet/EC2 combo > than me: > > We're starting by using EC2 for testing and development purposes. This > means that we won't be running our instances full-time; rather, we'll > be spinning them up and down for a few hours at a time, as and when > needed. I'd like the instances to call back to my local puppetmaster > to configure themselves post-boot. > > Now, what I'm not sure about is how to make this play nicely with > puppet. If I have an AMI with puppet installed (I'm using an ubuntu > base, if it matters), then as soon as I run it, I need to sign it's > certificate. I also need to add a new node definition to my config, > since each time the AMI starts it, gets a new host name. > > So, this is going to be a bit of a faff. I can think of some ways > around it; specifying the certname option (which I could do via a > userdata script when I boot the VM) would allow me to get around the > "each boot is a new node", but I'm not so sure about the certificates. > Should I pre-generate the cert and then try and push that to the node > when it boots? Or enable autosigning? > > Any ideas gratefully received! > > Thanks > > Chris > > > > --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
