Puppet » Facter

FWIW, we have recently hit this same problem at a different level:

We use both KVM virtual hardware machines and OpenVZ container system to divide up machine. Specifically: have have KVM guest systems that are OpenVZ host systems.

To avoid things like installing hardware layer management tools on the OpenVZ host system we are going to have to do something that reports both “KVM guest” and “OpenVZ host” at the same time.

We have no current design to solve this, although I hope to have something in the next week or so to address it.

Does it make any sense to return this as a comma-separated list in a string ?

That’s our only real option until Facter supports rich data types.

On Thu, Apr 21, 2011 at 10:24, Mark Lehrer mark@knm.org wrote:

Does it make any sense to return this as a comma-separated list in a string ?

This would work fine for me.  I was thinking about something like the processorcount arrangement, but that might be over-engineering it.

So, er, changing the incorrect “there can be only one” fact will actually break production code, since we defined it that way and the values of facts are totally API.

However, the processor count like model of “export one boolean for each matching virtual type” would not have that problem. :)

Daniel