Wednesday, 2018-11-14

*** efried has joined #openstack-placement05:13
*** efried has quit IRC05:36
*** alex_xu has quit IRC06:11
*** alex_xu has joined #openstack-placement06:14
*** tetsuro has joined #openstack-placement06:30
*** tetsuro has quit IRC07:20
*** mriedem has joined #openstack-placement07:40
*** cdent has joined #openstack-placement08:04
*** e0ne has joined #openstack-placement08:13
mriedemcdent: i've got a debug patch up for that grenade-py3 job failure, not sure what's going on there08:13
cdentI saw your comments on it perhaps being osc-placement08:13
cdentwhich makes sense08:13
cdentand good find if it is that08:14
mriedemdansmith: this is the placement fixture stuff from gibi so nova can continue to use it https://review.openstack.org/#/c/599551/08:14
mriedemi'm going to setup a py3 devstack to mess with that as well08:16
dansmithmriedem: is there a nova-side patch that depends on that to show that it works for nova functional tests?08:18
dansmithI'm a bit fuzzy on how we're going to get the in-master placement bits via pip for our functional tests without needing a release of placement in between every feature that crosses the boundary08:19
cdentdansmith: there's a couple of wips from gibi : https://review.openstack.org/#/c/601641/ and https://review.openstack.org/#/c/599556/ but I'm not sure of the state on those as it's been quite a while08:20
dansmithcdent: so we're going to have placement in our requirements and placement-from-git in our test-requirements?08:21
dansmitheven still, I don't think we'll be able to test nova patches against un-merged placement patches that way08:21
openstackgerritMerged openstack/nova-specs master: Spec: allocation candidates in tree  https://review.openstack.org/60358508:22
cdentI don't recall the details because it's been now months since I was investigating that, but in terms of testing un-merged stuff I think the solution to that is the same as ever: depends-on.08:23
cdentI can pick it back up now that the alembic stuff and other testing stuff has made some progress08:24
dansmithI'm saying I don't think depends-on will fix that unless I'm missing something08:24
dansmithmeaning zuul would have to know to re-write our test-requirements08:24
* cdent is still on his first cup of coffee08:24
cdentso apologies for being slow08:25
cdentbut tox-siblings may be helpful on this08:25
cdentbut I need to refresh my brain08:25
cdenthttps://docs.openstack.org/infra/manual/zuulv3.html#installation-of-sibling-requirements08:27
mriedemi'm not sure the test-requirements thing is going to be an issue,08:28
mriedemi didn't know we had a git link to placement in nova's test-requirements, i'm not sure what that's for,08:28
cdentI think that's just an artifact of gibi's testing, not a thing that will stick around08:29
mriedembut i'd expect placement gets released to pypi, nova's test-requirements depends on placement, and we use depends-on for zuulv3 to pull in and install whatever dependent change we need08:29
dansmithyeah that link from cdent says that zuul will specifically *fix* the venv which would be installed incorrectly from test-requirements08:29
dansmithlike test-requirements will be wrong, install the venv wrong, and then zuul fixes it before we run tests in it08:29
dansmith(wrong in the sense that it won't initially reflect the depends-on)08:30
dansmiththat's definitely different in zuulv3, so I'm just behind on that I guess08:30
cdentit's a) cool and interesting, b) problematic for local dev08:30
dansmithyeah the local dev thing is different and annoying08:31
dansmithbut not unlike other situations we have08:31
mriedemfwiw openstack/placement is already in required-projects for the base dsvm job in zuul08:33
mriedemwe needed that for the grenade stuff08:33
mriedemhttp://git.openstack.org/cgit/openstack-infra/openstack-zuul-jobs/tree/zuul.d/jobs.yaml#n95708:33
cdentanybody know: What's a reasonable base zuul job if you just wanna run a shell script on a simple linux box?08:43
*** e0ne has quit IRC08:47
cdentmriedem: weirdly the output columns are in a different order between py2 and py308:48
cdent2: http://logs.openstack.org/96/617896/1/check/neutron-grenade/a3f2510/logs/grenade.sh.txt.gz#_2018-11-14_08_35_19_46508:48
cdent3: http://logs.openstack.org/96/617896/1/check/grenade-py3/c5c1aba/logs/grenade.sh.txt.gz#_2018-11-14_08_44_04_93608:48
*** e0ne has joined #openstack-placement08:49
*** e0ne has quit IRC08:50
mriedemhmm, some column hash thing in the dict results from osc i'm guessing08:50
* cdent nods08:50
cdentcan we use -c to limit the output further?08:51
*** e0ne has joined #openstack-placement08:51
mriedemi think i asked that on the original grenade change to avoid a lot of the piping and grep'ing and there was a reason for those, but can't remember now, looking it up08:51
* cdent has no cloud handy at the moment08:52
mriedemhttps://review.openstack.org/#/c/597206/6/projects/60_nova/resources.sh@5708:53
mriedemand above that08:53
mriedembut that was on listing providers, not inventory08:54
mriedemi think we can use -c on getting the specific inventory08:54
mriedemi shall push a change08:54
mriedemallocation show won't work with -c b/c the CLI dumps the 'resources' json blob08:55
mriedemso...that's fun08:55
cdent"fun"08:55
*** e0ne has quit IRC08:57
*** e0ne has joined #openstack-placement08:59
*** e0ne has quit IRC09:10
*** e0ne has joined #openstack-placement09:12
*** e0ne has quit IRC09:13
*** e0ne has joined #openstack-placement09:14
*** e0ne has quit IRC09:15
mriedemta da https://review.openstack.org/61791409:21
mriedemwe should maybe add an "openstack resource provider allocation show <consumer_uuid> <resource_class>" CLI09:22
cdentmight make sense, at least for these kinds of things. another option would be to curl and pipe to jq, but I'm drawn that way09:24
*** cdent has quit IRC09:43
*** rubasov has joined #openstack-placement10:04
openstackgerritJim Rollenhagen proposed openstack/nova-specs master: Use conductor groups to partition nova-compute services for Ironic  https://review.openstack.org/60970910:05
*** cdent has joined #openstack-placement10:06
gibicdent, dansmith: making nova unit test run with splited out placement is on my todo list, but lately spent zero time on it unfortunately10:25
gibis/unit/functional/10:26
cdentgibi: do you think you'll be able to get back to it soonish? If not, I can probably pick it up.10:27
gibicdent: not earlier than next week but next week I can spend a day or two on it I think10:29
cdentgibi: okay, cool, if I get a chance before then I might poke at it10:30
gibicdent: are we on the same page about running nova functional test with which version of splitted placement if no depends-on specified? a) master b) last released10:31
cdentbased on the earlier discussion, because of tox-siblings the gate ought/should use master10:31
gibicdent: OK, so we assume we always release nova and placement in synch, that works for me10:32
gibicdent: I will ping you before I start picking up the work next week10:35
cdent10:35
*** rubasov has quit IRC10:36
*** mriedem has quit IRC10:40
cdentgibi: which one of these is the right one? https://review.openstack.org/#/c/599556/ or https://review.openstack.org/#/c/601641/10:41
cdentor is it worth starting over?10:41
cdentor something else? :)10:42
* gibi tries to remember :)10:45
gibicdent: I think my list trials was with https://review.openstack.org/#/c/596291 + https://review.openstack.org/#/c/60164110:46
gibis/list/last/10:46
cdentah, right, I forgot about the one I started, thanks10:51
gibicdent: yeah I started out on a different track first but then ended up going back to your original trial as that was workable10:53
* cdent plays with it10:54
*** e0ne has joined #openstack-placement10:57
*** e0ne has quit IRC11:30
*** cdent has quit IRC11:36
*** cdent has joined #openstack-placement12:12
*** mriedem has joined #openstack-placement12:19
*** tetsuro has joined #openstack-placement12:37
openstackgerritChris Dent proposed openstack/placement master: Adapt placement database fixture for external use  https://review.openstack.org/61793512:46
openstackgerritMerged openstack/nova-specs master: Use conductor groups to partition nova-compute services for Ironic  https://review.openstack.org/60970912:52
*** tetsuro has quit IRC12:57
*** tetsuro has joined #openstack-placement13:01
mriedemcdent: edleafe: i'm hacking on some sqlite model sync testing stuff13:17
mriedemjust fyi13:17
cdentcool, thanks13:17
cdentI'm hacking on external placement nova func tests13:17
cdentand am breaking everything13:18
*** e0ne has joined #openstack-placement13:23
*** tetsuro has quit IRC13:32
mriedemso, we just don't have any models sync testing in the placement change as far as i can see,13:33
mriedemnova gets that by extending an abc from oslo.db13:33
mriedemi mean there is ModelsMigrationSyncMixin13:34
mriedembut it's not being used13:34
mriedemoh nvm i missed it for sqlite13:34
mriedemi see, in nova there is a single mixin which extends both the walk and sync classes from oslo.db, so nova just has a single set of sqlite/mysql/pg tests which run both the walk versions and models sync tests13:37
*** tetsuro has joined #openstack-placement13:37
cdenti (very briefly) tried to make a subclass that used 'sqlite' as the driver but hit some bumps and then had to leave the room I was in13:37
*** e0ne has quit IRC13:38
mriedemgot it13:40
mriedemworking for sqlite i mean13:40
cdenthuzzah13:42
*** openstackgerrit has quit IRC13:51
mriedemi'll update and rebase the series13:52
*** openstackgerrit has joined #openstack-placement13:54
openstackgerritChris Dent proposed openstack/placement master: Adapt placement database fixture for external use  https://review.openstack.org/61793513:54
*** tetsuro has quit IRC13:55
*** tetsuro has joined #openstack-placement13:55
openstackgerritMatt Riedemann proposed openstack/placement master: Added alembic environment  https://review.openstack.org/61435013:59
openstackgerritMatt Riedemann proposed openstack/placement master: Delete the old migrations  https://review.openstack.org/61144013:59
openstackgerritMatt Riedemann proposed openstack/placement master: Add a document for creating DB revisions  https://review.openstack.org/61402413:59
openstackgerritMatt Riedemann proposed openstack/placement master: Remove sqlalchemy-migrate from requirements.txt  https://review.openstack.org/61453913:59
openstackgerritMatt Riedemann proposed openstack/placement master: Add a placement-manage CLI  https://review.openstack.org/60016113:59
cdentmriedem: that's almost exactly the same as what I did, but I hadn't got the db url quite right14:02
cdentsoo...yay14:02
*** tetsuro has quit IRC14:07
*** tetsuro has joined #openstack-placement14:11
*** efried has joined #openstack-placement14:16
cdentedleafe: you around today?14:25
edleafeyep14:26
cdentyou want to handle matt's final (?) comments on the alembic stuff?14:27
edleafeI looked at that earlier, before those comments. I should have time to address them before I descend into meeting hell.14:28
mriedemthe only hangup i seem to have is the initial empty placeholder migration,14:33
mriedemi'm not sure if that's just something with the sqlite backend or what14:34
mriedemlemme run it in isolation14:34
*** e0ne has joined #openstack-placement14:35
mriedemi suspect there might be a sqlite db from a previous run that's not cleaned up14:36
edleafemriedem: the test calls "self.migration_api.upgrade('158782c7f38c')", and you removed migration 158782c7f38c, so that exception should be expected.14:36
mriedemoh nvm14:36
mriedemi'm just dumb14:36
mriedemyup14:36
mriedemheh14:36
edleafemriedem: I just changed that to "self.migration_api.upgrade('base')", and that seems to work14:37
mriedemok sec14:37
mriedemi've got this change locally so i can just update and rebase if you're ok with that14:37
mriedemor you can if you're going to handle any other comments14:37
mriedemyup base works14:38
edleafeYou also have to change the initial migration to have "down_revision = None"14:39
mriedemi did,14:39
mriedemi pasted my diff in the review comments14:39
mriedemi'll let you do whatever you're going to update based on my comments14:39
edleafek14:40
cdentefried, mriedem : If we get a chance to talk to belmoria before he leaves before lunch tomorrow about the how's and why's of what's going on with all the info that the reource tracker is moving back and forth to/fro placement that would probably be useful for all of us14:41
mriedemwas b4ed3a175331_initial.py generated from the models?14:41
efried++14:41
mriedemif so, i didn't realize it was auto-generated14:42
efrieddo you have a line on where he might be hanging out?14:42
edleafemriedem: yeah, alembic generated that14:42
edleafemriedem: that's why cdent didn't want to edit it14:42
mriedemedleafe: ok, i didn't realize, i thought those scripts were hand generated14:42
mriedemsorry about the noise on that one then14:42
mriedemyeah14:42
mriedemdidn't realize14:42
edleafeBut as I commented, it is designed to be modified, so I prettied it up14:43
edleafejust for you!14:43
mriedem<314:43
cdentefried: he was "in the hall" just now, but he indicated that email would be a useful way to contact him14:44
*** tetsuro has quit IRC14:44
mriedemwould be nice if using email, it could be on the ML14:45
mriedemrather than private14:45
mriedemunless there are sensitive details he doesn't want to expose14:45
mriedemunless it's "wtf is going on, this is so complicated we don't know how to maintain it" and that might hurt feelings14:46
cdentno, it was a case of "let's have a chat in person somewhere here because we have the opportunity"14:46
*** tetsuro has joined #openstack-placement14:48
*** e0ne has quit IRC14:51
*** tetsuro has quit IRC14:56
*** mriedem has quit IRC15:06
*** cdent has quit IRC15:09
*** N3l1x has joined #openstack-placement15:10
*** cdent has joined #openstack-placement15:12
*** mriedem has joined #openstack-placement15:20
mriedemcdent: efried: i talked to belmiro15:20
mriedemi think he was ok with my answers15:20
mriedemand then he gave me 2 other issues to worry about15:20
cdentyeah, that's why I thought it would be good to have a sit down15:20
cdentbecause he gave me a few too15:21
*** e0ne has joined #openstack-placement15:22
*** efried has quit IRC15:26
openstackgerritmelanie witt proposed openstack/nova-specs master: Propose counting quota usage from placement and API database  https://review.openstack.org/50904215:29
openstackgerritEd Leafe proposed openstack/placement master: Added alembic environment  https://review.openstack.org/61435015:31
openstackgerritEd Leafe proposed openstack/placement master: Delete the old migrations  https://review.openstack.org/61144015:31
openstackgerritEd Leafe proposed openstack/placement master: Add a document for creating DB revisions  https://review.openstack.org/61402415:31
openstackgerritEd Leafe proposed openstack/placement master: WIP - Show an alembic migration  https://review.openstack.org/61402515:31
edleafemriedem: cdent: ^^ Placeholder migration is no more15:32
mriedemedleafe: so close...15:35
mriedemIf you want to tack on a follow up i'll +215:35
cdentas far as I can tell the nova-functional jobs aren't doing tox siblings15:36
edleafemriedem: I'll FUP it15:36
*** tetsuro has joined #openstack-placement15:37
mriedemedleafe: ok15:39
mriedem+215:39
cdentyay15:40
openstackgerritEd Leafe proposed openstack/placement master: Fix comment in earlier patch  https://review.openstack.org/61798815:40
edleafemriedem: FUP^^15:41
openstackgerritTakashi NATSUME proposed openstack/placement master: Remove build-openstack-api-ref jobs  https://review.openstack.org/61449715:46
cdentwowser, stephenfin, shared tox envs and zuul's tox_install_siblings behavior conflicts:15:50
cdentenvdir does not exist, skipping siblings15:51
cdentoops: http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/tox/library/tox_install_sibling_packages.py#n17215:51
openstackgerritChris Dent proposed openstack/placement master: Remove sqlalchemy-migrate from requirements.txt  https://review.openstack.org/61453915:53
openstackgerritChris Dent proposed openstack/placement master: Add a placement-manage CLI  https://review.openstack.org/60016115:53
stephenfincdent: I assume the whoops means different issue?16:00
cdentstephenfin: no, the oops was that I pasted the error message, not to the code that causes it. The problem is for real16:00
cdentthe diff between revisions 5 and 6 on https://review.openstack.org/#/c/617941/ fixes it16:01
stephenfincdent: Sounds like something you should ping mordred about. I know very little about this whole siblings thing16:02
cdentstephenfin I will, but for the time being I'll leave the tox.ini change in place. It's going to be hard for siblings to do what it does without what amounts to consistent naming16:03
stephenfinYeah, that sounds fair. Maybe add a TODO too, just for future reference?16:04
stephenfinLest we forget to investigate it16:04
cdentyeah, I'll tidy it up after I see it actually work...16:04
*** cdent has quit IRC16:06
*** irclogbot_2 has quit IRC16:08
*** mriedem has quit IRC16:10
*** mriedem has joined #openstack-placement16:12
*** irclogbot_2 has joined #openstack-placement16:17
*** tetsuro has quit IRC16:26
mriedemshould be easy to cleanup the alembic docs change https://review.openstack.org/#/c/614024/16:29
*** e0ne has quit IRC16:33
edleafemriedem: Not sure I understand the reason for a separate doc. All the contributor docs are in one place: http://logs.openstack.org/24/614024/19/check/openstack-tox-docs/76a4e0c/html/contributor/index.html. What would be the advantage of replacing the last section with a link?16:34
*** dims has quit IRC16:37
*** dims has joined #openstack-placement16:41
mriedemedleafe: it's just a subdoc16:41
mriedemhttps://github.com/openstack/nova/tree/master/doc/source/contributor16:41
mriedemso the index page doesn't hold everything ever, it's for organizing16:42
edleafemriedem: yeah, I can see why that's better, but that sort of refactoring isn't what this patch is doing. Placement isn't set up like that (not yet, anyway) https://github.com/openstack/placement/tree/master/doc/source/contributor16:43
*** cdent has joined #openstack-placement16:46
mriedemit's not a refactor16:47
mriedemcreate doc/source/contributor/db_schema_migrations.rst16:47
mriedemyou just add a section to index.rst that ref's the db_schema_migrations doc16:47
mriedemdon't get hung up on that comment, i can just refactor it later in a follow up, just fix the content issues16:48
edleafeIt would be nice to refactor those docs like nova's are, but that can be done later.16:49
*** mriedem has quit IRC16:53
openstackgerritEd Leafe proposed openstack/placement master: Add a document for creating DB revisions  https://review.openstack.org/61402417:19
edleafemrieden: ^^ cleaned up17:20
openstackgerritChris Dent proposed openstack/placement master: Adapt placement database fixture for external use  https://review.openstack.org/61793517:32
cdentedleafe: that ^ is probably going to conflict with the alembic changes, but not in any horrible way, and it will come out in the wash cleanly enough17:35
cdentand now it is dinner time17:35
edleafecdent: Remember you have to drink my share of beer, too17:36
cdenti know, I had a very large one yesterday, does that help?17:37
edleafea little <sob!>17:37
cdentI'LL TRY HARDER17:38
* cdent waves17:38
*** cdent has quit IRC17:38
edleafeo/17:38
openstackgerritEd Leafe proposed openstack/placement master: Consider root id is None in the database case  https://review.openstack.org/61332018:16
*** tetsuro has joined #openstack-placement20:23
*** tetsuro has quit IRC20:25
openstackgerritChris Dent proposed openstack/placement master: Adapt placement database fixture for external use  https://review.openstack.org/61793522:19
*** e0ne has joined #openstack-placement22:35
*** e0ne has quit IRC22:36
*** e0ne has joined #openstack-placement23:02
*** e0ne has quit IRC23:35

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!