Also: the dpm-* and dpns-* tools actually mostly don't depend on rfio
(although some of them depend on the DPM API, which they also need to
be ported from to the dmlite API - *my* tools depend on you having a
suitable MySQL backend to the DPM but on nothing else.)
Sam
On 13 January 2015 at 17:42, Wahid Bhimji <[log in to unmask]> wrote:
> Hi
>
> Well there is the dmlite shell which replaces much of the functionality of
> those admin tools.
>
> https://indico.cern.ch/event/324705/contribution/12/material/slides/1.pdf
>
> But I’m not sure if thats what you are asking.
>
> There is quite a lot of work to get off rfio internally to dpm (drain is the
> one I’d like to see change first..)
>
> Wahid
>
> On 13 Jan 2015, at 17:44, Alessandra Forti <[log in to unmask]> wrote:
>
> Hi,
>
> in the presentation Oliver has given this afternoon he wrote
>
> We keep ‘as it is’ the legacy metadata protocols, clients and tools:
> • SRM
> • rfio
> • Dpns-*
> • Dpm-*
> • Where needed/possible we transfer their functionality
> • Into the new plugin stack (
> DMLite)
> • Exposed via WebDAV where possible
>
> I might have missed this passage announcement but is there any documentation
> about the functionality transfer? Because one of the reasons rfio cannot be
> turned off seems to be the dpns-* and dpm-* tools.
>
> cheers
> alessandra
>
> --
> Respect is a rational process.
>
>
>
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
|