Excerpts from Michael Still's message of 2017-09-20 10:25:17 -0600: > Dims, I'm not sure that's actually possible though. Many of these files > have been through rewrites and developed over a large number of years. > Listing all authors isn't practical. > > Given the horse has bolted on forking these files, I feel like a comment > acknowledging the original source file is probably sufficient. > > What is concerning to me is that some of these files are part of the "ABI" > of nova, and if mogan diverges from that then I think we're going to see > user complaints in the future. Specifically configdrive, and metadata seem > like examples of this. I don't want to see us end up in another "managed > cut and paste" like early oslo where nova continues to develop these and > mogan doesn't notice the changes. > > I'm not sure how we resolve that. One option would be to refactor these > files into a shared library. >
Agreed 100%. It would be better to have something completely different than something that works 97% the same but constantly skews. Luckily, since these things are part of the ABI of Nova, they are versioned in many cases, and in all have a well defined interfaces on one side. Seems like it should be relatively straight forward to wrap the other side of them and call it a library. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
