Tuesday, 2015-06-02

*** electrocucaracha has joined #openstack-nova00:00
vilobhmm1dansmith : https://review.openstack.org/#/c/138607/ is ready for review…whenever you are free..00:08
dansmithdims___: done, will actually review it later00:08
dims___dansmith: sounds good. thanks00:09
*** gokrokve has quit IRC00:13
*** zzzeek has quit IRC00:14
*** gokrokve has joined #openstack-nova00:14
*** tjones1 has quit IRC00:14
*** sabari has quit IRC00:15
*** gokrokve has quit IRC00:18
*** patrickeast has quit IRC00:18
*** baoli has joined #openstack-nova00:21
openstackgerritThomas Maddox proposed openstack/nova: Adding IPv6 static routes and static routes template  https://review.openstack.org/18701200:23
*** sabari has joined #openstack-nova00:24
*** mtanino has quit IRC00:25
*** electrocucaracha has quit IRC00:27
*** electrocucaracha has joined #openstack-nova00:27
*** ijw has joined #openstack-nova00:28
openstackgerritDavanum Srinivas (dims) proposed openstack/nova: [WIP] Ignore me - trying oslo.* master against Nova unit tests  https://review.openstack.org/18641300:30
*** yamahata has quit IRC00:31
*** salv-orlando has joined #openstack-nova00:34
*** angdraug has quit IRC00:34
openstackgerritThomas Maddox proposed openstack/nova: Adding IPv6 static routes and static routes template  https://review.openstack.org/18701200:36
*** flwang1 has quit IRC00:37
*** salv-orlando has quit IRC00:41
dims___thomasem: ping00:42
dims___thomasem: left a question in https://review.openstack.org/#/c/187012/00:42
*** kfox1111 has quit IRC00:45
*** sdake_ has joined #openstack-nova00:45
nic@jbernard: with respect to tests, I might need a hand or three00:46
nicThis little change: https://review.openstack.org/#/c/187395/1/nova/virt/libvirt/imagebackend.py00:47
nic…seems to have knocked over three dozen unit tests that all expect the code to work that way00:47
nicI figure something as innocuous-looking as that causing that much trouble means I should stop and ask someone who knows what they are doing what's going on00:48
*** sdake has quit IRC00:49
jbernardnic: certainly, ill do what i can00:50
*** zhangtralon has joined #openstack-nova00:50
*** flwang has joined #openstack-nova00:51
nicIf the code change itself is uncontroversial, then it raises the question of why the unit tests went all explode-y over it00:52
*** electrocucaracha has quit IRC00:52
*** ian_brown has joined #openstack-nova00:52
nicBut that much trouble would hint that there's something wrong with my approach00:53
jbernardit might be worth asking: do we need to snapshot the volume and delete/rollback soonafter?00:53
*** hanzhang has quit IRC00:53
jbernardcould we get away without it? it would make the patchset smaller and avoid tripping over the image_create issue00:54
*** promulo_ has joined #openstack-nova00:54
nicWell, the image_create issue is the crux of why resizes don't work (but say they do)00:54
nicIt hits that code path, and then no-ops because the image exists00:54
nic…instead of doing the size check and resizing, like it would if it entered the create_image method00:55
*** zhangtralon has quit IRC00:55
nicAll the create_image implementations I looked at do their own existence checks, so it looks like somebody over-optimized it00:56
nicBut again, there's A LOT of tests around it, so I figure I must be missing something00:56
nic(small words and purple crayon drawings would be a huge help here)00:57
*** promulo has quit IRC00:57
jbernardnic: lol00:57
*** vilobhmm1 has quit IRC00:58
jbernardnic: these paths are new to me as well, i'll need to look closer in the morning00:58
*** shashankhegde has quit IRC00:59
nicthanks00:59
*** artom has quit IRC00:59
jroll.v 12901:00
jrolloops >.>01:00
jbernardnic: so things are broken before finish_migration() is called in the driver?01:01
jbernardnic: libvirt's _disk_resize() appears broken for rbd as well01:02
jbernardnic: size is passed as 001:02
nicAs far as I can tell, yes01:03
jbernardnic: and the info dict looks odd as well01:03
nicBut in my testing, resize and revert work with the patch set applied01:03
nic(and revert is way fast.  whee!)01:03
*** hanzhang has joined #openstack-nova01:05
jbernardnic: at least there is that :)01:05
nicsubunit disagrees with me as to the efficacy of my changes, but I swear, it works great with Ceph!  :-)01:07
nicI've got to disconnect, so further discussion can happen in the bug and/or review01:09
jbernardnic: sounds good, thanks for working on this!01:09
*** nic has quit IRC01:09
*** ijw_ has joined #openstack-nova01:12
*** shashankhegde has joined #openstack-nova01:13
*** ijw has quit IRC01:16
*** shashankhegde has quit IRC01:20
*** ijw has joined #openstack-nova01:23
*** Sukhdev has quit IRC01:24
*** Sukhdev has joined #openstack-nova01:25
*** ijw_ has quit IRC01:26
*** tjones1 has joined #openstack-nova01:33
*** sdake has joined #openstack-nova01:33
*** alanf-mc has quit IRC01:34
*** BadCub has quit IRC01:35
*** xylan_kong has quit IRC01:35
*** boris-42 has quit IRC01:35
*** wanghao has quit IRC01:35
*** aweeks has quit IRC01:35
*** DuncanT has quit IRC01:36
*** dougwig has quit IRC01:36
*** rex_lee has quit IRC01:36
*** briancurtin has quit IRC01:36
*** sdake_ has quit IRC01:37
*** BadCub has joined #openstack-nova01:38
openstackgerritFeng Xi Yan proposed openstack/nova: Transfer network info to metadata api when using config drive.  https://review.openstack.org/18398501:38
*** xylan_kong has joined #openstack-nova01:41
*** aweeks has joined #openstack-nova01:42
*** wanghao has joined #openstack-nova01:43
*** briancurtin has joined #openstack-nova01:43
*** Sukhdev has quit IRC01:43
*** otter768 has joined #openstack-nova01:44
*** DuncanT has joined #openstack-nova01:45
*** shakamunyi_ has joined #openstack-nova01:46
*** shakamunyi_ has quit IRC01:46
*** ijw has quit IRC01:46
*** sdake has quit IRC01:48
*** otter768 has quit IRC01:49
*** sdake has joined #openstack-nova01:52
*** wwriverrat has quit IRC01:53
*** rex_lee has joined #openstack-nova01:55
*** dougwig has joined #openstack-nova01:55
*** boris-42 has joined #openstack-nova01:55
*** alexpilotti has quit IRC02:00
*** liusheng has quit IRC02:02
*** tobe has joined #openstack-nova02:03
*** zhenguo has joined #openstack-nova02:03
*** popw has joined #openstack-nova02:03
*** unicell1 has quit IRC02:07
*** pixelbeat has quit IRC02:08
*** baoli has quit IRC02:08
*** browne has quit IRC02:11
*** tsekiyama has quit IRC02:11
*** baoli has joined #openstack-nova02:11
*** ssurana has quit IRC02:12
*** yamahata has joined #openstack-nova02:12
*** bkopilov has quit IRC02:13
*** shashankhegde has joined #openstack-nova02:13
*** salv-orlando has joined #openstack-nova02:14
openstackgerritRui Chen proposed openstack/nova: Set task_state=None when booting instance failed  https://review.openstack.org/18714502:15
*** salv-orlando has quit IRC02:20
*** lyanchih has joined #openstack-nova02:20
*** xyang1 has quit IRC02:20
*** lyanchih has joined #openstack-nova02:20
*** lyanchih has left #openstack-nova02:20
*** lyanchih has joined #openstack-nova02:21
*** liusheng has joined #openstack-nova02:22
*** lyanchih has quit IRC02:23
*** wwriverrat has joined #openstack-nova02:25
*** shakamunyi has joined #openstack-nova02:26
*** mohitsharma has joined #openstack-nova02:27
*** lyanchih has joined #openstack-nova02:27
*** yamahata has quit IRC02:29
*** dboik has joined #openstack-nova02:31
*** shakamunyi has quit IRC02:33
openstackgerritKen'ichi Ohmichi proposed openstack/nova: Add and use raise_feature_not_supported()  https://review.openstack.org/16369702:37
openstackgerritKen'ichi Ohmichi proposed openstack/nova: Add a hacking rule for consistent HTTP501 message  https://review.openstack.org/16369802:37
*** browne has joined #openstack-nova02:42
*** baoli has quit IRC02:43
*** jogo has quit IRC02:44
*** VW has joined #openstack-nova02:45
*** dboik has quit IRC02:45
*** dims___ has quit IRC02:48
*** tjones1 has quit IRC02:48
*** VW has quit IRC02:50
*** yingjun has joined #openstack-nova02:51
openstackgerritRui Chen proposed openstack/nova: CreateVM supports subnet specified  https://review.openstack.org/18296902:56
*** VW has joined #openstack-nova02:56
*** lyanchih has quit IRC03:00
*** lyanchih has joined #openstack-nova03:12
*** shashankhegde has quit IRC03:13
*** lyanchih has quit IRC03:15
*** zhangtralon has joined #openstack-nova03:20
*** VW has quit IRC03:22
*** jogo has joined #openstack-nova03:22
*** zhangtralon has quit IRC03:26
*** yingjun has quit IRC03:33
*** VW has joined #openstack-nova03:38
*** yingjun has joined #openstack-nova03:39
*** yamahata has joined #openstack-nova03:43
*** otter768 has joined #openstack-nova03:45
*** ssurana has joined #openstack-nova03:45
*** VW has quit IRC03:46
*** VW has joined #openstack-nova03:47
*** VW has quit IRC03:48
*** mtanino has joined #openstack-nova03:48
*** dims_ has joined #openstack-nova03:48
openstackgerritwangxiyuan proposed openstack/nova: Add backup error information  https://review.openstack.org/18744503:49
*** otter768 has quit IRC03:50
*** dims_ has quit IRC03:53
*** Nisha has joined #openstack-nova03:55
*** tjones1 has joined #openstack-nova03:59
*** deepthi has joined #openstack-nova04:03
*** yingjun has quit IRC04:07
*** unicell has joined #openstack-nova04:08
*** yamahata has quit IRC04:09
*** yamahata has joined #openstack-nova04:09
*** asettle has joined #openstack-nova04:10
*** garyk has joined #openstack-nova04:10
*** haigang has joined #openstack-nova04:19
*** fawadkhaliq has joined #openstack-nova04:21
*** Sukhdev has joined #openstack-nova04:21
*** bkopilov has joined #openstack-nova04:23
*** david-lyle has quit IRC04:24
*** david-lyle has joined #openstack-nova04:25
*** shashankhegde has joined #openstack-nova04:25
*** exploreshaifali has joined #openstack-nova04:26
*** mtanino has quit IRC04:27
*** tjones1 has quit IRC04:30
*** armax has quit IRC04:33
*** asettle has quit IRC04:34
*** Nisha has quit IRC04:38
*** Nisha has joined #openstack-nova04:43
*** salv-orlando has joined #openstack-nova04:46
*** pradipta has joined #openstack-nova04:50
*** exploreshaifali has quit IRC04:51
*** changbl_ has quit IRC04:52
*** salv-orlando has quit IRC04:53
*** shashankhegde has quit IRC04:55
*** Murali has joined #openstack-nova05:03
*** vilobhmm has joined #openstack-nova05:06
*** Longgeek has joined #openstack-nova05:07
*** sdake has quit IRC05:07
*** _gryf|afk has quit IRC05:08
*** tobe has quit IRC05:08
*** _gryf has joined #openstack-nova05:09
openstackgerritEarle F. Philhower, III proposed openstack/nova: Add support for HGST Solutions volumes to libvirt  https://review.openstack.org/18659405:12
*** nosnos has joined #openstack-nova05:12
*** kiran-r has joined #openstack-nova05:13
*** yingjun has joined #openstack-nova05:13
*** Longgeek has quit IRC05:13
*** yingjun has quit IRC05:14
*** shashankhegde has joined #openstack-nova05:19
*** dave-mccowan has quit IRC05:19
*** Mike_D_laptop has joined #openstack-nova05:21
*** tobasco has joined #openstack-nova05:25
*** Mike_D_laptop has quit IRC05:26
*** sudipto has joined #openstack-nova05:29
*** gabor_ has joined #openstack-nova05:30
*** gabor_ is now known as Guest9952705:30
*** achanda has joined #openstack-nova05:30
*** Guest99527 has quit IRC05:31
*** achanda_ has joined #openstack-nova05:37
*** nosnos has quit IRC05:37
*** zhenguo has quit IRC05:37
*** tobe has joined #openstack-nova05:37
*** achanda has quit IRC05:38
*** sgordon has quit IRC05:39
*** lpetrut has joined #openstack-nova05:39
*** sgordon has joined #openstack-nova05:39
*** otter768 has joined #openstack-nova05:46
*** rotbeard has joined #openstack-nova05:46
*** otter768 has quit IRC05:50
*** Longgeek has joined #openstack-nova05:52
openstackgerritAndrey Pavlov proposed openstack/nova: Extract helper method to get image metadata from volume  https://review.openstack.org/18746105:57
*** yingjun has joined #openstack-nova06:04
openstackgerritAndrey Pavlov proposed openstack/nova: Extract helper method to get image metadata from volume  https://review.openstack.org/18746106:04
*** Kennan2 has joined #openstack-nova06:06
*** Kennan has quit IRC06:06
*** achanda_ has quit IRC06:07
*** yuntong has joined #openstack-nova06:07
*** cfriesen has quit IRC06:10
*** salv-orlando has joined #openstack-nova06:13
*** tobe has quit IRC06:13
*** radek_ has joined #openstack-nova06:15
*** yingjun has quit IRC06:19
*** Sukhdev has quit IRC06:21
*** ajayaa has joined #openstack-nova06:23
*** salv-orlando has quit IRC06:25
*** ijw has joined #openstack-nova06:26
*** yingjun has joined #openstack-nova06:34
*** ildikov has quit IRC06:36
openstackgerritwangxiyuan proposed openstack/nova: Add specific error information when createBackup is not supported  https://review.openstack.org/18744506:36
*** ian_brown has quit IRC06:37
*** dims_ has joined #openstack-nova06:37
*** tobe has joined #openstack-nova06:38
*** belmoreira has joined #openstack-nova06:38
*** ijw has quit IRC06:39
*** salv-orlando has joined #openstack-nova06:41
*** dims_ has quit IRC06:42
*** markus_z has joined #openstack-nova06:43
*** moshele has joined #openstack-nova06:43
*** masayukig_ has quit IRC06:47
*** arnaud____ has joined #openstack-nova06:47
*** jcoufal has joined #openstack-nova06:48
*** jcoufal has quit IRC06:50
*** jcoufal has joined #openstack-nova06:52
gilliardGood $Morning Nova!06:53
*** loquacity is now known as loquacities06:54
*** zhenguo has joined #openstack-nova06:54
*** qianli_ has joined #openstack-nova06:54
*** qianli has quit IRC06:55
*** masayukig_ has joined #openstack-nova06:59
*** paul-carlton has joined #openstack-nova07:02
*** gszasz has joined #openstack-nova07:05
*** ijw has joined #openstack-nova07:08
openstackgerritAndrey Pavlov proposed openstack/nova: Extract helper method to get image metadata from volume  https://review.openstack.org/18746107:09
*** ijw_ has joined #openstack-nova07:10
*** ijw_ has quit IRC07:11
*** haigang has quit IRC07:11
*** ijw_ has joined #openstack-nova07:11
*** haigang has joined #openstack-nova07:12
*** ijw has quit IRC07:14
*** yassine has joined #openstack-nova07:14
*** yassine has quit IRC07:14
*** yassine has joined #openstack-nova07:17
*** yassine has quit IRC07:17
*** yassine has joined #openstack-nova07:18
*** moshele has quit IRC07:18
*** lpetrut has quit IRC07:19
*** sahid has joined #openstack-nova07:21
*** browne has quit IRC07:22
*** shashankhegde has quit IRC07:26
*** ildikov has joined #openstack-nova07:27
*** shashankhegde has joined #openstack-nova07:27
*** moshele has joined #openstack-nova07:28
*** dulek has joined #openstack-nova07:29
*** fawadkhaliq has quit IRC07:29
*** matrohon has joined #openstack-nova07:34
*** yamahata has quit IRC07:39
*** Kennan has joined #openstack-nova07:39
*** Kennan2 has quit IRC07:39
*** Nisha has quit IRC07:43
*** vilobhmm has quit IRC07:44
*** shashankhegde has quit IRC07:44
openstackgerritZhengguang Ou proposed openstack/nova: libvirt: fix the race condition between detaching volume and creating image  https://review.openstack.org/16615207:46
*** otter768 has joined #openstack-nova07:46
*** jlanoux has joined #openstack-nova07:48
*** alex_klimov has joined #openstack-nova07:48
*** jistr has joined #openstack-nova07:48
*** arnaud____ has quit IRC07:50
*** otter768 has quit IRC07:51
*** lpetrut has joined #openstack-nova07:54
*** oro has joined #openstack-nova07:54
bauzasgilliard: "good" + random(set(['morning', afternoon', 'evening']))07:56
gilliard:)07:57
*** eantyshev has joined #openstack-nova08:08
*** mpavone has joined #openstack-nova08:10
*** lennyb has joined #openstack-nova08:10
*** zhangtralon has joined #openstack-nova08:11
*** danpb has joined #openstack-nova08:15
*** yingjun has quit IRC08:15
openstackgerritHans Lindgren proposed openstack/nova: Add a VolumeUsage object  https://review.openstack.org/18044208:15
openstackgerritHans Lindgren proposed openstack/nova: Replace conductor proxying calls with the new VolumeUsage object  https://review.openstack.org/18044308:15
openstackgerritHans Lindgren proposed openstack/nova: Remove and deprecate unused conductor method vol_usage_update()  https://review.openstack.org/18044408:15
*** moshele_ has joined #openstack-nova08:15
*** moshele has quit IRC08:16
*** romainh has joined #openstack-nova08:18
*** xgsa has quit IRC08:18
*** lucasagomes has joined #openstack-nova08:18
*** derekh has joined #openstack-nova08:19
*** paul-carlton has quit IRC08:24
*** bjornar has joined #openstack-nova08:24
*** ndipanov has joined #openstack-nova08:24
bauzasndipanov: hi, FYI since I had to continue to work on RequestSpec, I had to provide a new PS for the change you -108:25
bauzasndipanov: so I left a comment saying you were unhappy until we discuss with jaypipes and maybe more if possible today afternoon08:26
ndipanovbauzas, ok thanks very cool08:26
ndipanovI'll leave it until then08:26
bauzasndipanov: if we can't do this, I'll write an email08:26
ndipanovasync08:26
bauzasyup, that's the main problem we have, since the spec was merged this way08:27
*** xgsa has joined #openstack-nova08:27
*** ZZelle has quit IRC08:28
*** ZZelle has joined #openstack-nova08:28
*** pradipta has quit IRC08:29
ndipanovbauzas, well to me this is really expected - some things will not get figured out until there is code08:29
ndipanovespecially when ti comes to refactoring of an established itnernal workflow08:29
bauzasndipanov: yeah, I totally understand08:29
ndipanovwe should not get nervous about it imho08:29
bauzasndipanov: my point is, we have to find a way to discuss asyncly08:29
ndipanovah yeah - email08:30
ndipanov:)08:30
bauzasndipanov: honestly, I dislike mail threads because it's too much async and not serialized08:30
openstackgerritSudipta Biswas proposed openstack/nova-specs: Report host memory bandwidth as a metric in Nova  https://review.openstack.org/18098308:31
bauzasndipanov: if the thread is opiniating, then you'll 100+ different discussions within the thread so we miss the consensus08:31
*** paul-carlton has joined #openstack-nova08:31
ndipanovyeah not ideal - though I would not necessarily got for consensus08:31
ndipanovmore like - enough people think it's fine even if (nikola for example) doesn't08:31
bauzasndipanov: okay, I thought about that, please provide a -1 again on my change, and I'll write an email08:31
bauzasndipanov: asking for comments on your comment08:32
ndipanovkk let me look at ti08:32
bauzasndipanov: and then I'll hassle the folks08:32
* bauzas time for coffee08:32
openstackgerritsahid proposed openstack/nova: libvirt: make _create_domain to return a Guest object  https://review.openstack.org/18218508:33
openstackgerritsahid proposed openstack/nova: libvirt: introduce method poweroff to Guest object  https://review.openstack.org/18219408:33
openstackgerritsahid proposed openstack/nova: libvirt: introduce method resume to Guest object  https://review.openstack.org/18219508:33
openstackgerritsahid proposed openstack/nova: libvirt: introduce a Guest to wrap around virConnect  https://review.openstack.org/17431308:33
openstackgerritsahid proposed openstack/nova: libvirt: introduce method get_guest to Host object  https://review.openstack.org/18196908:33
sahidndipanov: can i ask you to take a look at this serie ^08:34
ndipanovsahid, yes08:34
sahidndipanov: thank you08:34
*** popw has quit IRC08:35
sahiddanpb already gave a lot of reviews08:35
moshele_hi johnthetubaguy08:36
*** ssurana has quit IRC08:37
openstackgerritwangxiyuan proposed openstack/nova: Add specific error information when createBackup is not supported  https://review.openstack.org/18744508:39
*** promulo_ has quit IRC08:40
*** lennyb has left #openstack-nova08:41
*** lennyb_ has joined #openstack-nova08:41
*** mohitsharma has quit IRC08:43
*** dguitarbite has joined #openstack-nova08:45
*** zhangtralon has quit IRC08:46
*** mleroy has quit IRC08:47
*** moshele_ has quit IRC08:47
*** wwriverrat has quit IRC08:48
*** moshele has joined #openstack-nova08:48
*** wwriverrat has joined #openstack-nova08:50
*** leopoldj has joined #openstack-nova08:53
*** kbyrne has joined #openstack-nova08:53
*** achanda has joined #openstack-nova08:54
*** zhangtralon has joined #openstack-nova08:54
*** wwriverrat has quit IRC08:55
openstackgerritsahid proposed openstack/nova-specs: console: convert consoles code to use objects framework  https://review.openstack.org/16583808:56
*** achanda_ has joined #openstack-nova08:56
*** yingjun has joined #openstack-nova08:59
*** gszasz has quit IRC08:59
*** zhangtralon has quit IRC09:00
*** achanda has quit IRC09:00
*** zhangtralon has joined #openstack-nova09:01
*** aix has joined #openstack-nova09:01
*** claudiub has joined #openstack-nova09:03
johnthetubaguymoshele: hi, bit late starting today, was travelling down to london09:05
bauzasndipanov: oh man, I just discovered that the instance provided in the request spec can be a dict...09:05
bauzas*facepalm*09:06
*** ociuhandu has joined #openstack-nova09:07
bauzasndipanov: https://github.com/openstack/nova/blob/master/nova/virt/hardware.py#L1113-L111609:08
*** ssurana has joined #openstack-nova09:08
*** andreykurilin has joined #openstack-nova09:08
bauzasndipanov: loving your dirty ugly hacks you made in hardware.py09:08
moshelejohnthetubaguy: lots of traffic in london09:09
moshelejohnthetubaguy: I wanted to discuss Mellanox CI in nova09:09
johnthetubaguymoshele: I got the train, but its a long way from my house, so you know, worked on the train a bit09:10
johnthetubaguymoshele: ah, cool, hows it going?09:10
moshelejohnthetubaguy: it  seem we are commenting to patches we should be fillter09:12
ndipanovbauzas, yeah that was the quickest way to land numa without all of this09:13
bauzasndipanov: yup I know :)09:13
moshelejohnthetubaguy:  this is why dansmith is angry regarding our CI09:13
ndipanovbut if we can remove one case from that method09:13
ndipanovit's a win09:13
ndipanovwe really don't want them at all09:13
bauzasndipanov: so, I'll just make sure that if it's a dict, it will hydrate an object09:14
johnthetubaguymoshele: hmm, do you have an example he was upset about?09:14
*** ssurana has quit IRC09:14
bauzasndipanov: or the fields since we haven't yet agreed09:14
ndipanovbauzas, that thing does that already I think09:14
bauzasndipanov: I checked and we're just passing instance_props as it is09:15
bauzasndipanov: so the filters are using the get method09:15
johnthetubaguymoshele: did you see the list of requirements for 3rd party CI: http://docs.openstack.org/infra/system-config/third_party.html09:15
bauzasndipanov: which means they are not aware of it's a dict or an object, but that's fine09:15
ndipanovbauzas, the second bit of that function converts the dict to an object09:16
*** ociuhandu has quit IRC09:16
ndipanovif instance_numa_topology:09:16
bauzasndipanov: I was talking about instance itself :)09:16
bauzasndipanov: not the numa topology field :)09:17
johnthetubaguymoshele: we have a nova specific list of things as well: https://wiki.openstack.org/wiki/HypervisorSupportMatrix/DeprecationPlan#Specific_Requirements09:17
*** ociuhandu has joined #openstack-nova09:17
bauzasndipanov: anyway, it was more for off the records09:17
moshelejohnthetubaguy:  I see09:19
*** ijw_ has quit IRC09:19
moshelejohnthetubaguy: currently in the Mellanox CI we are filtering to be triggered only for pci code09:20
*** achanda_ has quit IRC09:21
johnthetubaguymoshele: oh, yeah, thats a hard thing, I would argue all patches except unit tests and docs might be a better filter09:21
moshelejohnthetubaguy: but it seem zuul is still commenting on patches we are not triggered for like this https://review.openstack.org/#/c/18722709:22
*** fawadkhaliq has joined #openstack-nova09:22
johnthetubaguymoshele: right, but its hard to prove what could break the PCI code, and running lots more tests shows up how more stable (or not) they system is09:23
moshelejohnthetubaguy: is the recommendation not to do any file filtering?09:23
johnthetubaguymoshele: well, not quite, no need to vote on docs only and unit test only patches09:23
johnthetubaguymoshele: but ideally voting on anything that touches code would be good09:24
johnthetubaguymoshele: now, if thats not practical, thats OK, we can discuss that, but the ideal situation is you voting on all changes09:24
johnthetubaguyall code changes, I mean09:25
lennyb_johnthetubaguy: the same issue of 'empty voing' will be on tests and docs as well. we cant 'decide' what to vote for and what not09:25
*** dims_ has joined #openstack-nova09:26
johnthetubaguylennyb_: sorry, what do you mean by "empty voting"? I am clearly missing the context of the previous discussion here09:27
*** toan-tran has joined #openstack-nova09:28
moshelejohnthetubaguy: it seems when you apply file filler rule on file in zuul, it will still comment on other files which are not in the filter09:29
openstackgerritDeepak C Shetty proposed openstack/nova: Nova part of volume snapshot improvements  https://review.openstack.org/17281309:30
moshelejohnthetubaguy: in this commit https://review.openstack.org/#/c/187227 we should have trigger because we had filler file in zuul but we still comment09:30
moshelejohnthetubaguy:   I mean we shouldn't09:31
*** dims_ has quit IRC09:31
johnthetubaguymoshele: oh, I would talk to infra about how they make that work, lots of the other CI system manage to not vote on docs, but vote on all other patches, but maybe they don't use zuul... not sure09:31
johnthetubaguylennyb_: moshele: oh, I see what you mean by an empty vote now, that is bad09:32
lennyb_johnthetubaguy: some of them not using zuul.09:32
*** yingjun has quit IRC09:33
*** gszasz has joined #openstack-nova09:34
*** Nisha has joined #openstack-nova09:34
moshelejohnthetubaguy: that why dansmith was angry, we missed it because in jenkins we didn't  see any job for that so we were not aware we are doing the empty voting09:34
*** Murali has quit IRC09:37
*** aix has quit IRC09:45
openstackgerritMaxim Nestratov proposed openstack/nova: libvirt: don't add filesystem disk to parallels containers unconditionally  https://review.openstack.org/18685809:45
*** aix has joined #openstack-nova09:45
openstackgerritHans Lindgren proposed openstack/nova: Remove/deprecate unused parts of the compute node object  https://review.openstack.org/18675709:46
openstackgerritHans Lindgren proposed openstack/nova: Make ComputeNode.service_id nullable to match db schema  https://review.openstack.org/16928409:46
*** otter768 has joined #openstack-nova09:47
openstackgerritSudipta Biswas proposed openstack/nova-specs: Report host memory bandwidth as a metric in Nova  https://review.openstack.org/18098309:49
*** josecastroleon has joined #openstack-nova09:49
*** haigang has quit IRC09:50
openstackgerritsahid proposed openstack/nova-specs: libvirt: set admin root password  https://review.openstack.org/18750909:50
openstackgerritHans Lindgren proposed openstack/nova: Avoid querying for Service in resource tracker  https://review.openstack.org/16928809:51
*** Nisha_away has joined #openstack-nova09:51
*** otter768 has quit IRC09:52
*** amotoki_ has joined #openstack-nova09:53
*** Nisha has quit IRC09:54
openstackgerritNikola Dipanov proposed openstack/nova: bdm: Make sure that delete_on_termination is a boolean  https://review.openstack.org/18691009:54
openstackgerritNikola Dipanov proposed openstack/nova: snapshot: Copy some missing attrs to the snapshot bdms  https://review.openstack.org/18691109:54
*** achanda has joined #openstack-nova10:00
*** Nisha_away has quit IRC10:00
*** Nisha has joined #openstack-nova10:04
johnthetubaguymoshele: sorry, lost my connection, long story, but yeah, the empty voting would be good to stop10:05
johnthetubaguymoshele: I suspect infra are the best folks to help with that, I guess there is another config for skipping the vote all together, I know some folks are doing that, not sure if they are doing that with zuul10:05
johnthetubaguymoshele: testing everything would be a possibly "quick" fix I guess10:06
openstackgerritDaniel Berrange proposed openstack/nova: compute: remove get_image_metadata method  https://review.openstack.org/18725110:06
ndipanovjohnthetubaguy, do you remember what was the story behind this: https://review.openstack.org/#/c/176805/10:08
ndipanovnot linked to a bug/bp...10:08
*** haigang has joined #openstack-nova10:08
Nishajohnthetubaguy, hi ...wanted to discuss on the capabilities specs as in links https://review.openstack.org/182572 and https://review.openstack.org/18258110:08
*** gholler has joined #openstack-nova10:08
johnthetubaguyndipanov: docimpact seemed enough with that one10:08
johnthetubaguyndipanov: there are quite a few bps tracking moving policy to more fine grained, it fits in with that I think10:09
ndipanova-hah10:09
ndipanovno I was only wondering what inspired that particular patch10:09
johnthetubaguyndipanov: I assume they want to restrict snapshots, I don't know the back story10:10
Nishajohnthetubaguy, the above specs are required for ironic or in other words ironic and nova work is interrelated for this.10:11
*** ssurana has joined #openstack-nova10:11
*** zhangtralon has quit IRC10:11
openstackgerritMatthew Booth proposed openstack/nova: Remove unused variables from images api  https://review.openstack.org/18347510:11
Nishajohnthetubaguy, i havent seen any reviews on these specs so not sure what is the opinion within nova community for these10:11
johnthetubaguyNisha: OK, not had chance to review many specs with all the pre/post summit work right now10:12
johnthetubaguyNisha: nothing jumps out as really bad, but I would have to give it a full review before I can give more context I am afraid10:13
Nishajohnthetubaguy, i just wanted to bring that in notice...if you/other members can go through the specs we can discuss in IRC at the suitable time10:13
johnthetubaguyNisha: hopefully will get to those this week, but afraid its hard to promise that at this point10:13
Nishajohnthetubaguy, that will help...thanks10:13
johnthetubaguyNisha: its just a case of waiting for a review at this point, I am afraid, sorry thats not quicker10:14
Nishaits not just review...its about the opinion from nova community10:14
*** gholler has quit IRC10:14
Nishathe ironic changes are dependent on what nova agrees10:14
Nishai have 4 specs in total, 2 in nova and 2 in ironic10:15
johnthetubaguyNisha: yeah, I should find a way to raise the priority of those, but its tricky right now10:15
Nishajohnthetubaguy, thanks10:15
*** ssurana has quit IRC10:15
*** ijw has joined #openstack-nova10:16
*** claudiub has quit IRC10:18
*** yassine has quit IRC10:19
*** ijw_ has joined #openstack-nova10:19
*** haigang has quit IRC10:22
*** ijw has quit IRC10:22
*** ijw_ has quit IRC10:24
*** moshele has quit IRC10:26
*** gholler has joined #openstack-nova10:26
*** jlanoux_ has joined #openstack-nova10:28
*** haigang has joined #openstack-nova10:28
*** jlanoux has quit IRC10:30
*** moshele has joined #openstack-nova10:34
*** jyuso1 has quit IRC10:34
openstackgerritJohn Garbutt proposed openstack/nova-specs: Add liberty priorities  https://review.openstack.org/18727210:36
*** pixelbeat has joined #openstack-nova10:36
openstackgerritJohn Garbutt proposed openstack/nova-specs: Add liberty priorities  https://review.openstack.org/18727210:38
*** zhangtralon has joined #openstack-nova10:41
*** samueldmq has joined #openstack-nova10:41
*** oro has quit IRC10:44
*** alexpilotti has joined #openstack-nova10:46
*** jlanoux has joined #openstack-nova10:53
*** dims_ has joined #openstack-nova10:55
*** jlanoux_ has quit IRC10:55
*** achanda_ has joined #openstack-nova10:56
*** fawadkhaliq has quit IRC10:56
*** achanda has quit IRC10:56
*** ian_brown has joined #openstack-nova10:57
*** Longgeek_ has joined #openstack-nova11:01
*** Longgeek has quit IRC11:01
jaypipesjohnthetubaguy: hey, you have the link to the etherpad that lists all the etherpads for nova at the summit?11:07
*** ssurana has joined #openstack-nova11:12
lxslijaypipes: https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads#Nova ?11:13
jaypipeslxsli: ty sir! :)11:13
lxslinw :)11:13
*** ssurana has quit IRC11:17
*** tobasco has quit IRC11:17
*** ijw has joined #openstack-nova11:19
bauzasjaypipes: hey11:21
*** ian_brown has quit IRC11:21
bauzasjaypipes: I discussed with ndipanov on the ReqSpec BP11:21
jaypipesbauzas: bonjour11:21
*** rushiagr_away is now known as rushiagr11:22
ndipanovjaypipes, hello\11:22
jaypipesndipanov: hi! :)11:22
openstackgerritZhenyu Zheng proposed openstack/nova: CONF.allow_resize_on_same_host should check only once in controller  https://review.openstack.org/18623611:22
bauzasjaypipes: and it seems we have different views11:22
jaypipesndipanov: missed you in YVR :(11:22
bauzasjaypipes: aloha11:22
bauzas(note, my 9mo daughter is on my knees, don't expect me to discuss quickly) :)11:22
bauzasso11:22
*** ijw_ has joined #openstack-nova11:23
ndipanovyeah - couldn't really make it this time :(11:23
bauzasjaypipes: I would love your views on https://review.openstack.org/#/c/145528/13/nova/objects/request_spec.py,cm11:23
bauzasjaypipes: I will write an email11:23
bauzasjaypipes: so ndipanov and you could just reply11:23
ndipanovjaypipes, and if it's not clear what I meant on that review - pls ping me and I'll try to explain11:23
jaypipesndipanov: will do.11:24
jaypipesguys, gimme some time to read and reply.11:24
bauzasjaypipes: tbc, here is the point https://review.openstack.org/#/c/145528/12/nova/objects/request_spec.py,cm11:24
*** zhangtralon has quit IRC11:24
ndipanovnp - I'm here all day11:24
jaypipeskk11:24
bauzasjaypipes: sure thing, I'm not blocked11:24
bauzasjaypipes: since I'm working on the next changes11:24
bauzasfolks, going out to lunch11:25
jaypipesbauzas: I have a weekly ops meeting from 11am EST - 12:30pm EST, every week. this means I always am missing the gantt/scheduler meeting now that daylight savings is in effect :( Any chance you can talk with n0ano about maybe moving that meeting?11:25
bauzasjaypipes: will do :)11:25
*** ijw has quit IRC11:25
jaypipesbauzas: merci11:25
bauzasjaypipes: we can just doodle it11:26
jaypipeskk11:26
*** ijw_ has quit IRC11:27
*** mwagner_afk has quit IRC11:28
*** triggerz has joined #openstack-nova11:28
samueldmqmorning11:28
samueldmqcould someone from nova take a look at bug #145894511:28
openstackbug 1458945 in murano "Use graduated oslo.policy instead of oslo-incubator code" [High,Confirmed] https://launchpad.net/bugs/1458945 - Assigned to Ekaterina Chernova (efedorova)11:28
jaypipessamueldmq: mornin.11:28
*** achanda_ has quit IRC11:28
jaypipessamueldmq: is this a Nova thing?11:28
samueldmqjaypipes, it's a policy thing .. incubated code that got graduated11:29
jaypipessamueldmq: but that bug is for Murano, not Nova...?11:29
samueldmqjaypipes, https://bugs.launchpad.net/nova/+bug/145894511:29
openstackLaunchpad bug 1458945 in murano "Use graduated oslo.policy instead of oslo-incubator code" [High,Confirmed] - Assigned to Ekaterina Chernova (efedorova)11:29
samueldmqjaypipes, that affects several projects11:29
jaypipessamueldmq: ah, I see now..11:29
jaypipesdims_: can you handle the nova patch for ^^?11:30
samueldmqjaypipes, hmm.. actually that's interesting, it said murano because it was the last update in there :)11:30
jaypipessamueldmq: yeah :)11:30
samueldmqjaypipes, great, if people are very busy with other tasks, let me know if you need me to do that11:31
samueldmqjaypipes, just to make sure we keep moving11:32
samueldmqjaypipes, thanks :)11:32
*** zhangtralon has joined #openstack-nova11:36
*** yingjun has joined #openstack-nova11:37
*** Nisha has quit IRC11:40
*** ildikov has quit IRC11:41
jaypipessamueldmq: of course, you are more than welcome to submit a patch for that to nova!11:42
openstackgerritgaryk proposed openstack/nova: Compute: replace incorrect instance object with dict  https://review.openstack.org/18753711:42
*** deepthi has quit IRC11:42
garykdims_: ^11:43
*** lucasagomes is now known as lucas-hungry11:43
samueldmqjaypipes, nice .. I will in the case dims_ can't, since I also have some other changes in the Dynamic Policy thing11:44
dims_jaypipes: oslo.policy? there was a feature request from sdague for oslo.policy and he does not want it merged without it11:44
samueldmqjaypipes, hope you had heard about that in the summit :)11:44
* dims_ trying to see if it's mentioned in any etherpad11:45
openstackgerritwangxiyuan proposed openstack/nova: Fix bdm image_meta when boot from volume  https://review.openstack.org/18624711:45
kashyapndipanov: Hi, when you get a moment, re: https://bugs.launchpad.net/nova/+bug/137586811:46
openstackLaunchpad bug 1375868 in OpenStack Compute (nova) "libvirt: race between hot unplug and XMLDesc in _get_instance_disk_info" [High,Confirmed]11:46
ndipanovyes11:47
ndipanovkashyap, what about it11:47
ndipanov?11:47
dims_samueldmq: jaypipes: https://etherpad.openstack.org/p/YVR-nova-contributor-meetup lines 154 onwards. specifically 16011:47
samueldmqdims_, looking11:47
kashyapI see you're fixing bugs in that area (65d6eb0 - libvirt: make _get_instance_disk_info conservative)11:47
*** dprince has joined #openstack-nova11:48
kashyapndipanov: Is that race still present?11:48
sdagueright, it just doesn't seem sensible to do that merge until we get the new bits in11:48
dims_sdague: ack. was someone on policy team going to do a spec?11:48
ndipanovkashyap, well it's not really a race11:48
kashyapndipanov: Or as the bug you point to in that, which has a lot more detail, that says that libvirt's XML shouldn't be referred11:48
*** otter768 has joined #openstack-nova11:48
ndipanovkashyap, yes basically that's it11:49
ndipanovI looked into it briefly11:49
*** sdake has joined #openstack-nova11:49
sdagueso, I think I need to write it up. Right now I'm writing up some english about the Nova microversions structure and solution as that seemed the most urgent11:49
*** oro has joined #openstack-nova11:49
ndipanovand I think it can be changed to not use the XML11:49
sdaguejamielennox and I talked about it quite a bit11:49
ndipanovbut it won't be a small change11:49
samueldmqsdague, hi .. what are the missing bits specifically ?11:49
sdagueas well as with morganfainberg, it's on my list :)11:49
kashyapndipanov: Okay, no rush. Just was looking through some bugs, and `git blame` said Nikola is fixing bugs in this area, so I pinged :-)11:49
sdaguesamueldmq: so the nova team would like base policy to be encoded in code, not a json file11:50
ndipanovkashyap, I think the race itslef was mitigated11:50
sdaguethe json files could be use to override11:50
ndipanovplus I did another horrible hack there to make it even less likely11:50
sdagueand ideally some overrides would trigger warnings in the logs on startup as "terrible idea, might impact compatibility"11:50
samueldmqsdague, hmm, cool .. I will be glad to follow this, looks to be an interesting idea11:50
ndipanovbut the root cauyse is still there11:50
samueldmqsdague, ++11:51
samueldmqsdague, but for now ... we are only migrating the oslo-incubator version of policy.json to the graduated library11:51
samueldmqsdague, I don't see how this affects other changes, it just keep it as is11:51
kashyapndipanov: Noted, thanks for the detail. You might want to update the bug with this context.11:52
sdaguethere are other things that emerged there right? Also the whole policy.d performance issues were never really addressed.11:52
ndipanovwell all the context is in the linked bug really11:52
ndipanovor hmmm11:52
sdagueit just seemed like making those changes now didn't really help anything11:53
kashyapndipanov: Okay, if that's sufficient, please disregard me.11:53
*** otter768 has quit IRC11:53
dims_samueldmq: there's no policy.json or py in oslo-incubator :)11:53
ndipanovwell this is on my list of things to look at this month so will get to it for sure11:53
samueldmqdims_, policy.py11:53
garykmdbooth: please check https://review.openstack.org/#/c/183475/ - silly pep8 stuff11:53
samueldmqdims_, it would only replace https://github.com/openstack/nova/blob/master/etc/nova/policy.json11:54
samueldmqdims_, by https://github.com/openstack/oslo.policy/blob/master/oslo_policy/policy.py, basically11:54
dims_samueldmq: i mean we deletd policy.py from oslo-incubator https://github.com/openstack/oslo-incubator/tree/master/openstack/common11:54
*** romainh has quit IRC11:54
mdboothgaryk: Argh! pep8 failure due to merge conflict >:(11:54
*** romainh1 has joined #openstack-nova11:54
mdboothThanks11:54
samueldmqdims_, but sdague may be seeing things I am not :)11:54
sdagueyeh, the incubator deleted it already. Honestly, part of the reason I want to have this done in this order is I think we need to make sure we've got buy in on direction before committing to the library, because we're going to have a hard minimum requirement here.11:55
samueldmqdims_, yes, and that's the reason we need to update nova to use oslo.policy, incubator code has gone11:55
sdaguesamueldmq: is there a specific bug you are trying to address?11:56
*** sdake_ has joined #openstack-nova11:56
*** ildikov has joined #openstack-nova11:56
dims_samueldmq: as sdague said, if the nova team is not comfortable with oslo.policy, they can move policy.py in their tree to another location and own it11:56
*** dave-mccowan has joined #openstack-nova11:56
samueldmqsdague, only the bug for the migration itself https://bugs.launchpad.net/nova/+bug/145894511:56
openstackLaunchpad bug 1458945 in murano "Use graduated oslo.policy instead of oslo-incubator code" [High,Confirmed] - Assigned to Ekaterina Chernova (efedorova)11:56
samueldmqsdague, which affects multiple projects11:56
samueldmq(yes, it says murano, but it's multiproject)11:57
*** sdake has quit IRC11:57
sahidjaypipes: hello, i wanted to ask you.. I like the idea you purpose during a design session about "ressource templates""11:57
sahidhttps://etherpad.openstack.org/p/YVR-nova-liberty-priorities line 6311:57
*** zhenguo has quit IRC11:57
sahidi guess a good use case could be fore NUMA11:57
jaypipessahid: cool :)11:57
jaypipessahid: yes, and Ironic stuffs.11:58
sahidso i would like to know if i can help here11:58
dims_samueldmq: what is the CVE vulnerability itself?11:58
sahidyes for sure11:58
sdaguesamueldmq: right, so I feel like it would be better to get focus on supporting the policy changes we'd like first, then we'll happily jump. But the current transition just seems like a sideways bit of busy work.11:58
samueldmqdims_, ok I understand, I'll be following this work in here11:58
sahiddid you think about to push a spec? or perhaps i can try to wor on a draft?11:58
jaypipessahid: you certainly can. I will work on the nova spec for this today and will add you as a reviewer when I push it11:58
samueldmqsdague, ok I respect your decision in nova side :)11:58
dims_samueldmq: happy to get help in oslo.policy for features needed by nova. so we can start there first?11:58
samueldmqsdague, I am working on the dynamic policy thing with ayoung11:59
sahidjaypipes: great, thank you11:59
jaypipessahid: pas de probleme.11:59
samueldmqsdague, let me know if you need me for something related to policies11:59
sahid:)11:59
*** radek_ has quit IRC11:59
* mdbooth really wishes we didn't use repeatable reads in MySQL. The context required to reason about it robustly is insane.11:59
dims_samueldmq: would love your help with oslo.policy features12:00
sdaguesamueldmq: right, this is going to intersect with that some as well. We probably need a discussion thread somewhere as well. jamielennox and I talked through some of the implications. I think the 2 are compatible, but they do impact each other12:00
samueldmqdims_, I need to understand your requirements first (sdague is going to write a spec right?)12:00
sdaguesamueldmq: yes, I will, I will try to get it out this week12:00
sdaguewhich repo should it go in?12:00
dims_samueldmq: not mine...nova team's12:00
samueldmqdims_, I will be happy to collaborate (although time is a bit thigh with the other dynamic policies changes)12:01
dims_sdague: oslo-specs12:01
sdaguedims_: ok12:01
dims_samueldmq: ack thanks12:01
samueldmqdims_, yes, your = nova ;)12:01
dims_samueldmq: i am wearing my oslo hat for this discussion :)12:01
sdaguesamueldmq: right, so I think the dynamic policy architecture needs to get exposed to more projects, because there were some assumptions there which I think don't match with the way projects think about things12:01
* dims_ switching hats12:02
* mdbooth just wrote a 36 line comment explaining why the next 3 lines don't do the obvious thing12:02
sdagueit has far reaching consequences, and I'd hate to see us log jammed late on that one12:02
dims_mdbooth: "Trust me, this works!" should be enough? :)12:02
samueldmqsdague, ++ I agree12:02
mdboothdims_: For some cores, maybe ;)12:03
samueldmqsdague, I will sync up with ayoung (Adam Young), and once we have agreed on the overview spec internally (https://review.openstack.org/#/c/147651/)12:03
*** radek_ has joined #openstack-nova12:03
samueldmqsdague, we should be starting a ml thread, etc (what is needed ..)12:04
samueldmqmorganfainberg, cc ^12:04
samueldmqsdague, please feel free to ping me/add me to the spec review in gerrit12:04
samueldmqsdague, dims_ thanks12:05
dims_samueldmq: thanks for bringing this up12:05
samueldmqdims_, np .. this way we make it as better as we can, together :)12:06
*** haigang has quit IRC12:06
*** baoli has joined #openstack-nova12:07
*** haigang has joined #openstack-nova12:07
*** nihilifer has joined #openstack-nova12:07
*** tobe has quit IRC12:07
*** achanda has joined #openstack-nova12:09
openstackgerritwangxiyuan proposed openstack/nova: Add specific error information when createBackup is not supported  https://review.openstack.org/18744512:10
openstackgerritwuhao proposed openstack/nova-specs: Add previous page links for Nova GET servers API  https://review.openstack.org/16504112:11
*** thiagop has quit IRC12:11
*** ildikov has quit IRC12:12
*** ssurana has joined #openstack-nova12:13
*** ivasev has joined #openstack-nova12:14
*** sdake has joined #openstack-nova12:15
samueldmqdims_, sdague I will mark the bug as confirmed on nova side, makes sense ? (even if it depends on other changes, it is valid)12:15
sdaguesamueldmq: yep, confirmed works for me12:16
samueldmqsdague, great, thanks12:16
*** sdake has quit IRC12:16
*** yingjun has quit IRC12:16
*** rfolco has joined #openstack-nova12:16
*** claudiub has joined #openstack-nova12:17
*** jistr is now known as jistr|class12:17
*** sdake_ has quit IRC12:17
openstackgerritsahid proposed openstack/nova-specs: libvirt: set admin root password  https://review.openstack.org/18750912:17
*** ssurana has quit IRC12:18
*** ijw has joined #openstack-nova12:18
*** radek_ has quit IRC12:20
*** achanda has quit IRC12:20
*** pask81 has joined #openstack-nova12:21
*** achanda has joined #openstack-nova12:21
*** jistr|class is now known as jistr12:22
*** ijw has quit IRC12:23
garykjogo: https://review.openstack.org/#/c/163043/ - this now has the VMware CI +112:24
*** vladikr has joined #openstack-nova12:24
openstackgerritgaryk proposed openstack/nova: Compute: improve logging using {} instead of dict  https://review.openstack.org/18754912:25
*** achanda has quit IRC12:25
*** ildikov has joined #openstack-nova12:27
*** ajayaa has quit IRC12:29
*** aysyanne has joined #openstack-nova12:30
*** b3nt_pin is now known as beagles12:31
*** bkopilov has quit IRC12:32
*** sdake has joined #openstack-nova12:32
*** sdake has quit IRC12:34
RuiChenany chance that who can please look at this spec https://review.openstack.org/#/c/169638/12:35
*** sdake has joined #openstack-nova12:40
lxslijohnthetubaguy: mikal: is there a recommended hotel for the midcycle please?12:40
lxslimriedem_away: ^^12:46
openstackgerritAdelina Tuvenie proposed openstack/nova: Adds Hyper-V vNic hot-plug implementation  https://review.openstack.org/13825512:51
openstackgerritAdelina Tuvenie proposed openstack/nova: Moves OVS related code to a common location  https://review.openstack.org/17972712:51
openstackgerritAdelina Tuvenie proposed openstack/nova: Adds Hyper-V OVS ViF driver  https://review.openstack.org/14004512:51
garykclaudiub: can you please check out my comments on https://review.openstack.org/#/c/169732. the test case is already covered12:52
garykclaudiub: this is a super importnat blocking bug…12:52
*** sudipto has quit IRC12:54
*** ildikov has quit IRC12:55
*** ildikov has joined #openstack-nova12:56
*** kylek3h has joined #openstack-nova12:59
mriedem_awaylxsli: not really, there aren't any discount rates i'm aware of. there are quite a few hotels around the ibm campus though so if you want to go close and not too expensive that's probably available13:00
*** oro has quit IRC13:01
mriedem_awaythe more expensive hotels are downtown near the clinic/hospitals13:01
*** yassine has joined #openstack-nova13:01
*** mriedem_away is now known as mriedem13:01
*** yassine has quit IRC13:01
*** mdrabe has joined #openstack-nova13:02
*** yassine has joined #openstack-nova13:02
lxslimriedem: OK, we were just hoping to stay in the same place as some others for ease of organising after work drinks + meals13:04
sdaguejohnthetubaguy: so I'm writing a lot of english right now about the Nova API changes13:05
mriedemlxsli: i haven't heard of any others booking a place yet13:05
sdagueI've got a super raw buffer, which is how these things tend to work for me - https://www.dropbox.com/s/wb2lbwq63n1xg9p/NovaAPI.rst?dl=013:05
sdaguewhile I think the history bits are long term useful somewhere, honestly, I'd skip them for now, because I mostly just had to get that out of my system before explaining what we had13:06
sdagueLine 162 forward is the part that would be good to look at (starts with A New Beginning)13:06
sdaguenot complete yet, but feedback is probably useful at this point13:07
openstackgerritMatthew Booth proposed openstack/nova: Implement compare-and-swap for instance update  https://review.openstack.org/14111513:07
*** _gryf is now known as gryf|afk13:08
*** pask81 has quit IRC13:08
*** kiran-r has quit IRC13:09
openstackgerritMatthew Booth proposed openstack/nova: Remove unused variables from images api  https://review.openstack.org/18347513:09
*** sdake_ has joined #openstack-nova13:09
*** emagana has joined #openstack-nova13:09
*** ajo has joined #openstack-nova13:09
openstackgerritMarkus Zoeller (markus_z) proposed openstack/nova: docs: Add bug handling description to developer reference  https://review.openstack.org/18757113:10
*** zhangtralon has quit IRC13:11
*** emagana has quit IRC13:12
*** emagana has joined #openstack-nova13:12
*** sdake has quit IRC13:13
garyksdague: if you are dealing with the api would it be possible that you also please look at https://review.openstack.org/#/c/177778/13:15
lxslimriedem: OK, I threw a dart and looks like we'll be in Homewood Suites13:15
johnthetubaguylxsli: I know there wasn't one with a special rate, but yeah, a bit like palo alto13:16
mriedemlxsli: oh, the one with all of those murders a few years back13:16
lxslisdague: ^^13:16
mriedemgood luck!13:16
garyklxsli: i heard that people who do not find accomodation can crash in mriedem s garden13:16
mriedemgo ahead, sprinklers start at 3am13:16
garyk:)13:16
*** emagana has quit IRC13:16
lxslimriedem: we all live in castles over here of course so we're used to a few ghosts13:17
johnthetubaguysdague: hey, hows that english going?13:17
bauzasfolks, seriously considering to be remote for the midcycle this time :/13:17
claudiubgaryk: done13:17
mriedemhomewood suites is probably nice, a bit on the spendy side since it's right across the street from the hospital13:17
mriedembut whatevs13:17
*** mwagner_afk has joined #openstack-nova13:18
lxsliapparently getting ill is the #1 thing to do in Rochester13:18
*** sdake has joined #openstack-nova13:18
lxsli#2 appears to be a graveyard13:18
garykclaudiub: gracias!13:18
*** ijw has joined #openstack-nova13:18
mriedemlxsli: i think getting cured is the idea13:18
mriedemmost people here aren't from here, hence the bazillion hotels13:19
mriedemlxsli: anyway, you're within walking distance of a good breakfast place, so there's that at least13:19
moshelebaoli: hi13:21
baolimoshele: Hi13:21
*** sdake_ has quit IRC13:21
lxslimriedem: as long as there are pancakes <313:22
bauzasmriedem: I just looked at the air routes, but RST seems really hard13:22
mriedembauzas: i know there was a direct delta flight from paris to MSP13:22
bauzasmriedem: do you know if there would be an alternative, ie. a bigger airport than Rochester, and then go by rail ?13:22
lxsli+1, we're flying LHR-MSP and driving for 1h25m13:23
mriedembauzas: but i'm not sure it's worth it for a 3 day meetup, 8-9 hours of flying both ways13:23
moshelebaoli: pci meeting, did I missed it?13:23
bauzasmriedem: luckily, I'm not a Parisian13:23
mriedembauzas: i think most people will fly into MSP and then rent a car13:23
bauzasmriedem: how far is it ?13:23
lxsli80 miles13:23
mriedemyeah, about an hour and a half drive or so13:23
*** ijw has quit IRC13:23
bauzasmriedem: oooh13:23
bauzasmriedem: good to know13:23
mriedemthere are also shuttles that run between MSP and rochester13:23
bauzasbecause atm, the connections are pretty bad from my place13:24
bauzasand that's awfully expensive :/13:24
mriedemhttp://www.gorochesterdirect.com/13:24
mriedem^ is the shuttle13:24
bauzaslemme check with MST13:24
bauzas(gosh the name is funny)13:24
bauzasdon't find the French acronym13:24
bauzasoh MSP13:25
bauzasmy bad :)13:25
baolimoshele, not really. I remember that during summit "P" said he was going to call a biweekly meeting13:25
*** yingjun has joined #openstack-nova13:26
moshelebaoli: you still call him "P" :) , so it is next week13:26
openstackgerritOpenStack Proposal Bot proposed openstack/nova: Updated from global requirements  https://review.openstack.org/18693513:27
*** Nisha has joined #openstack-nova13:27
baolimoshele: still struggling to learn to pronounce it, and he didn't want to teach me13:27
moshelebaoli: I hear you. I have the same problem13:28
bauzasso, MSP is actually also expensive and with 20 hours of travel (2 hops)13:28
bauzasgosh...13:28
*** lucas-hungry is now known as lucasagomes13:29
mriedembauzas: you shouldn't feel required to come, it's a long haul for anyone outside the US13:29
mriedembauzas: i probably won't be going to a meetup in europe if that's what happens in M13:29
bauzasmriedem: well, that's not all about having meetings, that's also a good opportunity for socializing :)13:30
bauzasmriedem: but yeah, sounds it's going to be the plan /13:30
bauzas:/13:30
*** VW has joined #openstack-nova13:30
*** nickchase has joined #openstack-nova13:30
moshelepczesno: hi13:31
bauzasmriedem: I've been heard that johnthetubaguy was having a solid offer from HP Bristol :)13:31
bauzasfor M midcycle I mean13:31
dims_bauzas: MSP to rochester is a short drive as well, not sure i am helping13:32
*** xyang1 has joined #openstack-nova13:32
bauzasdims_: LYS/MSP is around 1800 USD and 20 hours travel, so I will probably pass13:32
*** unicell has quit IRC13:32
dims_bauzas: we cans till try google hangouts + conf line when appropriate13:33
bauzasdims_: yeah, mikal made a good thing last time13:33
* dims_ remembers mikal's special mike thingy13:34
bauzasdims_: I would counteroffer the M midcycle to be in Grenoble for the winter season, but that would be harsh for PaulMurray :p13:34
dims_thomasem: i am all set. thanks13:35
*** ajayaa has joined #openstack-nova13:39
kashyapmriedem: You're still testing this? https://review.openstack.org/#/c/147332/3/nova/utils.py13:40
mriedemkashyap: nope13:40
*** ErickHeinrich has joined #openstack-nova13:41
*** ErickHeinrich has quit IRC13:41
*** rushiagr is now known as rushiagr_away13:41
*** marun has joined #openstack-nova13:45
*** yingjun has quit IRC13:46
*** yamahata has joined #openstack-nova13:48
claudiubmriedem: I gots a question, if you don't mind13:49
*** burt has joined #openstack-nova13:49
claudiubmriedem: is this valid? https://review.openstack.org/#/c/184339/13:49
*** otter768 has joined #openstack-nova13:49
claudiubmriedem: in requirements.txt, oslo.messaging is >=1.4.0,<1.5.013:49
mriedemclaudiub: so, that came up at the ops session on rabbitmq in vancouver13:49
mriedemclaudiub: b/c some big operators using cells were using newer oslo.messaging for the heartbeat patch13:50
sdaguejohnthetubaguy: https://www.dropbox.com/s/wb2lbwq63n1xg9p/NovaAPI.rst?dl=013:50
claudiuband the bug it is addressed in the commit message is targeted to 1.5013:50
mriedemclaudiub: yeah, i know the oslo.messaging versions don't line up with g-r13:50
*** dboik has joined #openstack-nova13:50
*** dims_ has quit IRC13:51
claudiubmriedem: I see, so operators are using newer olso.messaging than the recommended one. Ok, ty for the info. :)13:51
*** dims_ has joined #openstack-nova13:51
*** mtanino has joined #openstack-nova13:51
mriedemclaudiub: yeah, for that heartbeat patch for rabbit13:52
*** jecarey has joined #openstack-nova13:52
mriedemso they are on juno w/ oslo.messaging 1.8.0 + patches i think, and patches for cells13:52
mriedemlike that one ^13:52
claudiubk, I see.13:53
mriedemupdated the meetup wiki with more details for anyone looking at this today: https://wiki.openstack.org/wiki/Sprints/NovaLibertySprint13:53
*** armax has joined #openstack-nova13:54
*** otter768 has quit IRC13:54
*** artom has joined #openstack-nova13:57
*** artom has quit IRC13:57
*** artom has joined #openstack-nova13:58
*** marun has quit IRC13:58
*** marun has joined #openstack-nova13:59
*** annegentle has joined #openstack-nova13:59
*** sdake_ has joined #openstack-nova14:00
*** eharney has joined #openstack-nova14:01
openstackgerritThomas Maddox proposed openstack/nova: Adding IPv6 static routes and static routes template  https://review.openstack.org/18701214:02
thomasemdims_: Great! I went ahead and removed the preserve_routes stuff14:02
thomasemthanks! :)14:02
*** sdake has quit IRC14:03
sahidjaypipes: thanks for your reviews, i have replied to the first one and since i would like to address your comments.. - can you take a look?14:04
sahidhttps://review.openstack.org/#/c/174313/1614:04
jaypipessahid: yup, got it.14:05
sahidcool14:05
*** moshele has quit IRC14:05
*** sdake_ has quit IRC14:07
*** sdake has joined #openstack-nova14:08
*** annegentle has quit IRC14:08
dims_mriedem: want me to throw in this to the mid-cycle wiki? http://www-03.ibm.com/systems/resources/Driving_parking.pdf14:09
*** gokrokve has joined #openstack-nova14:09
dims_mriedem: there's one more - http://www-03.ibm.com/systems/resources/TravelDirections2012.pdf14:09
*** bkopilov has joined #openstack-nova14:11
*** tonytan4ever has joined #openstack-nova14:12
*** mohitsharma has joined #openstack-nova14:14
bauzasdims_: so you hacked IBM ? :p14:14
* bauzas tries to joke14:15
dims_bauzas: used to go often there to build systems :) those pdf(s) helped14:15
*** annegentle has joined #openstack-nova14:15
*** jistr is now known as jistr|mtg14:16
openstackgerritAlvaro Lopez Garcia proposed openstack/nova: scheduler: weight nodes based on their cached images  https://review.openstack.org/17330414:18
openstackgerritAlvaro Lopez Garcia proposed openstack/nova: Add new image cache monitor in compute nodes  https://review.openstack.org/17330314:18
openstackgerritAlvaro Lopez Garcia proposed openstack/nova: compute monitors: set update delta from base class  https://review.openstack.org/17398714:18
openstackgerritAlvaro Lopez Garcia proposed openstack/nova: vmware: add image_cache_manager property  https://review.openstack.org/18760214:18
*** boris-42 has quit IRC14:18
*** ijw has joined #openstack-nova14:18
openstackgerritDaniel Berrange proposed openstack/nova: libvirt: convert imagebackend to support nova.virt.image.model classes  https://review.openstack.org/13202414:19
openstackgerritDaniel Berrange proposed openstack/nova: virt: convert VFS API to use nova.virt.image.model  https://review.openstack.org/13202214:19
openstackgerritDaniel Berrange proposed openstack/nova: virt: convert disk API over to use nova.virt.image.model  https://review.openstack.org/13202314:19
openstackgerritDaniel Berrange proposed openstack/nova: virt: introduce model for describing local image metadata  https://review.openstack.org/13202014:19
openstackgerritDaniel Berrange proposed openstack/nova: virt: convert disk mount API to use nova.virt.image.model  https://review.openstack.org/13202114:19
*** radek_ has joined #openstack-nova14:19
*** nkrinner has quit IRC14:20
*** ajayaa has quit IRC14:21
*** gszasz has quit IRC14:21
openstackgerritBaodong (Robert) Li proposed openstack/nova: Handle port delete event  https://review.openstack.org/17939014:21
*** mdrabe has quit IRC14:22
*** ijw has quit IRC14:23
*** gszasz has joined #openstack-nova14:24
dims_garyk: easy oslo.vmware review when you get a chance - https://review.openstack.org/#/c/183654/14:25
bauzasjaypipes: ndipanov: dansmith: alaski: FYI http://lists.openstack.org/pipermail/openstack-dev/2015-June/065463.html14:25
garykdims_: thanks. looking now14:26
openstackgerritMarkus Zoeller (markus_z) proposed openstack/nova: docs: Add bug handling description to developer reference  https://review.openstack.org/18757114:26
*** fawadkhaliq has joined #openstack-nova14:26
garykdims_: minor nit with import section. other than that looks great. Can you update if you have a sec14:27
dims_garyk: ack14:27
garykgracias14:27
jaypipesbauzas: yeah, I saw that... need to read it through and provide you feedback.14:27
bauzasjaypipes: np14:28
bauzasjaypipes: I tried to discuss on the high-level14:28
alaskibauzas: yeah, just saw that14:28
bauzasjaypipes: ie. should we use the request spec for more than what's used now ?14:28
dims_garyk: done. thanks14:29
*** READ10 has joined #openstack-nova14:29
garykdims_: done. thanks!14:30
*** emagana has joined #openstack-nova14:30
*** jistr|mtg is now known as jistr14:30
garyksorry for taking a while to getting round to this. too many rebases as of late14:30
alaskibauzas: just thinking out loud for a second, but what about turning this around?  Why does this duplicated info need to be stored on the instance object?14:32
alaskiI guess that's sort of what ndipanov is saying in the second part of his review comment14:32
luv hey. i see there have been changes before juno and current git master in how security groups are handled14:33
luvin juno, secgroups listed by  nova secgroup-list  and neutron security-group-list match14:33
luv in current git master the security groups listed in nova use integers as ids14:33
*** thangp has joined #openstack-nova14:33
ndipanovalaski, it does not but imho14:33
ndipanovthis will make us change a lot of assumptions in a lot of places14:34
ndipanovassumption being that instance is what gets passed into everything on the compute host14:34
luvim running in an issue regarding this. If I do "nova secgroup-add-rule default tcp 22 22 0.0.0.0/0" the rule is not ignored by neutron openvswitch agent but if i do "neutron security-group-rule-create --port-range-min 22 --port-range-max 22 --ethertype ipv4 --protocol tcp a73604dc-bde4-46cd-802a-7ea3be3fde2d" the rule works fine14:34
ndipanovalaski, there was a parallel discussion about the fact that we need to save the _new and _old for "complicated" resources like NUMA when doing migrates14:35
ndipanovand the question is where to stick it14:35
ndipanov(this is for a not completely unrelated bug :) )14:36
ndipanovand everyone seems to have been more comfortable with this being part of instance_extra than anything else...14:36
ndipanovI am unsure if this is the write answer in the grand scheme of things :)14:37
alaskindipanov: very true re: compute manager apis needing a huge change to accomadate a change like that14:37
ndipanovbut I think making things require a spec object for data we asumed will be on the instance will make for a lot of refactoring14:37
ndipanovyes14:37
ndipanovright* not write answer :)14:38
luvhttp://pastebin.blesmrt.net/prxnwhbbq#line-1 ... Im really confused here why i see "id=1" but in the docs  http://docs.openstack.org/kilo/install-guide/install/apt/content/launch-instance-neutron.html  the ID is an identifier like a neutron secgroup id14:38
alaskiright now we have pretty convoluted models for things, and I'm trying to think about what it might look like in a more ideal situation14:38
luvbut if i do "describe security_groups;" in nova database id is int(11)14:38
mdboothMy Jenkins job has failed, all subtasks complete, but it's still sat in the gate14:38
ndipanovalaski, my somwhat pragmatic suggestion was14:38
mdboothanybody know why that might be?14:38
ndipanovmake a nice clear API on the instance object14:39
bauzasalaski: ndipanov: sorry, I have been diverted for 10 mins by a 9mo goblin14:39
luvhave there been changes between kilo and current git in this respect?14:39
luvim also noticed following in the logs: http://pastebin.blesmrt.net/psghyiunw14:39
mdboothAh, never mind. Browser snafu by the looks of it. Manual refresh shows unfinished job.14:39
*** cfriesen has joined #openstack-nova14:40
openstackgerritgaryk proposed openstack/nova: VMware: detach cinder volume when instance destroyed  https://review.openstack.org/16973214:40
*** baoli has quit IRC14:40
jaypipesluv: probably best to write a ML post to get answers on that...14:40
*** mdrabe has joined #openstack-nova14:40
ndipanovbauzas, good for you my 3wo goblin is asleep so guess when he will be wide awake...14:40
bauzasalaski: ndipanov: so, the question I would say is "do we make sure that we need more than what's currently in the spec", and ndipanov had a nice insight with the flavor stuff14:41
*** n0ano has joined #openstack-nova14:41
bauzasndipanov: eh14:41
alaskindipanov: that sounds like a good approach to me.  I'm trying to sort out what the reason is for certain things, like a lot of stuff in the request spec is only there for movement of an instance.  but something like numa_topology may have more meaning than that, and I'm not sure how to conceptualize it properly14:41
bauzasndipanov: at least, I'm making sure not to food her after midnight14:41
bauzasndipanov: alaski: which kind of nice "API" would you see for that ?14:42
*** Hosam has joined #openstack-nova14:42
ndipanovbauzas, I think I had an example14:42
openstackgerritgaryk proposed openstack/nova: VMware: remove redundant check for block devices  https://review.openstack.org/17064114:42
bauzasndipanov: oh it would be welcomed14:42
ndipanovsomething like instance.current_flavor(request_spec)14:43
*** baoli has joined #openstack-nova14:43
*** zz_jgrimm is now known as jgrimm14:43
ndipanovwhich would also check for migration objects created etc14:43
bauzasndipanov: and then the spec would have the whole instance object so this helper would basically check if that's the new or the old flavor ?14:43
*** armax has quit IRC14:44
bauzasattached to the instance stored in the spec, I mean14:44
ndipanovbauzas, well I haven't really thought it out :)14:44
*** armax has joined #openstack-nova14:44
ndipanovI assumed only the reference to it14:44
dansmith+1 for the reference if we can get away with it14:44
*** Nisha has quit IRC14:45
dansmithwe really only should nest them if we need to pass the parent and child together over rpc to save a db hit later14:45
bauzasndipanov: you mean the reference to the instance is stored in the spec object ?14:45
*** coolsvap|afk has quit IRC14:45
ndipanovthe idea was to use the Instance object to store the logic (and thus design API's in that fashion)14:45
ndipanovsince this is really waht request object is about - what's happening to an instance14:46
ndipanovhowever flipping it on it's head14:46
ndipanovand making the request object central14:46
ndipanovmight be too much work14:46
bauzasthat said, a request can be for multiple instances14:46
luvjaypipes: do i have to register to openstack ML or can I just email? (different open source MLs have different rules ...)14:47
bauzasat least until we get rid of min_count/max_count14:47
dansmithbauzas: but we would persist one request spec for each instance we create, right?14:47
bauzasdansmith: I would assume a N:1 relationship yup14:47
bauzasdansmith: ie. multiple instances can have the same spec reference14:48
*** henrique_ has quit IRC14:48
dansmithno, see what I meant was,14:48
jaypipesluv: you need to register: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev14:48
dansmithwe would have an initial request spec that we dupe and save per instance in the multi-create case14:48
*** htruta has joined #openstack-nova14:48
luvumm, i better dig in the code and git blame then *punk smiley*14:48
*** coolsvap|afk has joined #openstack-nova14:48
*** VW has quit IRC14:49
bauzasdansmith: oic14:49
ndipanovone other thing that occurred to me when reviewing that spec is our famous DB races14:49
ndipanovso from that POV I'd prefer the model where14:49
bauzasfor the reference, the current approved model for persisting is http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/persist-request-spec.html14:49
ndipanovtransact stuff to an instance14:49
ndipanovand use request object just to talk to the scheduler14:49
bauzasndipanov: in that case, you don't need the whole Instance14:50
bauzasndipanov: and I prefer to only keep what's checked by the filters and consume_from_instance()14:50
alaskindipanov: if I'm understanding you correcty, that's what I would prefer as well.  But we can have a requestspec before we have an instance, so the ownership is hard to model that way14:51
dansmithbauzas: I don't think that spec prescribes a behavior for multi-create, does it?14:51
*** exploreshaifali has joined #openstack-nova14:51
bauzasdansmith: it doesn't14:51
bauzasdansmith: but it implicitely accepts to duplicate14:51
bauzasdansmith: since it's based on instance_extra14:51
ndipanovalaski, yeah....14:51
ndipanovalaski, the more I think about it having 1 thing (Instance) and no request_spec would be very useful14:52
ndipanovexcept for a lot of RPC overhead14:52
*** exploreshaifali has quit IRC14:52
bauzasndipanov: RequestSpec was originally designed for being used solely by the Scheduler14:53
bauzasndipanov: and just replace that dict14:53
bauzasincluding filter_properties14:53
openstackgerritPetrut Lucian proposed openstack/nova: Libvirt: Fix SMBFS volume attach race condition  https://review.openstack.org/18761914:53
dansmithndipanov: you mean just storing the request details with the instance, yes?14:53
ndipanovbauzas, well - the thing is that it is also kind of used for communicating retries14:53
bauzaswhich means that it keeps more than just an instance14:53
alaskindipanov: what I really want is a way to get an object to send to the scheduler, I'm less concerned with where that data is persisted(on instance or duped in a request_spec table)14:53
bauzasndipanov: agreed, that's why I proposed to model it using the Retry object14:54
mdboothMy jenkins job has a sub-job, check-tempest-dsvm-cells, which is still running after 1hr 46mins14:54
dansmithalaski: how about we persist the request spec in the api database during build and then stash it in instance_extra once the instance is built?14:54
mdboothLooking at another, successful job, it completed in 18 minutes14:54
*** jaypipes has quit IRC14:54
mdboothIs there any way to kill it?14:54
alaskindipanov: but I need a way to get that scheduler object before an instance has been created, or to rethink instances a bit14:54
dansmithmdbooth: you can try pushing a new rev14:54
mdboothPreferrably with fire, as it's non-voting anyway14:54
alaskidansmith: I'm good with that, I think I had that in one of my spec revisions14:55
dansmiththat makes the most sense to me14:55
mdboothdansmith: Well I have 2 other failures which I'd genuinely like to investigate. They're probably bogus, but not necessarily.14:55
ndipanovdansmith, that seems like what I'm saying14:55
alaskidansmith: it complicates rehydrating the object a bit, but seems doable14:55
dansmithalaski: why?14:55
dansmithmdbooth: ah, then I think you need to wait for the job timeout14:56
bauzasok, initially the question was not about how to persist it, but what kind of information to persist :)14:56
alaskidansmith: because it can come from the api db in one format, or instance extra in another.  Since I'm assuming we may only store info in instance_extra that's not already on instance14:56
dansmithalaski: I don't think that makes it hard at all14:56
dansmithalaski: we store flavors in the flavors table, and in instance_extra14:56
dansmithpulling them out of either location is different, but not hard14:56
alaskidansmith: no, not hard.  just more complicated than what has been done to this point14:56
dansmithalaski: okay14:57
*** VW has joined #openstack-nova14:57
alaskiI'll propose a spec update with that14:58
ndipanovI'm really mostly concerned with the migration case14:58
bauzasdansmith: alaski: ndipanov: I have to run for the scheduler meeting14:58
bauzasalaski: feel free to CC me on your spec change14:58
alaskibauzas: can do14:59
ndipanovwe are moving an instance around - what is a) the data scheduler needs b) the data both resource trackers need and how to have it accessible through a not horrible API14:59
bauzasalaski: but I think we haven't agreed on what to store *within* the spec :)14:59
ndipanovfor the record '_new' is a horrible API :)14:59
ndipanovbauzas, I don't think we have it figured out15:01
bauzasndipanov: yeah hence my point :)15:01
bauzasndipanov: that said, that discussion was interesting because we told about some new things about how to persist it15:01
ndipanovcurrently what alaski said made me think... what if request_spec is what is being done to the instance at this very moment...15:02
bauzasand the relationship with an instancze15:02
ndipanovso then we have on boot a blank instance, and a request spec15:02
dansmithndipanov: you mean having request and new_request for a resize is a horrible API?15:02
*** hemnafk is now known as hemna15:02
ndipanovdansmith, more like naming is horrible and the fact that we pass a _new string15:02
*** patrickeast has joined #openstack-nova15:02
ndipanovnot the very existance of it15:03
dansmithndipanov: is this specified somewhere in a spec or something?15:03
ndipanovdansmith, what?15:03
dansmithndipanov: I feel like you're talking about some specific thing someone has suggested doing, or that we're currently doing.. the "_new" string bit15:04
bauzasndipanov: honestly, what we need to pass to the scheduler is like a flavor saying 'please decrement your usage by this'15:04
dansmithor do you mean the flavor stashing namespace example/15:04
*** jcoufal has quit IRC15:04
bauzasndipanov: what I still wonder is why we need to have more than a flavor and some extra fields like AZ15:04
openstackgerritDeepak C Shetty proposed openstack/nova: Nova part of volume snapshot improvements  https://review.openstack.org/17281315:05
alaskidansmith: this conversation spawned from https://review.openstack.org/#/c/145528/12 and a ML post from bauzas15:05
lxslibauzas: I'm looking (well, rewriting) Jay's resource-objects spec right now15:05
ndipanovdansmith, right so - I think: having flavor_new and flavor_old is very bad from a semantic POV15:05
mriedemdims_: sure, i'd have to review to see if they are still accurate15:05
alaskidansmith: the _new thing wasn't proposed anywhere that I saw15:05
dansmithalaski: right, I missed .. ah okay15:05
ndipanovrather we have sched asking - what flavor do I need to consider now15:06
ndipanovand we have 2 RTs asking the same question for tracking15:06
ndipanovand the answer is different and _new and _old gives us no clear way of mapping the data to the answer15:06
ndipanovwithout knowing a bunch of other things15:07
dansmithhmm, not sure I get it15:07
*** arnaud____ has joined #openstack-nova15:07
dansmithif we have a request_spec and we want to change that to ask the scheduler for a different thing, feels like we need to store a request_spec_new as well15:07
dansmithbauzas: I think the reason to have an actual request_spec and not just a flavor+AZ is if we go forward with something like jaypipes was suggesting, a request may be a flavor+option1+option7+option315:08
ndipanovwell we really only ever have one request spec and a series of obsolete ones15:08
bauzastechnically a resize is another request15:08
ndipanovone or 0 that is15:08
ndipanovif instance is just staying where it is and no requests are in flight15:08
edleafedansmith: +115:09
dansmithndipanov: I dunno, splitting hairs I guess15:09
edleafendipanov: if an instance was created and then moved, why do we need the original spec?15:10
bauzasdansmith: I agree, that's more than just a flavor, but looking at the consumers of the spec, it's just redunding data15:10
ndipanovwell I'm not sure about that since there are several bugs that have been in nova forever that are exactly the consequence of not having a clear model15:10
ndipanovedleafe, well we don't once the request is successful (resize is confirmed for example)15:10
dansmithedleafe: once it's moved we don't, but since moving it is a long process, we do need two at times15:10
*** zzzeek has joined #openstack-nova15:10
ndipanovbut up until then you need all the data doubled15:10
ndipanovand I guess what we are trying to solve here is which data needs to go to the scheduler and which doesn't15:11
bauzasndipanov: I was speaking of https://github.com/openstack/nova/blob/master/nova/scheduler/filter_scheduler.py#L17215:11
ndipanovand where is the best place to keep them15:11
bauzasndipanov: which is why we need to pass an instance-ish object15:11
alaskiI think we have a pretty good view of what data the scheduler needs, just not where to store it all15:12
edleafendipanov: sure - I thought you wanted to persist N specs forever15:12
bauzasndipanov: plus some filters that are consuming the instance properties, like the NUMA one15:12
ndipanovedleafe, well we kind of already do that with migration objects15:12
ndipanovthere's a ton of overlap between the 2 actually as well15:12
edleafendipanov: even if we do that now, *should* we be doing that? Is it important?15:13
ndipanovedleafe, no no - but orthogonal to this discussion I think15:14
bauzasokay, that's now 40 mins that we're discussing about it, could we try to find a direction for http://lists.openstack.org/pipermail/openstack-dev/2015-June/065463.html ?15:15
edleafendipanov: well, unless you were thinking that because we do that with migration objects, we should do it here15:15
bauzasie. what's needed by the scheduler is part of the existing spec object15:16
ndipanovedleafe, I mean keeping stuff forever is orthogonal to this discussion - because soft deletes are what they are15:16
*** agireud has joined #openstack-nova15:16
bauzasif we consider to add more than that, then it would mean that we change how we access the information15:16
ndipanovbauzas, right15:16
bauzasndipanov: yeah, agreed, we should not focus on how to persist, but *what* to persist15:17
bauzasthere is a spec for persisting, and alaski told us that he'll provide an update about it15:17
bauzasso the "how" is covered15:17
bauzasbut the "what in" isn't15:17
*** ijw has joined #openstack-nova15:18
bauzasso, unless there is a clear win on storing more than what the scheduler needs, I'm in favor of leaving what's in, until someone comes up with a plan to use ReqSpec for more than what's it's used today15:19
openstackgerritjichenjc proposed openstack/nova: Add common function for v2.1 API flavor_get.  https://review.openstack.org/13656815:19
openstackgerritjichenjc proposed openstack/nova: Add common function for v2 API flavor_get.  https://review.openstack.org/13656715:19
bauzassaying that if we persist, that's only for the sake of giving it back to the scheduler in case of a later reschedule15:19
ndipanovbauzas, imho - we should flip this question around15:19
ndipanovwe should ask ourselves15:19
ndipanovwhat data does a) RT thread need b) claim thread need c) scheduler service need15:20
*** changbl_ has joined #openstack-nova15:20
bauzasndipanov: well, RT and claims are being covered by resource-objects15:21
bauzasndipanov: https://blueprints.launchpad.net/nova/+spec/resource-objects15:21
alaskiI definitely think we should figure that out.  this is just focused on c) atm15:21
bauzasalaski: fair enough, but atm we at least to do c)15:21
bauzasat least *need15:22
bauzasevezn15:22
* bauzas has gloves today15:22
*** markus_z has quit IRC15:22
ndipanovso if it's just focused on c) - maybe just dupe it on the request_spec as you did bauzas15:22
bauzasndipanov: for the moment, the contract was on the head of the scheduler15:23
ndipanovand be clear that none of that data is to be used on the compute node, i.e needs to be recalculated15:23
bauzasndipanov: http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/resource-objects.html15:23
bauzasndipanov: ^ is what you ask15:23
ndipanovbauzas, not sure what "on the head of the scheduler" means15:23
*** ijw has quit IRC15:24
bauzasndipanov: sorry, it was a metaphor about guns15:24
bauzasand bandits15:24
bauzasanyway15:24
openstackgerritgaryk proposed openstack/nova: Compute: replace incorrect instance object with dict  https://review.openstack.org/18753715:24
bauzasso, the plan is to have c) covered by reqspec, and a) and b) covered by resource-objects15:25
ndipanovyeah I guess I'm not an armed robbery enthusiast so it was lost on me - sorry15:25
bauzaswell, if you're reading it like a git thing, then yeah :)15:26
bauzasgit HEAD15:26
bauzasanyway15:26
ndipanovbauzas, tbh I don't think so - resource objects are just about having a unified API for dealing with resources15:26
bauzasndipanov: isn't what claims are ?15:26
ndipanovthey don't answer how we store them and when duplicated which ones to consider15:26
bauzasndipanov: because I think that's another step :)15:27
bauzasndipanov: for the moment, we have big blobs having redundant data15:27
*** krtaylor has quit IRC15:27
bauzasndipanov: anyone can just add the key he wants15:27
ndipanovbauzas, ok ok15:27
ndipanovgot your point15:27
bauzasso I need to stop that :)15:27
ndipanovyeah I don't know - I feel that there is stuff ehre that needs to be thought through a bit better15:29
bauzasfor example, I'm not a fan of https://review.openstack.org/#/c/118010/15:29
bauzasndipanov: yeah I know15:29
bauzasndipanov: and I don't disagree with you :)15:29
bauzasndipanov: what is still unclear in my mind is how ReqSpec can help more than the scheduler15:30
*** andreykurilin has quit IRC15:30
bauzaswell, there is the cells effort, for sure15:30
ndipanovbauzas, so is this BP related to persisting that information to have later access to affinity info?15:32
ndipanovor is that "the next step"15:32
bauzasndipanov: you mean request-spec-object ?15:32
ndipanovyes15:32
bauzasndipanov: yeah15:32
bauzasndipanov: since the hints will be stored as well15:32
bauzasndipanov: we're merging the filter properties and the request spec15:33
ndipanovso in that case - we definitely need to rethink this since that stuff is needed on the instance when migrating15:33
bauzasndipanov: the general use case was that in case of a migration or an evacuation, the scheduler was called with no filter properties15:34
*** andreykurilin has joined #openstack-nova15:34
bauzasndipanov: so the scheduler was having zero way to know what the user asked at boot time15:34
ndipanovbauzas, ok so we solve that by creating a whole new table to store it15:35
ndipanovI mean15:35
bauzasndipanov: what is ran by the compute manager once the scheduler elected it is not covered by this spec15:35
bauzass/ran/run (dammit !=15:35
*** barra204 has joined #openstack-nova15:35
*** shakamunyi has joined #openstack-nova15:35
ndipanovI think this kind of design work is exactly where the whole spec process hopelessly fails15:35
bauzasndipanov: but I'm not against thinking about it, for sure15:35
*** cbader has quit IRC15:35
bauzasndipanov: lol15:36
ndipanovno I'm serious15:36
bauzasndipanov: yeah take it as an ironic laugh15:36
alaskindipanov: in the past what I've done is create a high level spec to work through this stuff, then split it out into work specs15:36
bauzassooooo15:36
ndipanovalaski, that seems like the better approach here15:36
ndipanovwe really need a high level : there are the problems we want to solve, this is a series of steps that we'll take15:37
bauzasat least we need to make sure that we reach the number of people reviewing the spec so that we're sure that we covered the whole lifecycle15:37
*** beagles is now known as beagles_brb15:37
*** boris-42 has joined #openstack-nova15:37
claudiubalaski:15:38
ndipanovwe are talking about at least 4 different issues here15:38
claudiubalaski: I heard you are the database master expert, right? :)15:38
ndipanovthat are very much inter-dependent as they deal with the same data model15:38
alaskiclaudiub: I certainly wouldn't call myself that.  but I know a few things15:39
claudiubalaski: well, I hope my problem is among those things. :) So, any idea how to add a new element to an Enum? I have a commit on this, https://review.openstack.org/#/c/185962/  but it's not a proper solution, at least not for postgresql.15:40
bauzasndipanov: okay, so what are we doing ?15:40
bauzasndipanov: while I probably missed the compute side of the spec15:40
claudiubalaski: I was hoping for some advice on that.15:40
bauzasndipanov: shall we just leave that out and continue or just kill the existing progress and discuss ?15:40
*** lucasagomes has quit IRC15:40
bauzasndipanov: because that spec is around for now 2 cycles and I really would like to land something in the right direction15:41
ndipanovwell I don't know15:41
openstackgerritsahid proposed openstack/nova: libvirt: make _create_domain return a Guest object  https://review.openstack.org/18218515:42
openstackgerritsahid proposed openstack/nova: libvirt: introduce method poweroff to Guest object  https://review.openstack.org/18219415:42
openstackgerritsahid proposed openstack/nova: libvirt: introduce method resume to Guest object  https://review.openstack.org/18219515:42
openstackgerritsahid proposed openstack/nova: libvirt: introduce a Guest to wrap around virDomain  https://review.openstack.org/17431315:42
openstackgerritsahid proposed openstack/nova: libvirt: introduce method get_guest to Host object  https://review.openstack.org/18196915:42
ndipanovI didn't know some of this stuff 2 cycles ago15:42
openstackgerritjichenjc proposed openstack/nova: Add DiskNotFound and VolumeNotFound test  https://review.openstack.org/18145515:42
openstackgerritjichenjc proposed openstack/nova: Ignore Cinder error when shutdown instance  https://review.openstack.org/18145415:42
bauzasbut before doing anything, I just want to make sure that my spec is not basically hurting something bad15:42
ndipanovnow we know them so we need to adjust15:42
alaskimy opinion is that we shouldn't stop what's in progress, but it would be good to have the big picture laid out for discussion, and understanding, somewhere15:42
*** lucasagomes has joined #openstack-nova15:42
*** VirtualPCGuy has joined #openstack-nova15:42
bauzasso the question is turned into 'is the current design flexible enough for being adapted in the future ?'15:42
ndipanovbauzas, in this case - probably reducing the scope of the spec to just objectifying stuff would not block it15:42
*** openstackgerrit has quit IRC15:42
bauzasndipanov: that's exactly the rationale :)15:43
ndipanovwhile we can accept changes to the object later15:43
alaskiclaudiub: is your question about the bd migration in the previous patch, or the object change?15:43
*** Nisha has joined #openstack-nova15:43
*** openstackgerrit has joined #openstack-nova15:43
cfriesenbauzas: ndipanov: alaski: somewhere in all this we should be factoring in the fact we need to do proper resource tracking over migrate/live-migrate/resize/rebuild/evacuate15:43
bauzasndipanov: ie. define a contract between the conductor and the scheduler15:43
ndipanovpersistence part is imho in need of further discussion15:43
ndipanovcfriesen, yes15:43
ndipanovthat's why I'm complaining mostly :)15:44
*** agireud has quit IRC15:44
bauzasndipanov: if we're just storing that spec information in a separate table and read it only when the conductor is calling the scheduler, then it doesn't really hurt any model change we could do15:45
claudiubalaski: oups, my bad. db migration in the previous patch15:45
openstackgerritVladik Romanovsky proposed openstack/nova: Adding user_id handling to keypair index api call  https://review.openstack.org/7048515:45
openstackgerritVladik Romanovsky proposed openstack/nova: Adding user_id handling to keypair show api call  https://review.openstack.org/18364315:45
claudiubalaski: my bad, the commit message titles are similar, I misread.15:45
openstackgerritVladik Romanovsky proposed openstack/nova: tests: functional tests for keypairs create in API microversion 2.4  https://review.openstack.org/18364515:45
openstackgerritVladik Romanovsky proposed openstack/nova: Adding user_id handling to keypair create api call  https://review.openstack.org/18364415:45
alaskibauzas: what I'm getting from this is that it's hard to reason about the changes in isolation because it's not clear how, if at all, it affects other related areas that people care about15:45
ndipanovbauzas, idk - that really seems like a big hatchet to me15:45
ndipanovI mean - it seems fine to do that just to get somewhere15:46
bauzasndipanov: tbc, I'm no more opiniated on splitting the scheduler since we made good progress in Nova15:46
*** wznoinsk has joined #openstack-nova15:46
ndipanovbut we know what (some of) the downsides are15:46
ndipanovit seems silly to pretend we don't15:46
bauzasndipanov: so defining clear APIs for the scheduler is cool, but the main point is how we can make sure that we replay the information for each reschedule15:46
*** yamahata has quit IRC15:46
*** tsekiyama has joined #openstack-nova15:47
bauzasndipanov: so, I think we actually have 2 problems : 1/ a design problem, and 2/ a process problem since we are post-Summit and the next discussions will be either in Rochester, MN or at the Summit15:48
bauzasndipanov: I'm sincerely not sure we can kick-off some nice effort about redesign how we can manage our global lifecycle for VMs (about resources)15:48
bauzasnow15:48
ndipanovidk - by having just a wiki that clearly lists the problems we want to solve isntead of having 15 useless specs that talk about testing and security impact15:49
ndipanovwe might have something to go on15:49
bauzasndipanov: we now have a new process called backlog spec15:50
*** otter768 has joined #openstack-nova15:50
bauzasndipanov: that's basically a manifesto saying that we have a problem15:50
bauzasndipanov: and that we need to agree on a plan15:50
ndipanovyes that would be useful15:50
bauzasndipanov: at least, it describes the problem15:50
ndipanovexcept it's several bugs here an there in this case that require us to remodel things15:51
bauzasndipanov: happy with filling a backlog spec at least ?15:51
ndipanov1) we need scheduler hints for later15:51
bauzashints are a pure scheduler information15:51
bauzasthey are not used for claiming right ?15:51
ndipanovbauzas, well IDK - you could say they are - what happens if I move a host to a different aggregate15:52
*** sdake_ has joined #openstack-nova15:52
*** cbader has joined #openstack-nova15:52
ndipanovthey don't need to be15:52
ndipanov2) we need to store information for an ongoing live-migration for resource tracking15:53
ndipanov3) we need to do the same for rebuilds15:53
ndipanov4) we need to store additional information than what is currently available in the migration object15:53
ndipanov5) do we need the migration object if we persist RequestSpec15:54
openstackgerritjichenjc proposed openstack/nova: Add os_shutdown_timeout support  https://review.openstack.org/17721715:54
ndipanov6) (probably) we need a nicer API than just flipping a bunch of instance attributes inline when doing/reverting migrations15:55
*** otter768 has quit IRC15:55
ndipanov7) WE need to structure request spec15:55
ndipanov8) with previous 6 in mind, also decide what goes in it15:55
*** agireud has joined #openstack-nova15:55
ndipanovso yeah a high level document that focuses on this stuff would be very useful15:55
*** sdake has quit IRC15:56
ndipanov9) also probably some stuff about resource tracking and what is a resource15:56
bauzasmmm15:56
bauzasmmm15:56
bauzasmmm15:56
bauzas(does it show how I'm torn ?)15:56
alaskiclaudiub: sorry, got pulled away.  This isn't something I'm really knowledgeable on, but I might suggest zzzeek as a good resource15:57
ndipanov10) also a bunch of stuff dansmith found with restarting flapping services15:57
bauzasndipanov: what I know is that we have multiple items in place for being written or currently being written15:57
bauzasndipanov: 1/ we have the ReqSpec stuff15:57
claudiubalaski: I see. Thanks for the pointer. :)15:57
*** yamahata has joined #openstack-nova15:57
bauzas2/ we have the resource-objects BP15:57
bauzas3/ we have the robustify-evacuation which will allow to keep track of evacuations15:58
ndipanovbut they also don't take into account a ton of stuff15:58
bauzasndipanov: what you ask is a more high-level view15:58
ndipanovI'm all for the agile approach15:58
ndipanovbut it seems silly to simply disregard issues about stuff we already know15:58
bauzasndipanov: ssssshhhht :)15:59
bauzaseh15:59
bauzashonestly, I'm all for discussion15:59
bauzasndipanov: the problem I have is that I only know certain pieces of the puzzle15:59
bauzasndipanov: which is one of the reasons I'm no longer only focusing on the scheduler, since it's just silly to do so16:00
bauzasbut still, you have your own experience16:00
*** READ10 has quit IRC16:00
bauzasndipanov: so the point is, how we can make sure that our mutual feedback are helpful ?16:00
zzzeekclaudiub: that isn’t the database model, if nova uses the PG ENUM type, that would require an ALTER TYPE directive.  at the very least if the sqlalchemy.types.Enum type is being used that directive would have to change.16:00
bauzasndipanov: saying that, I just want to figure out an action plan if possible and then iterate while we discuss on the bigger problem16:01
bauzasndipanov: but at least including johnthetubaguy is worth it :)16:01
*** jlanoux has quit IRC16:03
*** krtaylor has joined #openstack-nova16:04
ndipanovbauzas, I think these kind of issues that require a more in depth design effort just won't be easily solved with "iteration"16:04
ndipanovat least not with our constraints16:04
*** unicell has joined #openstack-nova16:04
bauzasndipanov: hence johnthetubaguy in the loop and probably a backlog spec for describing the problem :)16:05
zzzeekclaudiub: yeah that is also in models.py and also I dont know that that is upgradable at the moment16:05
*** jistr has quit IRC16:05
*** oro has joined #openstack-nova16:05
*** Mike_D_laptop has joined #openstack-nova16:05
*** amotoki_ has quit IRC16:05
claudiubzzzeek: so, I did not find any way to alter through sqlalchemy. The only way I know now would be through raw sql, but i don't know how acceptable that is as a commit.16:05
zzzeekclaudiub: nova uses sqlalchemy-migrate for DB migrations but they are moving to a new system that I dont think yet supports this16:06
ndipanovbauzas, not sure what johnthetubaguy has to do with it - as I said: let's try to come up with a list of known issues16:06
ndipanovthat we know are related to this whole modeling exercise16:06
ndipanovand then go from there - see which ones we can maybe put off for later16:07
ndipanovand see how we can come up with an approach that lets us cover some of the existing oens16:07
*** agireud has quit IRC16:07
claudiubzzzeek: I see. That is a bit problematic then.16:07
ndipanovand then iterate16:07
zzzeekclaudiub: ill ask :)16:07
ndipanovbauzas, if you think you need more info on the migration stuff16:08
claudiubzzzeek: thanks, let me know if you find out anything. :)16:08
ndipanovfeel free to ping us16:08
ndipanover me16:08
bauzasndipanov: what I need to understand are the corner cases that you identify16:08
dansmithzzzeek: claudiub: right now, migrations still have to be written with sqlalchemy-migrate.. the "other thing" is experimental to find things like this16:09
*** mleroy has joined #openstack-nova16:09
dansmithzzzeek: claudiub: so sqla-migrate can't describe an enum change?16:09
ndipanovbauzas, yes - that's exaclty the "design" process we keep skipping16:09
zzzeekdansmith: this is a thing that the “other thing” cannot do right now16:09
bauzasndipanov: in the mean time, I need to dig into the compute manager code and the virt code since it seems I'm missing something crucial to your eyes16:09
zzzeekdansmith: migrate can, b.c. at worst you just write the “ALTER” directly.  it is very different on MySQL vs. Postgresql16:10
zzzeekdansmith: not sure if migrate has a built-in directive16:10
*** browne has joined #openstack-nova16:10
claudiubdansmith: I don't know of any direct / nice way to do that. Changing the enum is only problematic for postgresql, from what I can see.16:10
dansmithzzzeek: okay, well, that's all claudiub needs to worry about16:10
zzzeekdansmith: truth be told I don’t use native enums in any case for this reason, adding elements is a total pita16:10
openstackgerritjichenjc proposed openstack/nova: Handle MessageTimeout to MigrationPreCheckError  https://review.openstack.org/16863516:10
dansmithzzzeek: we have enums in our upper layers, so I'd be fine with saying "don't use native enums" if we know they're hard16:11
*** ildikov has quit IRC16:11
zzzeekdansmith: if this is merged into L as a migrate-only change then…we can’t do an “expand” unless we add support16:11
zzzeekdansmith: OK but you alreay have three native enums in your model16:11
ndipanovbauzas, let me try to write some of these down in the response to that email pls16:11
*** shashankhegde has joined #openstack-nova16:11
dansmithzzzeek: yep, understand16:11
bauzasndipanov: fair enougfh16:11
*** leopoldj has quit IRC16:11
*** fawadkhaliq has quit IRC16:12
*** belmoreira has quit IRC16:12
dansmithzzzeek: sqla-migrate is the only thing that has to work. The point of having the online stuff in-tree alongside migrate is specifically to find things like this that we need to do that it doesn't support, so that16:12
dansmithis fine16:12
zzzeekdansmith: OK but you want online to support this eventually right16:12
dansmithbut if native enums are problematic, we should probably just nuke them first16:12
dansmithzzzeek: if we just make a call not to use native enums, then I don't car4e16:13
dansmithif it's reasonable to add it to online, then sure16:13
dansmithclaudiub: are you asking if this is okay to do? https://review.openstack.org/#/c/185961/1/nova/db/sqlalchemy/migrate_repo/versions/294_add_live_resize_migration_type.py,cm16:14
*** gokrokve_ has joined #openstack-nova16:14
*** alex_klimov has quit IRC16:14
zzzeekdansmith: just noting, my alternative approach does not have this problem16:14
claudiubdansmith: yeah. It only fails for postgresql.16:14
dansmithclaudiub: oh, I see16:15
dansmithclaudiub: this is a tangent, but two things: (a) I thought we weren't going to do live resize in L, and (b) I'm not sure we need a migration record for something like that if we're not moving the instance16:15
*** sahid has quit IRC16:16
*** gokrokve has quit IRC16:17
claudiubdansmith: so, it's not yet been decided, if we do live resize or not. The question was if there are enough people that would want this feature or not. I've had some reply / replies on the spec, saying that that would be something they would like.16:18
dansmithclaudiub: I don't think that was the decision point (demand) :)16:18
*** dprince has quit IRC16:18
*** ijw has joined #openstack-nova16:18
claudiubdansmith: as for (b), well, it's a bit complicated. In the first phase, it will live resize on the same host, Second phase, live resize on a different host.16:18
mdboothIs there a strict upgrade ordering for api and compute, by any chance?16:19
dansmithI think it was about discoverability of policy and/or support of the feature, which is an api impacting thing we're not going to do in L (IIRC)16:19
mdboothSpecifically, is it ever permissible to have an api service older than your compute nodes?16:19
dansmithmdbooth: no16:19
mdboothdansmith: That makes life simpler :) Thanks.16:19
edleafebauzas: jaypipes: n0ano: lxsli: PaulMurray: here's the doodle for a new meeting time: http://doodle.com/akuv4b4ftv68q3me16:19
mdboothdansmith: Actually, let me just check what that no referred to16:20
mdboothNo strict ordering16:20
mdboothOr no api older than compute16:20
dansmithmdbooth: let me clarify then16:20
claudiubdansmith: I don't think I got what you are saying.16:20
dansmithmdbooth: api and conductor (and scheduler) have to match the database schema because they speak directly to it16:20
*** arnaud____ has quit IRC16:21
dansmithmdbooth: so the way we prescribe that an upgrade happens is api first then computes16:21
*** mohitsharma has quit IRC16:21
dansmithmdbooth: because api is mostly stateless and fast16:21
mdboothdansmith: Awesome, thanks.16:21
dansmithmdbooth: so, that's the arrangement we try to ensure works.. newer computes with newer conductors and an older api might kinda work, but it's not something we test or aim for16:22
*** garyk has quit IRC16:22
*** arnaud____ has joined #openstack-nova16:22
dansmithsdague: I recall we're punting on live inplace resize until we have discoverable policy for disabling such a thing, which won't happen in L. Is that you recollection of that discussion as well?16:23
*** ijw has quit IRC16:24
sdaguedansmith: that was my preference16:24
*** nelsnelson has joined #openstack-nova16:24
*** jaypipes has joined #openstack-nova16:24
sdagueand I think the folks in the room were generally on board with that16:25
dansmithagreed16:25
dansmithclaudiub: ^16:25
*** danpb has quit IRC16:25
*** agireud has joined #openstack-nova16:25
claudiubdansmith: well, can't it just be simply disabled through existing ways, if there are people that do not want it?16:26
sdaguedims_, samueldmq - http://lists.openstack.org/pipermail/openstack-dev/2015-June/065496.html I'm starting that as an ML thread before writing up specs on it16:26
sdagueclaudiub: the problem is interop16:26
sdagueadding features that are basically going to be turned off all the time to the API with no discovery mechanism of that fact is taking a bad situation and making it worse16:26
*** arnaud____ has quit IRC16:27
dims_sdague: ack16:27
*** shashankhegde has quit IRC16:27
samueldmqsdague, great, thanks!16:27
openstackgerritJeffrey Zhang proposed openstack/nova: Support all_tenants search_opts for neutron  https://review.openstack.org/18765716:27
*** amotoki_ has joined #openstack-nova16:29
*** annegentle has quit IRC16:29
*** sdake has joined #openstack-nova16:29
*** baoli has quit IRC16:29
*** yassine has quit IRC16:29
*** jogo has quit IRC16:30
*** toan-tran has quit IRC16:30
*** baoli has joined #openstack-nova16:30
luvjaypipes: alright. so i figured it out (by following the source and pdb'ing around :) ) .... I had security_group_api = nova in my nova.conf instead of security_group_api = neutron16:31
jaypipesmakes sense, luv16:31
lxsliedleafe: I see times 2pm - 6pm, those have been localised for me right?16:31
*** sdake__ has joined #openstack-nova16:32
luvyup16:32
*** sdake_ has quit IRC16:32
*** liusheng has quit IRC16:33
*** Nisha has quit IRC16:33
*** liusheng has joined #openstack-nova16:33
*** rpodolyaka2 has joined #openstack-nova16:34
edleafelxsli: yes. It should note the time zone it's showing on the page16:34
edleafeI see 8am - noon16:34
lxsliedleafe: awesome, thanks for confirming16:35
claudiubsdague: that discovery, isn't / can't it done through extensions?16:35
sdagueclaudiub: extensions are deprecated16:36
*** sdake has quit IRC16:36
sdaguebecause they were a giant interop problem16:36
*** sdake has joined #openstack-nova16:36
*** dprince has joined #openstack-nova16:36
*** jogo has joined #openstack-nova16:37
claudiubI get that, but it is a bit strange to deprecate something and offer nothing in its stead..16:37
*** shashankhegde has joined #openstack-nova16:38
sdaguethe goal is actually much less optionality16:38
sdagueso it's not that weird, we really want the nova api to mean one thing, not just be a random pass through layer16:39
dansmithright, it's not so much deprecating extensions as making a conscious decision not to allow pluggability16:39
sdagueexactly16:39
*** sdake__ has quit IRC16:40
*** nelsnels_ has joined #openstack-nova16:40
*** nelsnelson has quit IRC16:40
cfriesensdague: it would be good to define for vendors what the expected method of doing extensions is though, since most are going to want to do some sort of "special sauce" to differentiate themselves rather than compete purely on price/value16:41
dansmiththere is no method16:41
dansmiththat's the point16:42
*** nic has joined #openstack-nova16:42
cfriesendansmith: I've heard a few people say "use a separate endpoint"16:42
cfriesendansmith: which I think would be reasonable....you'd have the vanilla openstack endpoint and then the vendor-specific one for people that want to access special features16:42
*** gokrokve_ has quit IRC16:43
dansmithif it's an endpoint of just vendor things, then maybe, but not if the separate endpoint is nova+vendor16:43
*** gokrokve has joined #openstack-nova16:43
dansmithbut the former is really outside the scope of nova entirely, so us providing a recipe for doing that would be kinda silly, IMHO16:44
cfriesendansmith: so what's the expectation if a vendor wants to add a parameter to an instance that is never going to make it upstream (for vertical scaling, for example)16:44
dansmithcfriesen: not doing it, or not calling themselves openstack16:44
*** beagles_brb is now known as beagles16:44
cfriesendansmith: not sure how we can restrict them from doing a nova+vendor endpoint16:45
dansmithI don't know that defcore would know or care about a nova+vendor endpoint if the nova one exists16:45
cfriesendansmith: and not sure if we want to, as long as they also have a pure nova endpoint16:45
*** gokrokve has quit IRC16:45
dansmithbut that one would not be the nova api16:45
*** gokrokve_ has joined #openstack-nova16:45
dansmithwe can't prevent people from doing it, of course16:46
dansmithbut we can not concern ourselves with making it easy/pluggable, which is all I think we've decided to do, yes?16:46
*** mpavone has quit IRC16:46
lxsliby forcing it to go on a separate endpoint you clearly demarcate the OpenStack (interoperable) API from the proprietary API, which allows cloud users to choose whether to rely on the proprietary API or not16:47
cfriesendansmith: I'm actually thinking that it would be better to be pragmatic and say "you need a pure nova endpoint, but if you want to add extensions then here is how you add a new nova+changes endpoint efficiently".  Clearly there is demand for extensions (witness the number that were added) so I think it makes sense to plan for it somehow.16:47
dansmithcfriesen: everything was an extension before, so measuring the demand by the count is an error.16:48
openstackgerritPetrut Lucian proposed openstack/nova: Hyper-V: Fix SMBFS volume attach race condition  https://review.openstack.org/18767316:48
cfriesendansmith: okay, fair enough16:48
dansmithcfriesen: I don't doubt the demand of vendors wanting to customize the api to their heart's content16:48
openstackgerritNicolas Simonds proposed openstack/nova: Fix/implement resize and revert for RBD-backed images  https://review.openstack.org/18739516:49
cfriesendansmith: my worry is simply that if we say "we don't support extensions", then they'll all go off and implement them in different ways.  If we say "we support extensions in this way as long as you *also* have a pure nova API", then we exercise a bit of control.16:50
dansmithcfriesen: do you think it's okay for vendors to define their own syscalls in their linux distros?16:51
cfriesenAnd then end-users using the pure API get interop, while ones that really want the extra functionality can make an informed decision to use non-interoperable calls.16:51
*** thangp has quit IRC16:51
cfriesendansmith: sure.  I've done it, because our customers wanted a way to do something efficiently that couldn't be done any other way.16:51
dansmithcfriesen: end users will use the thing that gives them the thing they want right now. That locks them in retroactively16:51
dansmithcfriesen: so you break ABI compatibility when you have to move that syscall number?16:52
cfriesendansmith: yep, because it was for an embedded device that got built from source each time16:52
openstackgerritPetrut Lucian proposed openstack/nova: Hyper-V: Implement nova rescue  https://review.openstack.org/12715916:52
dansmithheh, okay, so if you're exposing a non-public interface where you control the client and server at all times, then you just add a microversion on top (or don't if it suits you) and then just replace both each time you upgrade, right?16:53
dansmithif you care about public-facing things where you don't have that control,16:53
dansmiththen you can't do it, just like you can't do it in your kernel and expect binary compatibility with the rest of the world16:53
*** Nisha has joined #openstack-nova16:54
*** IanGovett has joined #openstack-nova16:54
*** diegolp has quit IRC16:55
*** pixelbeat has quit IRC16:57
*** yamahata has quit IRC16:57
*** emagana has quit IRC16:57
*** thangp has joined #openstack-nova16:57
*** lpetrut has quit IRC16:58
cfriesendansmith: right...this is different than the kernel case in that we do want to preserve the stock nova endpoint.  But it coming from a project that used to support extensions, it now seems harsh to say "if you want anything other than stock upstream API then you have to patch the source".16:58
*** baoli has quit IRC16:58
*** matrohon has quit IRC16:58
cfriesendansmith: anyways, not the most important thing to work on right now. :)16:58
*** emagana has joined #openstack-nova16:59
dansmithit seems completely undifferent from the kernel case, but yeah, very happy to stop discussing it :)16:59
*** IanGovett1 has joined #openstack-nova16:59
*** IanGovett has quit IRC17:01
mriedemso...i want my own nova v2.1.1 api, that's cool right?17:01
mriedemsorry, hello friends17:01
*** baoli has joined #openstack-nova17:01
mriedemi meant to preface with 'hello friends'17:01
*** nelsnels_ has quit IRC17:02
*** nelsnelson has joined #openstack-nova17:02
dansmithmine is nova v2.1.37-dan.el7-321extrasuff~317:02
mriedemv2.1.1 is sure to be much glorious api #117:02
*** nelsnelson has quit IRC17:02
*** nelsnelson has joined #openstack-nova17:04
*** nelsnelson has quit IRC17:04
*** ildikov has joined #openstack-nova17:05
*** derekh has quit IRC17:06
mriedemi'd like to propose an api that allows you to dynamically create flavors when booting or resizing an instance....17:06
dansmithmriedem: lol :)17:06
*** agireud has quit IRC17:07
*** achanda has joined #openstack-nova17:08
*** IanGovett has joined #openstack-nova17:09
*** IanGovett has quit IRC17:09
*** pbandzi has quit IRC17:09
*** vilobhmm has joined #openstack-nova17:09
*** dulek has quit IRC17:10
*** alanf-mc has joined #openstack-nova17:10
*** gszasz_ has joined #openstack-nova17:11
*** gszasz_ has quit IRC17:11
*** IanGovett1 has quit IRC17:11
*** baoli has quit IRC17:12
*** gszasz has quit IRC17:14
*** jdurgin has joined #openstack-nova17:15
*** angdraug has joined #openstack-nova17:16
*** rushiagr_away is now known as rushiagr17:17
*** baoli has joined #openstack-nova17:18
*** lpetrut has joined #openstack-nova17:18
*** ijw has joined #openstack-nova17:18
*** lucasagomes is now known as lucas-dinner17:19
*** shashankhegde has quit IRC17:22
*** ijw has quit IRC17:24
*** yamahata has joined #openstack-nova17:24
*** gholler has quit IRC17:24
*** zhangtralon has joined #openstack-nova17:27
*** tonytan4ever has quit IRC17:28
*** Hosam has quit IRC17:28
*** baoli has quit IRC17:28
*** tonytan4ever has joined #openstack-nova17:28
*** baoli has joined #openstack-nova17:29
*** emagana has quit IRC17:32
*** mtanino has quit IRC17:33
*** paul-carlton has quit IRC17:33
*** tonytan4ever has quit IRC17:33
*** zhangtralon has quit IRC17:33
*** amotoki_ has quit IRC17:34
*** romainh1 has left #openstack-nova17:37
melwittdansmith: I've been investigating an intermittent problem while I test my "send Instance object to cells" patch where an instance.destroy() fails because "host changed". however when I look at "host" on the instance, it's None still and with sqlalchemy debugging turned all the way up, I see a "ROLLBACK" after the UPDATE that's supposed to delete the row. do you know what the ROLLBACK means?17:38
dansmithmelwitt: well, it means it undoes everything in the transaction17:39
dansmithmelwitt: is the rollback the thing that is changing host, or the thing that fails because host is changed?17:39
*** josecastroleon has quit IRC17:39
melwittdansmith: the latter. it's the update to soft delete the instance17:40
*** agireud has joined #openstack-nova17:40
dansmithmelwitt: so there is something in instance_destroy() that checks instance.host?17:40
*** baoli has quit IRC17:41
*** lpetrut has quit IRC17:41
dansmithmelwitt: ah, is it the constraint thing?17:41
melwittdansmith: sorry I'm confused about how this stuff works. yes, the constraint, if host isn't set on the instance, it will do the db.instance_destroy with a constraint that host must be null17:41
*** ildikov has quit IRC17:42
*** mriedem has quit IRC17:42
dansmithmelwitt: okay, so the raise because of the failed constraint is why the ROLLBACK is happening, I think17:42
dansmithso that's expected17:42
dansmiththe reason for the constraint being unsatisfied is what you need to chase I think17:42
*** ociuhandu has quit IRC17:43
dansmithI think maybe alaski had some thoughts about this, relating to the instance being  updated in one cell (and gaining a host or something) before this delete happens...17:43
melwittyeah, it's just it seems like the constraint was satisfied, at least host is null after it's all done and failed. and recently alaski added a catch ObjectActionError to retry delete if cell_name is set, which it seems to be, but that doesn't fire either17:44
*** tonytan4ever has joined #openstack-nova17:44
*** baoli has joined #openstack-nova17:44
*** ssurana has joined #openstack-nova17:44
*** lpetrut has joined #openstack-nova17:44
alaskiyeah, I added a retry in one spot for this17:45
alaskimelwitt: are you sure host is null in the db when it fails, not just on the object?17:45
dansmithso the constraint is that if we don't know what our host is, or it's set to None, make sure we don't delete the instance if the DB has host != None, yes?17:45
melwittalaski: yeah, in looking at the code, I don't see how host could change without cell_name being set17:45
melwittbut that's what I'm seeing. I just don't get it17:45
melwittdansmith: yes17:46
alaskimelwitt: I agree, I don't see how host could change without cell_name being set17:46
alaskibut there could be a difference between the db, and whats on your current object17:47
melwittalaski: I'm not sure. I've got all this sqlalchemy debug output that doesn't seem to tell me as much as I thought it would. I thought it would show what the fields in the instance row are at the time the soft delete fails17:47
*** shashankhegde has joined #openstack-nova17:47
dansmithalaski: the constraint is only set if the current object is unset or =None, so it has to be non-None in the database to fail, right?17:47
alaskidansmith: right17:48
alaskimelwitt: can you try an instance.refresh and then see what's set?17:48
melwittwhen I check the db manually after this happens, host is NULL17:48
alaskithat's odd17:49
melwittso I was wondering if it was at all possible the constraint wasn't querying right, but I see with the debug output it's UPDATE instances SET updated_at=updated_at, deleted_at=%s, deleted=id WHERE instances.deleted = %s AND instances.uuid = %s AND instances.host IS NULL17:49
melwittwhich should be right17:49
*** Nisha has quit IRC17:50
*** otter768 has joined #openstack-nova17:51
alaskilooking at instance_destroy in sqlalchemy/api.py it seems that the constraint failure can be raised if no rows are updated17:52
alaskiso it's possible the instances.deleted = %s is failing17:52
*** zhangtralon has joined #openstack-nova17:53
melwittalaski: right. that's what I was trying to figure out, if there was some other way it could fail since host seems to be null17:53
alaskiif deleted != 0 it could fail I think17:54
melwittdoesn't instances.deleted mean not deleted? that is,17:54
*** baoli has quit IRC17:54
*** ildikov has joined #openstack-nova17:55
*** nickchase has quit IRC17:55
*** otter768 has quit IRC17:55
alaskiif we assume it passes in 0 there, yeah.  it won't try to redelete something that's deleted17:55
melwittthe delete path before scheduled involves a broadcast to all cells to delete, followed by a local delete at the top17:55
*** mriedem has joined #openstack-nova17:57
melwittso it might be possible for an instance_destroy_at_top to happen before the local delete, if there was indeed an instance found in the child. I need to check that17:57
*** ociuhandu has joined #openstack-nova17:57
*** jlk has joined #openstack-nova17:57
*** aix has quit IRC17:57
jlkHey all, fighting a resize issue, trying to figure out where Nova resolves hostname to IP address in order to talk to other compute hosts to set up the transfer over ssh. Can anybody help?17:58
*** zhangtralon has quit IRC17:59
melwittalaski: you're right, it's because it was already deleted. now I will find out how that happened17:59
alaskimelwitt: ahh, cool.  seems likely that it's the race you described18:00
alaskiI mean, cool that I'm right, not that it's happening :)18:01
*** baoli has joined #openstack-nova18:01
melwittalaski: hehe. yeah, while my patch "solves" the race where instances can be "undeleted" I found we just move to a different race, the opposite double delete18:02
dansmithjlk: there is this thing18:02
dansmithjlk: it does the translation18:02
dansmithjlk: it's called DNS18:02
* dansmith ducks18:02
* jlk tweets nasty things18:02
dansmithbackfired!18:03
jlkokay, looks like migrate_disk_and_power_off gets a dest from somewhere18:03
dansmithfrom the scheduler, if you didn't select a destination18:04
jlkalright, and scheduler does the resolution?18:04
jlkI ask because nova-compute is logging the resolved IP address18:04
dansmithso the hypervisor hostname is what nova will try to use for the ssh command I think18:04
*** jwcroppe has joined #openstack-nova18:04
dansmithit is?18:04
*** zhangtralon has joined #openstack-nova18:04
*** rotbeard has quit IRC18:04
jlkerror while running command. Command: ssh 173.247.104.36 mkdir -p /var/lib/nova/instances/195e844c-18:05
jlkbut my host-list is names like ds1351.sea0318:05
dansmithjlk: hmm, does nova show on the instance show that the hypervisor hostname is an IP?18:05
jlkso somewhere along the way this host-list is getting resolved into an IP address (wrongly)18:05
jlkno, it shows the host-list name, ds1352.sea0318:05
dansmithI could be wrong, but I don't think it's pre-resolving it18:06
jlkthen it would be rootwrap doing it?18:06
jlk| OS-EXT-SRV-ATTR:hypervisor_hostname  | ds1352.sea0318:06
dansmithno, I don't think so18:07
jrolljlk: you haven't learned by now to always blame dns? :)18:07
jlkI tried, by stuffing values in /etc/hosts18:07
jlkbut either I'm doing that wrong, or...18:07
jlkah hah18:08
jlknova/compute/resource_tracker.py:        migration.dest_host = self.driver.get_host_ip_addr()18:08
dansmithhuh18:09
jlkreturns CONF.my_ip18:09
jlkfor libvirt18:09
* jlk shaves the yak some more18:09
dansmithoh, on the destination call?18:09
*** openstackgerrit has quit IRC18:09
jlkyeah when it's determining a destination, it does the IP look up18:10
*** openstackgerrit has joined #openstack-nova18:10
jlkso if my_ip isn't defined, goes to nova.netconf18:10
dansmithno, I think that's after it has determined the host,18:10
jlksure18:10
dansmithand when the source makes the call to the destination, it's saying "so, what IP should I use?"18:11
jlkpicks a host, and then translates that host into an IP, to pass off to the migration calls18:11
dansmithI think it's asking the host itself to do the translation (which is really just "tell me what your configured IP is")18:11
dansmithbut yeah18:11
*** ociuhandu has quit IRC18:11
jlkoh, and that does a socket.socket.getsockname()18:12
jlkbut which service is this, shoudl be the nova-compute service, ya?18:13
dansmithyeah18:13
jlkI'm betting this doesn't take /etc/hosts into account dos it?18:13
dansmithif it's just looking at CONF then no18:13
jlkthere is nothing in my conf for my_ip18:14
*** promulo has joined #openstack-nova18:14
dansmithoh you mean in the fallback path18:14
*** mtanino has joined #openstack-nova18:14
* dansmith shrugs18:14
jlkyeah18:14
jlkoh dear18:17
jlkI see what this is doing18:17
jlkit's checking to see what address it would connect /out/ as to the Internet. Which in our case is odd.18:17
jlkyeah that's not going to work at all, guess we have to configure my_ip18:17
*** annegentle has joined #openstack-nova18:21
jlksuccess!18:21
vilobhmmdansmith, melwitt : can you please review https://review.openstack.org/#/c/138607/ when you are free?18:21
dansmithvilobhmm: you don't need to ask me every day.. I will re-review it when I'm free.. honest.18:22
*** gokrokve_ has quit IRC18:23
vilobhmmcool18:23
*** thiagop has joined #openstack-nova18:26
*** amotoki_ has joined #openstack-nova18:35
*** tralon_ has joined #openstack-nova18:36
*** vilobhmm has quit IRC18:38
*** zhangtralon has quit IRC18:39
*** amotoki_ has quit IRC18:40
*** tjones1 has joined #openstack-nova18:40
tjones1@jaypipes if you need any help with https://review.openstack.org/#/c/184534/1 i'd love to be involved18:41
*** nelsnelson has joined #openstack-nova18:41
ndipanovhey does anyone by any chance remember how to display instance faults with the cli?18:41
jaypipestjones1: sweet! thanks! I will certainly keep that in mind18:41
dansmithndipanov: nova show, if the instance is in error state18:41
*** nelsnelson has quit IRC18:41
*** erhudy has quit IRC18:42
*** gokrokve has joined #openstack-nova18:42
ndipanovbut if not then nothing...18:42
ndipanovI see18:42
*** nelsnelson has joined #openstack-nova18:42
*** tralon_ has quit IRC18:43
*** jwcroppe has quit IRC18:43
melwittdansmith: another thing I learned is behavior has changed from what cells expects when broadcasting a delete to all cells (when host is None). there are several places in compute where InstanceNotFound is caught and ignored for cells, as it expects the exception to be raised when attempting instance.save(). this isn't necessarily true when instance goes to _save_flavor() and does db.instance_extra_update_by_uuid before the db.instance_update_and_ge18:43
melwittt_original. in that case, if the instance doesn't exist, the FK constraint will fail trying to do the instance_extra update18:43
melwittoops18:43
*** gokrokve has quit IRC18:44
dansmithah18:44
*** gokrokve has joined #openstack-nova18:44
openstackgerritDan Smith proposed openstack/nova: Begin the transition to an explicit object registry  https://review.openstack.org/18771818:44
openstackgerritDan Smith proposed openstack/nova: Convert test objects to new field formats  https://review.openstack.org/18771918:44
openstackgerritDan Smith proposed openstack/nova: Use fields from oslo.versionedobjects  https://review.openstack.org/18772018:44
dansmithmelwitt: we really need to make instance_update do all of that more atomically and in a single transaction anyway18:44
*** achanda has quit IRC18:45
melwittdansmith: yeah. I was about to ask what you suggest :)18:45
dansmithmelwitt: is it hurting anything (i.e. failing) or just doing extra stuff in the DB?18:47
melwittdansmith: well, for deleting an instance that hasn't been scheduled, the broadcast to delete in all cells will fail in cells that don't have the instance. DBReferenceError is raised instead of the expected and caught InstanceNotFound which rolls back quotas18:49
*** vilobhmm has joined #openstack-nova18:49
dansmithah, hmm18:50
mriedemdansmith: when is your birthday? http://www.amazon.com/Am-Better-Than-Your-Kids/dp/1439182868/ref=asap_bc?ie=UTF818:50
*** kiran-r has joined #openstack-nova18:50
dansmithmriedem: heh18:50
*** cbader has quit IRC18:51
dansmithmriedem: if you're going to get me something, a poster of this would be better: http://photos1.meetupstatic.com/photos/event/b/3/4/e/highres_323505902.jpeg18:51
*** cbader has joined #openstack-nova18:51
mriedemno18:51
mriedembook or nothing18:51
melwittdansmith: like this https://github.com/openstack/nova/blob/master/nova/compute/api.py#L1615-L1618 thought it says "race condition" which I thought it wouldn't be in the case of the broadcast for non-scheduled instance18:51
*** cbader has quit IRC18:51
*** cbader has joined #openstack-nova18:52
melwittdansmith: and this is where the DBReferenceError gets raised if the instance doesn't exist https://github.com/openstack/nova/blob/master/nova/compute/api.py#L153818:52
*** alexpilotti has quit IRC18:52
dansmithmelwitt: just so I'm clear, it raises DBReferenceError when you try to save something like the flavor, yes?18:53
dansmithas part of the instance save18:53
melwittdansmith: yes. I saw it was trying to save flavor in there18:54
dansmithright, so could we make things like _save_flavor() catch DBReferenceError and raise InstanceNotFound? I would think "instance doesn't exist" is the only way we can hit that anyway, so that should be accurate, right?18:54
melwittduring the broadcast to instance_delete_everywhere for all cells18:54
melwittdansmith: yeah, I think that would work18:55
*** asselin has quit IRC18:55
*** artom has quit IRC18:55
*** cbader has quit IRC18:55
*** artom has joined #openstack-nova18:55
*** cbader has joined #openstack-nova18:55
*** asselin has joined #openstack-nova18:55
dansmithshould be able to check it even in unit tests, by hand-creating an instance object with a dirty flavor and trying to run .save() on it18:55
*** asselin has quit IRC18:56
*** cbader has quit IRC18:56
*** openstackgerrit has quit IRC18:56
*** kaisers1 has quit IRC18:56
*** asselin has joined #openstack-nova18:56
*** cbader has joined #openstack-nova18:56
*** cbader has quit IRC18:56
*** asselin has quit IRC18:56
*** openstackgerrit has joined #openstack-nova18:56
*** kaisers has quit IRC18:57
*** asselin has joined #openstack-nova18:57
*** cbader has joined #openstack-nova18:57
*** asselin has quit IRC18:57
*** cbader has quit IRC18:57
*** kaisers has joined #openstack-nova18:57
*** asselin has joined #openstack-nova18:57
*** cbader has joined #openstack-nova18:58
*** cbader has quit IRC18:58
*** cbader has joined #openstack-nova18:58
*** kaisers1 has joined #openstack-nova18:59
melwittdansmith: cool, I'll cook it! thanks18:59
*** asselin has quit IRC19:00
*** asselin has joined #openstack-nova19:00
*** rushiagr is now known as rushiagr_away19:01
dansmithmelwitt: cool :)19:01
*** asselin has quit IRC19:01
*** asselin has joined #openstack-nova19:01
*** asselin has quit IRC19:01
*** asselin has joined #openstack-nova19:02
*** asselin has quit IRC19:02
*** cbader has quit IRC19:03
*** asselin has joined #openstack-nova19:03
*** cbader has joined #openstack-nova19:03
*** achanda has joined #openstack-nova19:03
*** asselin has quit IRC19:04
*** cbader has quit IRC19:04
*** cbader has joined #openstack-nova19:04
*** asselin has joined #openstack-nova19:05
*** asselin has quit IRC19:05
*** cbader has quit IRC19:05
*** cbader has joined #openstack-nova19:06
*** asselin has joined #openstack-nova19:06
*** asselin has quit IRC19:06
*** asselin has joined #openstack-nova19:07
*** vladikr has quit IRC19:07
*** asselin has quit IRC19:08
*** asselin has joined #openstack-nova19:08
*** asselin has quit IRC19:09
*** cbader has quit IRC19:09
*** cbader has joined #openstack-nova19:09
*** asselin has joined #openstack-nova19:09
*** cbader has quit IRC19:10
*** asselin has quit IRC19:10
*** asselin has joined #openstack-nova19:10
*** cbader has joined #openstack-nova19:10
mriedemclaudiub: want to take another look at this? i fixed the test failures and squashed the other commit that it was pulling in so it's a bit more explicit https://review.openstack.org/#/c/174779/19:11
*** cbader has quit IRC19:12
*** cbader has joined #openstack-nova19:12
*** cbader has quit IRC19:14
samueldmqsdague, dims_ Dynamic Policy for Access Control Subteam Meeting  http://lists.openstack.org/pipermail/openstack-dev/2015-June/065524.html19:14
samueldmqsdague, dims_ you guys might be interested on this19:14
*** cbader has joined #openstack-nova19:15
*** tellesnobrega_ has joined #openstack-nova19:16
*** baoli has quit IRC19:17
*** tonytan4ever has quit IRC19:17
dansmithmriedem: actually that book looks pretty funny19:17
*** baoli_ has joined #openstack-nova19:18
*** gholler has joined #openstack-nova19:18
*** iamjarvo has joined #openstack-nova19:19
*** belmoreira has joined #openstack-nova19:20
*** kaisers has quit IRC19:21
openstackgerritDan Smith proposed openstack/nova: Use fields from oslo.versionedobjects  https://review.openstack.org/18772019:23
*** vladikr has joined #openstack-nova19:23
dansmithdims_: you don't need to waste your time reviewing (unless you want), but just for progress reporting ^^19:23
*** kaisers has joined #openstack-nova19:23
*** achanda has quit IRC19:26
*** VW has quit IRC19:27
*** tonytan4ever has joined #openstack-nova19:28
*** ajo has quit IRC19:29
dims_dansmith: +1'ed the g-r bump19:31
dansmithdims_: thanks19:31
openstackgerritEd Leafe proposed openstack/nova-specs: Improve reporting when Scheduler returns NoValidHost  https://review.openstack.org/18773919:31
*** mtanino has quit IRC19:33
*** kaisers1 has quit IRC19:35
dansmithman I hate gerrit's people searchg19:35
*** annegentle has quit IRC19:35
*** annegentle has joined #openstack-nova19:36
claudiubmriedem: done. will +A once Jenkins says he's happy.19:36
*** kaisers1 has joined #openstack-nova19:36
mriedemclaudiub: grenade failed so i'll check that out19:37
*** VW has joined #openstack-nova19:37
openstackgerritAnand Shanmugam proposed openstack/nova: Changing defult value of description from None to empty string  https://review.openstack.org/18774119:37
*** ajo has joined #openstack-nova19:38
melwittdansmith: me too. the best I could figure out is owner:"First Last" with the exact way their full name is19:39
dansmithyeah, but quotes don't seem to work in the add-to-this-review box19:39
mriedemalaski: check-tempest-dsvm-cells should probably not be running on stable/juno right?19:40
mriedemit's non-voting, but is there even a point in running it?19:40
openstackgerritAnand Shanmugam proposed openstack/nova: Changing defult value of description from None to empty string  https://review.openstack.org/18774119:40
openstackgerritAnand Shanmugam proposed openstack/nova: Changing default value of description from None to empty string  https://review.openstack.org/18774119:40
melwittdansmith: oh yeah, the add to review box. I haven't figured that out19:40
dansmithmelwitt: I tried swearing like a sailor at it, but that didn't help either :/19:41
melwittdansmith: :) I do the primitive "start typing their email" and hope it autocompletes and try that repeatedly19:42
*** krak has joined #openstack-nova19:43
*** kaisers has quit IRC19:43
*** qianli_ has quit IRC19:44
*** moshele has joined #openstack-nova19:44
*** qianli_ has joined #openstack-nova19:44
krakAlways reproducible, can someone please have a look? http://paste.openstack.org/show/257173/19:44
mriedemkrak: see channel topic please19:45
*** kaisers has joined #openstack-nova19:45
krak@mriedem : sorry didnt get you ?19:46
mriedemkrak: this is a development channel, not a support channel19:46
krakaah okay19:46
mriedemsupport questions are for the #openstack channel or ask.openstack.org19:46
kraksure . thanks mriedem19:47
*** annegent_ has joined #openstack-nova19:47
mriedemthe formatting of your paste is hard to read btw19:47
krakumm, you need to read it in raw.19:47
*** kiran-r has quit IRC19:48
krakmriedem: It's something related to VNC, so I thought someone must have worked on it here.19:48
*** mtanino has joined #openstack-nova19:48
*** ivasev has quit IRC19:49
*** belmoreira has quit IRC19:49
*** annegentle has quit IRC19:50
*** otter768 has joined #openstack-nova19:52
*** ddaskal has joined #openstack-nova19:54
*** alanf-mc has quit IRC19:54
*** otter768 has quit IRC19:56
*** tjones1 has quit IRC19:57
*** matrohon has joined #openstack-nova19:57
dansmithI've seen a several ironic pxe job fails in the last couple hours19:58
dansmithis that a thing?19:58
dims_dansmith: oslo.messaging tripped up ironic conductor we are trying to merge a fix for it19:59
mriedemdansmith: link?19:59
alaskimriedem: right, the tempest-cells job is never going to pass on juno unless we backport a lot of stuff, which isn't likely to happen19:59
mriedemdims_: is there a bug for it?19:59
dansmithdims_: okay19:59
dansmithmriedem: http://logs.openstack.org/18/187718/1/check/check-tempest-dsvm-ironic-pxe_ssh/2bfa220/console.html19:59
*** sdake_ has joined #openstack-nova19:59
mriedemha http://logs.openstack.org/18/187718/1/check/check-tempest-dsvm-ironic-pxe_ssh/2bfa220/logs/screen-ir-cond.txt.gz?level=TRACE19:59
dims_mriedem: yes https://review.openstack.org/#/c/187722/20:00
dansmithnot in e-r yet that I see20:00
mriedeme-r is behind20:00
alaskidansmith: melwitt it's not foolproof, but searching on lp and using their lp username often works20:00
mriedemjobs were hung since sundsay20:00
mriedem*sunday20:00
dansmithalaski: yeah, but that doesn't seem to always work, as you say20:01
dansmithmriedem: I'm seeing quick response from e-r this morning20:01
dansmithmriedem: but I mean I don't see it on the e-r page20:01
mriedemdansmith: that's why i asked for the bug number20:01
dansmithokay20:01
*** whenry has joined #openstack-nova20:01
mriedemi'll have it up shortly20:02
*** tjones1 has joined #openstack-nova20:02
dansmithseems like we should make a point of putting any gate-blocking thing into e-r immediately :)20:02
mriedemyeah20:02
dansmithto stop people like myself from asking dumb questions and feeling stupid :)20:02
mriedemhave to know there is an issue first20:02
dansmithwell, sounds like the oslo people knew20:02
*** sdake has quit IRC20:03
*** Mike_D_laptop has quit IRC20:03
mriedemi knew there were a bunch of oslo releases scheduled for today20:03
dims_mriedem: all of them were done this morning20:03
*** samueldmq has quit IRC20:05
dims_dansmith: bringing it up20:06
*** pixelbeat has joined #openstack-nova20:06
bauzasalaski: hey, do we have tomorrow's meeting for cells at 1700 UTC ?20:07
bauzasalaski: because I could maybe be off20:07
alaskibauzas: that's what I have on my calendar20:07
bauzasalaski: okay20:07
*** ddaskal has quit IRC20:08
bauzasalaski: so did you get the discussion with ndipanov ?20:08
bauzasalaski: sounds like he would be unhappy with persisting the ReqSpecd20:08
alaskiI think I got most of it20:08
ndipanovwell not exactly unhappy20:08
*** Raildo has joined #openstack-nova20:08
ndipanovI'd just like to see more thought put into it20:08
alaskiit's the duplication of data that's a big concern, right?20:08
ndipanovI may be wrong and persisting is the right thing to do20:08
ndipanovor it's not that big of a deal20:09
dansmithwell,20:09
alaskiand being clear which object is used for which purpose20:09
ndipanovalaski, yes that for sure20:09
dansmithwe *have* to persist it until we have scheduled20:09
dansmithalaski: right.?20:09
dansmithalaski: else we can't answer queries for the instance20:09
alaskidansmith: yes20:09
alaskibut once the instance is created, we can hydrate the object from data on the instance and not need to dupe it20:09
alaskiwhich I think addresses some concern20:10
dansmithwith the exception of the things we don't store currently20:10
*** openstackgerrit has quit IRC20:10
alaskiright, which can go to instance_extra20:10
bauzasthat's what alaski propopsed with BuildRequest right ?20:10
*** openstackgerrit has joined #openstack-nova20:10
ndipanovalaski, right20:10
bauzashttps://review.openstack.org/#/c/169901/3/specs/liberty/approved/add-buildrequest-obj.rst,cm20:11
alaskibauzas: sort of, buildrequest is sort of an empty instance20:11
bauzasokay, here are my thoughts20:11
bauzas1/ we know that ReqSpec can't be helping all the issues we have20:11
*** ddaskal has joined #openstack-nova20:12
bauzas2/ we need to sit down and discuss on the high-level issues that we have, and ndipanov will provide a view for that20:12
*** alex_klimov has joined #openstack-nova20:12
bauzas3/ in the meantime, we can move on and work on implementing the ReqSpec objectification and try to see how we can persist it20:12
openstackgerritVladik Romanovsky proposed openstack/nova: Adding user_id handling to keypair index api call  https://review.openstack.org/7048520:13
openstackgerritVladik Romanovsky proposed openstack/nova: Adding user_id handling to keypair show api call  https://review.openstack.org/18364320:13
openstackgerritVladik Romanovsky proposed openstack/nova: tests: functional tests for keypairs create in API microversion 2.4  https://review.openstack.org/18364520:13
openstackgerritVladik Romanovsky proposed openstack/nova: Adding user_id handling to keypair create api call  https://review.openstack.org/18364420:13
bauzas4/ if some new usage for ReqSpec has to be done, then we need to discuss on how it could be done20:13
bauzasguys ?20:13
bauzas(trying to figure out actions by 11pm here)20:13
bauzas10.20pm actually20:13
alaski5/ give up and go shopping20:14
dansmithyes20:14
dansmiththat20:14
bauzasalaski: yey20:14
bauzasalaski: I'll be in Disneyland next week20:14
bauzasalaski: so I'll ask Cinderall20:14
bauzasCinderella20:14
*** iamjarvo has quit IRC20:14
alaskimy take is that the requestspec object you have proposed is an interface for what we send to the scheduler, and that's good.  the issue of persistence is where the data is stored so it's not duped, or a total mess20:15
bauzasalaski: okay I think we agree then20:15
alaskiand overall we have a glob of data that we need to slice up for use by the scheduler/compute/resource tracker/whatever with as little duplication as possible20:16
*** tellesnobrega_ has quit IRC20:16
bauzasalaski: fair enough, will continue to work on the implementation20:17
alaskiand the important thing is getting the APIs right, and then sorting out persistence as best we can given what we have now20:17
bauzasalaski: oh +120:17
*** salv-orlando has quit IRC20:18
ndipanovaI completely agree with alaski fwiw20:18
*** ppal has joined #openstack-nova20:18
*** nihilifer has quit IRC20:19
bauzasokay, hands-on then :)20:19
bauzasthanks for the clarification folks, greatly appreciated20:20
ndipanovbauzas, so fleshing out that series more to the point where it is clear how the persisted data is accessed is where I think we would really see more informed oppinions forming20:20
alaskicool.  And this should be written up somewhere so we can talk things through as we flesh it out20:20
bauzasndipanov: that's on my path :)20:21
ndipanovalaski, I will respond to the email bauzas sent with some of the details I poitned out20:21
bauzasalaski: you mean amending the persistence spec ?20:22
*** apmelton_away is now known as apmelton20:22
bauzasnvm20:22
bauzasndipanov: thanks for that20:22
*** dprince has quit IRC20:22
bauzasokay, I didn't want initially to discuss on the ReqSpec object, but rather on cells :)20:22
alaskindipanov: great, that will be helpful20:23
bauzasalaski: I've been heard that melwitt is chasing the last 2 outstanding bugs that we have for the v1 job ?20:23
ndipanovok folks I'm off20:23
*** ppal has quit IRC20:23
alaskio/20:24
*** ndipanov has quit IRC20:24
bauzas\o and thanks20:24
alaskibauzas: she's chasing one that I know of20:24
alaskithe big one that's causing the unexpected task state failures20:24
*** amotoki_ has joined #openstack-nova20:24
bauzasalaski: okay, I need fresh flesh for changing my mind from that reqspec bp20:24
alaskithere's still the list instances negative test failure, I don't know if it's on her list20:25
bauzasalaski: yeah, saw that one20:25
bauzasalaski: okay, let's sort that out tomorrow20:26
bauzasalaski: I'll try to attend the meeting hopefully20:26
bauzasalaski: and see how I can help20:26
bauzas(for the negative test I mean)20:26
alaskicool20:26
bauzasalaski: gotta go, bye20:27
bauzasalaski: will review the cells specs by tomorrow before the meeting20:27
alaskibye20:27
*** ddaskal has quit IRC20:28
alaskihmm, that means I should probably update those20:28
*** amotoki_ has quit IRC20:29
*** alanf-mc has joined #openstack-nova20:29
bauzasalaski: based on the Summit feedback ? eh, if you have time20:30
bauzasalaski: I said that because I have a awful review backlog and I need to refresh my mind before the meeting20:31
alaskiI need to scrape the etherpads and remind myself what I signed up for.  But I really do need to update those specs and push up a few more20:32
bauzasalaski: good tip https://etherpad.openstack.org/p/YVR-nova-liberty-summit-action-items20:32
alaskiwell that's handy20:33
bauzasalaski: that's WIP20:33
bauzasalaski: at the bottom are the etherpads processed by johnthetubaguy's brain engine20:34
*** Raildo_ has joined #openstack-nova20:35
melwittbauzas alaski: I think the unexpected task state isn't really the problem, it's the "sync from cells can undelete an instance" that's the issue, I opened this bug to track https://launchpad.net/bugs/146035020:38
openstackLaunchpad bug 1460350 in OpenStack Compute (nova) "Cells: Race deleting instance can lead to instances "undeleted" at the top" [Low,In progress] - Assigned to melanie witt (melwitt)20:38
*** operator99 is now known as gyee20:39
bauzasoh my20:39
*** Raildo has quit IRC20:39
melwittI think it gets solved by my patch that sends object to cells update_at_top, since that can't undelete anything. right now I'm running my patch through the failing test in a loop and exposing other race conditions20:40
bauzasmelwitt: fair point20:40
alaskimelwitt: nice20:40
*** ociuhandu has joined #openstack-nova20:40
bauzasmelwitt: you mean https://review.openstack.org/#/c/176518/ ?20:41
melwittthe metadata key delete failure is another race, where the metadata delete request hits before the metadata update that adds the key hits, I think. I have to look at that one more20:41
*** radek_ has quit IRC20:41
*** emagana has joined #openstack-nova20:41
alaskian issue that I looked at internally just before the summit is instances that are deleted, but terminated_at isn't set.  Which I think is a similar thing, out of order messages causing updates to fail20:41
bauzasmelwitt: could you please update the old testing etherpad we have so I could dig into it ?20:41
melwittbauzas: yes that's the patch. and do you mean update it about the metadata key thing?20:42
bauzasalaski: which is a bit worrying me since we will also have 2 databases for cells v220:42
*** iamjarvo has joined #openstack-nova20:42
bauzasmelwitt: yeah, I need to refresh my mind20:42
alaskibauzas: but not two databases with the same info that needs to be synced20:43
bauzasmelwitt: that's too long that I didn't help the cells job20:43
bauzasalaski: right20:43
*** emagana has quit IRC20:43
alaskibauzas: in general I don't think info is going to propagate up in cellsv220:43
*** emagana has joined #openstack-nova20:44
bauzasalaski: I remember some discussion we had about a possible usecase20:44
bauzasalaski: but I don't figure out which one20:44
*** krtaylor has quit IRC20:44
bauzasalaski: oh right, I remember now20:44
bauzasalaski: but we agreed on not doing it now20:45
*** ddaskal has joined #openstack-nova20:45
bauzasalaski: ie. migrations or evacuations out of child cells20:45
*** moshele has quit IRC20:46
bauzasokay, this time leaving20:47
bauzasbye20:47
*** shashankhegde has quit IRC20:51
*** gyee has quit IRC20:53
*** gyee has joined #openstack-nova20:53
*** salv-orlando has joined #openstack-nova20:54
*** shashankhegde has joined #openstack-nova20:56
*** emagana has quit IRC20:58
*** shakamunyi_ has joined #openstack-nova21:03
*** vilobhmm has quit IRC21:03
*** vilobhmm has joined #openstack-nova21:03
*** Raildo__ has joined #openstack-nova21:03
*** aysyanne has quit IRC21:04
*** thangp has quit IRC21:04
*** shakamunyi__ has joined #openstack-nova21:04
*** lpetrut has quit IRC21:05
*** shakamunyi__ is now known as tylerdurden21:05
*** tylerdurden has quit IRC21:08
*** shakamunyi_ has quit IRC21:08
*** Raildo_ has quit IRC21:08
*** baoli_ has quit IRC21:08
*** VW_ has joined #openstack-nova21:09
*** krtaylor has joined #openstack-nova21:11
*** shashankhegde has quit IRC21:11
*** VW has quit IRC21:12
*** VW_ has quit IRC21:14
*** yamahata has quit IRC21:14
*** eharney has quit IRC21:15
openstackgerritMatt Riedemann proposed openstack/python-novaclient: Add documentation on command deprecation process  https://review.openstack.org/18526021:15
openstackgerritMatt Riedemann proposed openstack/python-novaclient: Remove unused novaclient.tests.unit.v2.utils module  https://review.openstack.org/18526121:15
openstackgerritMatt Riedemann proposed openstack/python-novaclient: Deprecate volume/volume-type/volume-snapshot CRUD CLIs/APIs  https://review.openstack.org/18514121:15
*** burt has quit IRC21:16
openstackgerritMatt Riedemann proposed openstack/python-novaclient: Add documentation on command deprecation process  https://review.openstack.org/18526021:20
openstackgerritMatt Riedemann proposed openstack/python-novaclient: Remove unused novaclient.tests.unit.v2.utils module  https://review.openstack.org/18526121:20
openstackgerritMatt Riedemann proposed openstack/python-novaclient: Deprecate volume/volume-type/volume-snapshot CRUD CLIs/APIs  https://review.openstack.org/18514121:20
*** dboik has quit IRC21:21
*** Raildo__ has quit IRC21:22
*** jecarey has quit IRC21:22
*** shashankhegde has joined #openstack-nova21:24
*** iamjarvo has quit IRC21:25
*** matrohon has quit IRC21:27
*** annegent_ has quit IRC21:29
*** annegentle has joined #openstack-nova21:31
*** thiagop has quit IRC21:32
*** mriedem is now known as mriedem_away21:37
*** krak has quit IRC21:41
*** claudiub has quit IRC21:45
*** annegentle has quit IRC21:48
*** aix has joined #openstack-nova21:50
*** otter768 has joined #openstack-nova21:53
openstackgerritDavanum Srinivas (dims) proposed openstack/nova: [WIP] Enable more python34 tests  https://review.openstack.org/18778521:53
*** Raildo has joined #openstack-nova21:53
*** sdake has joined #openstack-nova21:54
*** ZZelle_ has joined #openstack-nova21:55
*** armax has quit IRC21:55
*** mwagner_afk has quit IRC21:57
*** fawadkhaliq has joined #openstack-nova21:57
*** otter768 has quit IRC21:58
*** sdake_ has quit IRC21:58
*** apuimedo has joined #openstack-nova21:58
*** wwriverrat has joined #openstack-nova21:58
*** lucas-dinner has quit IRC22:00
*** jlk has quit IRC22:01
*** jgrimm is now known as zz_jgrimm22:01
cfriesenif anyone's on still...is there a way to ensure that an object member has been loaded from the DB?  I'm hitting a case in build_request_spec() where it just assigns "instance" to "instance_properties", but the instance.pci_requests member isn't loaded22:03
*** agireud has quit IRC22:03
cfriesenI can trace back to where it's initially loaded from the uuid and make sure it's loaded there, but what about code paths where we don't know initially what we might need to load?22:04
*** kun_huang has quit IRC22:04
*** tonytan4ever has quit IRC22:06
*** tonytan4ever has joined #openstack-nova22:07
*** aweeks has quit IRC22:08
*** vilobhmm has quit IRC22:08
*** vilobhmm has joined #openstack-nova22:08
*** tonytan4ever has quit IRC22:11
*** annegentle has joined #openstack-nova22:12
*** ZZelle_ has quit IRC22:14
openstackgerritEd Leafe proposed openstack/nova-specs: Improve reporting when Scheduler returns NoValidHost  https://review.openstack.org/18773922:15
*** BadCub has quit IRC22:21
*** annegentle has quit IRC22:29
*** artom has quit IRC22:29
*** artom has joined #openstack-nova22:30
*** dims__ has joined #openstack-nova22:31
*** baoli has joined #openstack-nova22:33
*** Erming_ has joined #openstack-nova22:33
*** kylek3h has quit IRC22:34
*** mdrabe has quit IRC22:34
Erming_Hi, I am wondering if it's possible to let VM use a specified physical partition? For example, let ephemeral disk use a separated physical partition?22:34
*** dims_ has quit IRC22:34
*** Sukhdev has joined #openstack-nova22:35
*** kun_huang has joined #openstack-nova22:35
*** slong has joined #openstack-nova22:38
Erming_in default it only uses the root partition which often is tight on space.22:42
Erming_I mean on the hypervisor node22:42
*** baoli has quit IRC22:43
*** baoli has joined #openstack-nova22:46
openstackgerritDavanum Srinivas (dims) proposed openstack/nova: [WIP] Enable more python34 tests  https://review.openstack.org/18778522:47
*** ddaskal has quit IRC22:50
*** aweeks has joined #openstack-nova22:50
*** ian_brown has joined #openstack-nova22:52
*** whenry has quit IRC22:52
*** diegows has joined #openstack-nova22:53
*** mwagner_afk has joined #openstack-nova22:54
*** liusheng has quit IRC22:55
*** baoli has quit IRC22:56
*** liusheng has joined #openstack-nova22:56
*** marun has quit IRC22:57
*** apmelton is now known as apmelton_away22:59
*** baoli has joined #openstack-nova22:59
*** yamahata has joined #openstack-nova23:00
*** ian_brown has quit IRC23:03
*** zzzeek has quit IRC23:03
*** BadCub has joined #openstack-nova23:05
*** ian_brown has joined #openstack-nova23:06
*** BadCub has quit IRC23:09
*** aweeks has quit IRC23:09
*** baoli has quit IRC23:10
*** baoli has joined #openstack-nova23:15
*** BadCub has joined #openstack-nova23:16
*** Alexandra_ has joined #openstack-nova23:17
*** markvoelker_ has quit IRC23:18
*** annegentle has joined #openstack-nova23:18
*** aweeks has joined #openstack-nova23:19
*** annegentle has quit IRC23:20
*** nelsnelson has quit IRC23:22
*** armax has joined #openstack-nova23:27
*** baoli has quit IRC23:29
*** changbl_ has quit IRC23:30
mikal.23:31
openstackgerritZhang Ni proposed openstack/nova-specs: Add volume type to create server API  https://review.openstack.org/18781223:32
*** ian_brown has quit IRC23:32
openstackgerritZhang Ni proposed openstack/nova-specs: Add volume type to create server API  https://review.openstack.org/18781223:34
openstackgerritPuneet proposed openstack/nova: nova response code 403 on block device quota error  https://review.openstack.org/18781323:35
*** baoli has joined #openstack-nova23:37
*** markvoelker has joined #openstack-nova23:40
*** alex_klimov has quit IRC23:42
*** bradjones has quit IRC23:43
*** nelsnelson has joined #openstack-nova23:43
*** bradjones has joined #openstack-nova23:45
*** hshiina has joined #openstack-nova23:47
*** salv-orlando has quit IRC23:47
*** otter768 has joined #openstack-nova23:54
*** ijw has joined #openstack-nova23:54
*** diegows has quit IRC23:56
*** barra204 has quit IRC23:57
*** shakamunyi has quit IRC23:57
*** browne has quit IRC23:57
*** otter768 has quit IRC23:59

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