Re: [openstack-dev] [keystone][specs] listing the entire API in a new spec

2014-07-07 Thread Dolph Mathews
200 Warden Ave >> Markham, ON L6G 1C7 >> Canada >> >> >> >> >> >> From:Dolph Mathews >> To:"OpenStack Development Mailing List (not for usage >> questions)" , >> Date:07/07/2014 01:39 PM >> Sub

Re: [openstack-dev] [keystone][specs] listing the entire API in a new spec

2014-07-07 Thread Anne Gentle
> > > From:Dolph Mathews > To:"OpenStack Development Mailing List (not for usage questions)" > , > Date:07/07/2014 01:39 PM > Subject:Re: [openstack-dev] [keystone][specs] listing the entire > API in anew spec > --

Re: [openstack-dev] [keystone][specs] listing the entire API in a new spec

2014-07-07 Thread Steve Martinelli
; , Date:        07/07/2014 01:39 PM Subject:        Re: [openstack-dev] [keystone][specs] listing the entire API in a        new spec On Fri, Jul 4, 2014 at 12:31 AM, Steve Martinelli <steve...@ca.ibm.com> wrote: To add to the growing pains of keystone-specs, one thing I've not

Re: [openstack-dev] [keystone][specs] listing the entire API in a new spec

2014-07-07 Thread Dolph Mathews
On Fri, Jul 4, 2014 at 12:31 AM, Steve Martinelli wrote: > To add to the growing pains of keystone-specs, one thing I've noticed is, > there is inconsistency in the 'REST API Impact' section. > > To be clear here, I don't mean we shouldn't include what new APIs will be > created, I think that is

[openstack-dev] [keystone][specs] listing the entire API in a new spec

2014-07-03 Thread Steve Martinelli
To add to the growing pains of keystone-specs, one thing I've noticed is, there is inconsistency in the 'REST API Impact' section. To be clear here, I don't mean we shouldn't include what new APIs will be created, I think that is essential. But rather, remove the need to specifically spell out the