Thursday, 2018-11-29

*** mriedem has quit IRC00:13
openstackgerritArtom Lifshitz proposed openstack/nova-specs master: Re-propose numa-aware-live-migration spec  https://review.openstack.org/59958700:36
*** tetsuro has joined #openstack-placement00:58
*** tetsuro has quit IRC04:05
*** tetsuro has joined #openstack-placement05:55
*** tetsuro has quit IRC06:40
*** e0ne has joined #openstack-placement07:10
*** tetsuro has joined #openstack-placement07:54
*** tetsuro has quit IRC08:14
*** tetsuro has joined #openstack-placement08:16
*** helenafm has joined #openstack-placement08:17
*** dims has quit IRC08:32
*** dims has joined #openstack-placement08:33
*** ttsiouts has joined #openstack-placement08:34
*** ttsiouts has quit IRC08:36
*** ttsiouts has joined #openstack-placement08:37
*** ttsiouts has quit IRC08:41
*** tetsuro has quit IRC09:08
*** ttsiouts has joined #openstack-placement09:09
*** tssurya has joined #openstack-placement09:27
openstackgerritZhenyu Zheng proposed openstack/nova-specs master: Per aggregate scheduling weight (spec)  https://review.openstack.org/59930809:38
*** cdent has joined #openstack-placement09:39
cdentmoin09:42
*** ttsiouts has quit IRC10:05
*** ttsiouts has joined #openstack-placement10:05
*** ttsiouts has quit IRC10:08
*** ttsiouts has joined #openstack-placement10:08
gibicdent: PS25 from nova and PS3 from https://review.openstack.org/#/c/620617/ passed more than 50 full nova functional run10:32
cdentgibi: I got 77 overnight without 62061710:33
gibiseems your last change in https://review.openstack.org/#/c/619121 helped10:33
cdentyeah10:33
cdentI suspect that was the keystone10:33
gibiOK, then I can drop 62061710:33
cdentwe may wish to consider 620617 as a separate thing if we decide run_once is too inscrutable10:34
gibicdent: I think I will not push for 620617 until another problem hits the same area10:35
cdentI think we can be sure of plenty problems to come of all sorts :)10:35
gibi:)10:35
* gibi runs out for food 10:36
cdentI think you were right yesterday: whatever the root cause has been, we've improved a lot of code trying to get it right10:36
cdentnow all we need are some reviewers10:43
*** ttsiouts has quit IRC11:24
*** ttsiouts has joined #openstack-placement11:24
*** ttsiouts has quit IRC11:32
*** purplerbot has quit IRC11:32
*** purplerbot has joined #openstack-placement11:33
openstackgerritChris Dent proposed openstack/placement master: Allow placement to start without a config file  https://review.openstack.org/61904911:42
*** ttsiouts has joined #openstack-placement11:58
*** takashin has quit IRC12:25
*** ttsiouts has quit IRC12:30
*** ttsiouts has joined #openstack-placement12:31
*** ttsiouts has quit IRC12:32
*** ttsiouts has joined #openstack-placement12:32
*** Nel1x has joined #openstack-placement12:38
*** rubasov has quit IRC12:41
*** rubasov has joined #openstack-placement12:43
cdentjaypipes: in the realm of tiny containers, can you look at https://review.openstack.org/#/c/619049/12:46
jaypipescdent: soon as I'm finished with my second and final ML response of the day. :P12:53
*** e0ne has quit IRC12:53
cdentjaypipes: if the second one as enjoyable as the first...12:54
*** takashin has joined #openstack-placement13:00
jaypipescdent: not sure. see for yourself. ;)13:01
* cdent reads13:02
cdentyup13:04
jaypipescdent: small request on https://review.openstack.org/#/c/619049.13:05
cdentcool, thanks13:05
jaypipescdent: fix'r up and feel free to +W away13:05
jaypipessince giblet was +2 already13:05
jaypipescdent: also, question...13:08
jaypipescdent: are we requiring that version of oslo.cfg in our requirements already?13:08
jaypipescdent: easier to ask then look it up :)13:08
cdentah good catch13:09
cdentwell, actually13:09
cdentthe use of env and the use of no config is orthogonal13:09
cdentbut probably worth updating the reqs anyway13:09
cdentI'll fix both things, and expand the commit message a bit13:10
jaypipescdent: danke13:10
openstackgerritChris Dent proposed openstack/placement master: Allow placement to start without a config file  https://review.openstack.org/61904913:29
cdentgibi, jaypipes ^ updated to be a bit more correct, getting requirements as well13:29
gibicdent: looking...13:29
gibicdent: +213:30
cdentthanks13:30
*** e0ne has joined #openstack-placement13:31
jaypipescdent: +W13:34
cdentyay!13:34
*** ttsiouts has quit IRC13:37
gibinova meeting in two minutes on #openstack-meeting13:58
*** mriedem has joined #openstack-placement14:29
*** ttsiouts has joined #openstack-placement14:30
*** ttsiouts has quit IRC14:47
*** ttsiouts has joined #openstack-placement14:48
*** ttsiouts has quit IRC14:48
*** ttsiouts has joined #openstack-placement14:49
*** takashin has left #openstack-placement15:03
cdentgibi, efried, edleafe, mriedem: I just spent some time perusing coverage results for facebook and found that there are a few methods in objects/resource_provider that have zero coverage (neither unit nor functional). Should I make a) one bug, b) multiple bugs, c) make an email. I don't have time to just fix them right now but don't want it forgotten15:24
efriedcdent: facebook?15:25
* cdent guesses efried had a good breakfast15:25
efriedI have no idea what you're talking about.15:26
edleafecdent: I would prefer a single bug with a listing of the problematic methods15:27
efriedbut a) sounds good to me15:27
efriedyeah, what edleafe said.15:27
cdentwfm, on it15:27
efriedand/or a link to the coverage results15:27
edleafewait - are we on StoryBoard?15:28
* edleafe can never remember15:28
cdentnot yet15:28
cdentwill link to some results15:29
mriedemsingle bug15:29
*** mriedem is now known as mriedem_afk15:29
edleafethis seems like a perfect fit for the stories/tasks model of SB15:30
cdentyes15:32
*** ttsiouts has quit IRC15:32
*** ttsiouts has joined #openstack-placement15:33
cdentthere we go https://bugs.launchpad.net/nova/+bug/180585815:34
openstackLaunchpad bug 1805858 in OpenStack Compute (nova) "placement/objects/resource_provider.py missing test coverage for several methods" [Medium,Triaged]15:34
*** ttsiouts has quit IRC15:37
*** ttsiouts has joined #openstack-placement15:52
*** mriedem_afk is now known as mriedem16:22
*** e0ne has quit IRC16:26
*** rubasov has quit IRC16:28
*** e0ne has joined #openstack-placement16:38
*** e0ne has quit IRC16:48
*** ttsiouts has quit IRC16:51
*** ttsiouts has joined #openstack-placement16:52
*** ttsiouts has quit IRC16:56
openstackgerritJack Ding proposed openstack/nova-specs master: Select cpu model from a list of cpu models  https://review.openstack.org/62095916:58
*** helenafm has quit IRC17:06
guilhermesphello! I'm from openstack-ansible team and we are building our role to manage the installation of placement https://review.openstack.org/#/c/618820/18:34
guilhermespthere are some valuable information that you guys could provide tho18:34
guilhermespwe appreciate any support from you18:35
guilhermespthere are some things that we are still add to that PR, for example, we are not sure which dependencies placement would need https://review.openstack.org/#/c/618820/35/vars/redhat-7.yml18:36
efriedcdent: ^^18:37
efriedand mriedem ^^18:37
guilhermespalso which port placement runs http://logs.openstack.org/20/618820/35/check/openstack-ansible-functional-centos-7/ec63f00/ara-report/result/65e95372-f3ff-4aff-853e-be25b379d6a4/ that we didn't set yet18:37
cdentguilhermesp: ideally it would run on :80/placement or :443/placement but if that is not an option, whatever you like, just make sure it gets set properly in the service catalog18:39
cdentguilhermesp: I'll give that stuff a fresh review tomorrow (off to dinner in a moment) but generally I think you're being a bit of pioneer here. Some of that stuff you'll need to just try and see what works18:40
guilhermespthanks cdent ! Yeah, our role already deals with service catalog18:41
guilhermespit's been challenging but i think we are doing a good progress18:41
cdentgreat to here18:41
cdentand hear too!18:41
guilhermespand als, I think we can make things easy communicating the process of developing via irc channel18:41
guilhermespalso, is that the placement package https://github.com/openstack/placement/blob/4a2a26bf78c404ce962353f938d3582d901d1de6/setup.cfg#L2 ?18:42
cdentyes, that's its name on pypi18:43
cdentpeople thought just "placement" was too generic18:44
guilhermespthat's good. We assume for now that there're no dependencies so, I will just make the correction of the placement port on the PR and see what happens next :)18:45
mnaserguilhermesp: i remember this now but we're actually using some generic port for placement in os_nova .. we should probably use that same one18:52
guilhermespI will take a look at our os_nova role mnaser !18:53
*** e0ne has joined #openstack-placement20:20
*** e0ne has quit IRC20:30
openstackgerritMerged openstack/placement master: Allow placement to start without a config file  https://review.openstack.org/61904920:33
*** cdent has quit IRC21:40
dansmitham I missing something or is https://developer.openstack.org/api-ref/placement/?expanded=update-resource-provider-aggregates-detail#update-resource-provider-aggregates very wrong?21:59
dansmiththe first request and request example don't line up, amirite/21:59
*** mriedem is now known as mriedem_afk22:33
efrieddansmith: looks aight to me, I think. Is the concern that the list is named 'aggregates' in the table, but has no name in the sample?22:42
efriedThe alternative would be what, to leave that table cell blank? Not sure that's less confusing.22:42
dansmithmaybe I'm not used to reading api-refs but yeah that looks really confusing to me22:43
dansmithlike, the example below it looks like I would expect,22:43
dansmithyet the tables look basically the same22:43
dansmithand we have some single-key dict bodies in places which would look like the second example, but identical table to the first22:44
dansmithI would maybe change "aggregates" to "<body>" or something I guess22:44
dansmithanyway, we figured out our issue by just looking at a working client and seeing that it matched the example not the table, but...22:45

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