Re: [openstack-dev] [neutron] API models [was: PTL candidacy]

>This is why it should be easy to do. The easier it is, the more Neutron work you'll have time for, in fact. I agree that writing them should be easy. But I don't want to enable operators to just tweak config files to alter APIs. So +1000 to developer productivity. I just don't want it to

Re: [openstack-dev] [neutron] API models [was: PTL candidacy]

On 25 January 2017 at 18:07, Kevin Benton wrote: > >Setting aside all the above talk about how we might do things for a > moment: to take one specific feature example, it actually took several > /years/ to add VLAN-aware ports to OpenStack. This is an example of a > feature

Re: [openstack-dev] [neutron] API models [was: PTL candidacy]

>Obviously this is close to my interests, and I see Kevin's raised Gluon as the bogeyman (which it isn't trying to be). No, I was pointing out that it's not what I want Neutron to become. It's entire purpose is to make defining new APIs as simple as writing YAML (i.e. networking APIs as a

Re: [openstack-dev] [neutron] API models [was: PTL candidacy]

I would certainly be interested in dicussing this, though I'm not currently signed up for the PTG. Obviously this is close to my interests, and I see Kevin's raised Gluon as the bogeyman (which it isn't trying to be). Setting aside all the above talk about how we might do things for a moment: to