Hi all,
I'm wondering if anyone has any best practice when needing to do a service
stop, and exec, and then a service start in a sequential order. Up until
now notifying a service has been fine, but i've now come across an issue
where I need to make sure a service is stoppped, so something then s
> there is the config_version
> optionhttp://docs.reductivelabs.com/references/stable/configuration.html#co...
> which gives you the possibility to give the possibility to generate a
> certain version for the current used manifests.
Great ! I think it's the thing I need :)
Thanks a lot,
--
Yo
> Also I believe there is work to implement module or class metadata which may
> provide what you're
> looking for--but I'm not sure how far off that is.
So do I.
And I think there's really a need here.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users
Anyone have a workaround/patch for the Solaris zones ensure => running bug?
Cheers.
--
bda
cyberpunk is dead. long live cyberpunk.
--
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.c
hi, all
Its a very common use-case to set common password for user/s on all
nodes, i like to know if there is any Type or Function or Recipe
available in puppet which support this case?
I have tried following approach but it didn't worked;
I am reading the password (md5 hash) stored in a file
'Provider useradd does not support features manages_passwords; not
managing attribute password'
I have read this;
http://reductivelabs.com/trac/puppet/wiki/PuppetRedHatCentos
However, libshadow package (libshadow.so) is in /usr/local/libshadow
directry.
can anyone help me out please!
On Jan 28, 3:44 am, Matt wrote:
> I'm wondering if anyone has any best practice when needing to do a service
> stop, and exec, and then a service start in a sequential order. Up until
> now notifying a service has been fine, but i've now come across an issue
> where I need to make sure a servic
On Wed, 27 Jan 2010, Scott Smith wrote:
The only annoying part is that if I ever revoke something, I have to
distribute the CRL to my puppetmasters. Oh well.
openssl discusses this in the 'verify' man page
Nothing says a certificate has to be of any particular
duration. A certificate outsid
I use a combination of both solutions to achieve a similar result.
I tag modules based on internal development cycle, and then I put them all
on a directory on the server (e.g. /etc/puppet/modules/stable).
each module would have a version as a suffix (e.g. ssh_1.5)
then I automatically build env
On Wed, 27 Jan 2010 14:42:12 -0600, Carl Caum wrote:
> Make extra sure that's true. I found it won't give you an error but the
> package still won't always be installed.
>
> On Jan 27, 2010, at 12:05 PM, James Cammarata wrote:
>
>>
>> On Wed, 27 Jan 2010 11:50:41 -0600, Carl Caum
>> wrote:
On Jan 28, 2010, at 10:08 AM, James Cammarata wrote:
>
> On Wed, 27 Jan 2010 14:42:12 -0600, Carl Caum wrote:
>> Make extra sure that's true. I found it won't give you an error but the
>> package still won't always be installed.
>>
>> On Jan 27, 2010, at 12:05 PM, James Cammarata wrote:
>>
Hi,
I would like to use Puppet in the cloud (think gogrid) to configure
stem images.
Virtual machines are created/destroyed on the fly under control of a
load monitor.
For this reason we cannot sign manually new Puppet clients, instead,
we must use Puppet's autosign feature.
At the moment, Puppet
Has anyone found a clean way to manage Glassfish configuration with puppet?
Glassfish was designed to be managed through a WebUI or a CLI tool known as
asadmin. Making changes using these tools modifies a domain.xml file.
Glassfish reads and writes this file every time it restarts, even if the
c
We have a client-server puppetmaster running puppetd and
puppetmasterd,
however I would like to test configurations locally before committing
the changes
on the puppetmaster.
Running the puppet config locally with /usr/bin/puppet mostly works.
The thing that fails ( which I have commented out on
Have you tried with --server ?
I have a Test Puppetmaster where I change configs and for testing I can run
on a client the new configuration with puppeetd --test --server
mytestserver.example.com ...
Hope that helps.
On Thu, Jan 28, 2010 at 1:23 PM, steve.majew...@gmail.com <
steve.majew...@gma
On Jan 28, 5:14 pm, "Tony G." wrote:
> Have you tried with --server ?
>
Yes. Same error:
info: Autoloaded module puppet
debug: Scope(Class[puppet]): Retrieving template puppet/
puppet.conf.erb
debug: template[/home/sdm7g/puppet/modules/puppet/templates/
puppet.conf.erb]: Bound template variab
I just created a simple manifest using puppet, might work for you.
notice $servername
if $servername == "" {
$servername = "puppet"
}
notice $servername
output:
notice: Scope(Class[main]):
notice: Scope(Class[main]): puppet
On Fri, Jan 29, 2010 at 3:23 AM, steve.majew...@gmail.com <
steve.ma
after a very long discussion about this topic in the past, we internally
decided to have a simple script which checks the yum repo for 32bit versions
when the 64bit version exists.
e.g. if you did
package{"libacl": ensure => installed}
then the script will install the 32bit version of the same pa
On Thu, Jan 28, 2010 at 9:54 PM, valentino
wrote:
> Hi,
> I would like to use Puppet in the cloud (think gogrid) to configure
> stem images.
> Virtual machines are created/destroyed on the fly under control of a
> load monitor.
>
cant it also add remove entries in autosign?
in my opinion, you nee
19 matches
Mail list logo
