On 11/20/2013 02:06 AM, Boris Pavlovic wrote:
I faced some social problems in community.
We started working on purge engine for DB (before HK summit)
This is very important, because at this moment we don't have any working
way to purge DB... so admins should make it by hand.
And we made this BP (in october)
https://blueprints.launchpad.net/nova/+spec/db-purge-engine
And made patch that makes this work.
But only because our BP wasn't approved we got -2 from Joe Gordon.
(https://review.openstack.org/#/c/51523/ ) And there was long discussion
to remove this -2.
And now after summit David Ripton made the similar BP (probably he
didn't know):
https://blueprints.launchpad.net/nova/+spec/db-purge2
That is already approved by Joe Gordon. (that already know that we are
working on same problem)
Why?
(btw question about Purge Engine was raised by me on the summit and
community accepted that)
I discussed this with Boris on IRC yesterday. When I volunteered to
write a DB purger at Summit, I wasn't aware that there was already one
actively in progress. (So many patches around the end of Havana.) When
I went to file a blueprint and noticed the existing db-purge blueprint,
I saw that its patch had been -2'd and figured it was dead. But as long
as Boris is working to actively improve that patch (he's on vacation now
but said he'd probably have something on Monday), I won't submit a patch
for the competing blueprint. Instead, I'll work to make sure Boris's
code meets everyone's requirements (some that I got from Joe Gordon and
Phil Day are mentioned in db-purge2), and when it does I'll withdraw the
db-purge2 blueprint and retarget remove-db-archiving to depend on
Boris's blueprint instead.
--
David Ripton Red Hat drip...@redhat.com
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
