[CSS-CLOUD] Update CDDS Actions and CDDS Tracking Data Service

[Holger Dreihahn]

Dear CDDS Colleagues,
Some updates on the CDDS actions from the Spring Meeting.

OB-1 Use the production state description to introduce the nature of the production
A first attempt has been made, and one or two sentences have been added for each service. Please review and let me know what you think.
When updating that, I thought a little diagram would also help. If that is perceived as helpful, we could base this either on functional resources or in a free format.

OB-2 Define gRPC CDDS Tracking Data Service
Both, the Orange Book and the CDDS GitHub repository have been updated, and a gRPC service has been defined along with a TD endpoint. The TD endpoint makes use of the tracking data types coming from the conversion of the TDM XSDs to the TDM Protobufs. While that is in my mind correct, it raises a question how to document and describe the TDM Protobuf types. To avoid repeating the TDM book, the CDDS TD service references the TDM book and explains that the TDM Protobuf types follow systematically the TDM book and therefore the TDM is a valid reference. Please let me know if that is a workable approach, needs more explanation or whatsoever. Moreover please scrutinize if the CDDS TD service can actually select and provide meaningful tracking data, I am not an expert on that.

To have a systematic conversion it would be good to have the TDM XSD to TDM proto conversion automated and available for everybody. I see two options:

  1.
Include the conversion in the CDDS GitHub maven build
  2.
Define an own little TDM2PROTO project in the CCSDS GitHub and have the automatic conversion there

Let me know what you prefer.

OB-9 Shift message definitions from section 4 to section 3
The Orange Book has been updated in that regard. I think that was a good move.

Best regards,
Holger
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-cloud/attachments/20260610/8db3d5ed/attachment.htm>