Thanks Sudhakar.
In that case, I think it would be best to keep the gateway level
ComputeResourcePreference models for the usageReportingGatewayId field and
deprecate their other fields.
Thanks,
Marcus
On Sep 18, 2018, at 4:11 PM, Pamidighantam, Sudhakar
mailto:pamid...@iu.edu>> wrote:
Marcus:
The reporting and ingestion mechanism could be resource dependent. For XSEDE
resources the gateway id is important and is same across the resources. For
others like campus gateways it may be different.
Even among XSEDE several current resources do not have this working. So this
should
Thanks Sudhakar. One quick question, is the gateway id reported ever different
for some compute resources than others? That is, would all of the resources for
which SEAGrid reports usage use the same id (“seagrid”)? I’m wondering if we
really need a per compute host settings for the
