Foreman to ship custom facts

Development
1

Hello,

OpenStack team is interested in some custom facts to be ship with
Foreman, disk sizes specifically. We currently do not ship any of these
AFAIK. Are folks fine if we ship some?

If so, what is preferred way of doing this? I assume puppet should be
leveraged to deploy custom facts. But we do not ship any
modules/manifests as it is expected that users will download their own.

We could deploy the facts via Foreman templates as well. Not sure if
folks like this approach.

Opinions?

··· -- Later, Lukas #lzap Zapletal
2

> Hello,
>
> OpenStack team is interested in some custom facts to be ship with
> Foreman, disk sizes specifically. We currently do not ship any of these
> AFAIK. Are folks fine if we ship some?

Facter already ships disk size facts:
https://docs.puppetlabs.com/facter/latest/core_facts.html#blockdevicedevicenamesize

> If so, what is preferred way of doing this? I assume puppet should be
> leveraged to deploy custom facts. But we do not ship any
> modules/manifests as it is expected that users will download their own.
>
> We could deploy the facts via Foreman templates as well. Not sure if
> folks like this approach.

Facts really belong in the Facter project, not Foreman (core at least,
which I assume is what you mean by Foreman.)

If there's a plugin that relies on one, then perhaps the plugin can
publish a module to the Forge and optionally deploy it to Puppet masters
or during installation.

··· On 18/09/14 13:29, Lukas Zapletal wrote:

–
Dominic Cleal
Red Hat Engineering

3

> > OpenStack team is interested in some custom facts to be ship with
> > Foreman, disk sizes specifically. We currently do not ship any of these
> > AFAIK. Are folks fine if we ship some?
>
> Facter already ships disk size facts:
> https://docs.puppetlabs.com/facter/latest/core_facts.html#blockdevicedevicenamesize

Yeah, this was misunderstanding from my side. I think they want this in
the discovery image (where not all facts are reported currently).

> Facts really belong in the Facter project, not Foreman (core at least,
> which I assume is what you mean by Foreman.)
>
> If there's a plugin that relies on one, then perhaps the plugin can
> publish a module to the Forge and optionally deploy it to Puppet masters
> or during installation.

This looks sane, thanks.

··· -- Later, Lukas #lzap Zapletal
4

Discovery images don't connect to Puppet masters, do they?

Better to update Facter, or figure out why the existing facts aren't
working & send fixes there.

··· On 18/09/14 13:43, Lukas Zapletal wrote: >>> OpenStack team is interested in some custom facts to be ship with >>> Foreman, disk sizes specifically. We currently do not ship any of these >>> AFAIK. Are folks fine if we ship some? >> >> Facter already ships disk size facts: >> https://docs.puppetlabs.com/facter/latest/core_facts.html#blockdevicedevicenamesize > > Yeah, this was misunderstanding from my side. I think they want this in > the discovery image (where not all facts are reported currently). > >> Facts really belong in the Facter project, not Foreman (core at least, >> which I assume is what you mean by Foreman.) >> >> If there's a plugin that relies on one, then perhaps the plugin can >> publish a module to the Forge and optionally deploy it to Puppet masters >> or during installation. > > This looks sane, thanks.

–
Dominic Cleal
Red Hat Engineering

5

> Discovery images don't connect to Puppet masters, do they?
>
> Better to update Facter, or figure out why the existing facts aren't
> working & send fixes there.

Yeah, all my fault. I did not get it right.

Filed: Feature #7525: Report volume sizes via facter - Foreman

Easy to fix I suppose.

··· -- Later, Lukas #lzap Zapletal