Hi all,
if you don't mind, I would like to take the liberty to ask a question about xrootd configuration, given that there are the experts in this thread.
I don't know if you are also familiar with the dpm configuration of xrootd, but I will pose the questions anyway :)
The first question is about dpm xrootd configuration with yaim, the second about xrootd config directly (basically one question from different aspects).
First:
In yaim, there is the variable DPM_XROOT_FEDREDIRS. What kind of values can it assume?
In the manual they give the example
DPM_XROOTD_FEDREDIRS="atlas-xrd-uk.cern.ch:1094:1098,atlas,/atlas"
and a similar one for CMS, but it is not clear to me how it looks when
a) you have multiple paths
b) you join both the atlas _and_ cms federation
If you don't know about dpm xrootd config, here' the second question:
Is there a situation where you would start more than one daemon configurations for one VO? That is, having two or more lines like XROOTD_INSTANCES_CMS(1|2)_OPTION = … in the sysconfig
If you are exporting multiple paths and join multiple federations, how does the xrootd.redirect parameter look like in the config?
Can you have multiple mentions of it, e.g.:
...
xrootd.redirect $(dpmhost):$(xrootfedlport2) /store/
xrootd.redirect $(dpmhost):$(xrootfedlport1) /atlas/
…
Thank you for any answers!
Cheers
Martin
On May 22, 2013, at 11:17 AM, Henrik Öhman <[log in to unmask]> wrote:
> Hi Martin,
>
> No, sorry. Something came up. I will have time to try it out after today.
>
> Regards,
> Henrik
>
> On 22 May 2013 09:53, Martin Philipp Hellmich <[log in to unmask]> wrote:
>> Hi Henrik,
>>
>> did you get a chance to try it?
>>
>> Cheers
>> Martin
>>
>> On May 17, 2013, at 3:55 PM, Martin Philipp Hellmich <[log in to unmask]> wrote:
>>
>>> Hi all,
>>>
>>> so the module should be able to configure a dpm with xrootd as head node or disk node, but _without_ federation.
>>> It would be great, if you could test that.
>>>
>>> The federation part is trickier and I am still working on it.
>>> If you want to have a look at this, I believe it can follow the same schema as the other configs, look into "modules/dmlite/manifest/xrootd.pp".
>>>
>>> Cheers
>>> Martin
>>>
>>> On May 17, 2013, at 11:10 AM, Henrik Öhman <[log in to unmask]> wrote:
>>>
>>>> Thanks Martin,
>>>>
>>>> I'll have a look over the weekend!
>>>>
>>>> Best regards,
>>>> Henrik
>>>>
>>>> On 17 May 2013 10:52, Martin Philipp Hellmich <[log in to unmask]> wrote:
>>>>> Hi Henrik
>>>>>
>>>>> the branch to use is 'test'. The punch-modules are the collection of all puppet modules used at CERN.
>>>>> This is where the xrootd module should go in the end, too.
>>>>>
>>>>> If you look in the folder 'modules', you can find the xrootd and the lcgdm modules.
>>>>> The templates are inside there, too, in a template folder.
>>>>> You can find an example how to use it in a dpm configuration here:
>>>>> https://svnweb.cern.ch/trac/lcgdm/browser/extras/puppet/manifests-testbed
>>>>>
>>>>> The xrootd manifests are in 'xrootd'. The xrdbase.pp holds all the information.
>>>>>
>>>>> Hope that helps, please ask if I missed something!
>>>>>
>>>>> Cheers
>>>>> Martin
>>>>>
>>>>>
>>>>> On May 17, 2013, at 10:43 AM, Henrik Öhman <[log in to unmask]>
>>>>> wrote:
>>>>>
>>>>>> Dear Martin,
>>>>>>
>>>>>> Thanks for the repo link. I have cloned it, but there is no default
>>>>>> branch (e.g. master), only 'devel' and 'test'. Which one should I use?
>>>>>>
>>>>>> Further I have no experience with punch-modules - could you tell me
>>>>>> where to start digging? For the ATLAS (US) Tier3 perspective, I'd like
>>>>>> to examine the configuration file templates and also the manifests
>>>>>> responsible for creating the configuration files. Could you give me a
>>>>>> pointer or two?
>>>>>>
>>>>>> Thanks,
>>>>>> Henrik
>>>>>>
>>>>>> On 16 May 2013 11:06, Martin Philipp Hellmich <[log in to unmask]> wrote:
>>>>>>> Hi Henrik, Andrea,
>>>>>>>
>>>>>>> I am very happy to collaborate.
>>>>>>> I have started making an xrootd puppet module, which is general and extensible.
>>>>>>> It now works together with a dpm-xrootd module defining extra variables and parameters and hiding some of the configuration complexity to the user.
>>>>>>>
>>>>>>> The xrootd part should be invoked through
>>>>>>> class{"xrootd::config":}
>>>>>>> class{"xrootd::install":}
>>>>>>> class{"xrootd::service":}
>>>>>>> plus two functions after config, which create the configuration files:
>>>>>>> create_config{"config_disk":}
>>>>>>> create_config{"config_redir":}
>>>>>>> create_sysconfig{"sysconfig":}
>>>>>>>
>>>>>>> so in all it looks like this in your manifest:
>>>>>>> class{"xrootd::config":}
>>>>>>> create_config{"config_disk":}
>>>>>>> create_config{"config_redir":}
>>>>>>> create_sysconfig{"sysconfig":}
>>>>>>> class{"xrootd::install":}
>>>>>>> class{"xrootd::service":}
>>>>>>>
>>>>>>> If you are interested to have a look at the code, checkout the test branch from here:
>>>>>>> [log in to unmask]:./public/repo/punch-modules
>>>>>>> It's the punch module repo with the xrootd and lcgdm::xrootd modules added (and some minor changes throughout so it works without hiera)
>>>>>>>
>>>>>>> I am happy to help dig through the code and try it!
>>>>>>>
>>>>>>> Cheers
>>>>>>> Martin
>>>>>>>
>>>>>>> On May 16, 2013, at 10:00 AM, Henrik Öhman <[log in to unmask]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Dear Fabrizio,
>>>>>>>>
>>>>>>>> I got this mail through Sergey Panitkin, and I believe I can be of some help. Note that I'm not on the xrootd-l list, so please make sure that my email is among the recipients in your reply.
>>>>>>>>
>>>>>>>> I have been using puppet to configure xrootd on Google Compute Engine (GCE). In this activity I have based my modules and templates on the ATLAS US Tier3 puppet modules. I am by no means an expert on puppet, but I do have some experience crafting puppet modules and templates for different services. I have some spare time right now, so if you'd like me to take a look at your specific setup let me know.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Henrik
>>>>>>>>
>>>>>>>>
>>>>>>>> -------- Original Message --------
>>>>>>>> Subject: Anybody with puppet for xrootd ?
>>>>>>>> Date: Wed, 15 May 2013 16:09:38 +0200
>>>>>>>> From: Fabrizio Furano <[log in to unmask]>
>>>>>>>> To: xrootd-l <[log in to unmask]>
>>>>>>>> CC: Martin Philipp Hellmich <[log in to unmask]>, Oliver Keeble <[log in to unmask]>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi xrootd folks,
>>>>>>>>
>>>>>>>> as DPM team we are planning to invest into puppet for the setup, and
>>>>>>>> of course this would cover also the so-called xrootd plugin, that
>>>>>>>> involves an xrootd setup as a frontend of DPM, plus some DPM-related
>>>>>>>> Xrd* plugins.
>>>>>>>>
>>>>>>>> The question is... is there anybody who has experience/templates/etc.
>>>>>>>> about setting up xrootd clusters with puppet ? Our idea is to be
>>>>>>>> compatible with existing practices, if any, or, even better, to share
>>>>>>>> material on this.
>>>>>>>>
>>>>>>>> Thank you!
>>>>>>>>
>>>>>>>> Fabrizio
>>>>>>>>
>>>>>>>> ########################################################################
>>>>>>>> Use REPLY-ALL to reply to list
>>>>>>>>
>>>>>>>> To unsubscribe from the XROOTD-L list, click the following link:
>>>>>>>>
>>>>>>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Martin Hellmich Information Technology Department
>>>>>>> [log in to unmask] CERN
>>>>>>> +41 22 76 765 26 CH-1211 Geneva 23
>>>>>>>
>>>>>
>>>>> --
>>>>> Martin Hellmich Information Technology Department
>>>>> [log in to unmask] CERN
>>>>> +41 22 76 765 26 CH-1211 Geneva 23
>>>>>
>>>
>>> --
>>> Martin Hellmich Information Technology Department
>>> [log in to unmask] CERN
>>> +41 22 76 765 26 CH-1211 Geneva 23
>>>
>>
>> --
>> Martin Hellmich Information Technology Department
>> [log in to unmask] CERN
>> +41 22 76 765 26 CH-1211 Geneva 23
>>
--
Martin Hellmich Information Technology Department
[log in to unmask] CERN
+41 22 76 765 26 CH-1211 Geneva 23
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
|