On 20/01/17 01:40, Mike Perez wrote:
> On 17:38 Jan 18, Morales, Victor wrote:
>> Just a FYI, Ankur have been working on have a Feature Classification Matrix
>> in Neutron[1] which collects some of this information
>>
>> [1] https://review.openstack.org/#/c/318192/
>
> I actually didn't know Nova
: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 16/01/2017 21:56
Subject: Re: [openstack-dev] [all] Improving Vendor Driver
Discoverability
On 01/16/2017 12:19 PM, Jonathan Bryce wrote:
On Jan 16, 2017, at
Mike,
Similar the evil driver support matrix that Cinder has had forever [1].
So, there is a precedent and this looks like it would be better than
something that has to be manually updated.
No initial objections. :-)
Jay
[1] https://wiki.openstack.org/wiki/CinderSupportMatrix
On
On 2017-01-19 17:37:13 -0800 (-0800), Mike Perez wrote:
> I actually didn't know Nova also generated this with a script and
> ini file. Perhaps this would be a better approach than a giant
> JSON file like driver log is today. I could then have the
> marketplace parse these ini files using the
On 17:38 Jan 18, Morales, Victor wrote:
> Just a FYI, Ankur have been working on have a Feature Classification Matrix
> in Neutron[1] which collects some of this information
>
> [1] https://review.openstack.org/#/c/318192/
I actually didn't know Nova also generated this with a script and ini
Just a FYI, Ankur have been working on have a Feature Classification Matrix in
Neutron[1] which collects some of this information
[1] https://review.openstack.org/#/c/318192/
Regards/Saludos
Victor Morales
Irc: electrocucaracha
On 1/13/17, 10:29 PM, "Mike Perez" wrote:
g List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 16/01/2017 21:56
Subject: Re: [openstack-dev] [all] Improving Vendor Driver
Discoverability
On 01/16/2017 12:19 PM, Jonathan Bryce wrote:
>> On Jan 16, 2017, at 11:58 AM, Jay S. Bryant
<jsbry...
On 01/16/2017 12:19 PM, Jonathan Bryce wrote:
On Jan 16, 2017, at 11:58 AM, Jay S. Bryant
wrote:
On 01/13/2017 10:29 PM, Mike Perez wrote:
The way validation works is completely up to the project team. In my research
as shown in the Summit etherpad [5]
On 2017-01-16 01:19 PM, Jonathan Bryce wrote:
On Jan 16, 2017, at 11:58 AM, Jay S. Bryant
wrote:
On 01/13/2017 10:29 PM, Mike Perez wrote:
The way validation works is completely up to the project team. In my research
as shown in the Summit etherpad [5] there's
> On Jan 16, 2017, at 11:58 AM, Jay S. Bryant
> wrote:
>
> On 01/13/2017 10:29 PM, Mike Perez wrote:
>> The way validation works is completely up to the project team. In my research
>> as shown in the Summit etherpad [5] there's a clear trend in projects doing
>>
On 01/13/2017 10:29 PM, Mike Perez wrote:
Hello all,
In the spirit of recent Technical Committee discussions I would like to bring
focus on how we're doing vendor driver discoverability. Today we're doing this
with the OpenStack Foundation marketplace [1] which is powered by the driverlog
Hello all,
In the spirit of recent Technical Committee discussions I would like to bring
focus on how we're doing vendor driver discoverability. Today we're doing this
with the OpenStack Foundation marketplace [1] which is powered by the driverlog
project. In a nutshell, it is a big JSON file [2]
12 matches
Mail list logo