o need to
be an existing placement core, everyone with an interest is welcome.
Thanks.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
reenode: cdent tw: @anticdent_
open placement
patches](https://review.openstack.org/#/q/project:openstack/placement+status:open)
and patches from everywhere which [mention placement in the commit
message](https://review.openstack.org/#/q/message:placement+status:open).
# End
In case anyone is wondering where I am, I
Since there were no objections and a week has passed, I've made
Tetsuro a member of placement-core.
Thanks for your willingness and continued help. Use your powers
wisely.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode:
have the plugin installed, thus no gabbi tests are
found:
http://logs.openstack.org/14/601614/21/check/placement-tempest-gabbi/f44c185/job-output.txt.gz#_2018-09-28_11_13_25_798683
How do I get my plugin installed into the right venv while still
following the guidelines for good zuul be
ng to try to get the gabbits in the
right place is not working as desired.
A few patchsets ago when I was using the oogly way of doing things
it was all working.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
s:open)
and patches from everywhere which [mention placement in the commit
message](https://review.openstack.org/#/q/message:placement+status:open).
# End
Taking a few days off is a great way to get out of sync.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freen
at have or do not have a specific trait. This
has the effect of making the meaning of a trait a descriptor of the
resource provider. What the descriptor signifies is up to the thing
creating and using the resource provider, not place
here, but I have no interest in being a
fundamentalist about it. We should argue about it strongly to make
sure we get the right result, but it's not a huge deal either way.
--
Chris Dent ٩◔̯◔۶
people do things. In the context of the orchestration between nova
and ironic and how that interaction happens, nova has every right to
set some guidelines if it needs to.
--
Chris Dent ٩◔̯◔۶
effectively "run the gabbits in these dirs" against a
tempest set up. Doing so will require some minor changes to the
tempest tox passenv settings but I think it ought to
straightforwardish.
Some reviews from people who understand these things more than me
would be most welcome.
--
lcoming the
newly elected members of the TC: Lance Bragstad, Jean-Philippe
Evrard, Doug Hellman, Julia Kreger, Ghanshyam Mann, and Jeremy
Stanley.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
On Tue, 2 Oct 2018, Chris Dent wrote:
One of the comments in there is about the idea of making a zuul job
which is effectively "run the gabbits in these dirs" against a
tempest set up. Doing so will require some minor changes to the
tempest tox passenv settings but I think i
On Wed, 3 Oct 2018, Chris Dent wrote:
I'd really like to see this become a real thing, so if I could get
some help from tempest people on how to make it in line with
expectations that would be great.
I've written up the end game of what I'm trying to achieve in a bit
more
n the day when
there were weekly meetings.
The "raising hands" thing that came along towards the end sort of
worked, so a variant on that may be sufficient.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
stack.org/#/c/601407/>
WIP: Add placement to devstack-gate PROJECTS
* <https://review.openstack.org/#/c/586960/>
zun: Use placement for unified resource management
# End
I'm going to be away next week, s
xplicitly, that they would not
bother contributing if they had to go through what they perceive to
be the OpenStack hoops. That's anecdata, but for me it is pretty
compelling.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
how things got away from them.
For community goals, in particular, preferring email for discussion
and planning seems pretty key.
I wonder if instead of specifying topics for TC office hours, we kill
them instead? They've turned into gossiping echo chambers.
--
Chris Dent
king happily in Python 3.7.
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-August/132792.html
[2] https://bitbucket.org/ianb/paste
[3] https://bitbucket.org/ianb/paste/pull-requests/41/python-37-support/diff
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
pport other databases during the upgrade,
captured in this change
https://review.openstack.org/#/c/604028/
[1] There's a stack of code for enabling placement integration tests
starting at https://review.openstack.org/#/c/601614/ . It depends on
the devstack changes.
--
Chris Dent
WIP: Add placement to devstack-gate PROJECTS
This was done somewhere else wasn't it, so could this be
abandoned?
* <https://review.openstack.org/#/c/586960/>
zun: Use placement for unified resource management
# End
Hi!
--
Chris Dent ٩◔̯◔۶ https://antic
On Fri, 19 Oct 2018, Thierry Carrez wrote:
Ed Leafe wrote:
On Oct 15, 2018, at 7:40 AM, Chris Dent wrote:
I'd like some input from the community on how we'd like this to go.
I would say it depends on the long-term plans for paste. Are we planning on
weaning ourselves off of
nscious actions, awareness and
self-testing by each project to move forward to a thing with a
reasonable name (the cycle name).
I don't think we should call that "churn". "Intention" might be a
better word.
--
Chris Dent ٩◔̯◔۶
On Mon, 22 Oct 2018, Chris Dent wrote:
Thus far I'm not hearing any volunteers. If that continues to be the
case, I'll just keep it on bitbucket as that's the minimal change.
As there was some noise that suggested "if you make it use git I
might help", I put
[1]
work is in progress to make using something else easier for people.
If you want to help with Paste, make some issues and pull requests
in the repo above. Thanks.
Next step? paste.deploy (which is a separate repo).
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/135937.html
Harden placement init under wsgi
* <https://review.openstack.org/#/q/topic:cd/gabbi-tempest-job>
Using gabbi-tempest for integration tests.
* <https://review.openstack.org/#/c/613118/>
Make tox -ereleasenotes work
* <https://review.openstack.org/#
me know if you have any questions or if you are interested in
helping to make gabbi-tempest more complete and well documented.
I've been approving my own code the past few patches and that feels
a bit dirty.
--
Chris Dent ٩◔̯◔۶ https://antic
those steps can translate to both the ansible and
tripleo environments.
Please feel free to add me to any of the reviews and come calling in
#openstack-placement with questions if there are any.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode:
On Wed, 31 Oct 2018, Eduardo Gonzalez wrote:
- Run db syncs as there is not command for that yet in the master branch
- Apply upgrade process for db changes
The placement-side pieces for this are nearly ready, see the stack
beginning at https://review.openstack.org/#/c/611441/
--
Chris Dent
ad.openstack.org/p/osux-api-oct2016
Thanks,
Thank you.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Ma
e code is linked from the blog post.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage qu
[5]: http://eavesdrop.openstack.org/meetings/api_wg/
[6]: https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
[7]: Thread starting at
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103988.html
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freen
lways be more of those). We
need to keep looking and pushing forward.
To that end I'm nominating myself to be a member of the Technical
Committee.
If you have specific questions about my goals, my background or anything
else, please feel free to ask. I'm on IRC as cdent or send some email
in addition to the git
log, are something to consider for TC activity.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Deve
in the election
:)
Yeah, that sounds good. Please keep me involved.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Deve
s the knee?)
* Tempest or other form of integration test
(currently we can only evaluate success of resource tracker +
placement api by lack of smoke, no real details)
--
Chris Dent ┬─┬ノ( º _ ºノ
s for prompting this.
1. This is a great example how much this attitude of "full contact
community engagement" is *needed* and how much it's *lacking* with the
current set of representatives ->
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103223.html -
not surpri
issues you'd like the TC address
in the coming year?
I ended up getting overly excited in my response to Clay and answering
over there. So by the power of hypertext:
http://lists.openstack.org/pipermail/openstack-dev/2016-October/105000.html
--
Chris Dent ┬─┬ノ( º
ering (and to some extent transforming) parts are the only
parts of ceilometer that are particularly unique so it would be good
for those to be preserved.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
then we should either have
TC elections every week or come up with some other catalysts.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent_
involvement in it but are concerned about
Nova to feel excluded.
[1] https://etherpad.openstack.org/p/nova-newton-retrospective
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
nstack.org/meetings/api_wg/
[6]: https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
[7]: Thread starting at
http://lists.openstack.org/pipermail/openstack-dev/2016-October/105198.html
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freen
On Sun, 2 Oct 2016, Chris Dent wrote:
I'm posting this as it would be great to get some feedback on:
* which of these things matter
* what is missing from the list
* how (or if) we should formalize the doing of the work
* who would like to help out in the doing (getting some help is the
emonstrated, perhaps it needs to be formalized?
* [your idea here please]
[1]
http://governance.openstack.org/reference/principles.html#changes-in-leadership-are-good
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
only realistic way to go. I
mention it more as a way jumping off point for further thinking than
a concrete proposal.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
ee that siloing the stuff in the code is bad in the long term,
but I guess it is good that it has started somewhere.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
ed mostly on the economic power their
corporate patrons are willing to wield for them. And finally it
feels like we are making it harder for more people to be engaged in
cross project work.
I'm certain that none of these things are the desired outcomes.
What can we do to clarify the situation an
doing real things with OpenStack.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for
most important. Trying to achieve strict
consistency on query parameters across the entire breadth of
OpenStack isn't being considerate of the differents contexts of use
and users.
[1] https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
--
Chris Dent
http://www.sharmaclimbingbcn.com/en/gym/
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing Lis
ng is dangerous. If
you choose to climb, it is at your own risk.
(Sharma's people will take care of that in the registration.)
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
an etherpad where we can accumulate some plans,
and also linked a doodle poll in there to figure out some good ideas
for when. If I should put more day time slots into the poll, let me
know.
https://etherpad.openstack.org/p/ocata-climb
--
Chris Dent ┬─┬ノ( º _ ºノ)https:
ard to some of the proxy APIs at the nova midcycle but I
can't remember the details of the outcome.
(Of course one way to avoid this conundrum is to not allow it either
by crook or convention, but that seems to limit the power of
microversions to turn things off. A power that is important to
ha
GI server.
One could, if one wanted, hosted a pecan based application with
gunicorn. Or uwsgi. Or apache+mod_wsgi. Or nginx+uwsgi. Or a bunch
of other stuff.
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent
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
uld the link 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 ┬─┬ノ( º _ ºノ)h
one and only one‽)
* dynamic v static 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/
fre
at the gym at the chosen time.
https://etherpad.openstack.org/p/ocata-climb
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
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/
freen
t_the_Barcelona_Summit.21
--
Chris Dent ┬─┬ノ( º _ ºノ)https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (not for usage question
h other than 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 ┬─┬ノ( º
o trust
people, and we will talk about it all (better than we do now) because 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 ┬─┬ノ( º _ ºノ
pers, users and
operators that we have the capacity to adapt and learn for sake of new
stuff that is good.
[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
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
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
ng the bait to respond in detail to something
like this. But I felt the need to do so.
I'm glad you did. I wish more people would. I really hate the way
that people think communicating is such a drag and a bad thing. I
know more now than I did before I read your message. Surely tha
ork
out the details.
# End
Thanks for reading this far. If you have anything to add or have
questions please post a response.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent_
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
1/
Thanks _very_ much for getting this started.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing Lis
s is useful or could be more useful
please let me know.
--
Chris Dent ¯\_(ツ)_/¯ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Ma
;d prefer to wait 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
that microversions are being used on both sides 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
701 - 771 of 771 matches
Mail list logo