| 72 | | |
| | 100 | Documentation may be organized in 2 different parts: |
| | 101 | * Getting started: build/describe an optimized procedure for a user to start with Quattor both for evaluating AND setting up a production infrastructure (could then be used to produce an appliance) |
| | 102 | * Prerequisite hardware/site config |
| | 103 | * Install server: prefer Aquilon if mature enough. We don't want to attract new sites to SCDB. |
| | 104 | * Take control of a client (already installed): should include a basic configuration description that is as less intrusive as possible for the existing configuration |
| | 105 | * Mini-demonstration illustrating how to change some service configuration, for example ssh keys, account creations, add a RPM |
| | 106 | * Next steps |
| | 107 | * How to find docs and examples |
| | 108 | * Initial installation: AII/kickstart customization |
| | 109 | * Security |
| | 110 | * Customizing node configurations: common services and recipes |
| | 111 | * Document how to execute an arbitrary command with existing config modules like filecopy or metaconfig |
| | 112 | |
| | 113 | Put documentation on GitHub: start with a non public (review) section |
| | 114 | * Review how to improve the documentation structure on gitHub: see documentation discussion later during the workshop |
| | 115 | |
| | 116 | Documentation: activate robot indexing for Quattor wiki hosted at LAL |
| | 117 | |
| | 118 | Timeline |
| | 119 | * Getting Started done at next workshop (April 2014) |
| | 120 | * Next steps after |
| | 121 | |
| | 122 | Encourage adoption of new YUM-based ncm-spma: make it clear that YUM is used in a completely standard way and that people may/must refer to YUM docs for details on advance YUM management (like mirroring). |
| | 123 | |
| | 124 | |
| | 125 | === QWG Status - G. Philippon === |
| | 126 | |
| | 127 | Recent changes |
| | 128 | * No more release for more than 1 year |
| | 129 | * No update to branches: all changes in the trunk |
| | 130 | * standard/ almost stable: most things are in fact imported from other places |
| | 131 | |
| | 132 | Current trunk status |
| | 133 | * Partly based on Quattor 13.1: most components not yet updated (validation required) |
| | 134 | * Support SL5 and SL6 |
| | 135 | |
| | 136 | 3 different subsets shipped together |
| | 137 | * "Standard" templates |
| | 138 | * Provide a core node type without any grid dependency |
| | 139 | * Should be really standard: can it be the case for a Web server? |
| | 140 | * Grid templates |
| | 141 | * Templates generated from other Quattor components like AII or config modules |
| | 142 | |
| | 143 | StratusLab templates delivered separately (git repo) |
| | 144 | * Support both ncm-spma v2 and v3 |
| | 145 | |
| | 146 | Work in progress |
| | 147 | * Remove templates related other Quattor components from standard/ |
| | 148 | * Create a new namespace quattor/ with one sub-namespace per Quattor version: easier to move from one version to another one |
| | 149 | * YUM-based ncm-spma |
| | 150 | * Move to GitHub: do we keep the history? |
| | 151 | |
| | 152 | To be done but not yet handled by lack of time |
| | 153 | * Namespace structure of OS templates |
| | 154 | * Integration of Aquilon |
| | 155 | * NFS configuration independent of grid templates |
| | 156 | |
| | 157 | GitHub migration based on several repositories, no history kept |
| | 158 | * templ-library-standard: standard/ without the stuff imported from other places and without monitoring |
| | 159 | * monitoring not migrated |
| | 160 | * templ-library-core: templates imported from other Quattor components (config modules, AII, schema, Pan types...). Generated by the release process ideally, else some SCDB scripts may help (e.g. updateComponents) |
| | 161 | * master branch + 13.1 branch (ncm-spma v2) |
| | 162 | * Add standard/pan and standard/quattor other than AII |
| | 163 | * templ-library-grid: grid templates |
| | 164 | * 1 branch per major grid MW version |
| | 165 | * templ-library-stratuslab: current strastuslab repository |
| | 166 | * templ-library-examples: current clusters/ and sites in SVN |
| | 167 | * Minor issue: how to keep a "unified view" of these separate repositories for pushing back from a unique place like in the past |
| | 168 | * git submodule are not appropriate for this |
| | 169 | * git subtree: requires additional options when pushing but may be explored |
| | 170 | * Luis will try to find some examples |
| | 171 | |
| | 172 | === Core Quattor Schema === |
| | 173 | |
| | 174 | standard/pan and standard/quattor general templates were not migrated from SF SVN: need to be added to template-library-core |
| | 175 | |
| | 176 | Some suff added/changed for Aquilon: need to merge asap |
| | 177 | * Mostly additions but a few mods (network part in particular) |
| | 178 | |
| | 179 | |
| | 180 | == Actions == |
| | 181 | |
| | 182 | Documentation |
| | 183 | * Getting Started section on quattor.org |
| | 184 | * Allow indexing of Trac wiki by robots |
| | 185 | * Move to quattor.org parts of general interest on QWG wiki |
| | 186 | |
| | 187 | Configuration modules |
| | 188 | * Implement ncm-ncd hooks |
| | 189 | * Add support for component aliasing |
| | 190 | |
