> I don't think that code should be added to Nova that depends on half-baked projects.
Agree that Nova *core* should only depend on stable/mature projects. For extensions, I think we can relax those requirements and allow much more flexibility and freedom to experiment.
The problem as it stand now, though, is that Nova doesn't really have a notion of a completely optional extension. As Nova goes to production and we start integrating it with more and more custom systems, I think we're going to need to really think hard about how to do Nova extensions right, from a packaging, unit-test, and virt/compute/api layer perspective.
Perhaps we can get this discussion started at the Essex design summit?
blamar: Good points; I'll fix those up shortly.
jaypipes:
> I don't think that code should be added to Nova that depends on half-baked projects.
Agree that Nova *core* should only depend on stable/mature projects. For extensions, I think we can relax those requirements and allow much more flexibility and freedom to experiment.
The problem as it stand now, though, is that Nova doesn't really have a notion of a completely optional extension. As Nova goes to production and we start integrating it with more and more custom systems, I think we're going to need to really think hard about how to do Nova extensions right, from a packaging, unit-test, and virt/compute/api layer perspective.
Perhaps we can get this discussion started at the Essex design summit?