Changes between Version 58 and Version 59 of Development/Scrum
- Timestamp:
- Oct 14, 2011, 3:15:17 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Development/Scrum
v58 v59 17 17 || 2010-01 || 03/02/2011 || [/wiki/Development/Scrum/Sprint-201102] || 18 18 19 This page contains the Quattor backlog. It reflects the state of the backlog at the beginning of the current sprint, ''with all items moved to the sprint backlog removed''. Each section describes the backlog for a specific part of the Quattor toolkit. 19 This page contains the Quattor backlog. It reflects the state of the backlog at the beginning of the current sprint, ''with all items moved to the sprint backlog removed''. Each section describes the backlog for a specific part of the Quattor toolkit. '''The contents should not be interpreted as a commitment to implement the listed features.''' 20 20 21 21 … … 42 42 * Use of new build tools for other toolkit components (probably 1 by 1) 43 43 44 == Pan Compiler == 45 46 * Function to dump all defined global variables at a specific point to help debugging. Like `debug()` function, should do nothing if the appropriate option is not passed to the compiler. An optional argument may restrict the name of the variables dumped, with a regexp on the name (if feasible). 47 * Add ability with a compiler option to get a message printed everytime a template is included with an information display wheter it has been executed or skipped because it had the `unique` tag and was previously executed. 48 * Would be great if it worked also with structure templates... 49 44 50 == Configuration Modules == 45 51 52 * [ticket:249 ncm-network full rewrite] 53 * See [/wiki/Meetings/Workshops/20111011#NetworkConfig discussion] during Strasbourg workshop 46 54 * ncm-dpmlfc 47 55 * [ticket:254 New schema using nlist rather than list (key=hostname) for service host lists]: this is required to simplify checks wheter an entry already exists. This change will not be backword compatible at the template level but the component may support both old and new schema. 56 * Allow writing components in Python 57 * See [/wiki/Meetings/Workshops/20111011#CompPython discussion] during Strasbourg workshop 58 * First step could be a proof of concept using Python APIs developped for QuattorFS 48 59 49 60 == Package Deployment ==