Tenancy on Hawkular Services
by Juraci Paixão Kröhling
(this email uses the Hawkular naming as proposed by lponce)
It seems there has been some confusion about the situation around the
multi tenancy in Hawkular Services. Most of what was discussed today on
IRC was already discussed in a way or another before, but here's a
summary of the previous discussions + what was discussed today on IRC:
Hawkular Services, except Agent:
* Tenant data is not going to be derived from Hawkular Services Auth Data.
* Tenancy is to be determined by the client and sent to Hawkular
Services via the "Hawkular-Tenant" header.
* As tenancy is not to be determined at Hawkular Services, there's no
point in having Accounts anymore. Most, if not all, components have
already a "remove Accounts dependency" JIRA. If you need help on this
task, let me know
* Removing Accounts != removing tenancy support. Multi tenancy is still
a requirement for Hawkular Services!
* If the tenant is not provided (ie: Hawkular-Tenant HTTP header is
non-existent or invalid), your endpoint should return a "400 - Bad Request".
* We might still have multi tenancy on Hawkular. But that's irrelevant
for your component.
Agent and non-Hawkular Services:
* Agent will allow the user to set a tenant on standalone.xml . By
default, it will be set to "hawkular"
* The Hawkular Ruby Gem, used by MiQ, will use tenancy information from
MiQ when available. By default, it will be set to "hawkular"
* OpenShift already sends Hawkular-Tenant to Hawkular Metrics
- Juca.
9 years, 11 months
Keycloak on Hawkular
by Juraci Paixão Kröhling
Similar to the thread about Tenancy on Hawkular Services, I thought I'd
also post about the current state of Keycloak for Hawkular.
Hawkular Services cannot depend on Keycloak. Because of that, Nest is
being changed to not consume the Keycloak Feature pack as before.
As a side effect, we do not have support for tokens anymore (key/secret
tokens, created via the "Tokens" UI), as those tokens were backed by
OAuth Offline Tokens.
Hawkular Services will have a simple JAAS integration, which should give
us enough flexibility for the scenarios that we need to support.
The UI on Hawkular will also have to remove the keycloak.js . I have yet
to talk to the UI developers, but I think the main idea for now would be
to have the WAR for the UI to be deployed and protected like any other
backend component. The Accounts-related part will also have to be
removed, such as the Organization and Token management.
Nothing prevents Hawkular from shipping with Keycloak (server and/or
adapter), as recent versions of Keycloak can protect any WAR deployments
transparently, via the Keycloak Adapter Subsystem for Wildfly. This can
be done by the community if interest in that integration exists but I
currently have no plans on working on that.
For reference, this is how you can activate a simple JAAS for your
deployments:
https://git.io/vwADp - web.xml (on your WAR)
https://git.io/vwAyT - application-roles.properties
https://git.io/vwAyL - application-users.properties
- Juca.
9 years, 11 months
Collapsing of Repos ?
by Heiko W.Rupp
Hi,
we do have a larger number of repositories and source trees.
Now that we have narrowed down the scope of our work a bit and also
have an idea of what we need for the "core services" package, I wonder
if we can collapse repositories and source trees into larger ones.
As an example: alerts and metrics could go together into
hawkular-metrics and the forwarding of data to alerts could be
done with Java method invocation.
What else could be done here?
9 years, 11 months
accounts, tenants, the agent
by John Mazzitelli
Now that Accounts is getting taken out, how is the agent to determine its tenant ID?
The agent needs to know its tenant ID when inserting data into Hawkular Metrics.
Right now, the agent makes an explicit http call to the Accounts URL to obtain the tenant of its user. If Accounts goes away, the only thing left that I can see is to make required the agent attribute "tenantId" in standalone.xml configuraiton of the agent subsystem.
Is that correct? There is no other way to get the tenant ID of a user now, I guess.
(for what its worth, tenant IDs are important in the Open Shift use-case)
9 years, 11 months
Hawkular-Archive - New Org
by Stefan Negrea
Hello,
I would like to propose a new organization in Github to host projects that
no longer receive development. "Hawkular-Archive" seems a good name for
this purpose. The goal is to keep the main Hawkular org focused on
important projects and at the same time preserve work that was already done
but away from the main organization.
>From a quick look at the current organization here are two repositories
that can be moved right away: hawkular-metrics-openshift (Openshit 2.x
cartridge for Hawkular Metrics 0.2.7 or earlier) and hawkular-bus (code
moved to another repo). Am I am sure we can find other repositories to
move.
In the long run we can develop some criteria for archiving projects but for
now we can just do a one-time major cleanup.
Any repositories that should be archived right away? Any other suggestions
for a name? Any thoughts on the idea in general?
Thank you,
Stefan Negrea
Software Engineer
9 years, 11 months
Hawkular-BTM UI Details
by Preethi Kannan
Hi Team,
I am analysing Hawkular-BTM and trying to record business transactions for various applications.
I wish to get more detail about the various tabs we have in the Hawkular-BTM UI like (Candidate,Active,Disabled,Ignored).
It would be great to know the various features and use Hawkular to a greater extent.
Thanks,
Preethi
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
9 years, 11 months
Inventory 0.15.1.Final released
by Lukas Krejci
Hi all,
Inventory 0.15.0.Final had a serious performance regression in the bulk
insert. The 0.15.1.Final fixes that problem and the performance should now be
on the same order of magnitude as previously (still 0.15.x is slower on
creates, updates and deletes than 0.14.x thanks to the new identity hashing
functionality).
Please update as soon as possible,
Thanks,
--
Lukas Krejci
9 years, 11 months
Agent - EAP Domain mode support
by Thomas Heute
The question is likely for Mazz, but I wanted to check how we will support
the WF domain mode.
As far as I understand, we are now able to run the agent in the host
controller but wanted to know a bit more on how we expect the setup to be
(one agent on the host controller for the whole domain ?)
Also I wanted to ask if older versions of the app server could be supported
or only WF 10 ? (in particular in the context of EAP7/EAP6 support)
Thomas
9 years, 11 months
