Hi Sam,
Long term, we want to switch to just Karaf (installed via RPM/DEB).
However, before we switch to Karaf being the "official Brooklyn way",
we'll need to spend some more time working on Karaf and on RPM/DEB.
(The previous RPM/DEB work was against the tgz dist, and will need
revisiting).
I therefore expect we'll continue to support the tgz dist for a while
yet (including in the 0.10.0 release, when that happens).
I think we should leave the existing BrooklynNode as just supporting the
tgz dist. It's a Java-based implementation, which is not where we want
to be long-term.
We can create a yaml-only entity for Karaf-via-rpm/deb, but postpone
doing that until the Karaf/RPM work is finished.
Aled
On 12/09/2016 18:31, Sam Corbett wrote:
Hi all,
Are we moving to a pure Karaf distribution or are we going to continue
to maintain the old `dist' format too?
I'm wondering about the status of the `BrooklynNode' entity. It
expects the dist format and does not work with Karaf. We could update
the entity to try to handle both, create a second entity specifically
for Karaf or change it to drop handling of dists. I think the first
option could be implemented by writing a new driver and changing the
return type of getDriverInterface per a new config key on the
interface that switches between dist+karaf mode. But this is
unnecessary if we don't care about the dist format any more.
Any comments?
Thanks,
Sam
