On Mon, Feb 02, 2015 at 07:44:24AM -0800, Dan Smith wrote:
> > I'm with Daniel on that one. We shouldn't "deprecate" until we are 100%
> > sure that the replacement is up to the task and that strategy is solid.
> My problem with this is: If there wasn't a stackforge project, what
> would we do? Nova's in-tree EC2 support has been rotting for years now,
> and despite several rallies for developers, no real progress has been
> made to rescue it. I don't think that it's reasonable to say that if
> there wasn't a stackforge project we'd just have to suck it up and
> magically produce the developers to work on EC2; it's clear that's not
> going to happen.

I think that is exactly what we'd would have todo. We exist as a project
to serve the needs of our users and it seems pretty clear from the survey
results that users are deploying the EC2 impl in significant numbers,
so to just remove it would essentially be ignoring what our users want
from the project. If we're saying it is reasonable to ignore what our
users want, then this project is frankly doomed.

> Thus, it seems to me that we need to communicate that our EC2 support is
> going away. Hopefully the stackforge project will be at a point to
> support users that want to keep the functionality. However, the fate of
> our in-tree support seems clear regardless of how that turns out.

If the external EC2 support doesn't work out for whatever reason, then
I don't think the fate of the in-tree support is at all clear. I think
it would have a very strong case for continuing to exist.

|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to