[Smwg] CSTS procedure instances and service packages

[John Pietras]

Erik,
The paradigm is that, for those procedure types that can have multiple instances (some types are limited to one instance), Service Management configures the maximum number of instances that can be activated for the execution of the Service Package (in reality it could be more of a permanent upper limit established in the Service Agreement, but since we're going in the direction of making the SA a collection of Configuration Profiles, the upper limits will be specified as part of those CPs).

The instance numbers are sequentially ordered (that is, if SM configures 10 instances, the procedure instance numbers are 1 -10), and at the time of the initial configuration all instances of a given procedure type for a given CSTS instance have the same initial configuration parameter values. Whether or not the CSTS user chooses to activate some or all of the procedure instances (up to the SM-configured max) is up to them, and the degree to which a user can tailor each instance (e.g., what parameters a given procedure instance reports and at what intervals) is all handled in-line as part of the protocol of the procedure type. So it's all hands-off for SM beyond the specification of the max number of procedure instances.

John

From: Barkley, Erik J (3970) [mailto:erik.j.barkley at jpl.nasa.gov]
Sent: Monday, May 21, 2018 12:20 PM
To: John Pietras <john.pietras at gst.com>; Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP] (wesley.m.eddy at nasa.gov) <wesley.m.eddy at nasa.gov>
Cc: CCSDS Service Mgmt WG <smwg at mailman.ccsds.org>
Subject: RE: CSTS procedure instances and service packages

John,

Do any CSTSes have dynamically spawned procedures, implying on-the-fly procedure instance Ids?  If not, then, yes, this is more of a concern to address in the configuration profile.  But if so, then we might have an issue to address?

-Erik

From: John Pietras <john.pietras at gst.com<mailto:john.pietras at gst.com>>
Sent: Monday, May 21, 2018 4:49 AM
To: Barkley, Erik J (3970) <erik.j.barkley at jpl.nasa.gov<mailto:erik.j.barkley at jpl.nasa.gov>>; Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP] (wesley.m.eddy at nasa.gov<mailto:wesley.m.eddy at nasa.gov>) <wesley.m.eddy at nasa.gov<mailto:wesley.m.eddy at nasa.gov>>
Cc: CCSDS Service Mgmt WG <smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>>
Subject: RE: CSTS procedure instances and service packages

Erik,
This is something that will be part of the configuration profiles. The Service Package format isn't "aware" of it outside of carrying the inherited configuration profile information when a Service Package Result is in verbose mode.

John

From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Barkley, Erik J (3970)
Sent: Friday, May 18, 2018 7:50 PM
To: Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP] (wesley.m.eddy at nasa.gov<mailto:wesley.m.eddy at nasa.gov>) <wesley.m.eddy at nasa.gov<mailto:wesley.m.eddy at nasa.gov>>
Cc: CCSDS Service Mgmt WG <smwg at mailman.ccsds.org<mailto:smwg at mailman.ccsds.org>>
Subject: [Smwg] CSTS procedure instances and service packages

Hello Wes,

I am currently reviewing the CSTS concept book prior to publication polling and came across the following sentence in reference to CSTS procedures:

"Different instances of the procedure are distinguished by a 'procedure instance identifier' that is assigned by Service Management and included in all operation invocation headers."

I took a quick look at the service package draft book and I don't think this level of concern has been addressed yet. I think we may have some coordination work to do with regard to how to represent CSTS service instances in service packages. In any case, just a heads up for now.

Best regards,
-Erik



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/smwg/attachments/20180521/e103fce0/attachment.html>