[Moims-sc] Actions for the Configuration service (with the attachment)

Thu Jan 29 15:44:46 UTC 2015

Hi Francois,

sorry for the delay of my answer. However, I did forward your email to Sam 
immediately when I received it as he is working on the configuration 
service. 

I have not had any discussion on this topic so far, but I find your charts 
very helpful. I will check with Sam if he would like to have a short webex 
with you to clarify any of the concepts. 

Thanks for these inputs!

__Mario

From:   Francois Allard/estec/ESA
To:     Mario Merri/esoc/ESA at ESA, 
Date:   23/01/2015 17:16
Subject:        Re: [Moims-sc] Actions for the Configuration service

Mario

The attached is preliminary. 
For now it summarizes where we are within MOSSG. Which is not very 
detailed as an output
However here it is. Know we will be revisiting it at the MOSSG face to 
face meeting in March and may be at an SMC MOSSG meeting like we did in 
London. Are you interested in that idea?
Best Regards

Francois Allard
Ground Segment Maintenance and Operations Manager
ESTEC HSO-ICG
Tel: +31 715653250
Mob: +31 652062149
e-mail: francois.allard at esa.int

From:   Mario Merri/esoc/ESA
To:     Francois Allard/estec/ESA at ESA, 
Date:   16/01/2015 12:24
Subject:        [Moims-sc] Actions for the Configuration service

Hi Francois,

Happy New Year.

I attach a recent note from Sam which is asking for inputs on the 
configuration services. This was a request from the MOSSG. Maybe you want 
to distribute this note the the MOSSG group and ask fro their use cases.

Thanks

__Mario
----- Forwarded by Mario Merri/esoc/ESA on 16/01/2015 12:22 -----

From:   "Sam Cooper" <Sam.Cooper at scisys.co.uk>
To:     <moims-sc at mailman.ccsds.org>, 
Date:   13/01/2015 11:05
Subject:        [Moims-sc] Actions for the Configuration service
Sent by:        moims-sc-bounces at mailman.ccsds.org

Dear All,

This is a quick reminder that there was a couple of actions on us all to 
review the need for the access control service and also to provide use 
cases for the configuration service. Specifically this would be how you 
would expect to use the configuration service and what information you 
would expect to see in it.

>From the minutes of the meeting (and as a reminder):

Access Control Service. This service is currently not in the book. The 
basic idea of the service is to manage the access to functions. This 
service is also considered as a way to match the new PUS-C feature to 
manage compound checking functions. After some discussion, it was not 
clear if this requirement is needed at all. 
Action 141111-01 ALL to provide SC with use cases that justify the need 
for the Access Control Service. Due 10Dec14.

Configuration Service: Currently the service contains only 1 operation to 
activate a given configuration. It was discussed if the service should be 
expanded to include also other capabilities, for instance the ability to 
ingest/deliver a specific configuration. Also, the availability of a 
standard (file) format to hold the configuration could be useful: in this 
way the service provider and consumer could be automatically configure 
their ends. 
Action 141111-04 ALL, including the MOSSG, to provide SC with use cases 
for the Configuration Service. Due 10Dec14.

Myself and Cesar have proposed a solution to the access control issue with 
the mapping to PUS-C check protection so my immediate feeling is that as 
Access Control is not a problem that we can quickly address if we want to 
keep the moment going we should put it on the back burner for now.

Regarding Configuration, my idea is to have it such that you can request 
from a service provider its configuration, that there would be a standard 
format for that configuration, and that you can request the configuration 
for a service provider that may cover several services i.e. of the 
application rather than one specific service of that application. Cesar 
has also suggested that the Directory service should allow you to request 
the XML service specification which I also think is a good idea. This fits 
with MOSSG?s request for automatic configuration of clients.

If you could send me any thoughts you have by the beginning of next week 
that would help me a lot.

Best regards,
Sam.

__________________________________________________________________

Sam Cooper
Systems Architect ? Space Division
SCISYS UK Limited
T: +44 (0)117 916 5127 | F: +44 (0)117 916 5299
E: sam.cooper at scisys.co.uk | www.scisys.co.uk

SCISYS UK Limited. Registered in England and Wales No. 4373530.
Registered Office: Methuen Park, Chippenham, Wiltshire SN14 0GB, UK.

Before printing, please think about the environment.
_______________________________________________
Moims-sc mailing list
Moims-sc at mailman.ccsds.org
http://mailman.ccsds.org/mailman/listinfo/moims-sc

This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-sc/attachments/20150129/43cb3296/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MOSSG Telecon 22 January 2015.pptx
Type: application/octet-stream
Size: 306672 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-sc/attachments/20150129/43cb3296/attachment.obj>