Hey Peter,
> * Bus - messaging framework for communicating between
components
>
Maybe Nest should be listed here. AFAIK, Bus is always consumed
together with Nest, hence the one can replace "Bus" with "Nest+Bus"
in
your original proposal and I'll be satisfied :)
Yes sure, thanks for pointing it out.
> use a special purpose UI for MiQ.
You say say something about Keycloak, but you do not mention Accounts.
I see that Accounts 2.x will not be included and I suppose that
Accouns 3.x will perhaps not be needed at all (as follows from the
parallel thread), right?
Perhaps? :-) I think you and/or Juca know better which
version of Accounts will be needed if at all.
For core-services we do not need the full multi-tenancy
with KC solution we have and which should still be available
in the community distro.
Here we have a technical user that MiQ uses to connect to
Hawkular-core-services(HCS). And then most probably the
same user that the agents use to talk to HCS.
We may decide that we add more than one user where
e.g. only the super-admin has r/w rights and other users have
r/o. But all those could be configured in a properties file or
via the JBoss-EAP way of setting up users.
For agents talking to the HCS server, we should still have
a way to get tokens so that the user credentials don't need
to be stored in the agent.
If we decide that there will be no Accounts 3.x, then Command Gateway
(being quite small and closely related to Bus) can move to Commons git
repository. Command Gateway does not need to depend on Inventory since
Commons 0.6.0.Final. The change was recently merged to CmdGW.
Sounds good to me.