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

Fox, Kevin M Kevin.Fox at pnnl.gov
Wed Feb 17 18:41:40 UTC 2016

You should be able to test that the functionality of using the api, and seeing an appropriate plugin call gets called without a proprietary back end. Then its up to each plugin to test for their own compliance to the reference.

Another approach for testing, maybe you could create the "dead simple cdn" that basically just uploads stuff to the local swift? Its not much of a cdn, but you may not need more then that. For my cloud, that amount of "cdn" would be enough in a lot of cases.

From: Jay Pipes [jaypipes at gmail.com]
Sent: Wednesday, February 17, 2016 10:20 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 02/17/2016 09:30 AM, Doug Hellmann wrote:
> Excerpts from Mike Perez's message of 2016-02-17 03:21:51 -0800:
>> On 02/16/2016 11:30 AM, Doug Hellmann wrote:
>>> So I think the project team is doing everything we've asked.  We
>>> changed our policies around new projects to emphasize the social
>>> aspects of projects, and community interactions. Telling a bunch
>>> of folks that they "are not OpenStack" even though they follow those
>>> policies is rather distressing.  I think we should be looking for
>>> ways to say "yes" to new projects, rather than "no."
>> My disagreements with accepting Poppy has been around testing, so let me
>> reiterate what I've already said in this thread.
>> The governance currently states that under Open Development "The project
>> has core reviewers and adopts a test-driven gate in the OpenStack
>> infrastructure for changes" [1].
>> If we don't have a solution like OpenCDN, Poppy has to adopt a reference
>> implementation that is a commercial entity, and infra has to also be
>> dependent on it. I get Infra is already dependent on public cloud
>> donations, but if we start opening the door to allow projects to bring
>> in those commercial dependencies, that's not good.
> Only Poppy's test suite would rely on that, though, right? And other
> projects can choose whether to co-gate with Poppy or not. So I don't see
> how this limitation has an effect on anyone other than the Poppy team.

But what would really be tested in Poppy without any commercial CDN
vendor? Nothing functional, right? I believe the fact that Poppy cannot
be functionally tested in the OpenStack CI gate basically disqualifies
it from being "in OpenStack".


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

More information about the OpenStack-dev mailing list