arc.conf

Thursday 20 Apr 2017, 10:00 → 11:00 Europe/Stockholm

Fysiska institutionen-Physics Department

Mattias, Florido, Balazs, Aleksandr, Martin, Oxana, Andrii (joins later) 10:00 - 11:??

1)  no objections for the decisions taken last time. Everybody succeeded to implement the agreed new block header, and other structural decisions.

DECISION: a follow up decision (was discussed on the chat, this is just to record it): everything after a colon must be parsed as a name, no further structures/subblocks are allowed after a ":" in a block header.

2) Andrii's DNS-Index  and the  arc.conf

postponed

3) TODOs: almost all of them resolved, Martin will complete the remaining default related ones next week.

4) repeating parameters in several blocks (e.g. authorizedvo)

it is clear that currently we can't make a strong statement such as "one parameter can only occur in one block". sometimes variables of a block overwrite another variable in another blocks

TODO: collect all the multiple occuring parameters

Discussion postponed.

5) merging grid-manager/ws/cache  and ws/candypond ?

postponed

6)  Attribute precedence in LRMS scripts/Valid attributes

postponed (see point 4)

7) spaces

TODO: Florido to come with  space usage rules in variable and block structures

8) grid-manager.log:

DECISION: to be renamed as arex.log

9) [arc/ganglia]

her we need Maiken: postponed

10)  [acix/cacheserver] [acix/indexserver] is not following block logic, rename as [asixsscanner] ?

postponed

11) use some other way of indicating which variable is mandatory? like an asterix?

proposal something like 

hostname (mandatory) - The text of the description bla bla

Feedback from David is needed, final decision postponed.

12) decide later the most logical ordering of the blocks (for better readibility)

postponed

13) terminology: attribute value or option value or variable value?  parameter... make it consistent

postponed

15) tracking document: Aleksandr, Andriii is done for their own part Mattias, Martin, Florido started to use the tracker.

16) location of the arcconfig-parser:

DECISION: arc/utils/config  and then specify that it is not for use with the libraries.

module is called config.py

17) next meeting: either next week Thursday same time slot 10-11 or if there'll be the conflicting "ARC-CE  crisis" meeting then two weeks from now.