Changes between Version 7 and Version 8 of Meetings/Workshops/20081027

Timestamp:

Oct 29, 2008, 11:53:49 AM (17 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Meetings/Workshops/20081027

@@ -594 +594 @@
 
 Mailing lists, issue trackers: not investigated yet
- * Any need to migrate from CERN Savanah ?
+ * Any need to migrate from CERN savannah ?
 
 Forums: not investigated yet, are they useful for us?
@@ -601 +601 @@
  * Try to redirect to wiki
  
+
+=== Migration Status - S. Childs ===
+
+First prototype based on an import from CVS of the agreed components from CVS with cvs2svn
+ * First version of SVN-ready quattor build tools
+ * trunk, tags, branches at the top level
+
+Quattor build tools: 1 copy per "core component" (through svn:externals)
+ * ncm-components must be treated specifically to avoid one copy per component: they are considered as 1 Quattor component
+ * Proposal:
+   * 1 copy for all components
+   * Tagging per component, with a 'stable' release
+   * tags/ncm-components/stable containing an svn:externals to each individual component release
+
+Tags:
+ * Same hierarchy as under trunk
+ * tags/ncm-components must contain an external reference to  quattor build tools
+ * Global release tags must be defined under tags/ with a reference (either a branch copy or svn:externals) to all individual component versions part of the release
+
+Action plan: '''open new repository Dec. 1st'''
+ 1. Implement new agreed structure, modify build tools to handle it
+ 1. Test new structure
+ 1. Set CVS readonly
+ 1. Reexport CVS
+
+Issue tracker, mailing lists... discussed at next workshop
+ * panc will use the bug tracker as soon as it is mooved
+
+Need also to work on backup of what is in SF as there is no backup provided.
+ * 1 unique backup solution for SVN , wiki... ?
+ * SVN mirrored with svnk ?
+
+=== QWG Migration ===
+
+In principle agreement to move sources to SF
+ * SCDB can be moved as soon as SF is "stable" and backuped
+ * QWG templates: more difficult because of the cross-reference from TracWiki relying on SVN Python API that doesn't support non local references (Trac and SVN server must run on same machine)
+
+Need to gain more experience with SF wiki to decide if it is worth migrating the documentation.
+
+
+== Quattor Releases ==
+
+=== Release Status - ME Poleggi ===
+
+[http://indico.cern.ch/materialDisplay.py?contribId=25&sessionId=2&materialId=slides&confId=40056 Slides].
+
+1.4-1 underway
+ * Still to fix CDB issue with panc v8
+ * SL3 not supported anymore
+
+1.4-2 or 1.5 will support SL5
+
+Release are still important for starters... would like to continue providing a semestrial release.
+ * But ME contract is ending in a few months...
+ * Is it really worth the effort ? Probably a Quattor appliance would be more useful... Lets do 1.4-1 and revisit global releases later.
+
+
+=== Build Process and Tools - S. Childs ===
+
+[http://indico.cern.ch/materialDisplay.py?contribId=26&sessionId=2&materialId=slides&confId=40056 Slides].
+
+We need automatic builds to provide a public SW repository, in particular for ncm-components
+ * May also ease release process
+ * SourceForge doesn't provide any build facilities 
+
+Experience with ETICS during the last year: it works but client is awkard and unstable
+ * Is it work to stick with it ?
+ * What other alternative (Cruise?) ? Who can host it ?
+   * LAL could rebuild all components in its RPM repository and provide them with a YUM repository
+   * LAPP is also proposing to do it, as its contribution to Quattor
+
+Building documentation: documentation and status page must be derived from the code. '''Solutions requiring editing a wiki will not work.'''
+ * For ncm-components, gencompswebdoc was developped to extract documentation for components
+ * Need to be run regularly
+
+
+== Open Bug Review ==
+
+We should do it before the meeting...
+
+
+== Action Summary ==
+
+== Decisions ==
+ * Structure of code in SF finalised:
+   * quattor-build-tools referenced as externals at the root of every "product" (where all ncm-components are treated as a single product)
+   * requires build tools to be updated for components within tags (to dynamically work out how far back up the tree the build tools are)
+{{{
+quattor-build-tools
+trunk/ccm/qbt
+trunk/ncm-components/qbt
+trunk/ncm-components/ncm-*
+
+tags/ccm/stable/qbt
+        /a.a.a/qbt
+    /ncm-components/qbt
+    /ncm-components/ncm-accounts/a.a.b/
+}}}
+ * CERN CVS to be set as read-only on Dec. 1st 2008
+
+
+== Actions ==
+
+=== Stephen Childs === 
+ * Check in AII web interface 
+ * Integrate Grid-Ireland site/cluster hierarchy for SCDB 
+ * Make sure TCD monitoring additions are checked in to QWG and documented (in particular conversion of lists of machine classes to nagios hostgroups)
+ * Check in code for QuatView
+ * Revisit checkdeps to try and get it working with SL4
+  * Investigate potential enhancements to YUM
+ * Put tools inventory on wiki
+
+=== Morgan Stanley === 
+ * Check in patches for AII (via Luis) 
+ * Check in patches to components (once SF migration complete) 
+ * Report on ease of use of cdb2sql (and compatibility with different sql implementations)
+
+=== MEP ===
+ * Finish quattor release 1.4
+ * Update quattor build tools 
+
+=== Luis ===
+ * Extend coding conventions page with all code snippets (and move to SF wiki?)
+ * Provide OpenVZ image for quattor server
+ * Provide cut-down rpmlist for grid nodes?
+
+=== LAPP/LAL ===
+ * Set up nightly build system for quattor components 
+
+=== All === 
+ * Review component writing howto -- recommend gettree method
+  * Include list of files modified by a component
+ * Analyse components to make it easier to start: common boilerplate
+ * Need volunteer(s) to set up and host back up for content and code on SourceForge:
+  * SVN
+  * wiki
+  * other ...?
+
+== Wrap-up ==
+
+Next meeting to be held in London (Morgan & Stanley), March 11-13, 2009.