At 09:36 31/3/01 +0200, Leo Simons wrote: >So, the process to follow as I envision it would be: > >1 - get Enhydra running, compare jmx impl to reference impl >2 - if we choose Enhydra, extract jmx code from it >3 - look into license issues (I don't expect difficulties) enhydra is MPLed which is fine for us to use. >4 - redesign kernel to prepare for jmx (especially Main.class, probably) >5 - use dynamic MBeans/model MBeans/std mbeans/custom solution to > implement Phoenix's services as MBeans. >6 - write custom adapter (avalon-based using RMI, probably) >7 - write management app to talk to adapter (either java program or >servlet-based) excellent! /me does my best impression of Mr Burns >long-term: >8 - create our own jmx impl egads ! you are keen ;) >9 - design authentication scheme for allowing access to adapter > >I'd like any and all suggestions for #4-7, as well as help actually >implementing all this stuff. If you want help cleaning/understanding the kernel then I am your man ;) >Harmeet, I'm guessing you'd be most >productive helping out with the kernel design. So draw up some >schematics, if you want ;-) one thing I would like to see is that is that some of this is implemented in user-space (ie as a .sar). The closest thing I guess is the way syslog works under many unixes. In many cases there is a kernel module that redirects kernel logging (and sometimes logging originating in libc) to a file and/or user-level process. The user level process (ie syslogd) would then do with it as it wills. In terms of Phoenix I would love to see the agent/distributor/entry-point as a sar but the core access-points provided by the kernel somehow. That way we could theoretically have multiple management apps or none at all or any other combination ;) Thoughts? >Oh, comments on the route to follow welcome as well =) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
