APEL Client Requirements

Description

Volatile information publishing, producers will retry publishing if there is no acknowledgement from consumer.

Client types

Producers

Producers publishing accounting data, WAN distributed.

Consumers

Consumer consuming collected accounting data, could be LAN distributed.

Destination types

  • short-term destination type, for example: grid.accounting.cpudata.<ROC-NAME>
  • long-term will be looking at one destination type per type of accounting data

For a give destination type:

  • instances number: at least 1 central instance, maximum 1 instance per NGI plus 1 central (~41)
  • messages content: encrypted accounting data
  • messages size: between ~1kB and 1MB
  • format of the messages body: SMIME wrapper
  • messages lifetime: 0 since producers will resend
  • maximum latency: < 15 seconds
  • permanent vs occasional connections: permanent connections
  • security requirements: none at messaging level

For a given destination instance:

  • 1 producer, 1 consumer, 20 messages per day

For a given destination type:

  • maximum 330 producers, 1 consumer, ~7K messages per day

Programming Languages

  • Python


This topic: EMI > WebHome > EmiProjectStructure > EmiProductTeams > EMIMessaging > EMIMessagingRequirements > EMIMessagingRequirementsApelClient
Topic revision: r4 - 2011-10-06 - LionelCons
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback