Changes between Initial Version and Version 1 of Meetings/Workshops/20130306


Ignore:
Timestamp:
Mar 6, 2013, 5:10:48 PM (13 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Meetings/Workshops/20130306

    v1 v1  
     1= 15th Quattor Workshop - Bordeaux - 6-8/3/2013 =
     2[[TracNav]]
     3
     4[[TOC(inline)]]
     5
     6== Update since last workshop ==
     7
     82 releases made: who use them?
     9 * Probably no site using them yet...
     10 
     11New ncm-spma is production ready: need to be tested
     12
     13panc v10 released.
     14
     15QWG
     16 * grid templates: continued support, up-to-date with last MW versions
     17   * Mostly done by Guillaume and Jerome
     18   * Migration to GitHub still to be done
     19 * StratusLab templates: available for new versions of the MW but insufficiently sync with GitHub
     20   * Discuss with Guillaume (main maintainer) a more regular contribution to GitHub: use branches if necessary
     21
     22Aquilon
     23 * Packaging still in progress: 2 repositories, mainly done at UGent and RAL
     24 * RAL is already using it to manage the cloud machines and some other test machines
     25   * Still trying to figure out how to migrate the QWG machine types and database related things
     26 
     27Dashboard
     28 * Still working on it: indexing added
     29   * Requires Python 2.7
     30 * `datawharehouse` repo on GitHub
     31
     32Solaris port working at MS
     33 * Solaris 11
     34 * Based on a fork made 1 year ago
     35   * Main changes are in network config and cron
     36   * No package management yet: everything installed from AFS before running components
     37   * Would like to merge back to the mainstream Quattor
     38
     39QRD/QRC
     40 * New QRD available and used at MS. Hope to publish it in one month.
     41   * VMWare (MS specific) and NetApp
     42   * Python
     43 * Would like to do the NetApp management through QRD this year
     44   * Currently, only used at initial installation
     45 * Also plans for switches
     46
     47Quattor FS
     48 * A few bug fixes and enhancements
     49 
     50JSON profiles
     51 * Smaller, no need to escape
     52 
     53SCDB
     54 * Pb with last scdb-ant-utils: changes related to JSON support?
     55 * Try to work on it during the workshop
     56 
     57ncm-network
     58 * Not part of the release
     59 * Need to clarify status/future
     60 * Check with Loic the status of the rewrite
     61 
     62
     63== Pan Compiler Status and Roadmap ==
     64
     65v10.0 released
     66 * Old, deprecated features are all removed
     67   * Session-related features removed (used only at CERN)
     68 * Streamline, consistent options across CLI, Maven and Ant tasks
     69 * Significant parts in clojure
     70 * Speed: 13% in real time but 11% faster in CPU...
     71   * Probably unoptimal handling of disk I/O: to be investigated
     72 * Not a drop-in replacement for 9.x due to the option changes
     73   * Need to ocordinate with a new release of SCDB (changes in quattor.build.xml) for SCDB users
     74 
     75v9.2 and 9.3 in maintenance mode
     76 * Only serious bugs will be fixed
     77 
     78v10 roadmap
     79 * Performance improvements
     80 * Internal simplification for maintenance
     81 * Flag for turning off escaping: if turned off, escape()/unescape() will be there but do nothing
     82   * Coordinate with CCM
     83
     84Discussion
     85 * Other wishes
     86   * Rename `nlist` into `dict`: will be first done as an alias
     87   * `if_exists` for files to be used with `file_contents`
     88   * Print template name as part of debug function
     89 * Looking at possibilities for // compile
     90   * Cal interested to see new people working on the compiler... but require a minimum amount of time to get used to the compiler
     91
     92
     93== ncm-spma v3 ==
     94
     95Part of Quattor release since 13.02 but one important bug fixed in 13.03
     96 * Do not upgrade if you are not happy with the concept presented!
     97 * In production at U-Gent: happy with it
     98   * both SL5 and SL6
     99 * Tests started at RAL and GRIF
     100
     101Preserved features
     102 * Ability to fix versions
     103 * All changes in one transaction
     104 * Use of proxies possible
     105   * Need to document recommended setting, in particular for repo metadata
     106 
     107Last AII version only capable of using YUM
     108
     109SL5 support ready, including initial installation
     110 * Requires a YUM upgade: RPMs availabe at U-Gent
     111 
     112If not caring about a specific version, a package in the configuration can be just an empty nlist()
     113
     114Before upgrading
     115 * Refactor the repositories to be sure they mirror the upstream repos
     116   * Do not throw random RPMs in upstream mirrors else risk of conflict
     117 * Use separate repo for local RPMs
     118 * Use one repo for each Quattor version
     119 
     120Repository hell/nightmare
     121 * RPMfore is evil: many conflicting RPMs with SL ones
     122 * Same for JPackage
     123 * Use `include_pkgs` in the repository definition to restrict the packages that are considered in them
     124 
     125Conflicts hell
     126 * YUM's obsoletes causing a lot of conflicts if there is an explicit RPM in the profile that is obsoleted.
     127   * By default ncm-spma disable YUM obsoletes
     128   * Exemple: perl-Compress-Lib required by ccm
     129 * Real fix/cleanup is to remove explicit specification of dependencies that are not controlled by Quattor
     130 * Another issue arises if a package is not specified with a specific version but one of its subpackage is
     131   * Eg. python without an explicit version but python-libs with one: clean up pan description
     132 
     133Repo priority hell
     134 * If there is an explicit version required which is in a repo with a lower priority than another repo containing another version, YUM will not install the package and SPMA will fails
     135 * Advice: do not use priority except for very specific cases
     136 
     137Snapshotting the repos is mandatory to avoid unexpected updates
     138 * Moving from one snapshot to the other can be done either at the file system level (symlinks) or in the template defining the URL for the repo
     139   * URL can be build from a snapshod_id using the format() function
     140   
     141Future directions
     142 * Remove backward compatibility (repository resolution) to improve compile time (30% saving)
     143 * Allow for RPM signatures
     144 * Support for the YUM fs-snapshot plugin: ability for YUM to do a snapshots of main filesystems before making any modification, allowing easier rollback
     145   * No experience yet
     146   
     147SCDB
     148 * needs to reenable the recompile of profile if there is a change in a repo template
     149   * Change in the URL as part of the template handling, change in include_pkgs
     150 * Improve update.rep.templates to handle properly `include_pkgs`
     151 
     152Discussion
     153 * Rollback: doesn't guarantee a roll back to the exact previous state as only explicit versions will be rollback
     154 * Not clear that when there is a set of explicit package (eg. main package, -lib, -devel...), only specifying the version for one of them is sufficient
     155 * `/etc/spma.conf` is not used anymore. Only `userpkgs` is still taken into account by `ncm-spma` if defined in the profile
     156 * New quattor releases can be used with the old ncm-spma
     157
     158== Aquilon ==
     159
     160Agreement received from MS legal department to release it under an Apache2 license
     161 * Need to figure out how to integrate features MS specifics as separate part
     162
     163Seems that MS should be able to contribute directly to GitHub in the future but not immediately
     164
     165Working on entitlement: reduce entitlement to change some particular parameters
     166 * Declaration of parameters than can be changed from outside: will not protect against misusage/mistake of people with direct access to the templates
     167 
     168Integration with Active Directory Kerberos: working at RAL
     169 * Just the matter of creating the keytab from AD
     170 
     171Test instances outside MS: RAL and U-Gent
     172
     173Start an aquilon book.
     174 * Cal agrees to setup a vanilla book based on pan docs
     175   * Docbook (XML): requires an appropriate editor, one free exists
     176 * Where to put it as there is no file service in GitHub
     177   * Check if we could put it in stratuslab-srv1 and try to automate generation from Maven?
     178   * Keep using Source Forge?
     179 * Any possibility to generate it in markdown format?
     180   * According to Luis a plugin should exist
     181
     182Packaging: handled by Luis, hope to have an RPM ready by the summer
     183
     184Web interface (from appliance): works at RAL (with a few mods)
     185 * Add it to the Aquilon packages as an optional component
     186
     187
     188