308 Permanent Redirect
Location: /api-sig/news
Greetings OpenStack community,
As with last week, today's meeting started off with continued discussion about
the Guided Review process that we are trying to create ahead of the Denver PTG.
elmiko continues to shape the proposal in a review [0].
Greetings OpenStack community,
Today's meeting started off with continued discussion about the Guided Review
process that we are trying to create ahead of the Denver PTG, where we would
like to incorporate such a process as part of our sessions. This has been
crystallized into a document [0] by
Greetings OpenStack community,
Today's meeting continued the discussion about the newly posted gerrit
review for the Guided Review Process[0]. There is still some work to be
done before the process is in shape to announce for the Denver PTG, but
the group is confident about having the process
Greetings OpenStack community,
Most of the time in today's meeting was dedicated to discussing ideas for the
Guided Review Process [0] (that link will expire in favor of a gerrit review
soon) we are considering for the PTG. The idea is that projects which are
enmeshed in debate over how to co
Greetings OpenStack community,
If you missed our meeting today, well, you didn't miss much. Not a lot of new
things going on. The bulk of the meeting was taken up with ideas for what we'd
like to accomplish at the upcoming Denver PTG. We thought that it might be
useful to have an informal "what
Greetings OpenStack community,
For the first time in a while, the entire API-WG core was present, along with a
fly by from mordred. The main topic of conversation was related to a proposed
cloud profile document [4] including a static version of a thing like the
service catalog. More discussi
Greetings OpenStack community,
Today's meeting was slightly longer than last week's, with a few more in
attendance as well. There were no new major issues brought up and the
main topics were last week's frozen change[4] and a few minor
fixes[5][6] in the queue now. These fixes were considered
Greetings OpenStack community,
Today's meeting was even shorter and sweeter than last week's, as only edleafe
was present, due to cdent being on PTO and elmiko being on the road. Prior to
the meeting, though, we had decided that the guideline change for raising the
minimum microversion was read
Greetings OpenStack community,
Today's meeting was short and sweet. We merged some frozen reivews (see below) and
determined that other pending reviews are still pending. The survey to get some feedback
on how to express the earliest possible date a microversion might raise didn't get a ton
o
On Jun 8, 2017, at 11:59 AM, Chris Dent wrote:
>
> The naming issue related to an optional field we want to add to the
> microversion discovery document. Some projects wish to be able to signal that
> they are intending to raise the minimum microversion at a point in the
> future. The name for
Greetings OpenStack community,
Today's meeting was mostly devoted to two topics: Which of Monty's several
patches were ready for freeze and some naming issues with raising the minimum
microversion.
We decided three of Monty's patches are ready, they are listed below in the
"Freeze" section.
Greetings OpenStack community,
A very lively meeting today, with all the participants in a seemingly jovial
mood. Must be something in the water. Or maybe June just brings out
lightheartedness.
Much of the discussion centered on Monty Taylor's chain of patches [4]
regarding version discovery a
Greetings OpenStack community,
Today was a relatively short meeting with most the time being devoted to
a discussion of Monty Taylor's document chain regarding using the
service catalog for version discovery[4]. The group was largely in
agreement that work is proceeding well and with a few mor
Greetings OpenStack community,
A short meeting today, mostly reflecting on the Birds of a Feather session [4]
at Summit last week. It was well attended and engendered plenty of good
discussion. There are notes on an etherpad at
https://etherpad.openstack.org/p/BOS-API-WG-BOF that continue to
Greetings OpenStack community,
Small group today, mostly edleafe and I (cdent) speaking to one another, with
the ghostly presence of dtantsur lurking nearby. Main action today is that we
finally merged the Interoperability Guideline (links below). It took months of
sometimes heated discussion
Greetings OpenStack community,
We were joined today by mordred who introduced a stack of documents that describe the
current state of API version discovery, some of the hoops required to do it today, and
the clean way to do it henceforth. There is a ton of information in these proposals
(link
Greetings OpenStack community,
A bit of a lonely meeting today, as only cdent and edleafe were present for
most of it, although having elmiko join at the end brightened all of our days.
The main item of discussion was the status of the various project liaisons to
the API WG [0], and how to hand
Greetings OpenStack community,
This week's meeting was lightly attended but provided a useful
discussion about the future of the working group and how we will
continue to improve the API experience for all OpenStack users. The
group is considering its role with respect to the guidelines that i
Greetings OpenStack community,
In today's API-WG meeting we renamed the group twice. First to the "microversion support group".
This is because any conversation that is even tangentially related to microversions becomes rather involved,
leaking into metaphysics. Today involved some discussion
Greetings OpenStack community,
Well, today's meeting was very brief. For the longest time, edleafe had the
room to himself, and breezed through the prepared topics, until stevelle showed
up. We had a good discussion about the stability guidelines and some of the
issues in resolving the two diff
Greetings OpenStack community,
An after an initially slow start, today's meeting turned into a rollicking good
time. Probably because we talked about microversions.
First we discussed the need to clarify that the API-WG is governed by TC
(Technical Committee) not the UC (User Committee). The
Greetings OpenStack community,
Today's meeting was short and sweet. We lamented the decline in active
membership in our group, and discussed ways to encourage more participation
from others. So if you have an interest in helping OpenStack APIs become better
and more consistent, please join us!
On Mon, 13 Mar 2017, Thierry Carrez wrote:
At the recent Board+TC+UC meeting, the User Committee presented the API
workgroup as a User Committee workgroup, based on data from:
https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee
Yeah, that's been ongoing for a while and not som
Ed Leafe wrote:
> On Mar 9, 2017, at 9:30 PM, Everett Toews wrote:
>
>>> For those who don't know, Everett and I started the API-WG a few years ago,
>>
>> Umm...given this statement, I feel I _must_ provide some clarity.
>>
>> The API WG was started by myself, Jay Pipes, and Chris Yeoh. The b
On Mar 9, 2017, at 9:30 PM, Everett Toews wrote:
>> For those who don't know, Everett and I started the API-WG a few years ago,
>
> Umm...given this statement, I feel I _must_ provide some clarity.
>
> The API WG was started by myself, Jay Pipes, and Chris Yeoh. The ball got
> rolling in t
> On Mar 9, 2017, at 11:52 AM, Ed Leafe wrote:
>
> Greetings OpenStack community,
>
> Today's meeting started on a heavyhearted note, as we hoisted our virtual
> beers and gave a toast to Everett Toews, who recently had to step down from
> his API-WG duties due to a job re-assignment.
I'm pr
Greetings OpenStack community,
Today's meeting started on a heavyhearted note, as we hoisted our virtual beers
and gave a toast to Everett Toews, who recently had to step down from his
API-WG duties due to a job re-assignment. For those who don't know, Everett and
I started the API-WG a few yea
Greetings OpenStack community,
Only two of us in attendance at today's API-WG meeting. We mostly reflected on
the work that needs to be done to summarize activity at the PTG last week.
Despite not having a room of our own until the last minute, on Monday and
Tuesday we had a large gathering w
Greetings OpenStack community,
This week's meeting[0] was relatively light, with some discussion about
the recently released Ethercalc[4], and the first draft of the API
compatiblity guideline[5] (many thanks to Chris Dent). The compatibility
guideline lays out some concrete standards by which
On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi
mailto:ken1ohmi...@gmail.com>> wrote:
2017-02-06 6:45 GMT-08:00 Brian Rosmaita
mailto:rosmaita.foss...@gmail.com>>:
On 2/6/17 5:51 AM, Jordan Pittier wrote:
[super-enormous snip -- Chris, Ken, and Jordan make good points, I
encourage you to read the
2017-02-07 10:31 GMT-08:00 Ed Leafe :
> On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi wrote:
>>
>>> To summarize, my point is that we shouldn't be worried that this case is
>>> going to set a precedent. It would be worrisome if it were going to set
>>> a *bad* precedent, but when you look at the d
2017-02-07 6:56 GMT-08:00 Brian Rosmaita :
> On 2/6/17 4:28 PM, Ken'ichi Ohmichi wrote:
>> 2017-02-06 6:45 GMT-08:00 Brian Rosmaita :
>>> On 2/6/17 5:51 AM, Jordan Pittier wrote:
>>> [super-enormous snip -- Chris, Ken, and Jordan make good points, I
>>> encourage you to read the entire thread; I ju
On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi wrote:
>
>> To summarize, my point is that we shouldn't be worried that this case is
>> going to set a precedent. It would be worrisome if it were going to set
>> a *bad* precedent, but when you look at the details of the situation, I
>> don't think i
On 2/6/17 4:28 PM, Ken'ichi Ohmichi wrote:
> 2017-02-06 6:45 GMT-08:00 Brian Rosmaita :
>> On 2/6/17 5:51 AM, Jordan Pittier wrote:
>> [super-enormous snip -- Chris, Ken, and Jordan make good points, I
>> encourage you to read the entire thread; I just want to concentrate on
>> one point]
>>>
>>> I
2017-02-06 6:45 GMT-08:00 Brian Rosmaita :
> On 2/6/17 5:51 AM, Jordan Pittier wrote:
> [super-enormous snip -- Chris, Ken, and Jordan make good points, I
> encourage you to read the entire thread; I just want to concentrate on
> one point]
>>
>> I would say we should make compromise, not solve dil
2017-02-06 2:51 GMT-08:00 Jordan Pittier :
>>
>> >> If we change the success status code (200 ->204) without any version
>> >> bumps, OpenStack clouds return different status codes on the same API
>> >> operations.
>> >> That will break OpenStack interoperability and clients' APPs need to
>> >> be
On 02/06/2017 08:45 AM, Brian Rosmaita wrote:
> On 2/6/17 5:51 AM, Jordan Pittier wrote:
> [super-enormous snip -- Chris, Ken, and Jordan make good points, I
> encourage you to read the entire thread; I just want to concentrate on
> one point]
>>
>> I would say we should make compromise, not solve
On 2/6/17 5:51 AM, Jordan Pittier wrote:
[super-enormous snip -- Chris, Ken, and Jordan make good points, I
encourage you to read the entire thread; I just want to concentrate on
one point]
>
> I would say we should make compromise, not solve dilemma. I can live in a
> world where we sometimes all
On Fri, Feb 3, 2017 at 7:51 PM, Ken'ichi Ohmichi
wrote:
> 2017-02-03 9:56 GMT-08:00 Chris Dent :
> > On Thu, 2 Feb 2017, Ken'ichi Ohmichi wrote:
> >>>
> >>> In today's meeting [0] after briefly covering old business we spent
> >>> nearly
> >>> 50 minutes going round in circles discussing the comp
2017-02-03 9:56 GMT-08:00 Chris Dent :
> On Thu, 2 Feb 2017, Ken'ichi Ohmichi wrote:
>>>
>>> In today's meeting [0] after briefly covering old business we spent
>>> nearly
>>> 50 minutes going round in circles discussing the complex interactions of
>>> expectations of API stability, the need to fix
On Thu, 2 Feb 2017, Ken'ichi Ohmichi wrote:
2017-02-02 9:38 GMT-08:00 Chris Dent :
Greetings OpenStack community,
In today's meeting [0] after briefly covering old business we spent nearly
50 minutes going round in circles discussing the complex interactions of
expectations of API stability, t
2017-02-02 9:38 GMT-08:00 Chris Dent :
>
> Greetings OpenStack community,
>
> In today's meeting [0] after briefly covering old business we spent nearly
> 50 minutes going round in circles discussing the complex interactions of
> expectations of API stability, the need to fix bugs and the costs and
Greetings OpenStack community,
In today's meeting [0] after briefly covering old business we spent nearly 50 minutes
going round in circles discussing the complex interactions of expectations of API
stability, the need to fix bugs and the costs and benefits of microversions. We didn't
make a
Greetings OpenStack community,
Today's meeting [0] covered two main topics: Making sure we get input on the
process for refactoring the api compatibility guidelines [4] and whether we
should have some official time at the PTG. Rather than having official time we
decided that the best thing to
Greetings OpenStack community,
Exciting meeting today, lots of people, lots of discussion[0]. We started out
talking about the service-types-authority[4] and whether the api-wg should be
more directly involved in it. Since there's a fair bit of overlap between
participants in both groups, we
Greetings OpenStack community,
Our first meeting for 2017 opened with a bang. Lots of people in attendance to
talk about the ongoing adventure of trying to improve the handling of the
concept of visibility in Glance. If we had had more time we could have
continued talking about it for a long
Greetings OpenStack community,
This week we have the pleasure of adding Ed Leafe as a core. Ed has been a
consistent and positive presence for quite some time and he'll be good, by hook
or crook.
Our discussion today was focused in two areas:
* The developing capabilities guideline (at
http
Greetings OpenStack community,
A new guideline merged this week, describing the "not in" operator for query
strings, and some clarification of when to use 400 vs 404 is ready for wider review. See
below for links to both. Other than that, not a lot going on. If you're aware of a
missing, misl
Greetings OpenStack community,
Some good attendance and discussion this week. For many months the API-WG has been
claiming that it would try to review any commit that contained an 'APIImpact' tag. This
has proven impractical so instead of maintaining a task on our list that we know we're
not
Greetings OpenStack community,
A pleasant but short meeting this week. During the open discussion we all
agreed that the increased activity on the mailing list using the [api] tag --
with explicit invitations to engage in discussions -- was great to see
happening and great to participate in.
Greetings OpenStack community,
Just me (cdent) and edleafe today. We burned through the agenda, quickly
merging the frozen guidelines that were ready to merge. See below. If you think
they are not complete please considering submitting a patch or bug [4] to get
them cleaned up.
The guideline
Greetings OpenStack community,
This week's meeting of the working group talked about the discussion at the API-WG
"birds of a feather" at last week's summit in Barcelona. Thanks to everyone who
showed up for that. I hope it was interesting and useful. Also thanks very much to all
the people w
Greetings OpenStack community,
This week's meeting of the working group saw some conversation about
activities related to API topics at the upcoming OpenStack summit. There
will be a "birds of a feather" session for the working group on
Wednesday from 12:15-12:55, please see our etherpad for t
Greetings OpenStack community,
Today's meeting began with a quick review of the API usability tests
that are being conducted at the Barcelona Summit[7]. We also had two
lively discussions which took up most of the meeting: one about
collecting and improving error messages across OpenStack, and
Greetings OpenStack community,
Today's meeting we welcomed back the long lost etoews. In addition to the usual
checking up on pending guidelines (there's one newly frozen) we also discussed
a posting made to the mailing list about how best to represent time intervals
[7] and the need to follo
Greetings OpenStack community,
Today's meeting was lightly attended and somewhat short, due to scheduling
conflicts. Thanks to those who were able attend. To those who weren't able to
make it: we missed you. The main new area of business was a need to discuss the
planned API usability testing
Greetings OpenStack community,
There was no meeting of the working group this week as several of our
members have scheduling conflicts.
The meeting logs are in the usual place [5]. If you find an issue with
an existing guideline [3] or think of one that needs to exist, make a
bug [4].
# Ne
Greetings OpenStack community,
This week the working group has been discussing an interesting topic
raised by Michael Krotscheck on the devel mailing list[7]. This
discussion is mainly about how we can create a more consistent API
version discovery mechanism across the OpenStack projects, and
Subject: [all][api] POST /api-wg/news
Greetings OpenStack community,
Today we were joined by Scott DAngelo (scottda) who has graciously taken over
the liaison role for Cinder as Alex Meade steps down. Thanks for stepping up
Scott and welcome to the API WG!
We also cleaned house today and merge
Greetings OpenStack community,
Just me (cdent) and etoews today. We merged one guideline, froze some others
and worked on making some links to the links guideline from other guidelines:
[5:40pm] cdent: hypermedia everywhere!
[5:41pm] etoews: it's the HT in HTML and HTTP!
[5:41pm] c
Greetings OpenStack community,
Today's open discussion centered around the concept of capabilities and
the need to ensure that however we end up doing them in APIs there
should be consistency amongst the existing OpenStack services. In fact,
it would be great if there were consistency between
Greetings OpenStack community,
Our main new topic for today was making sure that we take a more active role in
curating the bugs that are now being kept in launchpad [4] by including review
of those bugs in the workshopping that we do in each meeting. If you find
issues in the existing guidelin
Greetings OpenStack community,
This week, the API-WG was visited by Deepti Ramakrishna from the Cinder
project. Deepti brought up a spec currently being implemented by the
Cinder team about resource capabilities, "New public core APIs to expose
system capabilities"[5][6]. The result of this wa
Greetings OpenStack community,
No new guidelines have been merged or proposed for freeze this week.
There are 19 outstanding issues in the launchpad bug tracker for the
working group[4], and we are always looking for more help from the
community. A few hot issues currently are the need for an
Greetings OpenStack community,
No new guidelines have been merged or proposed for freeze this week, but
we have cleaned up some of the language in the guideline pages and have
had some productive discussions initiated by the Glance team about
changes they are working towards.
# Recently merg
Greetings OpenStack community,
A few interesting developments in the API WG this week.
The API WG reviewed the new Glance Artifact Repository (aka Glare) API [4]. The
team was already adhering to most of the API WG guidelines [3] and after some
reviews they were able to get excellent coverage o
Greetings OpenStack community,
No new guidelines this week but we did have a very productive time creating
launchpad bugs for all the TODOs that are in the existing guidelines. The idea
is that using launchpad will help to keep the TODOs visible and encourage
action. See them at
https://bugs
Greetings OpenStack community,
Nothing new for guidelines this week. In this week's api-wg meeting we had some
good dicussions about the API for image visibility in glance[1] and the
forthcoming Glare API[2], including the wisdom: If you're ever going to do
microversions, then you better micr
Greetings OpenStack community,
This week there are no new merged guidelines nor guidelines proposed for
freeze but there is a new guideline discussing ways to ensure that URIs
are semantically consistent: https://review.openstack.org/#/c/322194/
# Recently merged guidelines
These guidelines
Greetings OpenStack community,
Welcome to another edition of the API working group's weekly newsletter.
# Recently merged guidelines
These guidelines have been recently merged by the group.
* Description of how to use etags to avoid lost updates
https://review.openstack.org/#/c/301846
* Dele
70 matches
Mail list logo