Open Stack

> >> However, I'm not sure how people would feel about having both
> >> openstack.common.exception and nova.exception in the tree since they
> >> overlap quite a bit.  I like being able to do work in pieces, but
> >> having them both in the tree leaves the code in an odd state, so we
> >> need some end goal in mind.
> >
> > I'm not a huge fan of openstack.common.exception
> 
> Yeah, I don't see too much value in having everything inherit from a common
> exception base class. I think the different projects will typically want to
> customize the error message text...

My vote would be to have some handy mix-ins in openstack.common, if that works for everyone