On Tue, Jul 28, 2009 at 02:08:45PM +0200, Michael Hanselmann wrote: > > 2009/7/28 Iustin Pop <[email protected]>: > > On Tue, Jul 28, 2009 at 11:35:47AM +0200, Michael Hanselmann wrote: > >> Let me modify my proposal slightly: How about per-daemon namespaces > >> for code specific to a daemon? “backend” could go to > >> ganeti.noded.backend, “cmdlib”, “config” and “locking” to > >> ganeti.masterd.* (didn't check those in all details, it may not work). > >> Usually only a small part of the code is shared and could go into a > >> generic module (ganeti.*). > > > > Sounds good. I'll ask again though: how is better than simply > > documenting this split? > > It reduces the noise level in ganeti.* a bit and increases code > modularization. Of course documentation is good, but it easily gets > out of date (as opposed to realizing something isn't right when you > start importing noded code into masterd).
Sounds good then :) iustin
