Hi Stackers,

Intro:
It goes without saying words that we have the same code in different
projects: RPC, DB, Python clients, and a lot of other parts. In case of
fast growing OpenStack there were some issues in evolving and instead of
doing libs and new projects from the blank page on top of these libs. We
build new projects as a fork of already existing, removing unnecessary
code. During the time "same" code in different projects evolve in different
directions and now it is not "same". At this moment we have a lot of code
that makes same things in different projects. To assume we are spending too
much time for supporting and improving "same" code in different projects.

Ideal variant to resolve such problem is to create a lot of libs for every
logical piece of code. But it's well known that every change in API of lib
produce new version of it. Oslo-incubator initiative was started to avoid
versioning armageddon:
1) put all code to oslo incubator
2) reuse it in all projects
3) make a libs
4) switch to libs
5) ...
6) PROFIT!!

To put it in nutshell:
1) It is okay if you are not able to sync code from Oslo without any
changes in your project. (That's the main idea of Oslo-incubator be free to
change API)
2) Avoid syncing randomly code from Oslo if you are not related to it
(cause it probably have some changes in API or internal parts that could
probably brake something that won't be catch even by gates).
3) If you would like to sync and help Oslo team, contact please
 maintainers (they will help you):
https://github.com/openstack/oslo-incubator/blob/master/MAINTAINERS
4) Please PTL could you make high priority for reviews for syncs from oslo
(cause it is the major bottleneck for oslo team)
5) Do not make reverts for patches if they don't pass your gates like here:
https://review.openstack.org/#/c/76718/

So Doug could you please merge our revert to revert:
https://review.openstack.org/#/c/76836/

And we will sync it to nova:
https://review.openstack.org/#/c/76880/


Best regards,
Boris Pavlovic
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to