sibility that will
result from increased use of the mailing list will drive some of
that.
dhellman and ttx are going to start creating a presentation to the
board reminding them about how things work with regard to things
getting done. It's not just throwing requirements over the wall
if there any questions.
[1] https://review.openstack.org/#/c/457283/
https://review.openstack.org/#/c/459413/
https://review.openstack.org/#/c/461289/
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw
that because it confuses
traceability of a series of things. Instead, always use the request
id if it is valid and authentic.
But maybe you mean "if the request id could not be proven authentic,
don't use it"?
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freen
s the thing used to talk to the API.
I really hope we can avoid creating yet more special language for
OpenStack. We've got an API. We want to send keys or tokens. Let's
just call them that.
--
Chris Dent ┬──┬◡ﾉ(° -°
. I don't
know, but seems unlikely.
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List
ed something, please tell me.
# End
Instead of a cookie, this time you get beer.
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw: @anticdent
enda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freen
s/tc/2017/tc.2017-04-25-20.00.log.html#l-177
[2] https://www.openstack.org/assets/survey/April2017SurveyReport.pdf
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent
017/tc.2017-04-25-20.00.log.html#l-259>
# Colophon
This is an opinionated overview of Technical Committee activity from
my perspective. As such it is subjective and potentially wrong
enough to cause disagreements. That's a good thing if it leads to
discussions that make things better or more corr
e, but I'm not sure if there is
any active code.
* https://etherpad.openstack.org/p/placement-newton-leftovers
There's still some lingering stuff on here, some of which is
mentioned elsewhere in this message, but not all.
# End
You made it! Here's your cookie.
--
ack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Developme
someone else will start their
own newsletter. And then after a while every member of the TC will
be writing their own report.
--
Chris Dent ┬──┬◡ﾉ(° -°ﾉ) https://anticdent.org/
freenode: cdent
d elsewhere in this message, but not all.
# End
I feel like there are probably things I've forgotten, but I hope the
above list is sufficient to keep people busy. Thanks for reading.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
nstack.org/openstack/api-wg/liaisons.html
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not
ion
should indicate that.
Is there a different workflow that you (or the people complaining)
have in mind that could work better? Is there something that could
or should be clarified to make this more clear?
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freen
On Fri, 14 Apr 2017, Chris Dent wrote:
# Other Code/Specs
Missed one:
* https://review.openstack.org/#/c/455710/
A fix to some issues with CONTENT_LENGTH and CONTENT_TYPE when
running under nginx+uwsgi.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode
on an osc-plugin that can provide a command
line interface to the placement API.
# End
Thanks for reading.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
I work with everyday -- the people I regularly call my coworkers
(and friends!) when mentioning them to (other) friends and family --
are not all paid by the same company as me. That is _awesome_.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.
and implementation that the outer layer would interface
with to satisfy the same use cases using changed technologies.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
is inaccessible. Participation needs
to be more accessible.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development
would feel more
aware of and able to participate in the discussion and processes
working to shape the future of OpenStack.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw
ut not all.
# End
One of the best things about writing these things each week is I get
to see very clearly just how productive we're being in the realm of
placement. Thanks to everyone who is helping to make that possible.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freen
:open+project:openstack/api-wg,n,z
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/
h tempest, but gabbi files are still used[3].
If this might be useful and I can help out, please ask.
[1] http://gabbi.readthedocs.io/
[2] http://gabbi.readthedocs.io/en/latest/runner.html
[3]
https://github.com/openstack/ceilometer/tree/master/ceilometer/tests/integration
--
Chris Dent
Hi, I'm Chris Dent, cdent on IRC.
I'm once again nominating myself to be your representative on the
Technical Committee. I've been around OpenStack for about three
years, most recently visible as the guy who writes those weekly
updates about the placement API service and talks about the
API-WG
On Mon, 13 Mar 2017, Chris Dent wrote:
* The scheduler report client in nova, and to a minor degree the
filter scheduler, use some of the same exceptions and ovo.objects
that placement uses, which presents a bit of blechiness with
regards to code duplication. I suppose long term we could
h is
mentioned elsewhere in this message, but not all.
# End
Go think about claims.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
ver time, but I'm not sure if there is
any active code.
* https://etherpad.openstack.org/p/placement-newton-leftovers
There's still some lingering stuff on here, some of which is
mentioned elsewhere in this message, but not all.
# End
You made it!
--
Chris Dent
ack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
people outside the OpenStack
community increases. As a result it can become a better tool for
more people, including OpenStack people. Not all, or even many, of
the OpenStack projects are like that, but gnocchi is. More eyes,
less bugs, right?
--
Chris Dent ¯\_(ツ)_/¯ https
resolved in newer versions of the packaging.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List
cement-newton-leftovers
There's still some lingering stuff on here, some of which is
mentioned elsewhere in this message, but not all.
# End
Thanks (again?) for reading this far.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cd
ike/approved/resource-provider-traits.html#rest-api-impact
[3]
https://github.com/openstack/nova/blob/d02c0aa7ba0e37fb61d9fe2b683835f28f528623/nova/scheduler/client/report.py#L704
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
and we can have it in the record and hopefully make
the document more fully relevant as a result.
Thank you for participating.
[1] or at least accepting of as a useful compromise
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freen
resource".
I guess the most important questions I can ask at this point are "Can
you please define what you mean by schema?" and "If I had one, what
could I do with it?". That will go a long way to making sure we're
near to the same page. I can make some guesses, but better to b
(which it should be) what difference does
where the code lives make?
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack
, the TC
is the source of mediation and resolution.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing
y and only way to find placement, this ought to be okay.
I'm not sure how or if we want to proceed with this topic, but I
think this at least allows us to talk about it with less guessing.
My generally summary is "yeah, this is doable, without huge amounts
of work."
--
Chris Dent
he scheduler report client when a resource
provider is deleted.
* https://review.openstack.org/#/c/442498/
Gabbi test for invalid resource class name.
# End
Thanks for reading this far. Your reward is my sincere thanks and
credit in the beer bank.
--
Chris Dent
than doing that you may wish to move nova-placement-api
to a less global directory and grant access to that directory.
Providing wide access to /usr/bin is not a great idea.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
ome errors that are in the process of being fixed,
so make sure you read the associated comments.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent
org/421846
The gist is: do it on a different endpoint in the service catalog
while experimental and then migrate it or kill it as needed. That's
just an idea. If you have others would be great to hear them.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freen
On Fri, 3 Mar 2017, Chris Dent wrote:
* I produce a next version of the guidelines integrating the
feedback.
I've pushed out a new version that tries to integrate some chunk of
the feedback. Probably missed some. Please comment as required:
https://review.openstack.org/#/c/421846
Either here
in response to this message, on the associated reviews, or come to
an api-wg meeting [1] and have a chat. We are making progress.
[0] https://review.openstack.org/#/c/433272/
[1] http://eavesdrop.openstack.org/#API_Working_Group
--
Chris Dent ¯\_(ツ)_/¯
* neutron and cinder doing things with placement
* using a different database with placement [1]
* extracting placement to its own repo
[1] Patch to use separate database is being kept up to date:
https://review.openstack.org/#/c/362766/
--
Chris Dent ¯\_(ツ)_/¯ https://ant
tatus:open+project:openstack/api-wg,n,z
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ https://ant
f you find yourself justifying some cruft on side A for behavior on
side B we know that's a problem for other users of B. What we're less
good at is evolving B quickly enough such that A doesn't have to
compensate. There's likely no easy solution that also accounts for
compatibility.
--
available that reflects what happened.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not
e what the situation is.
Anyone have a clue?
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing
[4] https://review.openstack.org/#/c/421846/
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org
of the mod-wsgi
related configuration so that we are not duplicating the generic
bits between multiple services.
[1] https://bugs.launchpad.net/devstack/+bugs
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
who want to show up are able to do so.
[1] https://etherpad.openstack.org/p/ptg-architecture-workgroup
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw
ly show up in these reports.
Next week I will endeavor to gather enough information to make these
messages something actionable again. In the meantime thanks and
congrats to everyone for pushing things forward.
[1] This is probably a universal truth of any code, so perhaps
redundant to mention.
--
On Thu, 2 Feb 2017, Ken'ichi Ohmichi wrote:
2017-02-02 9:38 GMT-08:00 Chris Dent <cdent...@anticdent.org>:
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 intera
ug/1656183
[5] https://review.openstack.org/#/c/425487/
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ https://ant
On Thu, 26 Jan 2017, Chris Dent wrote:
On Wed, 25 Jan 2017, Chris Dent wrote:
#B3
The new GET to /placement/allocations is happening when the
resource tracker calls _update_usage_from_instance, which is always
being called becuause is_new_instance is always true in that method,
even when
===
There will be a more complete update and catch up next week, at
which point we should have a clear picture of what bugs need to be
addressed and where longer term things stand.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
On Wed, 25 Jan 2017, Chris Dent wrote:
#B3
The new GET to /placement/allocations is happening when the
resource tracker calls _update_usage_from_instance, which is always
being called becuause is_new_instance is always true in that method,
even when the instance is not "new". This is
/
[6] http://lists.openstack.org/pipermail/openstack-dev/2017-January/110043.html
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent
s out any accounting for the operations
from the scheduler itself, or the write operations that the resource
tracker does when things change.
[4] Which is kinda where I hoped but didn't get to today. Maybe
another day soon.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.
W: I think we should start using the term "stability" not
"compatibility".
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent
th something different (though we may) but
because more input from more than the usual suspects is a good
thing.
[1] https://review.openstack.org/421846
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode
On Wed, 18 Jan 2017, Chris Dent wrote:
The review starts with the original text. The hope is that
commentary here in this thread and on the review will eventually
lead to the best document.
https://review.openstack.org/#/c/421846
There's been a bit of commentary on the review which I'll
ew.openstack.org/#/c/414261/
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage qu
of what inspired the notion of a "base services"
which is a topic up for proposal in the architecture working group:
https://review.openstack.org/#/c/419397/
(In other words: yeah, important topic.)
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freen
On Wed, 11 Jan 2017, Chris Dent wrote:
The basis for this conclusion is from three assumptions:
* The value of 'local_gb' on the compute_node object is any disk the
compute_node can see/use and the concept of associating with shared
disk by aggregates is not something that is real yet[0
if this is
missing something I blame that (and society, man) and I hope anyone
who notices will followup with a correction. Thanks.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw
nchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage
On Fri, 6 Jan 2017, Chris Dent wrote:
## can_host, aggregates in filtering
There's still some confusion (from at least me) on whether the
can_host field is relevant when making queries to filter resource
providers. Similarly, when requesting resource providers to satisfy a
set of resources, we
d to the users, should always be 80 and 443 (so no need to
define a port, just a scheme) and the internal ports, if necessary,
should be up to the deployer and their own internal plans. If we
define a default port, people will use it and expose it to users.
imho, iana(deployer), ymmv, etc
--
Chris Dent
On Fri, 6 Jan 2017, Chris Dent wrote:
* CORS support in placement API:
https://review.openstack.org/#/c/392891/
This is one we should probably get in in Ocata because it enables
the sole piece of configurability that is present in the WSGI
middleware stack used for the placement API. Unlike
these things. Thanks to everyone
who helped out and persevered last cycle we got some good stuff out
the door. Thanks to those people and anyone else who helps out this
time, we'll do it again.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
nstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
://1.2.3.4/placement and disable the
virtualhost that listens on 8778?
I'd experiment with this myself but I'm going to be away from a
compute all day. If people think it is a good idea but nobody has a
chance to do it today I'll look into it tomorrow.
--
Chris Dent ¯\_(ツ
eing manipulated by
the task.
From a user's standpoint stop, start, pause, unpause, reboot etc are
isolated actions that describe a state of the container resource.
[1] https://review.openstack.org/#/c/234994/
--
Chris Dent
date script:
https://review.openstack.org/#/c/382613/
This one might be considered a WIP because how it chooses to do
things (rather simply and dumbly) may not be in line with expecations.
# End
Thanks to everyone for all the hard work.
--
Chris Dent ¯\_(ツ)_/¯ https://ant
ngs/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
loop to ResourceClass creation
https://review.openstack.org/#/c/399170/
There is a race condition in the creation of custom resource clases.
# End
Thanks for reading. Please post questions if you have them.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode
tack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
On Fri, 2 Dec 2016, Matt Riedemann wrote:
Some responses within to clarify a few points.
On 12/2/2016 12:04 PM, Chris Dent wrote:
There are some things to consider as that work progresses:
* The bit about aggregates in the previous section: the list of
returned resource providers needs
me, so I'd be doing it anyway, even if I wasn't
sending it out. I hope other people find it useful. If there's
something I can do to make it more useful, let me know.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
tack.org/#/c/401941/
[5] https://review.openstack.org/#/c/405515/
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ¯\_(ツ)_/¯ h
of the
placement API transactions (that's true in pending changes to
both the API and the resource tracker)
[6] http://lists.openstack.org/pipermail/openstack-dev/2016-November/107177.html
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
for the
meeting please add it as a topic to the agenda[1].
Thanks!
[1] https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw
please let me know.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage questions
_very_ much for getting this started.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List
ck.org/#/q/status:open+project:openstack/api-wg,n,z
[7]: http://markmail.org/message/yr3ex6u6kcv4itty
[8]: https://review.openstack.org/#/c/399131/
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent
have anything to add or have
questions please post a response.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Deve
such a drag and a bad thing. I
know more now than I did before I read your message. Surely that's
a good thing? I'm not sure why you should feel terrible. Did you
tell the truth as you see it? Great. Good on you. I'm grateful. And
I'm glad you feel relieved.
Thank you.
--
Chris Dent
On Thu, 10 Nov 2016, Matt Riedemann wrote:
Heads up, we are a GO for neutron by default in Ocata jobs:
This. Is. Awesome.
Nice work by everyone involved.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw
nstack.org/meetings/api_wg/
[6]: https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
.
[1] This is in fact a world I might want to live in, I like cats and
dogs and dood, anarchy now, please. But I wouldn't presume to impose
that here.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw
it
won't work if we don't.
That might work. It could be a mess, but it is better than an
alternative which is feeling increasingly likely: People go elsewhere.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw
in trust. We've got people who want to build stuff.
Isn't that the important part?
Let's just get on with making stuff and work out the problems (and of
course there will be many, there always are) as they happen. That's
what we do.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org
_Summit.21
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
have said has been convincing, I've
updated the code at: https://review.openstack.org/#/c/388115/
Jay's review of that has raised a new issue: which is should we even
bother with the decorator style?
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
at the chosen time.
https://etherpad.openstack.org/p/ocata-climb
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack
ic service catalogs in the face of different
contexts
* whatever else I'm forgetting right now because the coffee is weak
but I'm sure someone else remembers
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
to the non-existent handler just be removed?
If the discovery doc is for discovering stuff, it shouldn't list stuff
that doesn't exist. That's pretty simple and straightforward, right?
How could it be anything else?
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode
On Tue, 18 Oct 2016, Chris Dent wrote:
If the requested microversion is greater than the maximum, a 404 still
makes some sense (no mapping _now_), but a 406 could as well because it
provides a signal that if you used a different microversion the
situation could be different and the time
301 - 400 of 758 matches
Mail list logo
