On 09/14/2014 12:27 AM, Boris Pavlovic wrote: > Michael, > > I am so glad that you started this topic. > I really like idea of of taking a pause with features and concentrating > on improvement of current code base. > > Even if the >1 k open bugs https://bugs.launchpad.net/nova are vital > issue, there are other things that could be addressed to improve Nova > team throughput. > > Like it was said in another thread: "Nova code is current too big and > complex to be understand by one person". > It produces 2 issues: > A) There is hard to find person who can observer full project and make > global architecture decisions including work on cross projects interactions > (So project doesn't have straight direction of development) > B) It's really hard to find cores, and current cores are under too heavy > load (because of project complexity) > > I believe that whole current Nova functionality can be implemented in > much simpler manner.
Just a brief comment on the sentence above. This is a common thing to hear from coders, and is very rarely rooted in reality IMHO. Nova does _a lot_ of things. Saying that given an exhaustive list of features it has, we can implement them in a much simpler manner is completely disregarding all the complexity of building software that works within real world constraints. > Basically, complexity was added during the process of adding a lot of > features for years, that didn't perfectly fit to architecture of Nova. > And there wasn't much work on refactoring the architecture to cleanup > these features. > I agree with this of course - fixing architectural flaws is important and needs to be an ongoing part of the process, as I mention in my other mail to the thread. Halting all other development is not the way to do it though. N. > So maybe it's proper time to think about "what", "why" and "how" we are > doing. > That will allows us to find simpler solutions for current functionality. > > > Best regards, > Boris Pavlovic > > > On Sun, Sep 14, 2014 at 1:07 AM, Michael Still <mi...@stillhq.com > <mailto:mi...@stillhq.com>> wrote: > > Just an observation from the last week or so... > > The biggest problem nova faces at the moment isn't code review > latency. Our biggest problem is failing to fix our bugs so that the > gate is reliable. The number of rechecks we've done in the last week > to try and land code is truly startling. > > I know that some people are focused by their employers on feature > work, but those features aren't going to land in a world in which we > have to hand walk everything through the gate. > > Michael > > > -- > Rackspace Australia > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > <mailto:OpenStack-dev@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev