<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 25, 2016, at 9:29 AM, Jay Shaughnessy <<a href="mailto:jshaughn@redhat.com" class="">jshaughn@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
<br class="">
<font face="Calibri" class="">Juca, I think Lucas is correct, Alerts has the
multi-tenancy model built in and so requires a tenantId on
everything. We already have a standalone distribution (for use
outside of Hawkular) that drives off of the Hawkular-Tenant
header, so I guess we would just continue to use that mechanism in
all cases. I guess that means we may drop the h-accounts
dependency but I will discuss further with Lucas and we'll
continue to monitor the accounts changes.<br class="">
<br class="">
Lucas, this may further drive the need for schema refactoring
because if we only receive a single tenant on everything coming
from MIQ, we will get very little data distribution.<br class=""></font></div></div></blockquote><div><br class=""></div><div>I’ve said it in the past and it’s worth mentioning again. Even with multiple tenants, you should be partitioning by more than just tenant.</div></div></body></html>