[openstack-dev] [all] Embracing new languages in OpenStack

Thierry Carrez thierry at openstack.org
Fri Nov 11 12:42:55 UTC 2016

Pete Zaitcev wrote:
> I'm disappointed that TC voted Golang
> down on August 2, but I can see where they come from.
> The problem we're grappling with on the Swift side is (in my view) mainly
> that the Go reimplementation provides essential performance advantages
> which manifest at a certain scale (around 100 PB with current technology).
> For this reason, ignoring Hummingbird and prohibiting Go is not going to
> suppress them. As the operators deploy Hummingbird in preference to the
> Python implementation, the focus of the development is going to migrate,
> and the end result is going to be an effective exile of a founding
> project from the OpenStack.

Yes, and those same performance advantages are why so many people (yes,
including TC members) are uncomfortable with the current state. There is
no question (I think) that Swift would benefit from being able to
include Go-rewritten parts. We just need to make sure that what is a
benefit for Swift doesn't turn out to be a disaster for "OpenStack".

This is in my opinion the real reason for the "not yet" answer that was
given so far -- lack of visibility into what a Go-enabled OpenStack
would look like in the future. The clearer we are with what that future
would look like (not just for Swift for for "OpenStack" as a whole), and
the more people we have lined up to do the necessary work to turn that
specific case into a general success, the more likely it is that a
majority of TC members (who have "OpenStack" interests at heart beyond
any specific project) will support that addition to our toolbelt.

Thierry Carrez (ttx)

More information about the OpenStack-dev mailing list