[openstack-dev] [all] [tc] "No Open Core" in 2016

Amit Gandhi amit.gandhi at RACKSPACE.COM
Tue Feb 16 17:51:27 UTC 2016

OpenCDN is an abandoned project, although there have been a few attempts at creating one called “OpenCDN”.

As far as the we can tell (Poppy Team), there is currently no viable Open source CDN’s available.  If there is we would be happy to add it as a supported driver.

Also, even if the CDN software itself was open, the true value of a CDN comes from the distributed global network of servers it offers and its performance to serve requests.  Not just the features/API offered.

Poppy intends to be an abstraction API over the various CDNs available.  We do not want to be in the business of building a CDN itself.


On Feb 16, 2016, at 12:22 PM, Doug Hellmann <doug at doughellmann.com<mailto:doug at doughellmann.com>> wrote:

Excerpts from Sean M. Collins's message of 2016-02-16 07:15:34 +0000:
Thomas Goirand wrote:
Oh, that, and ... not using CassandraDB. And yes, this thread is a good
place to have this topic. I'm not sure who replied to me this thread
wasn't the place to discuss it: I respectfully disagree, since it's
another major blocker, IMO as important, if not more, as using a free
software CDN solution.

Let's handle the policy implications discussed in this thread before we
dive into the "don't use this component that I dislike" bikeshed.
Reading the thread, it appears that we've made good progress on building
consensus towards having Poppy consider an open source CDN as the
"reference implementation" (to use some Neutron parlance).

Then we can bikeshed about how good/bad the components used in the
reference implementation are. Later. The point being, there is an open
source solution that will be used to flesh out a true vendor-neutral API
(as I understand Mike Perez's position, and agree with!).

Is there? I thought the point was OpenCDN isn't actually usable. Maybe
someone from the Poppy team can provide more details about that.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160216/72361ea1/attachment.html>

More information about the OpenStack-dev mailing list