| | 1 | = Quattor Workshop - CNAF (Bologna) - 30/9/2013-2/10/2013 = |
| | 2 | [[TracNav]] |
| | 3 | |
| | 4 | [[TOC(inline)]] |
| | 5 | |
| | 6 | |
| | 7 | [http://indico.cern.ch/conferenceTimeTable.py?confId=252955#all.detailed Agenda] |
| | 8 | |
| | 9 | |
| | 10 | |
| | 11 | == Project Status - L. Munoz == |
| | 12 | |
| | 13 | Survey ran before the workshop |
| | 14 | * Significant improvement compared to previous ones |
| | 15 | * QWG : many were not able to move to QWG or forked a long time ago. We need to think more heavily at it. |
| | 16 | * Aquilon adoption making progress (2-3 sites) |
| | 17 | * Community support is perceived as good |
| | 18 | * Documentation: still the weak point, were not able to make significant progresses |
| | 19 | * LAL wiki: certificate problem still perceived as a barrier, a developer only resource |
| | 20 | |
| | 21 | == Core modules == |
| | 22 | |
| | 23 | === Configuration Modules - L. Munoz === |
| | 24 | |
| | 25 | Releases |
| | 26 | * Count : nine releases, 3 of them tagged as stable |
| | 27 | * New releases are not mandatory |
| | 28 | * Need a releaser manager backup for Luis |
| | 29 | |
| | 30 | Config modules: main activity is on the core components |
| | 31 | * Not much on grid components or on daemons |
| | 32 | * ncm-openldap and ncm-cups were resurrected |
| | 33 | |
| | 34 | New features |
| | 35 | * Preliminary support for SSSD in authconfig |
| | 36 | * YUM-based SPMA ready for production |
| | 37 | * Hooks for ncm-ncd before and after execution of components |
| | 38 | |
| | 39 | Metaconfig stuff |
| | 40 | * Ugent has schemas and templates for many services: would like to share them |
| | 41 | * But we can hardly promise backward compatibility |
| | 42 | |
| | 43 | Work in progress |
| | 44 | * Policy-based component dispatching in ncm-ncd |
| | 45 | * Solaris port |
| | 46 | * ncm-network: still not much progress |
| | 47 | |
| | 48 | |
| | 49 | === ncm-ncd hooks and policy-based component scheduling === |
| | 50 | |
| | 51 | See [/wiki/Development/PrePostActionsNCMNCD proposal]. |
| | 52 | |
| | 53 | Goal: execute some arbitrary actions before running all components and after. |
| | 54 | * These actions will have no access to node profile |
| | 55 | * Specified by `run-init` and `run-finalize`in `/etc/ncm-ncd.conf` |
| | 56 | * An error during `run-init` will prevent executing components but `run-finalize` will run |
| | 57 | |
| | 58 | Hooks may be used to implement site-specific policy for component scheduling, allowing to filter out some components from the initial list based on some local criteria |
| | 59 | * But what to do with dependencies if one is filtered out? Can be very complicated |
| | 60 | * Probably better/enough to implement a "everything or nothing" strategy: at least use case can be cleanly defined |
| | 61 | |
| | 62 | Some use cases for executing only part of the configuration changes for a component. Proposal: |
| | 63 | * Split component configuration into 2 different parts/subtree, e.g. `/software/components/filecopy` and `/software/components/filecopy-magic` |
| | 64 | * Bind `/software/components/filecopy-magic` to `type_filecopy` |
| | 65 | * Define a component alias name in `filecopy-magic` saying it will use component `filecopy` to execute the action |
| | 66 | * New field in `deps` structure |
| | 67 | * Filter out `filecopy-magic` in run-init hook |
| | 68 | |
| | 69 | |
| | 70 | |
| | 71 | |
| | 72 | |
