perfsonar development work

[Maciej Glowiak <>]

Hi Jason,

Jason Zurawski wrote:
(...)
>  * 'Selective' LSDeregister - Be able to pass metadata in the sent data
> to remove only certain things on a Deregistration message (Implemented
> in perfSONAR_PS, works well especially for ControlPlane services that
> will 'tear down' items and let us know they are going away).
>
>  * LSRegister 'Update' improvements - be able to 'add' to an existing
> registration without deleting all other things.  This is VERY necessary
> for dnyamic services and improves registration times dramatically
> (Implemented partially in perfSONAR_PS, I would like a separate LSUpdate
> message...)

I agree, separate LSUpdate message would be useful for that. We should 
also consider having selective "adding" and "removing" functionality 
within such message type. Now, updates as a part of LSRegisterRequest 
are useless. That was implemented mostly to follow the initial 
requirements of the service, but we didn't have any strong need for 
implementing it for services like RRD MA.

>  * Storage Structure Change - This is the area that I am exploring next
> and I think will also be very beneficial.  Currently the service info
> and data are all tied to the single control structure for time.  This
> means that when the service expires, so does the data.  This works well
> for services in which the data will never change, but is problematic for
> dynamic data sets/.  The Topology Service for example will experience
> constantly entering and leaving information, and shouldn't have to keep
> records on what needs deleting from the LS.  It would be much easier to
> let the 'data' expire on its own (hence freeing the services from
> needing to perform 'deregister bookeeping').  When the dynamic services
> 'register' or 'update' then, the older stuff will never be touched and
> eventually will be removed.  This will require a more frequent update
> interval.  This leads to the last item...

We could discuss it a bit (or a way how to implement it) during Zagreb 
meeting if you will be there. I'll add it to Szymon's list of proposed 
topics for the meeting.

>  * 'Selective' LSKeepalives - Similar to what is done in LSDeregister
> above.  Will allow us to keep individual data alive.
>
> Comments on any of the above welcome.

Going back to the Roman's question - now I set the default TTL for all 
services for 24 hours.

Best regards,
Maciej

--

 --------------------------------------------------------------------
| Maciej Glowiak        Network Research and Development            ||
| 

     Poznan Supercomputing and Networking Center ||
| (+48 61) 858 2024          -- skype_id: maciej_psnc   GG: 4526858 ||
 ====================================================================