ople who want to use our code. Will it
cause breakage and extra work us now? Possibly, but it's like making
an early payment on the mortgage: We are saving cost later.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
rom there start gathering up
information about the services and then their endpoints.
All of that seems of one piece to me and there should be one way to
do it.
But in the absence of that, this is a good plan.
What do people think?
I think cats are nice and so is this plan.
t seems like Eric and Jay are probably best situated to define
and refine what should really be going on with the resource
tracker and other actions on the compute-node.
* We need to have further discussion and investigation on
allocations getting out of sync. Volunteers?
What else?
[1] https:/
enstack.org/#/c/614896/>
Placement role for ansible project config
* <https://review.openstack.org/#/c/614285/>
hyperv bump placement version
# End
Apologies if this is messier than normal, I'm rushing to get it out
before I travel.
--
Chris Dent ٩◔̯◔۶
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
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:
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
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/#
[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
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
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 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
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
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
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/
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
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
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
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
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
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
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
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.
--
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 ٩◔̯◔۶
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 ٩◔̯◔۶
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
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
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
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
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:
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&#x
o need to
be an existing placement core, everyone with an interest is welcome.
Thanks.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
reenode: cdent tw: @anticdent_
n
thing, so I would hope could be DRYed up a bit. What's the best
way to that?
Thanks very much for any input.
[1] perf logging of a loaded placement: https://review.openstack.org/#/c/602484/
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
uss in too much depth the reasons why we killed meetings
in the first place. How would this meeting be different?
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
HTML: https://anticdent.org/tc-report-18-38.html
Rather than writing a TC Report this week, I've written a report on
the [OpenStack Stein
PTG](https://anticdent.org/openstack-stein-ptg.html).
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode:
/
It works well and is pretty critical in placement because most of
the "important" tests are functional.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
n the meantime if you want to
go looking around, [anything with 'placement' in the commit
mesage](https://review.openstack.org/#/q/message:placement+status:open)
is fun.
Next time I'll provide more detail.
# End
Thanks to
in devstack: Is it
useful to make those changes be guarded by a conditional of the
form:
if placement came from its own repo:
do the new stuff
else:
do the old stuff
?
[1] https://github.com/cdent/placedock
--
Chris Dent
[1] https://pypi.org/project/microversion_parse/
http://git.openstack.org/cgit/openstack/microversion-parse
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
o far.
* Presumably we can trim the placement DB migrations to just stuff
that is relevant to placement
Yah, I would hope so. What possible reason could there be to do otherwise?
Mel's plans looks good to me.
--
Chris Dent ٩◔̯◔۶ h
enstack.org/election/) is
right now. Nomination period ends at the end of the day (UTC) 6th of
September so there isn't much time left. If you're toying with the idea,
nominate yourself, the community wants your input. If you have any
questions please feel free to ask.
--
Chris De
me, again, is painful. Please,
let's not do it.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Deve
n the process of finishing a rename
now.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing List (n
ort placement' to do some openstack stuff,
yeah?
Last I checked the concept of the package name is sort of put off
until we have passing tests, but we're nearly there on that.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
at
one has stopped working too. I'm going to attempt to reconstruct it
today from copies that people.
[2] For certain values of...
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent
t and
functional for py 2.7 and 3.5 and is passing pep8.
More below, in the steps.
On Tue, 28 Aug 2018, Chris Dent wrote:
On Mon, 27 Aug 2018, melanie witt wrote:
1. We copy the placement code into the openstack/placement repo and have it
passing all of its own unit and functional tests.
To
vesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent_
goal here is for OpenStack to be good, as a technical
production _and_ as a community.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent___
that useful.
Thanks for the other info on the devstack and grenade stuff. If I
read you right, from your perspective it's a case of "we'll see" and
"we'll figure it out", which sounds good to me.
--
Chris Dent ٩◔
t (if
you don't send and allocation_ratio) is 1.0, so maybe there's some
code somewhere that is trying to use the default (by not sending)
but is accidentally sending 0 instead?
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
do because of the work over the last year or so
that has been hardening the boundary between placement and nova, in
place. I've been assuming that maintaining the option to use
original conf file is a helpful trick for people. Is that the case?
Thanks.
[1]
https:
g is still horrible, but again: a well
established pattern of use.
This is part of why I think it is better positioned in oslotest as
that signals its limitations.
However, like I said in my other message, copying nova's thing has
proven fine.
--
Chris Dent ٩◔̯◔۶
On Fri, 24 Aug 2018, Chris Dent wrote:
That work is in gerrit at
https://review.openstack.org/#/c/596291/
with a hopefully clear commit message about what's going on. As with
the rest of this work, this is not something to merge, rather an
experiment to learn from. The hot spots i
e
links and leave comments there, in response to this email, or join
#openstack-placement on freenode to talk about it.
Thanks.
[1] https://github.com/cdent/placecat
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cde
t from nova into the
placement extractions experiments with no changes and, as one would
expect, works just fine.
Unless people are wed to doing something else, Dan's right, let's
just do that.
--
Chris Dent ٩◔̯◔۶ https://
/eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-08-20.log.html#t2018-08-20T20:35:51
[3] https://pypi.org/project/microversion_parse/
[4]
http://specs.openstack.org/openstack/api-sig/guidelines/api_interoperability.html
--
Chris Dent ٩◔̯◔۶ ht
t;. It was "we've been trying to do some of
this for two years and if we do it incrementally, the end game is
further away, because it seems us take us forever to do anything."
Perhaps not a huge difference.
--
Chris Dent ٩◔̯◔
Does anyone disagree? If so, who is responsible if not the TC?
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Developme
ent/placedock and some of
the links in the README, the flexibility and lightness may become a
bit more clear.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent___
for so long, and I'm using various
forms of git blame and git log to extract names from the git history
and there's some degree of magic and guessing going on.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent t
appen is the one that makes sure
placement becomes useful to the most people and is worked on by the
most people, as quickly as possible. If how it is arranged as a
project will impact that, now is a good time to figure that out.
If you have thoughts about this, please share them in response.
--
it to something concise after
we've had plenty of input so we have a (small) series of discussion
points to resolve at the PTG.
If this is a topic you think is important or you have an interest
in, please add your thoughts to the etherpad.
--
Chris Dent ٩◔̯◔۶
ion period
will start at the end of this month. If you're considering running
and have any questions, please feel free to ask me.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
matter, please leave something on the
review.
Thanks.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing
enda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
On Wed, 8 Aug 2018, Thomas Goirand wrote:
I'll try to investigate then. However, the way you're suggesting
mandates systemd which is probably not desirable.
"or some other supervisor"
--
Chris Dent ٩◔̯◔۶ https://anticdent.
nged. Also that your bold
assertion that uwsgi doesn't work without paste is only true in the
narrow way in which you are using it (which is the wrong way to use
it).
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cde
there for.
[1] https://github.com/cdent/placedock/blob/master/shared/placement-uwsgi.ini
[2] https://github.com/cdent/placedock
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
I said in IRC a while ago: It doesn't really matter how many of
our projects are using Paste or PasteDeploy: If any of them are,
then we have a problem to address. We already know that some of the
big/popular ones use it. That's enough to require us to work on a
solution.
--
Chris Dent
ally there would be time for both, as the latter is required to
develop the shared language that is needed to take real action. But
as is rampant in the community we are constrained by time and other
responsibilities.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freen
shaping our attention. Also, I pretty
badly need a break and an opportunity to more narrowly focus on
fewer things for a while (you can translate that as "get things done
rather than tracking things"). Unless someone else would like to
pick up the mantle, I expect to pick it back up so
part, not figuring out how to load WSGI
middleware in a modern way.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack
ns, but in terms of
what can be accomplished with the new tooling, we're still not
there).
If our labour is indeed valuable we can choose to exercise greater
control over its direction.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
er at:
https://freenode.net/kb/answer/registration
Plenty of other channels have been doing the same thing, see:
https://etherpad.openstack.org/p/freenode-plus-r-08-2018
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode:
eptember](https://www.openstack.org/ptg), please add to the
[planning etherpad](https://etherpad.openstack.org/p/tc-stein-ptg).
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
On Mon, 30 Jul 2018, Jay Pipes wrote:
On 07/26/2018 12:15 PM, Chris Dent wrote:
The `in_tree` calls happen from the report client method
`_get_providers_in_tree` which is called by
`_ensure_resource_provider` which can be called from multiple
places, but in this case is being called both times
#/c/523006/>
Ignore some updates from virt driver
* <https://review.openstack.org/#/c/584338/>
Docs: Add Placement to Nova system architecture
# End
Lots to review, test, and document.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
've run out of time for now, so this doesn't address the requests
that happen once an instance exists. I'll get to that another time.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticden
pinion and
approach when it comes to accepting projects to be official
OpenStack projects. This is something that will be discussed at the
PTG. It would be helpful if people who care about this could make
their positions known.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org
der forbidden traits in early exit of _get_by_one_request
(Another TODO-related fix)
* <https://review.openstack.org/#/c/583489/>
Remove Ocata comments which expires now
* <https://review.openstack.org/#/c/523006/>
Ignore some updates from virt driver
* <h
ck.org/wiki/API_SIG
[5] https://bugs.launchpad.net/openstack-api-wg
[6] https://git.openstack.org/cgit/openstack/api-wg
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/opens
-model-limitations).
This is a continuation of the technical vision discussions that have
been happening on [an
etherpad](https://etherpad.openstack.org/p/tech-vision-2018) and
[email
thread](http://lists.openstack.org/pipermail/openstack-dev/2018-July/131955.html).
--
Chris Dent
ties to help a project, not punish it or give it a black
mark.
It is important, however, that the TC is making an [independent
evaluation](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-05.log.html#t2018-07-05T15:45:59).
--
Chris Dent ٩◔̯◔۶
is slipped through.
This was reported on testrepository some years ago and a bit of
analysis was done: https://bugs.launchpad.net/testrepository/+bug/1429196
So yeah, I did file a bug but it fell off the radar during those
dark times.
--
Chris Dent ٩◔̯◔۶ https://
On Fri, 6 Jul 2018, Chris Dent wrote:
This is placement update 18-27, a weekly update of ongoing
development related to the [OpenStack](https://www.openstack.org/)
[placement
service](https://developer.openstack.org/api-ref/placement/). This
is a contract version.
Forgot to mention: There
if force_hosts or force_nodes is set
* <https://review.openstack.org/#/c/576820/>
Rename auth_uri to www_authenticate_uri
*
<https://review.openstack.org/#/q/project:openstack/blazar+topic:bp/placement-api>
Blazar's work on using placement
# End
You are the key to the comi
iew.openstack.org/#/c/577118/
[11] https://review.openstack.org/#/c/578369/
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
--
Chris Dent
s usual, one of the main outcomes of that was that we need to make
the time to share and talk more and in a more accessible fashion. We
see bursts of that (we're seeing one now) but how do we sustain it
and how do we extract some agreement that can lead to concerted
action?
--
Chri
On Tue, 3 Jul 2018, Doug Hellmann wrote:
Chris and Thierry have been discussing a technical vision for OpenStack.
* https://etherpad.openstack.org/p/tech-vision-2018
Just so it's clear and credit where credit (or blame!) is due: Zane
has been a leading part of this too.
--
Chris
ng OpenStack in the
face of growth and change. It's quite likely it's junk, but there
may be something useful to extract as we try to achieve some focus.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
Thanks for the notes Matt, I'll try to incorporate this stuff into
the next one where it makes some. A response within.
On Fri, 29 Jun 2018, Matt Riedemann wrote:
On 6/29/2018 8:03 AM, Chris Dent wrote:
There are a patches left on the consumer generation topic, some tidy
ups, and some
s://review.openstack.org/#/c/576693/>
Disable limits if force_hosts or force_nodes is set
* <https://review.openstack.org/#/c/576820/>
Rename auth_uri to www_authenticate_uri
*
<https://review.openstack.org/#/q/project:openstack/blazar+topic:bp/placement-api>
rest in and
enthusiasm for making incremental progress (because if iterating in
code is good and just, perhaps it is in social groups too?) can mean
that we avoid the deeper analysis required for paradigm shifts.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cde
urce_requests field to RequestSpec
* <https://review.openstack.org/#/c/560107/>
normalize_name helper (in os-traits)
* <https://review.openstack.org/#/c/538498/>
Convert driver supported capabilities to compute node provider
traits
* <https://review.openstack.org/#/c/568639/>
thinks it is a good idea, but it is somewhat orthogonal to
the question above about being an external plugin.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent
to be filled in, but it's enough to frame
the idea.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development M
a bit more
context. Thanks for your interest and attention.
[1] https://anticdent.org/placement-container-playground-6.html
[2] https://bugs.launchpad.net/oslo-incubator/+bug/1196368
[3]
http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2018-06-19.log.html#t2018-06-1
er alacrity, what we, as a community, choose
to care about. We've done a pretty good job in the past talking
about things like the [four
opens](https://governance.openstack.org/tc/reference/opens.html),
but now we need to be more explicit about what we are making and h
provider allocation candidates(2)
* <https://review.openstack.org/#/c/538498/>
Convert driver supported capabilities to compute node provider
traits
* <https://review.openstack.org/#/c/568639/>
Use placement.inventory.inuse in report client
* <https://review.openstac
ly for special cases only, for use in extremis only.
--
Chris Dent ٩◔̯◔۶ https://anticdent.org/
freenode: cdent tw: @anticdent__
OpenStack Development Mailing
1 - 100 of 771 matches
Mail list logo
