[OpenStack-DefCore] Identifying and defining missing/new tests for capabilities :Was Image APIs in Glance and Nova
Monty Taylor
mordred at inaugust.com
Thu Jun 18 15:31:40 UTC 2015
On 06/18/2015 11:03 AM, Chris Hoge wrote:
>
>> On Jun 18, 2015, at 7:48 AM, Rob Hirschfeld <rob at zehicle.com> wrote:
>>
>> On 06/18/2015 07:43 AM, Monty Taylor wrote:
>>> ... bit of a step from being reflective towards influencing what folks _Should_ be doing. Agree - excellent topic fo mid-cycle.
>>
>> From an interop perspective, it's part of our charter. Some API differences are reasonable to absorb but we need to find a way to get ahead of the current sprawl and drive it back towards convergence. The goal of DefCore was to create carrots and sticks.
>
> We need to be willing and able to use the sticks. I truly don’t mind a cloud
> provider implementing proprietary or non-standard extensions, but I do
> mind calling that cloud OpenStack if it doesn’t play well with others.
Agree - as long as the proprietary or non-standard extensions don't
break or supplant the openstack bits. Like, the special rackspace auth
plugin thing is FINE with me because I do not have to use it - standard
upstream password auth works perfect well. I think this is an
_excellent_ example of the right way to go about differences.
More information about the Defcore-committee
mailing list