On 9 July 2014 12:53, Daniel P. Berrange <berra...@redhat.com> wrote: > This is yet another example of the many problems inherant in the cut+paste > approach used by olso incubator. I'd personally like to see olso-incubator > killed and everything there moved into its own module with whatever API > they have now. If we later find we need to break the APIs of some of the > split out modules, so be it. IMHO it would be less pain overall than we > have with the cut+paste approach. We'd be able to have fully integrated > CI testing running against the olso changes as they go on, rather than > only after copy+paste, whic would ease detection/avoid problems like you're > highlighting here.
CI wouldn't pick up this issue though, it is only noticeable via manual inspection. As a library it would be even more of a pain, since projects get the breakage and have no way of fixing it.... at least now we can back out the last sync until it is fixed. Some better automated testing can help here, but it is a long and boring job to pick up and do a good job of. TBH I'm not sure what value e.g. Cinder gets from OSLO logging - our logging requirements haven't significantly changed since almost day 1, except for a few taskflow integration bits - we'd do better froma stability point of view to ignore OSLO all together and do our own thing. -- Duncan Thomas _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
