would filtering based on a fact would be a good idea?

Ohad Levy wrote:

would filtering based on a fact would be a good idea?

Perhaps there could be a setting in the settings file.

It could specify "how much" of the domain I want to truncate.
(Like the number of "dots" settings in the resolv.conf file)

is this still requires after #183?

This is how I use the SETTING:

SETTINGS[:domain_name].nil? ? name : name.chomp(SETTINGS[:domain_name])

Any love for this ticket. :)

I am still using the above hack.

Are you planning to change the Hosts page in other ways to add this feature?

The above hack that I was using does not work in the latest develop branch.

Uhm, Ditto on wanting this. With multiple data centers we use a subdomain for each, now I just see multiple short host names and it detracts a lot from the usability. I'd prefer just cutting off the domain name. On a side note, I tried assigning all hosts to just domain.com instead of sub.domain.com, however puppet fact imports overwrite this. This was not the expected behavior as release notes for 0.1-6 mention:

"In previous version, when entering a FQDN as the hostname, Foreman would automatically create the domain name for the host, however, as its legitimate to have a full stop (".") as part of the hostname, foreman can no longer know what is the correct domain name, and therefore will not create it, if the domain already exists, Foreman would still associate the host to it."

I suppose I could fudge this on the facter end. Any suggestions ( a working hack? )

The original hack still works.
It needs the following additional change in app/views/hosts/_form.html.erb:

diff -Naur usr/share/foreman/app/views/hosts/_form.html.erb /usr/share/foreman/app/views/hosts/_form.html.erb
--- usr/share/foreman/app/views/hosts/_form.html.erb    2011-02-12 09:51:12.000000000 -0800
+++ /usr/share/foreman/app/views/hosts/_form.html.erb   2011-02-16 12:02:59.000000000 -0800
@@ -5,7 +5,7 @@
     <table>
       <tr>
         <td>Name</td>
-        <td><%= f.text_field :name, :size => 16, :value => @host.shortname %></td>
+        <td><%= f.text_field :name, :size => 16, :value => @host.name %></td> 
         <td>Host group</td>
         <td>
             <%= f.collection_select :hostgroup_id, accessible_hostgroups, :id, :name, {:include_blank => true},

Yes, showing a sortable domain column will work for us.

How difficult would it be to make the view customizable? I'm thinking every shop has different requirements on data they would feel important for this hostlist. (We might even consider multiple views, with default views that are tied to RBAC) I know this could be done with improved searching, but I am thinking something a little lighter weight, and prominent.