Paul Nasrat wrote:
> translation stuff but really I'd say if you have a complex multi-arch
> setup you should ensure you have "development" and "test" systems for
> your systems people to work on and that can integrate with manifest
> testing tools.
>
Good point. What about easily spinning up inst
2009/12/2 Scott Smith :
> Ohad Levy wrote:
>> Hi Scott,
>>
>> I don't see how this can help us, see explanation from previous email :)
>> Ohad
>>
>
> Yeah :) I guess I was just alluding to the idea of using a chrooted jail
> that emulated another arch. :)
Mock can pretty much only do setarch so th
Ohad Levy wrote:
> Hi Scott,
>
> I don't see how this can help us, see explanation from previous email :)
> Ohad
>
Yeah :) I guess I was just alluding to the idea of using a chrooted jail
that emulated another arch. :)
-scott
--
You received this message because you are subscribed to the Goo
On Wed, Dec 2, 2009 at 2:47 AM, Nigel Kersten wrote:
>
> Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired
> there. We actually serve our manifests out of a different location, so
> I had to do a minor tweak to get that working.
>
latest code allow you to tweak it via a command li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luke Kanies wrote:
> It seems a bit limited because it actually runs the whole
> configuration, but I like it. It should definitely be straightforward
> to extend it to use a given host's Facts.
>
> You might also be able to get some inspiration
On Nov 29, 2009, at 6:18 AM, Ohad Levy wrote:
> If it happened to you before that someone broke your manifest
> because of simple change (e.g. didnt test it on all hosts/classes
> external nodes ... combinations) this tool might be useful for you.
>
> the idea is very simple, just try to compi
On Wed, Dec 2, 2009 at 9:51 AM, Nigel Kersten wrote:
> Yep. It's the provider forcing stuff that is the problem. I was going
> to start digging in to work out what's a real alarm and what isn't.
>
> How are you using this Ohad? Are you running it on your servers?
>
> Currently we've created a lis
On Tue, Dec 1, 2009 at 5:46 PM, Ohad Levy wrote:
>
>
> On Wed, Dec 2, 2009 at 2:47 AM, Nigel Kersten wrote:
>>
>> Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired
>> there. We actually serve our manifests out of a different location, so
>> I had to do a minor tweak to get that wo
yé: Mardi 1 Décembre 2009 19:47:38 GMT +01:00 Amsterdam / Berlin /
> Berne / Rome / Stockholm / Vienne
> Objet: Re: [Puppet Users] manitest - a simple tool to help your puppet
> development and testing
>
> On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy wrote:
> > If it happened to
Hi Scott,
I don't see how this can help us, see explanation from previous email :)
Ohad
On Wed, Dec 2, 2009 at 3:04 AM, Scott Smith wrote:
> Nigel Kersten wrote:
> > It's a shame we can't impersonate architectures though... I'd love to
> > be able to simulate catalog runs of a Mac client on a L
On Wed, Dec 2, 2009 at 2:47 AM, Nigel Kersten wrote:
> Ohad, I noticed you have /etc/puppet/manifests/site.pp hard-wired
> there. We actually serve our manifests out of a different location, so
> I had to do a minor tweak to get that working.
>
I'll see what I can do about that ;)
>
> It's a sha
com
Envoyé: Mardi 1 Décembre 2009 19:47:38 GMT +01:00 Amsterdam / Berlin / Berne /
Rome / Stockholm / Vienne
Objet: Re: [Puppet Users] manitest - a simple tool to help your puppet
development and testing
On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy wrote:
> If it happened to you before that
Nigel Kersten wrote:
> It's a shame we can't impersonate architectures though... I'd love to
> be able to simulate catalog runs of a Mac client on a Linux continuous
> build server.
>
I wonder if you could with something like this...
http://fedoraproject.org/wiki/Projects/Mock
-scott
--
You r
On 12/01/2009 01:47 PM, Nigel Kersten wrote:
> On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy wrote:
>> If it happened to you before that someone broke your manifest because of
>> simple change (e.g. didnt test it on all hosts/classes external nodes ...
>> combinations) this tool might be useful for y
On Sun, Nov 29, 2009 at 6:18 AM, Ohad Levy wrote:
> If it happened to you before that someone broke your manifest because of
> simple change (e.g. didnt test it on all hosts/classes external nodes ...
> combinations) this tool might be useful for you.
No-one else tried this out? It's really quite
If it happened to you before that someone broke your manifest because of
simple change (e.g. didnt test it on all hosts/classes external nodes ...
combinations) this tool might be useful for you.
the idea is very simple, just try to compile the manifest based on
customized facts, classes, environm
16 matches
Mail list logo
