Hi,
while waiting on some input for the provisioning subsystem requirements, I
actually went ahead and tried to design a new plugin API that kind of merges
the capabilities of the current bundle and content subsystems, keeping the
functionality I thought might be useful.
I've created a pull request (between 2 branches in my fork of RHQ on github)
where I'd like to start the discussion about the API. The reason I want to do
it on Github is that we can have a discussion directly at the pull request but
more importantly we can put comments inside the diff itself at the concrete
lines of code, making the discussion targeted and focused.
I would love to hear some comments on the design, your initial thoughts, some
pitfalls I managed to fall into that you already avoided in the past, etc. I'm
looking especially at you, Jay and Mazz, because your input so far was
invaluable for me.
Note that this is *only* the plugin API - i.e. it only defines the blueprint
for interactions between the plugin container and the agent plugins. This does
not deal at all with how the bundles/packages/deployable files/however we are
going to call them are stored on the server, nor does it in any way define a
workflow for deployment, reverts, etc. Obviously these things, once we get to
them, will affect this API, too, but I wanted to get some discussion on the
general direction I'm heading in this piece of code.
You can review the pull request here:
https://github.com/metlos/RHQ/pull/8
and you can checkout the "feature/provision/plugin-api" branch from the above
repo to get the code yourselves.
Looking forward to your feedback,
Lukas