10:07 a.m.
This is primarily intended for OpenShift. Right now Metrics is included in OpenShift. In
the future, we want include Metrics and Alerts. There is a different security set up in
OpenShift, so accounts is not used in those deployments.
On Nov 16, 2015, at 10:56 AM, John Mazzitelli <mazz(a)redhat.com>
wrote:
Should this also be built on top of or use the thing that someone (Juca?) is doing to
build a common "nest+accounts" distro?
Because right now, this makes I think *four* different Wildfly+Hawkular-stuff assemblies
we have in the codebase. If anything changes in, say, accounts config, we're going to
have to chase down all these different assemblies to put that fix in all of them.
We really need a single base assembly distro that we can build all the other stuff on top
(which includes the kettle itself)
----- Original Message -----
> I believe the "metrics-component" module and this new distro module
> should move to the hawkular repository.
>
> Le 16/11/2015 16:03, John Sanda a écrit :
>> Over the past couple weeks I have been working on a standalone deployment
>> of Metrics and Alerts. The work is being tracked under HWKMETRICS-311. One
>> of the changes I made was to introduce a new maven module in the
>> hawkular-metrics project that builds and assembles a WildFly 10 distro
>> which includes Metrics and Alerts. Should this new module and other
>> integration modules live in the main hawkular repo instead of the
>> component repo?
>>
>> - John
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev