Hi <div><br></div><div>To illustrate what I had in mind, please find attached mock up. I was thinking of including the the additional fields about the traits (shown in red).</div><div><br></div><div>I agree using configuration would be an easy option, however this information would then be hidden away under a configuration tab. I have added this to the mockup to check my understanding. </div>
<div><br></div><div>thanks</div><div><br></div><div>Richard<br><br><div class="gmail_quote">On 19 October 2012 00:25, John Mazzitelli <span dir="ltr"><<a href="mailto:mazz@redhat.com" target="_blank">mazz@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">These definitely would NOT go into the Resource object. These look more like plugin configuration properties.<br>
<br>
You could look into using tags for something like this, too ( <a href="https://docs.jboss.org/author/display/RHQ/Tagging" target="_blank">https://docs.jboss.org/author/display/RHQ/Tagging</a> ). You could use this today without changing plugins or things like that.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
----- Original Message -----<br>
> Richard,<br>
><br>
> > I have a requirement to display some a additional on the platform<br>
> > in RHQ.<br>
> > • Make<br>
> > • Model<br>
> > • Asset Tag<br>
> > • Function<br>
> > • Notes<br>
> > Would it be ok to add these as additional fields to the Resource so<br>
> > that users can manually enter the values?<br>
><br>
> Not sure if you mean this: The Resource.class is a bad place, as this<br>
> is used for all the resources<br>
> in the system and thus the fields would also apply to services like a<br>
> war file.<br>
><br>
> What you could do though is to use the configuration object(s) for<br>
> this purpose and just e.g. add<br>
> a resource configuration object of the Linux type in the platform<br>
> plugin, which can then be filled by<br>
> hand or via the plugin. It is not exactly the right place, but a<br>
> place that already exists.<br>
><br>
> I was thinking in the past about adding some location area to the<br>
> platforms as well (geographical and/or<br>
> building/room/rack/... ), so one could even add (attention: more<br>
> work) a new configuration for this purpose<br>
> that is also shown on the inventory tab, but a different subtab.<br>
><br>
> I was also wondering in the past, if we could just have a generic<br>
> configuration definition, where<br>
> we'd provide some fields out of the box (e.g. "location" for a<br>
> platform) and where the admin could<br>
> then per resource type in the admin section of RHQ define additional<br>
> fields. So those additional<br>
> fields would then not be defined in the plugin descriptor, but<br>
> dynamically - and could also only set<br>
> manually and not through plugin code (as this may not even know about<br>
> the existence of the field).<br>
><br>
> > I have investigated populating Make and Model from the BIOS. This<br>
> > can be done on Linux using dmidecode. This does mean the agent<br>
> > would need to run as root though.<br>
><br>
> This is something which is already in some places I think and which<br>
> we may see more often.<br>
> Could it make sense to not call dmidecode directly from the<br>
> plugin/agent, but via some intermediary that<br>
> is small and runs suid root so that the agent does not need to run as<br>
> root?<br>
><br>
> I wonder if we should start writing SELinux policies for those<br>
> routines close to the operating system.<br>
><br>
> Heiko<br>
><br>
> --<br>
> Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,<br>
> Werner-von-Siemens-Ring 14, D-85630 Grasbrunn<br>
> Handelsregister: Amtsgericht München HRB 153243<br>
> Geschaeftsführer: Mark Hegarty, Charlie Peters, Michael Cunningham,<br>
> Charles Cachera<br>
><br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> rhq-devel mailing list<br>
> <a href="mailto:rhq-devel@lists.fedorahosted.org">rhq-devel@lists.fedorahosted.org</a><br>
> <a href="https://lists.fedorahosted.org/mailman/listinfo/rhq-devel" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/rhq-devel</a><br>
><br>
_______________________________________________<br>
rhq-devel mailing list<br>
<a href="mailto:rhq-devel@lists.fedorahosted.org">rhq-devel@lists.fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/rhq-devel" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/rhq-devel</a><br>
</div></div></blockquote></div><br></div>