Re: [openstack-dev] [api] Forming the API Working Group

2014-10-14 Thread Everett Toews
On Oct 14, 2014, at 8:57 AM, Jay Pipes wrote: > I personally think proposing patches to an openstack-api repository is the > most effective way to make those proposals. Etherpads and wiki pages are fine > for dumping content, but IMO, we don't need to dump content -- we already > have plenty o

[openstack-dev] [api] Forming the API Working Group

2014-10-08 Thread Everett Toews
https://wiki.openstack.org/wiki/API_Working_Group This is the start of the API Working Group (API WG). To avoid bike shedding over the name of the working group, I decided to title the wiki page API Working Group. Simple, to the point, and avoids loaded terms like standards, best practices, gu

Re: [openstack-dev] [Nova] [All] API standards working group

2014-09-24 Thread Everett Toews
On Sep 24, 2014, at 12:02 PM, Tim Bell wrote: > Seems like there is some overlap with the end user (i.e. consumer) working > group at https://wiki.openstack.org/wiki/End_User_Working_Group > > Sounds like it would be worth discussing with them on how to focus on these > needs. The scope of the

Re: [openstack-dev] [Nova] [All] API standards working group

2014-09-24 Thread Everett Toews
On Sep 24, 2014, at 9:42 AM, Dean Troyer wrote: > I'll bring an API consumer's perspective. +1 I’d bring an API consumer’s perspective as well. Looks like there’s lots of support for an API WG. What’s the next step? Form a WG under the User Committee [1] or is there something more appropria

Re: [openstack-dev] [zaqar] [marconi] Removing GET message by ID in v1.1 (Redux)

2014-08-29 Thread Everett Toews
On Aug 28, 2014, at 3:08 AM, Flavio Percoco wrote: > Unfortunately, as Nataliia mentioned, we can't just get rid of it in > v1.1 because that implies a major change in the API, which would require > a major release. What we can do, though, is start working on a spec for > the V2 of the API. +1

Re: [openstack-dev] [Programs] Client Tools program discussion

2014-05-11 Thread Everett Toews
For anyone following along this will be discussed in the OpenStackClient and SDKs and project libraries sessions [1] [2]. Everett [1] http://junodesignsummit.sched.org/event/ae9afc77278abb98f0fc35a540a1bb0b [2] http://junodesignsummit.sched.org/event/9c99888fba09c643834d4ef9241cc90a On May 7,

Re: [openstack-dev] [Programs] Client Tools program discussion

2014-05-07 Thread Everett Toews
On Apr 28, 2014, at 8:20 AM, Dean Troyer mailto:dtro...@gmail.com>> wrote: I want to open the discussion of an OpenStack Client Tools program proposal to a wider audience. It would initially consist of OpenStackClient and eventually add the existing SDK projects as they are ready to join. The

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

2014-03-05 Thread Everett Toews
On Mar 5, 2014, at 8:16 AM, Russell Bryant wrote: > I think SDK support is critical for the success of v3 long term. I > expect most people are using the APIs through one of the major SDKs, so > v3 won't take off until that happens. I think our top priority in Nova > to help ensure this happens

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

2014-03-03 Thread Everett Toews
On Mar 3, 2014, at 1:25 PM, Vishvananda Ishaya wrote: > This seems like a reasonable and well thought out approach but It feels > like we are removing our ability to innovate. I know we are worried about > maintaining multiple APIs, but I’m still leaning towards putting the v3 > API out and just

Re: [openstack-dev] Proposed Logging Standards

2014-01-28 Thread Everett Toews
Hi Sean, Could 1.1.1 "Every Inbound WSGI request should be logged Exactly Once" be used to track API call data in order to discover which API calls are being made most frequently? It certainly seems like it could but I want to confirm. I ask because this came up as B "Get aggregate API call da

Re: [openstack-dev] Diversity as a requirement for incubation

2013-12-21 Thread Everett Toews
On Dec 18, 2013, at 4:40 AM, Thierry Carrez wrote: > I guess there are 3 options: > > 1. Require diversity for incubation, but find ways to bless or recommend > projects pre-incubation so that this diversity can actually be achieved > > 2. Do not require diversity for incubation, but require it

Re: [openstack-dev] How to best make User Experience a priority in every project

2013-11-25 Thread Everett Toews
On Nov 21, 2013, at 10:20 AM, Jesse Noller wrote: > I’ve spoken to Everett and others about discussions had at the summit around > ideas like developer.openstack.org - and I think the idea is a good start > towards improving the lives of downstream application developers. Blueprint started by T

Re: [openstack-dev] [DevStack] Generalize config file settings

2013-09-13 Thread Everett Toews
On Sep 13, 2013, at 6:10 AM, Sean Dague wrote: > Because inevitably people ask for copies of other folks configs to duplicate > things, and a single file is easier to pass around than a tree. But that > would mean a unique parser to handle the top level stanza. +1 I share localrc files all the

Re: [openstack-dev] [Openstack] Keystone store-quota-data blueprint

2013-07-01 Thread Everett Toews
This topic came up at the last summit in Portland at [1] and [2]. Yehia and another colleague of his from HP had a design that was discussed and it seemed like they were going to start work on it. Another developer from CERN expressed interest too. I'm not sure if anything ever really got starte

<    1   2