Foreman vs katello host facts UI

Watching this sprint's demo[1] there has been some work on the host facts UI. The nutupane display for katello systems facts is buried on the system's details page. I'd like to suggest it be moved back to its own dedicated tab in katello and the design be reconsidered based upon their increased importance in provisioning.

Note that system facts in katello are delivered by subscription-manager (rhsmcertd); I am unfamiliar with both how foreman gets them and their overlap with katello system facts.

[1] http://www.youtube.com/watch?v=b7Bzl0yYgvA

··· -- @thomasmckay


“The leader must aim high, see big, judge widely, thus setting himself apart form the ordinary people who debate in narrow confines.” ~ Charles De Gaulle

“Leadership is about making others better as a result of your presence and making sure that impact lasts in your absence.” ~ Harvard Business School

>
> Watching this sprint's demo[1] there has been some work on the host facts
> UI. The nutupane display for katello systems facts is buried on the
> system's details page. I'd like to suggest it be moved back to its own
> dedicated tab in katello and the design be reconsidered based upon their
> increased importance in provisioning.
>

Also be aware that Facts are first-class objects in Foreman, with their own
models/controllers etc - no idea if that impacts the discussion, but I
figured you should be aware of it.

Note that system facts in katello are delivered by subscription-manager
> (rhsmcertd); I am unfamiliar with both how foreman gets them and their
> overlap with katello system facts.

They are delivered to Foreman from the Puppetmaster for that Host, via the
ENC script (node.rb[1]). The actual library collecting the facts is
Facter[2].

Hope that helps,
Greg

[1]
https://github.com/theforeman/puppet-foreman/blob/master/templates/external_node_v2.rb.erb#L86-L118
[2]http://puppetlabs.com/facter

··· On 11 November 2013 13:48, Tom McKay wrote:

From our discussions in Brno, Katello can largely harness the Facts
provided by Foreman. There are a few pricing related Candlepin facts that
may be needed and could potentially be handled via a Facter plugin to unify
how they are acquired and managed.

-Eric

··· On Mon, Nov 11, 2013 at 9:02 AM, Greg Sutcliffe wrote:

On 11 November 2013 13:48, Tom McKay thomasmckay@redhat.com wrote:

Watching this sprint’s demo[1] there has been some work on the host facts
UI. The nutupane display for katello systems facts is buried on the
system’s details page. I’d like to suggest it be moved back to its own
dedicated tab in katello and the design be reconsidered based upon their
increased importance in provisioning.

Also be aware that Facts are first-class objects in Foreman, with their
own models/controllers etc - no idea if that impacts the discussion, but I
figured you should be aware of it.

Note that system facts in katello are delivered by subscription-manager

(rhsmcertd); I am unfamiliar with both how foreman gets them and their
overlap with katello system facts.

They are delivered to Foreman from the Puppetmaster for that Host, via the
ENC script (node.rb[1]). The actual library collecting the facts is
Facter[2].

Hope that helps,
Greg

[1]
https://github.com/theforeman/puppet-foreman/blob/master/templates/external_node_v2.rb.erb#L86-L118
[2]http://puppetlabs.com/facter


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

I'm not sure about candlepin facts structure and requirements but we are near
to have a support for tree-structured facts. Also it should be easy to add new
types of facts (we use STI there) and modify the importing process for a
particular fact type if needed. So it seems to me that Katello could use
Foreman facts system.

Moving facts uploading to facter plugin adds another dependency on puppet
world. I think in future we may support other config management tools.
Therefore I'd like to ask why rhsmcertd can't send facts to foreman itself?

··· On Monday 11 of November 2013 09:15:10 Eric D Helms wrote: > From our discussions in Brno, Katello can largely harness the Facts > provided by Foreman. There are a few pricing related Candlepin facts that > may be needed and could potentially be handled via a Facter plugin to unify > how they are acquired and managed.


Marek

-Eric

On Mon, Nov 11, 2013 at 9:02 AM, Greg Sutcliffe greg.sutcliffe@gmail.comwrote:

On 11 November 2013 13:48, Tom McKay thomasmckay@redhat.com wrote:

Watching this sprint’s demo[1] there has been some work on the host facts
UI. The nutupane display for katello systems facts is buried on the
system’s details page. I’d like to suggest it be moved back to its own
dedicated tab in katello and the design be reconsidered based upon their
increased importance in provisioning.

Also be aware that Facts are first-class objects in Foreman, with their
own models/controllers etc - no idea if that impacts the discussion, but I
figured you should be aware of it.

Note that system facts in katello are delivered by subscription-manager

(rhsmcertd); I am unfamiliar with both how foreman gets them and their
overlap with katello system facts.

They are delivered to Foreman from the Puppetmaster for that Host, via the
ENC script (node.rb[1]). The actual library collecting the facts is
Facter[2].

Hope that helps,
Greg

[1]
https://github.com/theforeman/puppet-foreman/blob/master/templates/externa
l_node_v2.rb.erb#L86-L118 [2]http://puppetlabs.com/facter


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Marek