Wednesday, 2018-09-05

*** macza has quit IRC00:02
openstackgerritElancheran S proposed openstack/nova stable/pike: Add exact match aggregate image properties matcher/filter  https://review.openstack.org/59987000:13
openstackgerritElancheran S proposed openstack/nova master: Add exact match aggregate image properties matcher/filter  https://review.openstack.org/59316700:21
*** spartakos has quit IRC00:40
*** markvoelker has joined #openstack-nova00:42
*** markvoelker has quit IRC00:47
openstackgerritfupingxie proposed openstack/nova master: Delete allocations for instances that have been moved to another node  https://review.openstack.org/58289900:59
openstackgerritMatt Riedemann proposed openstack/nova master: Fix nova-status "_check_resource_providers" check  https://review.openstack.org/59987501:00
*** itlinux is now known as itlinux-away01:02
openstackgerritfupingxie proposed openstack/nova master: Add an example to add more pci devices in nova.conf  https://review.openstack.org/59224301:04
*** ivve has quit IRC01:06
openstackgerritSam Morrison proposed openstack/nova master: Fix DB archiver AttributeError due to wrong table name attribute used  https://review.openstack.org/59987801:09
*** ivve has joined #openstack-nova01:19
*** itlinux-away is now known as itlinux01:22
openstackgerritSam Morrison proposed openstack/nova stable/rocky: Fix DB archiver AttributeError due to wrong table name attribute used  https://review.openstack.org/59988101:23
openstackgerritSam Morrison proposed openstack/nova stable/queens: Fix DB archiver AttributeError due to wrong table name attribute used  https://review.openstack.org/59988201:24
*** moshele has joined #openstack-nova01:25
openstackgerritSam Morrison proposed openstack/nova stable/pike: Fix DB archiver AttributeError due to wrong table name attribute used  https://review.openstack.org/59988301:26
*** hongbin_ has joined #openstack-nova01:26
openstackgerritSam Morrison proposed openstack/nova stable/ocata: Fix DB archiver AttributeError due to wrong table name attribute used  https://review.openstack.org/59988501:27
prometheanfiremriedem: :D, not sure I can test it now without a rollback, but that else thing sounds right01:28
openstackgerritMatt Riedemann proposed openstack/nova master: Configure placement DB context manager for nova-manage/status  https://review.openstack.org/59974401:30
mriedemprometheanfire: here is the 2nd part of that ^01:30
mriedemthat should fix both the nova-status and nova-manage parts that hit the placement tables01:30
mriedemi have my devstack patch updated and should fail, and then i'll apply that patch to show it passing01:31
prometheanfirecool01:32
*** macza has joined #openstack-nova01:34
mriedemand with that i need to get the hell off this computer01:35
*** mriedem is now known as mriedem_afk01:35
*** cfriesen has joined #openstack-nova01:37
*** macza has quit IRC01:38
*** tbachman has joined #openstack-nova01:41
prometheanfirecya :D01:41
*** markvoelker has joined #openstack-nova01:43
mriedem_afkprometheanfire: yup devstack failed as expected http://logs.openstack.org/47/599847/2/check/tempest-full/d3ee11e/controller/logs/devstacklog.txt.gz#_2018-09-05_01_24_22_18701:46
prometheanfirewoo01:50
*** r-daneel has joined #openstack-nova01:53
*** spartakos has joined #openstack-nova01:56
*** Dinesh_Bhor has joined #openstack-nova01:57
*** gyee has quit IRC02:12
openstackgerritMerged openstack/nova master: Other host allocs may appear in gafpt during evac  https://review.openstack.org/59730102:14
*** sambetts_ has quit IRC02:16
openstackgerritSam Morrison proposed openstack/nova master: Allow ability for non admin users to use all filters on server list.  https://review.openstack.org/52655802:17
*** sambetts_ has joined #openstack-nova02:19
*** moshele has quit IRC02:20
*** threestrands has joined #openstack-nova02:22
*** ykarel|away is now known as ykarel02:28
*** lei-zh has joined #openstack-nova02:29
*** gbarros has joined #openstack-nova02:31
*** erlon has quit IRC02:31
*** lbragstad has quit IRC02:39
openstackgerritfupingxie proposed openstack/nova master: Delete allocations for instances that have been moved to another node  https://review.openstack.org/58289902:43
*** gbarros has quit IRC02:45
*** dave-mccowan has quit IRC02:45
*** dave-mccowan has joined #openstack-nova02:50
*** itlinux is now known as itlinux-away02:51
*** psachin has joined #openstack-nova02:58
*** itlinux-away is now known as itlinux03:00
*** psachin has quit IRC03:04
openstackgerrithuanhongda proposed openstack/nova-specs master: Return "deleted" and "estimated_reclaim" time of instance for admin  https://review.openstack.org/58163803:09
*** med_ has quit IRC03:26
*** erlon has joined #openstack-nova03:33
*** hongbin_ has quit IRC03:46
*** Dinesh_Bhor has quit IRC03:48
*** udesale has joined #openstack-nova03:54
*** Dinesh_Bhor has joined #openstack-nova03:56
*** spartakos has quit IRC03:57
*** vivsoni has joined #openstack-nova03:58
*** Dinesh_Bhor has quit IRC04:07
*** itlinux has quit IRC04:07
openstackgerrithuanhongda proposed openstack/nova-specs master: Return "deleted" and "estimated_reclaim" time of instance for admin  https://review.openstack.org/58163804:18
*** lei-zh has quit IRC04:23
*** ykarel has quit IRC04:25
*** ykarel has joined #openstack-nova04:25
*** itlinux has joined #openstack-nova04:26
*** cfriesen has quit IRC04:27
*** wznoinsk has quit IRC04:30
*** NostawRm has quit IRC04:30
*** jamiec has quit IRC04:30
*** edleafe has quit IRC04:31
*** jamiec has joined #openstack-nova04:34
*** bandini has quit IRC04:37
*** tonyb has quit IRC04:40
*** tonyb has joined #openstack-nova04:40
*** Dinesh_Bhor has joined #openstack-nova04:41
*** bhagyashris_ has joined #openstack-nova04:45
*** dave-mccowan has quit IRC04:48
*** macza has joined #openstack-nova04:50
*** macza has quit IRC04:55
*** bhagyashris_ has quit IRC05:04
*** vivsoni has quit IRC05:05
*** markvoelker has quit IRC05:13
*** lei-zh has joined #openstack-nova05:14
*** bandini has joined #openstack-nova05:32
*** pooja-jadhav has joined #openstack-nova05:33
*** ykarel has quit IRC05:35
*** ykarel has joined #openstack-nova05:36
*** ykarel has quit IRC05:38
*** ykarel has joined #openstack-nova05:39
pvchi guys05:40
*** ykarel has quit IRC05:41
*** ykarel has joined #openstack-nova05:41
*** sahid has joined #openstack-nova05:47
*** Luzi has joined #openstack-nova05:47
*** jiapei has joined #openstack-nova05:48
*** artom has joined #openstack-nova05:54
*** moshele has joined #openstack-nova05:58
gmannalex_xu: ping06:00
gmannalex_xu: i am back from PTO on monday. do not have much to discuss for API office hour. do you have anything or we start it after PTG when we have exact priority items for stein ?06:02
*** holser_ has joined #openstack-nova06:09
*** markvoelker has joined #openstack-nova06:10
*** pcaruana has joined #openstack-nova06:23
*** Bhujay has joined #openstack-nova06:25
*** Bhujay has quit IRC06:26
*** Bhujay has joined #openstack-nova06:26
*** luksky has joined #openstack-nova06:30
*** nnsingh has joined #openstack-nova06:34
*** fanzhang has joined #openstack-nova06:38
*** ykarel is now known as ykarel|afk06:47
*** adrianc has joined #openstack-nova06:48
*** sambetts_ has quit IRC06:52
*** Shilpa has joined #openstack-nova06:58
*** sambetts_ has joined #openstack-nova07:01
*** bhagyashris_ has joined #openstack-nova07:04
*** rcernin has quit IRC07:04
*** itlinux is now known as itlinux-away07:04
*** itlinux-away is now known as itlinux07:05
*** itlinux is now known as itlinux-away07:05
*** tssurya has joined #openstack-nova07:08
tssuryagmann: sorry for the rebases of https://review.openstack.org/#/c/585475 and https://review.openstack.org/#/c/592092, it was because I wanted the whole series to be on top of some latest commits that got merged,07:10
gmanntssurya: no issue, anyways i will continue work on those from tomorrow.07:15
openstackgerritBrin Zhang proposed openstack/nova master: Resource retrieving: add changes-before filter  https://review.openstack.org/59927607:18
*** itlinux-away is now known as itlinux07:18
*** itlinux is now known as itlinux-away07:18
*** adrianc has quit IRC07:20
*** janki has joined #openstack-nova07:21
*** itlinux-away is now known as itlinux07:21
*** itlinux is now known as itlinux-away07:21
*** itlinux-away is now known as itlinux07:23
*** itlinux is now known as itlinux-away07:23
*** itlinux-away is now known as itlinux07:31
*** itlinux is now known as itlinux-away07:31
*** itlinux-away is now known as itlinux07:33
*** itlinux is now known as itlinux-away07:33
*** ykarel|afk is now known as ykarel07:33
*** tetsuro has joined #openstack-nova07:35
*** itlinux-away is now known as itlinux07:35
*** itlinux is now known as itlinux-away07:35
*** adrianc has joined #openstack-nova07:40
*** alexchadin has joined #openstack-nova07:41
*** itlinux-away is now known as itlinux07:45
*** itlinux is now known as itlinux-away07:45
*** jpena|off is now known as jpena07:45
alex_xugmann: sorry, too busy this afternoon, forget to online07:51
*** ccamacho has joined #openstack-nova07:51
gmannalex_xu: np07:56
openstackgerritTushar Patil proposed openstack/nova-specs master: Allow overcommit of dedicated CPU  https://review.openstack.org/59995708:01
*** jaosorior has quit IRC08:03
*** itlinux-away is now known as itlinux08:03
*** itlinux is now known as itlinux-away08:03
*** jaosorior has joined #openstack-nova08:05
*** itlinux-away is now known as itlinux08:14
*** itlinux is now known as itlinux-away08:14
*** amarao has joined #openstack-nova08:15
*** bhagyashris_ has quit IRC08:16
tssuryagmann: thanks,08:18
*** alex_xu has quit IRC08:18
*** alex_xu has joined #openstack-nova08:20
*** luksky has quit IRC08:21
*** cdent has joined #openstack-nova08:25
*** threestrands has quit IRC08:26
*** macza has joined #openstack-nova08:26
*** Bhujay has quit IRC08:30
*** ttsiouts has joined #openstack-nova08:31
*** macza has quit IRC08:31
*** dtantsur|afk is now known as dtantsur08:35
*** Bhujay has joined #openstack-nova08:35
*** priteau has quit IRC08:42
*** priteau has joined #openstack-nova08:43
*** derekh has joined #openstack-nova08:44
*** itlinux-away is now known as itlinux08:44
*** itlinux is now known as itlinux-away08:44
*** ttsiouts has quit IRC08:46
*** pcaruana has quit IRC08:50
*** ttsiouts has joined #openstack-nova08:54
stephenfinkashyap: Sorry about the delay - not sure how I missed your ping yesterday. This is the output requested http://paste.openstack.org/show/729478/08:56
*** psachin has joined #openstack-nova08:56
pvchi08:56
pvccan anyone help me08:57
pvcit seems my server doesnt get the ip address from the metadata so icant ping it08:57
stephenfinkashyap: That's with 'hw_machine_type = x86_64=q35' and 'num_pcie_ports = 8' in '[libvirt]'08:57
kashyapstephenfin: No worries about the delay at all.  Was just refrehsing my DevStack env (after the goddamned dentist visit)08:57
pvchi anyone can help ?08:57
pvc Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f9b8ad30d30>: Failed to establish a new connection: [Errno 101] Network is unreachable',))]08:57
kashyapstephenfin: BTW, does the spacing affect at all?08:57
stephenfinkashyap: Spacing?08:58
stephenfinpvc: You'd have much better luck asking this on #openstack08:58
kashyapstephenfin: I mean, extra space between the config attribute values08:58
stephenfinkashyap: It shouldn't, no08:58
kashyapstephenfin: Excellent.  So why I asked for '8' was:08:59
stephenfinkashyap: Well, between the key and value. I wouldn't be so sure about spaces between the stuff on the value side (i.e. x86_64=q35) because that's not handled by oslo.config08:59
kashyapstephenfin: libvirt will ignore '2', because it will anyway give four PCIe ports: one for disk, n/w interface, memory balloon and RNG device09:00
kashyapstephenfin: So setting '8' should give us a few extra ports for hot-plugging, etc.09:00
kashyapstephenfin: I see, noted09:00
kashyapThanks for the quick test; great timing!09:00
stephenfinkashyap: Yup, I was thinking there was a lower bound on what you could set. I wonder if we should note that in the docs?09:01
stephenfinkashyap: though I guess it doesn't really matter, if we're being honest09:01
kashyapNoting in the docs will certainly be clearer09:03
kashyap(For the rare species that _do_ go and read the docs.)09:03
*** davidsha has joined #openstack-nova09:09
*** ttsiouts has quit IRC09:15
*** aloga has quit IRC09:27
*** aloga has joined #openstack-nova09:27
*** Dinesh_Bhor has quit IRC09:31
*** erlon has quit IRC09:35
*** Dinesh_Bhor has joined #openstack-nova09:43
*** tetsuro has quit IRC09:47
*** lei-zh has quit IRC09:51
*** tetsuro has joined #openstack-nova09:54
*** adrianc has quit IRC09:55
*** pcaruana has joined #openstack-nova09:58
*** slaweq_ is now known as slaweq10:00
*** zigo has joined #openstack-nova10:00
zigoI got new unit test failures when building Nova in Sid: http://paste.openstack.org/show/729497/10:02
*** adrianc has joined #openstack-nova10:04
*** tbachman has quit IRC10:07
cdentzigo: not surprised to see those, people have been slow to get on 3.6, let alone 3.710:13
*** luksky has joined #openstack-nova10:13
*** alexchadin has quit IRC10:17
gibifyi, I'm going offline soon and travelling to Denver tomorrow.10:18
*** udesale has quit IRC10:21
*** tbachman has joined #openstack-nova10:21
*** udesale has joined #openstack-nova10:21
*** udesale has quit IRC10:21
*** udesale has joined #openstack-nova10:22
*** tbachman has quit IRC10:23
pvc[FAILED] Failed to start Raise network interface10:35
cdentsafe travels gibi. Are you doing a bit of tourism in Denver?10:36
*** adrianc has quit IRC10:37
gibicdent: thanks. Yes, my wife and I will be up in the Rockies between Thurday-Sunday10:38
cdentexcellent. There are some _amazing_ places in the rockies. which part you going to?10:38
openstackgerritMerged openstack/nova stable/rocky: Remove noisy DEBUG log  https://review.openstack.org/59626410:39
zigocdent: Do you think it'd have impact on production?10:46
*** pvc has quit IRC10:46
cdentzigo: I'm not sure, I didn't have a chance to look very closely, I'm sort of all over the place this morning.10:46
* cdent looks again10:46
* zigo don't really care xenapi bugs btw10:47
gibicdent: Estes Park will be our home base and we will do some walking around in the National Park10:48
*** gibi is now known as gibi_off10:48
cdentyay, great place10:48
zigoSo, I care only about the first 2 unit test failures in fact.10:50
*** alexchadin has joined #openstack-nova10:50
cdentzigo: it's hard to say. It seems there's an issue in code we don't really see in the paste with how regular expressions are being used. whether that will impact production situations is non-obvious. those tests are not familiar to me. You may as well at least make a bug about it?10:51
zigocdent: Sure, will do, thanks!10:51
cdentthanks for your continued attention to the future10:52
zigohttps://bugs.launchpad.net/nova/+bug/179084710:54
openstackLaunchpad bug 1790847 in OpenStack Compute (nova) "Faiing tests when building Rocky Debian package in Python 3.7" [Undecided,New]10:54
zigocdent: Your future is my present when I upload to Sid ! :)10:54
zigoI'll file 2 other bugs for the xenapi and hacking tests.10:54
zigoOh, that makes me think: the issues I'm seeing with hacking are probably due to the new hacking version we've uploaded yesterday, and maybe same with os-xenapi.10:56
zigoThe xenapi stuff maybe is related to OpenSSL 1.1.1.10:58
zigohttps://bugs.launchpad.net/nova/+bug/179085010:59
openstackLaunchpad bug 1790850 in OpenStack Compute (nova) "Xenapi test failure when building the Debian 18.0.0 package in Sid" [Undecided,New]10:59
zigohttps://bugs.launchpad.net/nova/+bug/179084910:59
openstackLaunchpad bug 1790849 in OpenStack Compute (nova) "Faiing hacking tests when building Rocky Debian package under Python 3.7" [Undecided,New]10:59
*** erlon has joined #openstack-nova10:59
*** jamesdenton has quit IRC11:01
*** erlon_ has joined #openstack-nova11:02
*** ttsiouts has joined #openstack-nova11:03
*** erlon has quit IRC11:03
*** erlon_ has quit IRC11:04
*** erlon has joined #openstack-nova11:05
*** tetsuro has quit IRC11:05
*** erlon has quit IRC11:06
*** tetsuro has joined #openstack-nova11:06
*** dtantsur is now known as dtantsur|brb11:08
openstackgerritBrin Zhang proposed openstack/nova master: Resource retrieving: add changes-before filter  https://review.openstack.org/59927611:09
*** Dinesh_Bhor has quit IRC11:09
*** udesale has quit IRC11:10
*** kaliya has joined #openstack-nova11:18
*** luksky has quit IRC11:21
kashyapstephenfin: A quick question: Can you post what libvirt and QEMU versions you used to generate that test?11:22
*** kaliya has quit IRC11:23
*** erlon has joined #openstack-nova11:23
*** luksky has joined #openstack-nova11:24
*** kaliya has joined #openstack-nova11:24
*** kaliya has quit IRC11:29
*** eharney has quit IRC11:32
*** nicolasbock has joined #openstack-nova11:32
*** jpena is now known as jpena|lunch11:36
*** jamesdenton has joined #openstack-nova11:41
*** zigo has quit IRC11:45
*** dave-mccowan has joined #openstack-nova11:47
*** cfriesen has joined #openstack-nova11:47
openstackgerritMerged openstack/nova master: Don't persist zero allocation ratios in ResourceTracker  https://review.openstack.org/59836511:50
openstackgerritMerged openstack/nova master: Document unset/reset wrinkle for *_allocation_ratio options  https://review.openstack.org/59967011:50
*** helenafm has joined #openstack-nova11:52
*** odyssey4me has quit IRC11:53
*** tetsuro has quit IRC11:55
*** lbragstad has joined #openstack-nova11:57
*** tbachman has joined #openstack-nova12:00
*** gcb_ has joined #openstack-nova12:01
*** macza has joined #openstack-nova12:01
*** med_ has joined #openstack-nova12:03
*** moshele has quit IRC12:06
*** macza has quit IRC12:08
*** odyssey4me has joined #openstack-nova12:08
*** ttsiouts has quit IRC12:09
*** markvoelker has quit IRC12:09
*** ttsiouts has joined #openstack-nova12:10
*** moshele has joined #openstack-nova12:11
*** cfriesen has quit IRC12:12
openstackgerritChris Dent proposed openstack/nova-specs master: List resource providers having inventory  https://review.openstack.org/60001612:12
*** moshele has quit IRC12:13
*** tbachman has quit IRC12:16
*** tbachman has joined #openstack-nova12:24
*** tbachman has quit IRC12:28
*** ttsiouts has quit IRC12:31
*** edleafe has joined #openstack-nova12:32
*** ttsiouts has joined #openstack-nova12:34
*** tbachman has joined #openstack-nova12:35
efriedō/12:37
*** FoXMaN has quit IRC12:37
sean-k-mooneyefried: how are you o/12:37
sean-k-mooneyall set for ptg next week?12:37
efriedsean-k-mooney: Today is my birthday. Yes, as ready as I'm gonna be.12:38
sean-k-mooneycongrats, or commiserations depending on the cardonality of said event :)12:39
sean-k-mooneyin either case happy birthday.12:39
efried42, the Answer to the Ultimate Question of Life, the Universe, and Everything12:39
efriedthanks12:39
sean-k-mooneyalso the flvour id for m1.nano12:40
tssuryaefried: happy wishes12:40
stephenfinkashyap: libvirtd (libvirt) 4.0.012:40
efriedthanks tssurya :)12:40
stephenfinkashyap: QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.4~cloud0)12:40
stephenfinkashyap: (That's a DevStack deployment on Ubuntu 16.04)12:40
*** jpena|lunch is now known as jpena12:41
*** brinzhang has quit IRC12:41
sean-k-mooneystephenfin: you should really swap to 18.04 at somepoint but proably after the gate does12:42
stephenfinsean-k-mooney: Yeah, the choice of 16.04 was intentional for that reason12:42
*** brinzhang has joined #openstack-nova12:42
sean-k-mooneystephenfin: efried by the way i assume i need a spec rather than just a blueprint for sirov attach?12:45
*** jangutter has joined #openstack-nova12:45
stephenfinsean-k-mooney: I would think so, yes12:45
sean-k-mooneyspecificly via neutron port of vnic-type=direct|macvtap|driect-pyhical and maybe virtio-forwarder12:46
stephenfinjangutter: You asked me to look at some netronome os-vif patches a while back, but I think someone asked for a spec and it was deferred to stein. Is my recollection of events correct and, if so, is there a spec I can review?12:46
stephenfinsean-k-mooney: A spec would probably be a good idea if only so you can explain how one intends to solve the issue, assuming this is more than a one patch change (which I think it is)12:47
jangutterstephenfin: Yep, your recollection is correct, and sadly nothing new to review.12:47
openstackgerritJan Gutter proposed openstack/nova-specs master: Spec to implement vRouter HW offloads  https://review.openstack.org/56714812:48
*** brinzhang has quit IRC12:48
jangutterstephenfin: I'm just re-proposing the rocky spec to Stein (with some light updates as to what occurred thus far...)12:48
efriedsean-k-mooney: I started typing questions to figure out whether I thought a spec was necessary12:48
efriedsean-k-mooney: but there were enough of them and they were open-ended enough that the answer is obviously yes.12:49
stephenfinjangutter: ack12:49
sean-k-mooneystephenfin: for https://review.openstack.org/#/c/572081/12:49
jangutterstephenfin: apologies, I've been deep in the guts of bootstrapping a CI on our side. It's surprisingly fun, and also surprisingly time consuming.12:49
stephenfinjangutter: It's alllll good12:49
sean-k-mooneyefried: ya there was a spec for this in the past. i had assumed i would need wone but i just had not gotten around to it12:50
sean-k-mooneyjangutter: how closely have you been following the cyborg proposals? will you be at the ptg?12:51
jangutterwhat the heck, how did you guys start discussing the stuff I want to talk about after about 2 weeks of absence right as I log on?12:51
*** tetsuro has joined #openstack-nova12:51
janguttersean-k-mooney: yep I'll be at PTG for the week.12:52
kashyapstephenfin: Most excellent; thanks!12:52
janguttersean-k-mooney: could I convince a couple of people to knock heads together so we can get this "offload abstraction layer" up to the standards of jaypipes?12:52
janguttersean-k-mooney: to be honest, I've had only the briefest glances re: cyborg. what's the latest?12:53
*** moshele has joined #openstack-nova12:53
sean-k-mooneyjangutter: i can take a look if that will help.12:54
sean-k-mooneyjangutter: not much has changed but i have stared to look into it alot more closely in the last week or two12:54
sean-k-mooneyjangutter: i am hoping that we can make significat progress at the ptg. if we dont then i will have a very differnt counter propsal to solve the same usecase without cyborg12:56
sean-k-mooneyjangutter: that is generic device management12:56
*** udesale has joined #openstack-nova12:57
janguttersean-k-mooney: Yep, that's good to hear. One of the "nice things" is that we can at least _test_ the interface on one reference install.12:57
*** moshele has quit IRC12:58
*** alexchadin has quit IRC12:59
janguttersean-k-mooney: it's also pretty close to the time when Neutron should start passing os-vif objects to Nova.12:59
sean-k-mooneyjangutter: have you been looking at my rfe backlog and or the items i added for the nova-neutron cross project session :)13:00
*** med_ has quit IRC13:00
janguttersean-k-mooney: not yet! It's on my to-do list for today.13:00
sean-k-mooneyyes i would finally like to get to that point this cycle. i added it as a topic for the cross project session. i think the neutron folks would like to move in that direct question is finding time to do it but i may know some people that could help13:01
*** moshele has joined #openstack-nova13:03
*** adrianc has joined #openstack-nova13:06
*** eharney has joined #openstack-nova13:06
*** ykarel is now known as ykarel|afk13:07
*** alexchadin has joined #openstack-nova13:07
*** mriedem_afk is now known as mriedem13:15
*** dtantsur|brb is now known as dtantsur13:17
mriedemprometheanfire: clean run of nova-status upgrade check in devstack with the 2 nova patches applied http://logs.openstack.org/47/599847/3/check/tempest-full/2e19da6/controller/logs/devstacklog.txt.gz#_2018-09-05_06_31_52_98913:18
*** med_ has joined #openstack-nova13:20
mriedemdansmith: when you get a chance, probably need you to weigh in here https://review.openstack.org/#/c/599744/13:24
*** ykarel|afk has quit IRC13:25
*** ykarel|afk has joined #openstack-nova13:25
*** beagles is now known as beagles_mtgs13:30
*** r-daneel has quit IRC13:34
*** gbarros has joined #openstack-nova13:39
dansmithmriedem: okay, after coffee13:41
*** psachin has quit IRC13:42
*** ykarel|afk has quit IRC13:42
*** ykarel|afk has joined #openstack-nova13:43
*** udesale has quit IRC13:43
tssuryamriedem, dansmith, melwitt: I'll by flying out today, should be in airport transit for the cells meeting if we are having one13:45
openstackgerritChris Dent proposed openstack/nova-specs master: List resource providers having inventory  https://review.openstack.org/60001613:46
dansmithtssurya: ack, we should cancel.. I'm just getting back up to speed since last week anyway and we'll be together next week13:46
tssuryadansmith:ack13:47
*** med_ has quit IRC13:47
*** ttsiouts has quit IRC13:59
*** janki has quit IRC14:01
mriedemalex_xu: how about i just pull the try/except change out of https://review.openstack.org/#/c/599744/ and make it a follow up so we can discuss what to do about it separately?14:04
*** jaosorior has quit IRC14:06
*** med_ has joined #openstack-nova14:09
openstackgerritEric Fried proposed openstack/nova master: Use uuidsentinel from oslo.utils  https://review.openstack.org/60007014:12
efriedcdent: ^14:13
cdentroger14:13
efriedI guess I'll do the placement one... later14:13
pooja-jadhavefried: Hello14:13
efriedcdent: or redo https://review.openstack.org/#/c/599386/ actually14:14
efriedpooja-jadhav: Howdy.14:14
alex_xumriedem: sounds a good idea14:14
pooja-jadhavefried: R u aware about block device mapping?14:14
efriedpooja-jadhav: It's a roiling, swirling vortex of mystery to me.14:15
cdentefried: I suspect it is easier/clean to let 599386 merge and adapt it to uuidutils after14:15
efriedcdent: ack14:15
mriedemalex_xu: ok i'll pull that out then14:15
pooja-jadhavefried: can u locate me to the correct person who knows about it in detail??14:16
mriedempooja-jadhav: just ask the question and someone that maybe can help, can try to help14:16
efriedpooja-jadhav: I hate to throw mriedem under the bus for everything, but he's probabl...14:16
efriedyeah, that :)14:16
pooja-jadhavohk14:16
pooja-jadhavmriedem, efried: we can boot volume backed instance by two ways. 1. using --boot-volume 2. mentioned in the ref[1]https://docs.openstack.org/newton/user-guide/cli-nova-launch-instance-from-volume.html14:19
mriedemoh there are myriad ways to bfv14:20
mriedemdon't forget image-defined bdms14:20
pooja-jadhavmriedem, efried: When i boot an instance using --boot-volume. it creates single entry in block_device_mapping table. while when i use using --block-device in that case it creates 2 entries(1 for image and 1 for volume)14:20
mriedemwhen you say --boot-volume do you mean --block-device?14:20
pooja-jadhavno14:21
pooja-jadhav--boot-volume (we need to passed bootable volume there)14:21
pooja-jadhavvolume created by an image14:21
cdent"oh there are myriad ways to bfv" is the opening like to the poem that will get me the nobel prize for lit14:21
cdentbut only after my editor corrects my typing14:21
mriedempooja-jadhav: so this, "cinder create --image-id $IMAGE_ID --display_name=bootable_volume $SIZE_IN_GB"14:22
*** ttsiouts has joined #openstack-nova14:22
mriedem"When i boot an instance using --boot-volume. it creates single entry in block_device_mapping table. while when i use using --block-device in that case it creates 2 entries(1 for image and 1 for volume)"14:23
mriedemin the first case, the bootable volume is the root disk of the vm, it's the boot_index=0 bdm14:23
mriedemthat's why there is 1 bdm14:23
pooja-jadhavissue i observed is: when i checked the instance created by above ref doc and tried to verifies is it BFV then as block device mapping gives me two entries. this method(is_volume_backed_instance) returns false14:23
pooja-jadhavmriedem: yes14:24
mriedemin the 2nd case, there is an ephemeral root disk on the compute host, not a volume, and then a blank non-bootable volume is attached to the vm where boot_index=None14:24
mriedemb/c it's not volume-backed14:24
mriedemif you want a volume-backed server, the root volume is specified with boot_index=014:24
*** dtantsur is now known as dtantsur|brb14:24
mriedemhttps://docs.openstack.org/nova/latest/user/block-device-mapping.html might be helpful14:24
mriedemre: boot_index "Setting a negative value or None indicates that the device should not be used for booting."14:25
mriedemfrom the example,14:25
mriedem"nova boot --flavor FLAVOR --block-device \   source=SOURCE,id=ID,dest=DEST,size=SIZE,shutdown=PRESERVE,bootindex=INDEX \   NAME"14:25
mriedembootindex=INDEX Orders the boot disks. Use 0 to boot from this volume.14:25
mriedem"nova boot --flavor 2 \   --block-device source=volume,id=$VOLUME_ID,dest=volume,size=10,shutdown=preserve,bootindex=0 \   myInstanceFromVolume"14:26
mriedem^ means boot from bootable volume $VOLUME_ID14:26
mriedemthe size field should probably be omitted from that last example since i don't think it's used for a pre-existing volume14:27
mriedemthe --block-device size field is only used when nova creates the volume and boots from it14:27
*** jcosmao has joined #openstack-nova14:27
mriedemcdent: "call me mriedem"14:27
mriedempooja-jadhav: does that answer your questions?14:28
pooja-jadhavmriedem: yes, I will try this thing immediately, and let u know.. if anything more needed. Thanks for ur time :)14:29
mriedemyw14:29
pooja-jadhavmriedem: and for quick responses :)14:29
*** tetsuro has quit IRC14:32
*** tetsuro has joined #openstack-nova14:34
*** itlinux-away has quit IRC14:36
*** moshele has quit IRC14:38
*** Luzi has quit IRC14:38
openstackgerritMatt Riedemann proposed openstack/nova master: Configure placement DB context manager for nova-manage/status  https://review.openstack.org/59974414:41
openstackgerritMatt Riedemann proposed openstack/nova master: Remove error-masking try/except from _run_migration  https://review.openstack.org/60008514:41
mriedemgibi_off: alex_xu: ^14:41
*** tbachman has quit IRC14:44
prometheanfiremriedem: thanks14:46
*** sahid has quit IRC14:52
*** pvc has joined #openstack-nova14:55
pvchi anyone experience instance not getting an IP address? error on communication with the DHCP but when I create a new network it successfully get an IP address?14:55
*** r-daneel has joined #openstack-nova14:59
pvclvdombrkr15:00
pvchi anyone experience instance not getting an IP address? error on communication with the DHCP but when I create a new network it successfully get an IP address?15:00
mriedemlooks like we need some stable/rocky reviews https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/rocky15:03
mriedemmelwitt: you can exercise your newfound stable core powers ^15:03
*** luksky has quit IRC15:03
*** amarao has quit IRC15:04
melwittroger copy15:04
pvcmriedem15:06
*** sahid has joined #openstack-nova15:06
pvccan i ask15:06
pvccan i push this to queens?15:06
pvchttps://review.openstack.org/#/c/590188/15:06
*** breton has joined #openstack-nova15:09
*** luksky has joined #openstack-nova15:09
*** takamatsu has quit IRC15:10
*** alexchadin has quit IRC15:11
*** alexchadin has joined #openstack-nova15:11
*** alexchadin has quit IRC15:12
*** takamatsu has joined #openstack-nova15:12
*** alexchadin has joined #openstack-nova15:12
*** alexchadin has quit IRC15:12
*** alexchadin has joined #openstack-nova15:13
*** alexchadin has quit IRC15:13
*** alexchadin has joined #openstack-nova15:14
*** alexchadin has quit IRC15:14
*** alexchadin has joined #openstack-nova15:14
*** alexchadin has quit IRC15:15
*** tbachman has joined #openstack-nova15:15
*** awaugama has joined #openstack-nova15:17
*** Bhujay has quit IRC15:18
mriedempvc: backports go in order, so that would first have to merge on master, then backported to rocky, then backported to queens15:19
bretonhi! Are VMs with memory encryption supported now in Nova? Amd's SEV for example15:21
*** ykarel|afk is now known as ykarel15:22
mriedemnever heard of it15:22
*** gyee has joined #openstack-nova15:22
mriedemi bet windriver would be all over it though15:23
mriedemif only cfriesen were around15:23
*** pcaruana has quit IRC15:25
mriedemmnaser: re your questions about placement extraction and data migration,15:26
mriedemif placement were down but nova-api was up,15:26
*** awaugama has quit IRC15:26
mriedemusers could try to delete instances which should work in nova (i haven't tested this) but leave stale records in placement which would require a script to cleanup,15:26
mriedembut new requests for scheduling would also fail with NoValidHost15:26
mriedemis the latter something you're OK with?15:27
melwitttssurya, dansmith: ack for canceling15:27
pvcmriedem i see thank you15:27
pvccan i use to my openstack queens for testing?15:27
mriedempvc: you can do whatever you want in your local environment15:27
*** itlinux has joined #openstack-nova15:28
*** sahid has quit IRC15:30
*** sahid has joined #openstack-nova15:30
pvcboth on controller and compute?15:31
*** beagles_mtgs is now known as beagles15:33
mriedempvc: that patch only applies to compute15:34
*** tssurya has quit IRC15:36
*** sahid has quit IRC15:36
pvcif i push it, the ceph volume extension on fly will be okay also right15:37
*** kaliya has joined #openstack-nova15:37
openstackgerritMatt Riedemann proposed openstack/nova stable/rocky: Fix nova-status "_check_resource_providers" check  https://review.openstack.org/60009815:37
*** awaugama has joined #openstack-nova15:40
mriedempvc: i don't know what that means15:40
*** macza has joined #openstack-nova15:41
mriedembut i also can't speak for this patch because i haven't looked at it in awhile15:41
mriedemif it fixes your bug, and it applies to queens, then i guess you find out15:41
openstackgerritMatt Riedemann proposed openstack/nova stable/queens: Fix nova-status "_check_resource_providers" check  https://review.openstack.org/60010115:42
*** spartakos has joined #openstack-nova15:42
mriedemnaichuans: bauzas: efried: i added an item to the ptg etherpad about the libvirt/xenapi driver implementation for reshaper - my libvirt patch is only written to handle the existing upgrade case of moving a single VGPU inventory class from the root provider to a new child provider, it does not intend to handle multiple child providers for multiple VGPU types b/c we didn't support that yet, so we wouldn't reshape *from* that sc15:43
mriedemio yet15:43
mriedembut i'm worried that maybe there are things to come with multi-vgpu child providers that i'm not appreciating15:43
mriedemalthough i figured that might be handled with traits?15:43
*** dave-mccowan has quit IRC15:44
mriedemif you have multiple vgpu type providers on the same host, they'd be children under the same root with separate traits describing the vgpu type per provider15:44
efriedI would think so, yes.15:44
*** itlinux is now known as itlinux-away15:46
*** itlinux-away is now known as itlinux15:46
bauzasmriedem: yeah, and I agree with you15:46
*** itlinux is now known as itlinux-away15:46
*** itlinux-away is now known as itlinux15:46
bauzasmriedem: that's the comment I said15:46
*** itlinux is now known as itlinux-away15:46
*** ttsiouts has quit IRC15:46
mriedemok cool15:46
bauzasmriedem: if we need *more* types, then that's a new change15:46
bauzasfor the moment, we only support one, hence your change being good15:47
mriedembauzas: also, on that libvirt change, i haven't actually tested that with a real system that has vgpu inventory on it15:47
bauzasmriedem: tbh, that's the problem I have, my machine has been passed to another one...15:47
mriedemso if you have a setup like that, or are able to do it quicker than me, that would be great if you could actually make sure this does the needful15:47
mriedemah15:47
bauzasmriedem: yeah sure, it's just...15:48
bauzasyou know, hardware etc.15:48
*** artom has quit IRC15:49
*** artom has joined #openstack-nova15:49
mriedemi'm sure sean-k-mooney has some hardware that he nabbed from intel on the way out15:49
*** artom has quit IRC15:50
sean-k-mooneymriedem: unfortunetly not but i have some hardware i bought on ebay15:52
sean-k-mooneywhat was it in relation too?15:52
mriedemvgpu testing for my reshaper patch15:55
*** jaosorior has joined #openstack-nova15:57
pvcjust a quick question mriedem15:57
pvcwhat release does the cinder volume in-use state extension supported?15:57
sean-k-mooneymriedem: ah unforunetly i dont have any vgpu suff currently.15:57
dansmithmriedem: so do you think we squashed it? http://status.openstack.org/elastic-recheck/#178948416:00
* prometheanfire should be testing vgpu 'soon'16:00
*** dtantsur|brb is now known as dtantsur16:01
mgagneLets say your Ironic instance only has 2 physical nics and you don't want a 3rd interface attached because it just wouldn't work. Would Nova check for this limitation and fail at the API level?16:04
*** spartakos has quit IRC16:05
mriedempvc: let me go back to your original question: https://review.openstack.org/#/c/590188/ will not be backported upstream16:05
mriedembecause it's for a feature16:05
*** spartakos has joined #openstack-nova16:05
mriedemeven though it says it's a bug, it's a bug related to implementing a feature16:06
pvci see thank you :)16:06
mriedemvolume extend support was added in pike https://specs.openstack.org/openstack/nova-specs/specs/pike/implemented/nova-support-attached-volume-extend.html16:07
pvcyes but on LVM driver only. for rbd is not yet supported16:08
mriedemsure, that's not a bug though16:09
mriedemmore specifically, it's supported for iscsi and fibrechannel volume types16:09
mriedemwhich is more than just lvm16:09
pvcyes do you have idea when is the implementation for rbd?16:09
mriedemthe next patch in that series https://review.openstack.org/#/c/594273/16:10
mriedembut the blueprint isn't approved - it has to be discussed during the weekly nova meeting16:10
pvci see thank you so much for your time :)16:11
*** cfriesen has joined #openstack-nova16:11
*** itlinux has joined #openstack-nova16:12
*** pvc has quit IRC16:13
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: Fix nova-status "_check_resource_providers" check  https://review.openstack.org/60011316:15
*** efried is now known as efried_rollin16:17
*** helenafm has quit IRC16:22
*** jiapei has quit IRC16:22
openstackgerritMatt Riedemann proposed openstack/nova stable/ocata: Fix nova-status "_check_resource_providers" check  https://review.openstack.org/60011916:23
jaypipesmgagne: no, it would not fail at the API level, AFAIK. it would fail during node provisioning in ironic virt driver.16:32
openstackgerritmelanie witt proposed openstack/nova stable/rocky: Make scheduler.utils.setup_instance_group query all cells  https://review.openstack.org/59973216:33
openstackgerritmelanie witt proposed openstack/nova stable/queens: Make scheduler.utils.setup_instance_group query all cells  https://review.openstack.org/59976616:37
*** itlinux is now known as itlinux-away16:38
*** itlinux-away is now known as itlinux16:39
*** itlinux is now known as itlinux-away16:39
*** holser_ has quit IRC16:44
*** itlinux-away is now known as itlinux16:44
*** itlinux is now known as itlinux-away16:44
*** holser_ has joined #openstack-nova16:45
*** holser_ has quit IRC16:46
*** itlinux-away has quit IRC16:49
openstackgerritMerged openstack/nova master: Fix nova-status "_check_resource_providers" check  https://review.openstack.org/59987516:50
openstackgerritMerged openstack/nova master: Fix DB archiver AttributeError due to wrong table name attribute used  https://review.openstack.org/59987816:51
*** tetsuro has quit IRC16:51
*** davidsha has quit IRC16:52
mriedemalex_xu: Kevin_Zheng: yikun: replied in https://review.openstack.org/#/c/591976/ re: the changes-since == changes-before debate16:54
mriedemcdent: edleafe: from an API SIG pov you might have input on ^16:54
mriedemwould be interesting to know if any other APIs in openstack have filtering capability like that16:55
cdentmriedem: been a while since I looked at that so not caught up on the issues16:55
cdentnova drove the existence of changes-since, yeah?16:56
mriedemthe big debate is what to do if changes-since == changes-before16:56
*** moshele has joined #openstack-nova16:56
mriedemumm, i'm assuming so...16:56
* cdent reads16:56
mriedemglance has some funky filter-based filtering stuff using operators16:57
*** moshele has quit IRC16:57
*** mchlumsky has joined #openstack-nova16:59
mgagnejaypipes: I was referring to the attach-interface action, the hotplug feature16:59
mgagnehmm I think I reworded my question before sending, might not have been clear then :-/17:00
*** derekh has quit IRC17:00
*** imacdonn has quit IRC17:00
*** imacdonn has joined #openstack-nova17:05
openstackgerritElancheran S proposed openstack/nova master: Add exact match aggregate image properties matcher/filter  https://review.openstack.org/59316717:09
mgagneok, it seems it would fail on Ironic side with NoFreePhysicalPorts exception which would be mapped to a Bad Request at the Ironic API. This will be mapped to VirtualInterfacePlugException in Nova virt driver. There is a generic try catch in compute manager which will raise InterfaceAttachFailed. And API will map to HTTPInternalServerError17:10
*** luksky has quit IRC17:11
openstackgerritElancheran S proposed openstack/nova stable/pike: Add exact match aggregate image properties matcher/filter  https://review.openstack.org/59987017:11
sean-k-mooneymgagne: not in all cases. i know cisco added a thing where you can attach more interfaces then avaialble to a ironic system via neutron turnk port extition17:12
mgagnesean-k-mooney: yes, I'm concerned about "flat" networks where there is no trunk involved17:12
*** mchlumsky has quit IRC17:13
mgagneand about the UX in case of failure.17:13
sean-k-mooneyone thing i was not aware of and maybe you can clarify. do we today allow you to attach an interface to an ironic node after its deployed?17:13
mgagneyes17:13
sean-k-mooneymgagne: and if we execeed the available interfaces we get an error or silent failure today?17:14
*** adrianc has quit IRC17:14
mgagneif you have flat networks, Nova will fail with a 500 error without much information about the reason. This is what I understood from reading the code.17:15
*** mchlumsky has joined #openstack-nova17:15
sean-k-mooneyand you would like to chage that to a vifplug exception17:15
sean-k-mooneywell VirtualInterfacePlugException17:15
mgagneattach/detach for Ironic was added in Pike: https://docs.openstack.org/releasenotes/nova/pike.html#new-features (2nd item)17:15
mgagnesean-k-mooney: it would be a much better UX if the user got a 400 instead of a 50017:16
sean-k-mooneyso you want to make it a 400 calls bad request rather then a 500 server error as its an enduser error to try to attach more interface then phyically avaialble17:18
mgagneyes, anything in the 4XX range17:18
mgagnebecause I don't think it's a server side error from the user perspective17:19
sean-k-mooneyi mean that seam reasonable. i think i reivewd or partly reviewd code from you on this topic17:19
mgagnecould be 406, 409. I'm not an expert.17:20
mgagneso you are the person I want to be friend with =)17:20
sean-k-mooneyim not an expert either but i dont think 409 or 406 is correct17:21
sean-k-mooney406 is for content type mismatches e.g. server say i speak json and you give it xml17:22
openstackgerritmelanie witt proposed openstack/nova stable/pike: Add functional test for affinity with multiple cells  https://review.openstack.org/59984017:22
openstackgerritmelanie witt proposed openstack/nova stable/pike: Make scheduler.utils.setup_instance_group query all cells  https://review.openstack.org/59984117:22
sean-k-mooney409 is for rases e.g. you tried to update something but someone else also did please retry17:22
mgagneso 400 looks fine17:22
mgagneor 402 if you want to make them pay for that feature =)17:23
sean-k-mooneymgagne: i would use 400  or 418 if you are felling exotic or british17:25
sean-k-mooneyi would be tempted by 412 but i would have to read rfc 7232 so see if its correct or not17:26
mgagnehehe so my question is how to raise that exception from Ironic to Nova API without losing much details.17:26
*** dtantsur is now known as dtantsur|afk17:26
mgagnebecause Ironic returns a 400 too but the error message would need to be parsed to find the reason and map it to something else in Nova.17:27
mgagneand I'm not sure it's the right way to do it17:28
sean-k-mooneyi have to runn but a 400 with an embeded error code in the body might be the best option. this has been a topic dhellmann might be able to advise on. i think he had a session in vancouver on having consitent behavor in our error handling17:28
sean-k-mooneyif the api does not return a 400 already then that is proably enough17:29
mgagnecan we just assume that all 400 returned by Ironic are user errors at the Nova API level?17:29
sean-k-mooneynot all responces but perhaps for that specific endpoint + http method17:31
mgagne+117:31
*** munimeha1 has joined #openstack-nova17:33
jrollmgagne: you need to go through scheduling to be able to determine if the node you pick has enough NICs, so I don't think it can ever be a synchronous error in the API17:36
mgagnejroll: we are talking about the hotplug feature ;)17:37
jrollah17:37
jrollyou still need to reach down into the virt driver, right? which is always async17:37
melwittit's not always async -- depends on whether it's a cast or a call17:37
melwittit's usually async though17:38
mgagnethis is not what I found? or I misunderstood?17:38
jrollwell, so much for being well-informed :)17:38
melwittfor example, when we do an attach_volume, we call down to the driver synchronously first to see if there's room, and fail in the API if not17:38
melwittsomething I learned recently17:38
mgagnehttps://github.com/openstack/nova/blob/master/nova/api/openstack/compute/attach_interfaces.py#L131-L15417:38
*** ykarel is now known as ykarel|lunch17:39
*** ykarel|lunch is now known as ykarel|away17:39
*** jpena is now known as jpena|off17:40
mgagnehttps://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L465-L47417:40
mgagnecall() is used17:40
jrollmgagne: ah, cool, so I guess what I would do is add some sort of "NoNicsAvailable" exception that the ironic driver can return in this case17:40
melwittthanks, was just looking for that17:40
melwittindeed, call is synchronous17:41
dansmiththis would be a call to compute which does an http call to ironic, yeah?17:42
mgagnejroll: there is already an exception for that (NoFreePhysicalPorts which is mapped to Invalid) https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/network/common.py#L170-L17417:42
melwittdansmith: I think they'd add something to the already-existing synchronous attach_interface call to call ironic17:43
mgagnecompute does a call to virt driver which performs the HTTP call: https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L1450-L145117:43
jrollmgagne: oh, I meant add that exception to nova, so we can return it here: https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L147417:44
dansmithyeah the unfortunate bit there is that if the second call takes a long time, we'll time out, report to the user that it failed, but eventually it succeeded17:44
*** ccamacho has quit IRC17:44
dansmithbut, maybe this would be a good application of my long-call stuff17:45
jrollor add VirtualInterfacePlugException to the list here: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/attach_interfaces.py#L13417:45
mgagnejroll: yes! just need a way to detect this kind of error from Ironic API response and map accordingly17:45
melwittdansmith: ack17:45
jrollmgagne: yep, this is where someone says all API errors should have a "code" :)17:45
mgagnejroll: it's mapped to InterfaceAttachFailed in the compute manager https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L595617:46
mgagnewhich is handled already here https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/attach_interfaces.py#L14917:46
*** tbachman has quit IRC17:47
*** tbachman_ has joined #openstack-nova17:47
openstackgerritMatt Riedemann proposed openstack/nova master: Fix formatting in changes-since guide  https://review.openstack.org/60015017:47
jrollmgagne: ah, ok. so we should detect this specific case and make a new exception with better info for the user eh?17:47
mgagnejroll: yep =)17:48
*** mgariepy has quit IRC17:48
mgagneI'm just not sure how to do it properly without parsing error message which could theoretically be translated to a different language than english17:48
mgagneI have to run right now, brb in ~1h17:49
jrollgotcha17:49
jrollmgagne: might be more of a topic for the ironic channel when you're back17:49
*** pcaruana has joined #openstack-nova17:52
*** mgariepy has joined #openstack-nova17:53
sean-k-mooneyjroll: i was away but i did mention having a 400 with and embded code :P17:53
jrollsean-k-mooney: see, someone said it before I even predicted it :P17:54
sean-k-mooneybut if my memory is correct there was some converstation about makeing the apis more consitent in vancouver17:54
sean-k-mooneye.g. between different services17:54
sean-k-mooneyi dont know hat the outcome of that was17:54
sean-k-mooneythe only thing i do remember is never embed html in and error responce17:55
jrollyes, there was17:55
jrollpeople agree we should do it, nobody has set aside the time afaik17:56
sean-k-mooneyis it a topic at the ptg. i assumed it would continue to be discussed in that api working group or in one of the cross project sessions17:56
*** openstackgerrit has quit IRC18:00
jrollsean-k-mooney: dunno, haven't been following it closely18:02
*** eharney has quit IRC18:04
*** ykarel|away has quit IRC18:05
*** mgariepy has quit IRC18:05
*** spartakos has quit IRC18:09
*** tbachman_ is now known as tbachman18:11
mriedemi hope not18:15
mriedembut maybe it'll be on tuesday when i might have to sit in the kata containers qemu room all day because someone from my company has to know what's going on in that "community"18:17
cdentsean-k-mooney: feel free to come to api-sig session on monday if you wanna talk about that. the agenda is pretty light at the moment (although we intend to flesh it out more during tomorrow's meeting): https://etherpad.openstack.org/p/api-sig-stein-ptg18:21
*** mlavalle has joined #openstack-nova18:23
*** priteau has quit IRC18:35
*** luksky has joined #openstack-nova18:36
*** priteau has joined #openstack-nova18:36
*** spartakos has joined #openstack-nova18:38
*** spartakos has quit IRC18:39
*** spartakos has joined #openstack-nova18:40
*** dhellmann has left #openstack-nova18:41
*** mgariepy has joined #openstack-nova18:52
*** kaliya has quit IRC18:55
*** eharney has joined #openstack-nova19:00
*** r-daneel has quit IRC19:03
sean-k-mooneycdent: am i might, i think "starardising how we report errors" is a good goal. not sure i know enough about the options to add much to the conversation19:04
*** r-daneel has joined #openstack-nova19:05
cdentsean-k-mooney: there's an existing api guideline for errors: http://specs.openstack.org/openstack/api-wg/guidelines/errors.html but it is not implemented by much (placement does a bit of it, mostly to use 'code' to distinguish different 409 responses19:08
sean-k-mooneyoh ok i should read that.19:13
sean-k-mooneyby the way im glad ye used status code 418 in the example :)19:14
*** awaugama has quit IRC19:17
sean-k-mooneymgagne: you proably should check out the link cdent posted http://specs.openstack.org/openstack/api-wg/guidelines/errors.html19:18
sean-k-mooneyanyway i need to go sleep/pack. talk to everyone tomorrow19:18
mgagnesean-k-mooney: looks like a very cool spec =)19:19
*** efried_rollin is now known as efried19:31
*** holser_ has joined #openstack-nova19:42
*** holser_ has quit IRC19:43
*** tbachman has quit IRC19:44
*** r-daneel_ has joined #openstack-nova19:48
*** r-daneel has quit IRC19:49
*** r-daneel_ is now known as r-daneel19:49
*** mdrabe has joined #openstack-nova20:01
*** erlon has quit IRC20:05
*** holser_ has joined #openstack-nova20:18
*** openstackgerrit has joined #openstack-nova20:20
openstackgerritMatt Riedemann proposed openstack/nova master: Fix evacuate logging  https://review.openstack.org/59305520:20
*** tbachman has joined #openstack-nova20:23
*** tbachman has quit IRC20:25
*** tbachman has joined #openstack-nova20:29
*** erlon has joined #openstack-nova20:40
*** pcaruana has quit IRC20:40
*** itlinux has joined #openstack-nova20:48
*** holser_ has quit IRC20:52
mriedemugh i thought we had squashed this20:53
mriedemFutureWarning: ImageMeta(checksum=<?>,container_format=<?>,created_at=<?>,direct_url=<?>,disk_format=<?>,id=<?>,min_disk=<?>,min_ram=<?>,name=<?>,owner=<?>,properties=ImageMetaProps,protected=<?>,size=<?>,status=<?>,tags=<?>,updated_at=<?>,virtual_size=<?>,visibility=<?>) is an invalid UUID. Using UUIDFields with invalid UUIDs is no longer supported, and will be removed in a future release. Please update your code to input va20:53
mriedemUUIDs or accept ValueErrors for invalid UUIDs. See https://docs.openstack.org/oslo.versionedobjects/latest/reference/fields.html#oslo_versionedobjects.fields.UUIDField for further details20:53
mriedemi guess an ImageMeta object is certainly not a uuid20:54
*** tbachman has quit IRC20:54
melwittyeah... is it an error in a test or something? why is an ImageMeta object being treated as a UUIDField20:58
mriedemmissing mock i think20:59
*** erlon has quit IRC21:00
*** munimeha1 has quit IRC21:01
*** mchlumsky has quit IRC21:02
cdentIs "thin provisioning" of disk mostly a vmware thing, or does it also happen when using some other hypervisor+storage things?21:06
dansmithcdent: other things have it21:08
dansmithnot everything amazing is made by vmware. JEEZ21:08
dansmitha unix sparse file is kinda thing provisioning and pre-dates a lot of stuff21:09
*** r-daneel has quit IRC21:09
dansmithlike 3.5" floppies21:09
cdentthe reason I ask is I'm wondering how appropriate it is to consider dynamically adjusting allocation_ratio on DISK_GB in that sort of setting: compare actual versus perceived usage21:09
dansmith*thin21:09
dansmithcdent: well, it's not really the same thing21:10
dansmithit's similar21:10
cdentalso: dansmith you know I hate everything, so I don't think anything from vmware is amazing21:10
dansmithbut technically thin provisioning can blow up in your face if you overcommit21:10
cdentright, that's exactly the issue21:10
dansmithI do know that.21:10
dansmithIMHO, allocation_ratio can only be over 1.0 for disk if you like to gamble21:11
dansmithand shouldn't really be related to use of thin provisioning,21:11
dansmithexcept in that it may be the mechanism by which you gamble21:11
cdentthe nearby concrete problem here is: datastore with 50TB total, allocated to 50TB, but in reality has 41TB free because of "thing provisioning"21:12
* dansmith senses mockery21:12
dansmithbut yep21:12
cdentso the short term fix is bump allocation_ratio and watch real usage "real close like"21:12
dansmithyeah, i.e. gambling21:12
cdentthat was not mockery, I just can't type21:12
cdentwhich you also know21:12
dansmithso, every night before the op goes to sleep,21:12
dansmithhe decides how far he thinks he can get before 8am the next morning and sets the allocation_ratio accordingly21:13
cdentpretty much21:13
dansmithsolid plan21:13
cdentso the questioning is: if you know what placement thinks about usage, and you know what the datastore thinks of its free space, you ought to be able to calculate a dynamic allocation ratio every now and again, and save that op some sleep21:14
dansmithif your usage is very consistent21:15
dansmiththe other thing to think about/remember is:21:15
dansmiththin provisioning is somewhat of a space-saving thing, but it's also just to speed up the actual provisioning step21:15
dansmithmost filesystems will end up filling out the block device over time,21:16
cdentyeah, which is why it would need to be a failure regular thing21:16
dansmithunless they intentionally compact and fstrim() now and then to let go of things back to the underlying storage21:16
cdentlike maybe every update_provider_tree21:16
cdentthat was an awesome freudian slide on my part: meant fairly, but failure works too21:17
dansmithbut if you go to sleep with it set at 1.1,21:17
dansmithand something happens where a big tenant has a script that runs amok and fills the disk with logs,21:17
dansmithyou could end up getting a page21:17
dansmithso it's still a ticking time bomb, even if you calculate a conservative ratio based on recent history21:17
cdentI'm not sure I'm following that logic: at time 1 we set it to 1.1. a few minutes later the actual usage on the store goes up, so at time 2 we set it to 1.021:18
cdentif 1 and 2 are close together the risk is lessed (but not entirely removed)21:18
dansmithyou mean some automated thing that looks for the crash on the horizon and adjusts the ratio before it becomes a problem?21:19
*** david-lyle has joined #openstack-nova21:19
*** macza_ has joined #openstack-nova21:19
dansmithI'm trying to think about how that helps21:21
cdentin this vmware case the datastore knows how many bytes it says it has "free". this is different from what placement says. The ratio of that difference can be a multiplier for setting allocation_ratio. If you're saying "the datastores sense of 'free' is not real" then yeah, sure, we got a problem.21:21
dansmithuntil you get to 1.0, it might as well be 1.0, and once you're past 1.0 you can't go back21:21
*** macza has quit IRC21:22
*** dklyle has quit IRC21:22
dansmithit's free to the datastore, but it's not "uncommitted"21:22
cdentI think that may be where the vmware stuff is actually doing something "amazing" that is a bit different from sparse files21:22
dansmiththe other two things that it can be doing are compression and dedup21:23
*** itlinux has quit IRC21:23
dansmithboth of which have an optimal ratio, but that aren't consistent21:23
dansmithlike, if your users are into storing usenet archives, you might get 1.5x from compression, but if they're archiving "those" usenet articles, it'll be much closer to 1.0x21:24
*** r-daneel has joined #openstack-nova21:24
dansmithand if multiple tenants are storing the same things, then you might get 2x from dedup, but not if they're using different block sizes or encruption21:24
dansmith*encryption21:24
dansmithdang21:24
dansmithyou know.21:24
cdentyah, all that makes sense21:25
cdentbut the fundamental issue here is 41TB free, but placement says no bytes free21:25
cdent*issue for the customer21:25
dansmithright, I get that21:25
dansmith41TB is free because 41TB hasn't yet been used,21:26
dansmithbut it _is_ committed to some instances21:26
dansmithaccording to nova and placement21:26
cdentand for many of these flavors, probably never will, because somebody made big flavors, and people like big things even when they don't need them21:26
cdentyes to all that21:27
dansmithyou can tell placement to oversubscribe that to converge the two numbers to zero, but the end result will be someone writes a byte to disk and gets an EIO because you lost the bet21:27
dansmithyeah, but again, with disk, it all ends up filling out21:27
dansmithif you have a linux guest with a 1TB disk and 500MB used,21:27
dansmithand you write a 10MB file and then delete it, in a loop,21:27
dansmithyou will end up touching all sectors on the disk21:27
dansmithif you're fstrim()'ing then that will tell the underlying disk that you're only using some of those at a time,21:28
dansmithbut if you're not, it doesn't know21:28
dansmithnow, I'll grant you this:21:28
cdentas I understand things, in the vc situation, the datastore will reject a workload if _it_ thinks it doesn't have enough space to cope21:28
cdentso it's not going to lead to that level of disaster, at least not as quickly21:28
dansmithif the expectation or requirement is that the guest agent is running in all these instances and can ensure that it's trim'ing then you won't converge on full in the same way21:28
cdentthe split brain nature of the vc situation, sets up a lot of weird21:29
dansmithbased on what logic?21:29
cdentvmware magic?21:29
cdentit's what that stuff does. who knows how it works.21:29
dansmithwell, unless you can explain some magic, I don't believe :)21:30
cdentlet me see if I can find something21:30
mriedemhttps://www.youtube.com/watch?v=1-bt81UBDLI ?21:30
cdenthrmm, too many layers of indirection21:34
cdentso: in the general case a fix for this kind of thing is: train people to not use big disk using flavors when they don't need that. use a volume.21:34
dansmithI'm not saying you shouldn't gamble,21:35
dansmithI'm just saying if you do, be sure to let me know so I can move my instances elsewhere :)21:35
dansmithI think most probably do because they're economizing, and they take that risk, mitigated by willingness to throw disks at a growing problem21:36
dansmithif you're going for risk-and-reward, you gamble21:36
dansmithif you're going for "make sure the nukes don't EIO at a bad time" then maybe you don'21:37
dansmitht21:37
cdentaye aye21:38
cdentstill querying around for an answer on the "is there magic here" and so far the answer is "it's complicated"21:38
cdentand that, kids, is why grampy chris hates everything21:38
* melwitt will bbl21:40
openstackgerritMatt Riedemann proposed openstack/nova master: Remove redundant image GET call in _do_rebuild_instance  https://review.openstack.org/60026021:40
mriedemcdent: i imagine the VC resource tracker is infinitely worse than nova's21:40
mriedemwhich gives me some comfort21:40
mriedemby worse, i mean complicated21:40
*** tbachman has joined #openstack-nova21:40
cdentthankfully I get to stay far away from that stuff21:41
*** takamatsu has quit IRC21:42
*** tasker has joined #openstack-nova21:43
*** tasker has left #openstack-nova21:44
*** tbachman has quit IRC21:46
*** tbachman has joined #openstack-nova21:48
*** slaweq has quit IRC21:56
*** priteau has quit IRC21:56
*** mlavalle has quit IRC22:08
*** slaweq has joined #openstack-nova22:11
mriedemfun, just saw a gate failure where rebuild creates the libvirt guest then while polling the domain to see if it's running, libvirt says it's not found22:13
mriedemand we blow up22:13
*** slaweq has quit IRC22:16
*** mriedem has quit IRC22:18
*** itlinux has joined #openstack-nova22:19
*** cdent has quit IRC22:19
*** gbarros has quit IRC22:21
*** gbarros has joined #openstack-nova22:22
openstackgerritElancheran S proposed openstack/nova stable/pike: Add exact match aggregate image properties matcher/filter  https://review.openstack.org/59987022:24
openstackgerritElancheran S proposed openstack/nova master: Add exact match aggregate image properties matcher/filter  https://review.openstack.org/59316722:25
*** gibi_off has quit IRC22:26
openstackgerritJonte Watford proposed openstack/nova master: Modified version of 0027-Numa-object-string-representations.patch with some updates from the current numa files for nova: numa.py instance_numa_topology.py  https://review.openstack.org/60026922:31
*** _hemna has quit IRC22:31
*** _pewp_ has quit IRC22:31
*** _pewp_ has joined #openstack-nova22:32
*** cfriesen has quit IRC22:33
*** _hemna has joined #openstack-nova22:33
*** rcernin has joined #openstack-nova22:43
*** r-daneel has quit IRC22:45
*** luksky has quit IRC22:57
*** slaweq has joined #openstack-nova23:11
*** slaweq has quit IRC23:15
*** Sundar has joined #openstack-nova23:19
*** macza_ has quit IRC23:19
*** med_ has quit IRC23:27
Sundarmelwitt: Please ping me when you can23:31
*** r-daneel has joined #openstack-nova23:37
*** erlon has joined #openstack-nova23:38
*** med_ has joined #openstack-nova23:38
*** gbarros has quit IRC23:42
*** owalsh_ has joined #openstack-nova23:44
*** owalsh has quit IRC23:48
*** owalsh- has joined #openstack-nova23:48
*** owalsh_ has quit IRC23:51

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