I'm trying to figure out the easiest way to make use of the information
that mco has access to. To this end, I'm attempting to find queries that
answer "obvious" questions like "which hosts use module X" or "which hosts
are running apache". Things like that. So far, I've figured out how to do
On Friday, August 24, 2012 4:38:54 PM UTC-4, lamour wrote:
>
>
> On Wednesday, August 22, 2012 5:06:41 PM UTC-4, Ramin K wrote:
>>
>>
>>
> node 'some.node.my.domain.com inherits basenode {
>>include mysql
>>include general_devel
>>
On Wednesday, August 22, 2012 5:06:41 PM UTC-4, Ramin K wrote:
>
> On 8/22/2012 9:55 AM, lamour wrote:
>
> > So, my basic issue with both the class method and the virtual resources
> > method is that they basically require me to maintain a SECOND list of
> > every
On Tuesday, August 21, 2012 6:25:53 PM UTC-4, Tim Mooney wrote:
>
> In regard to: [Puppet Users] package handling in puppet?, lamour said
> (at...:
>
> > so, I've got most of the pieces worked out, but I've hit a major
> roadblock
> > with the way packag
On Tuesday, August 21, 2012 3:57:43 PM UTC-4, Ramin K wrote:
>
>
> What happens when you have two or more statements about the same
> resource in conflict?
>
> package { 'mysql': ensure => installed, }
> package { 'mysql': ensure => 5.0.92, }
> package { 'mysql': ensure => lates
On Tuesday, August 21, 2012 1:22:24 PM UTC-4, Craig White wrote:
>
>
>
> if you have packages that are pre-requisites for more than one other
> package, create a separate class and include the class where desired. Done.
>
>
Ok, I'm just making sure that I understand what you're sayi
I'm starting to feel like, maybe, I have a fundamentally flawed concept of
how puppet is intended to be used. (new to puppet. setting up initial
puppet environment. blah blah)
so, I've got most of the pieces worked out, but I've hit a major roadblock
with the way packages are handled in pupp
