12:08 p.m.
there is no distinction between config or trait in this new stuff. In this new stuff, they
are one and the same. I store these values inside inventory, not metrics. Have we come up
with a design for traits? Are they handled separately and distinctly in inventory and
h-metrics?
Metrics are different. Metric definitions and Metric Types definitions are first-class
concepts and are stored in inventory separately (resource types have explicit
relationships to metric types, and resources have explicit relationships to metrics).
There is no such thing for configuration properties. So I store config props definitions
as properties directly on the resource type and config prop values directly on the
resource as properties (these are stored in inventory). The metric data (the actual values
collected) are obviously stored in h-metrics.
----- Original Message -----
What are the distinctions between config, trait, and metric?
> On Jun 8, 2015, at 12:27 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
>
> I am working in my own branch, but am about to introduce resource
> configuration and operations to the resource type metadata. This was in
> part due to the UI folks needing the hostname to show in the GUI.
>
> I wanted to let people know what this looks like - speak now if you see
> problems.
>
> The resourceType will now have as part of its attached metadata a list
> named "resourceConfiguration" which consists of config property types
> (today, there is only "name" associated with resource config property
> types, but you can envision other things like "dataType" (for boolean,
> integers, etc)).
>
> There is also a list of operations (today, consists of only a name and
> optional "operationName").
>
> The JSON for resourceType looks like this inside inventory (this is for the
> top level "WildFly Server" type):
>
> "tenant": "28026b36-8fe4-4332-84c8-524e173a68bf",
> "id": "WildFly Server",
> "version": "0.1",
> "properties":
> {
> "name": "WildFly Server",
> "operations":
> [
> {
> "name": "Reload Server",
> "operationName": "reload"
> }
> ],
> "resourceConfiguration":
> [
> {
> "name": "Hostname"
> },
> {
> "name": "Max Heap"
> },
> {
> "name": "Version"
> }
> ]
> }
>
> A resource of this type would look like:
>
> "tenant": "28026b36-8fe4-4332-84c8-524e173a68bf",
> "environment": "test",
> "feed": "mazztower",
> "id": "[Local Host~/]",
> "type": <<<what I showed above>>>,
> "properties":
> {
> "name": "WildFly Server [Local Host] [mazztower]",
> "resourceConfiguration":
> [
> {
> "name": "Version",
> "value": "8.2.0.Final"
> },
> {
> "name": "Hostname",
> "value": "mazztower"
> },
> {
> "name": "Max Heap",
> "value": "477626368"
> }
> ]
> }
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev