Hello All,
As we try to release every month, I'm happy to announce the next stable
release of Foreman (0.1-3):
Main new features include:
- External nodes mode – Allows you to use foreman without automating your
server installation as well (e.g. you wont have to add additional
informati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'm no expert at external nodes, so I went and read:
> http://reductivelabs.com/trac/puppet/wiki/ExternalNodes
>
> That doc still really doesn't say exactly what external nodes are.
> It's a way of storing node info in an external source such as MyS
I got when I going to connect client & server...
r...@tbagchi-desktop:/home/tbagchi# puppetmasterd --debug --no-
daemonize --logdest console
/usr/local/lib/site_ruby/1.8/facter/util/resolution.rb:46: warning:
Insecure world writable dir /usr/bin in PATH, mode 040777
/usr/local/lib/site_ruby/1.8/pup
Douglas Garstang wrote:
> I don't think you understood my question Scott.
>
Ah, yes and no. I incorrectly assumed you had the syslog_ng::server class
managing itself as a
client as well.
> That doc still really doesn't say exactly what external nodes are.
> It's a way of storing node info in
On Sun, Dec 13, 2009 at 9:25 PM, James Turnbull wrote:
> 2009/12/14 Douglas Garstang :
>> I don't think you understood my question Scott.
>>
>> In any case, I'm avoiding external nodes because you lose all ability
>> to version control.
>
> How do you lose version control? You can easily version
2009/12/14 Douglas Garstang :
> I don't think you understood my question Scott.
>
> In any case, I'm avoiding external nodes because you lose all ability
> to version control.
How do you lose version control? You can easily version a whole
variety of external node stores. You can even include th
I don't think you understood my question Scott.
In any case, I'm avoiding external nodes because you lose all ability
to version control.
I found the solution anyway. It's to include the client node further
up the node hierarchy, since all nodes will have the client, and then
further down the nod
Douglas Garstang wrote:
> What's the best approach for this? I could combine both the client and
> server into one module and simple use case statements to serve out
> files based on their hostname, but that seems ugly. Is there a better
> idea? Can I "UN" include a class?
>
If you use external n
hello,
- "Douglas Garstang" wrote:
> Ohad,
>
> No, not really because for starters there are anywhere from 1 to 10
> instances of jboss running, but not always 10. It depends on the
> node.
> If it was always 10, I could say something like
> before=>Service["jboss-inst0"], before=>Service[
Ohad,
No, not really because for starters there are anywhere from 1 to 10
instances of jboss running, but not always 10. It depends on the node.
If it was always 10, I could say something like
before=>Service["jboss-inst0"], before=>Service["jboss-inst1"] etc.
PLUS the jboss service is controlled
So, I've been doing something like this for applications that have a
client and server component...
node base_node {
include syslog_ng::client
}}
node app_node inherits base_node {
}
node syslog_server inherits base_node {
include syslog_ng::server
}
... because I want the client portion,
Hi all!
Please help me get understand my error:
I have problems with onlyif/unless directives. Simple test work fine,
for example:
exec { "Update ovz templates":
command => "wget -O /vz/template/cache/centos-5-i386-
default.tar.gz http://install.local/ovz/templates/centos-5-i386-default.ta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> does anyone know if it is possibile to manage two or more gems with the same
> name but with different versions?
unfortunately not yet. as long as puppet isn't supporting composite-name
vars it isn't possible.
you might be able to do it with an own
13 matches
Mail list logo
