[Hawkular-dev] Future Packaging of Hawkular
Juraci Paixão Kröhling
jpkroehling at redhat.com
Mon Apr 25 03:32:46 EDT 2016
On 22.04.2016 18:35, Stefan Negrea wrote:
> *Motivation*
>
> So far we have created Hawkular "All-in-one" releases that contain
> everything,Hawkular server components, UI, the agent and also embedded
> versions of Cassandra and KeyCloak. It's certainly the case that for
> community we willstill deliver a fully featured all-in-one package. We
> also need to consider separate distributions for other projects that
> integrate with Hawkular.
>
> The recent effort to integrate with ManageIQ comes with its own set of
> requirements for services. Not all of the Hawkular components are
> neededand required components maybe configured differently.For example
> the UI is supplied from within ManageIQ side and Hawkular is to be run
> headless. Other components like Cassandra will not run embedded, so
> there is no need to supply it in an embedded package. KeyCloak will
> probably not be needed because we only have one technical user thatwill
> accessHawkularservices.
Let me reverse the question: what is the motivation for having the
"Community Distribution"? Why would one use it instead of MiQ +
Hawkular? What are the concrete use cases? What can we offer on this
distribution that MiQ + Hawkular can't?
Keeping a distribution like this if we have no concrete use cases or
clear benefits will only cause us to spend time creating/maintaining
when we could be spending time on other more relevant parts.
I asked a similar question already a couple of times in another threads,
but I still couldn't get a good answer. I'm starting to think that
everyone can clearly see the need for this, except me...
- Juca.
More information about the hawkular-dev
mailing list