Author: Martin Kirk
Modification Date:
15/06/06 18:01
Martin Kirk
Martine Wedlake
Art Colvig
Karl Schopmeyer
Krishna Harati
Mike Brasher
Abhishek Kar (Shaq)
Hope Hines
Larry Lamers
1. Discussion
Karl explained that a bunch of Pegasus bugs have been file to refactor some areas of the code which will probably be committed in the next couple of weeks. This should reduce the static footprint by around 50%.
Discussion of PEP#253 comments.
Memory manager - discussed how this might work and what it might actually do. Mike suggested that it could monitor memory usage based on a low and high water mark. Exceeding the lwm would restrict further memory allocation, and exceeding the hwm would cause drastic action. The manager could keep a stock of memory in reserve for special purposes. Other suggestions were discussed.
Need input on what people regard as optional or non-use functionality in their environment so that we can get a better handle on optionality. Also need to understand what short of options we are talking about - compile time, run-time, etc.
What sort of admin is going to be performed in the embedded environment. Does the CIM server need to be able to be stopped and started independently? Does it need to be reconfigurable? Does it need to generate statistics? Does it need to support multiple users and authenticate them, or does it have a single hard-wired super-user? Art reported that they had had to remove a load of code to do just that.
Would be nice to have a better restart capability. At present people have to cheat.
Several people have utilities that they have developed to do some of these things. Karl pointed out that they could be added to the pegasus-unsupported cvs tree and made generally available.
Thursday June 28th, 2006 - 1200EDT