Tuesday, 2017-04-04

*** suresh12 has quit IRC00:01
*** kaisers has quit IRC00:03
*** suresh12 has joined #openstack-nova00:03
*** sneti_ has quit IRC00:07
*** gouthamr has joined #openstack-nova00:07
*** sneti_ has joined #openstack-nova00:07
*** sneti_ has quit IRC00:07
*** sneti_ has joined #openstack-nova00:08
*** karimb has quit IRC00:08
*** sneti_ has quit IRC00:08
*** crushil has quit IRC00:11
*** hongbin has quit IRC00:11
*** suresh12 has quit IRC00:14
*** suresh12 has joined #openstack-nova00:21
*** catintheroof has joined #openstack-nova00:25
*** wangqwsh has joined #openstack-nova00:28
*** chyka has joined #openstack-nova00:29
*** kaisers has joined #openstack-nova00:29
*** thorst has quit IRC00:31
*** thorst has joined #openstack-nova00:31
*** suresh12 has quit IRC00:33
*** suresh12 has joined #openstack-nova00:33
*** chyka has quit IRC00:33
*** thorst has quit IRC00:35
*** Fdaisuke has quit IRC00:36
*** tjones has quit IRC00:37
*** joanna__ has quit IRC00:37
*** suresh12 has quit IRC00:39
*** suresh12 has joined #openstack-nova00:40
*** timello has joined #openstack-nova00:40
*** adrian_otto has joined #openstack-nova00:41
*** timello has quit IRC00:43
*** esberglu has quit IRC00:44
*** timello has joined #openstack-nova00:44
*** artom__ has joined #openstack-nova00:44
*** suresh12 has quit IRC00:44
*** esberglu has joined #openstack-nova00:44
*** artom__ has quit IRC00:46
*** artom__ has joined #openstack-nova00:46
*** suresh12 has joined #openstack-nova00:46
*** tovin07_ has joined #openstack-nova00:48
*** artom_ has quit IRC00:48
*** esberglu has quit IRC00:49
*** timello has quit IRC00:49
*** timello has joined #openstack-nova00:49
*** timello has quit IRC00:50
*** timello has joined #openstack-nova00:51
*** esberglu has joined #openstack-nova00:51
*** esberglu has quit IRC00:52
*** esberglu has joined #openstack-nova00:52
*** suresh12 has quit IRC00:55
*** timello has quit IRC00:56
*** esberglu has quit IRC00:56
*** timello has joined #openstack-nova00:56
*** nic has quit IRC00:58
*** kaisers has quit IRC00:58
*** dtp has quit IRC01:01
*** catintheroof has quit IRC01:02
*** rfolco has joined #openstack-nova01:04
*** rfolco has quit IRC01:04
*** sridharg has joined #openstack-nova01:04
*** adrian_otto has quit IRC01:04
*** phuongnh has joined #openstack-nova01:04
*** thorst has joined #openstack-nova01:07
*** NikhilS has joined #openstack-nova01:07
*** wangqwsh has quit IRC01:08
*** jbernard has quit IRC01:12
*** jbernard has joined #openstack-nova01:13
*** thorst has quit IRC01:15
*** dave-mccowan has quit IRC01:17
*** mriedem has left #openstack-nova01:18
*** suresh12 has joined #openstack-nova01:18
*** suresh12 has quit IRC01:41
*** Apoorva_ has joined #openstack-nova01:41
*** crushil has joined #openstack-nova01:41
*** Apoorva has quit IRC01:44
*** Apoorva_ has quit IRC01:46
*** kaisers has joined #openstack-nova01:48
*** jdillaman has quit IRC01:49
*** iceyao has joined #openstack-nova01:50
*** crushil has quit IRC02:01
*** jdillaman has joined #openstack-nova02:05
*** harlowja has quit IRC02:06
*** huyang_ has joined #openstack-nova02:08
*** bkopilov has quit IRC02:09
*** adrian_otto has joined #openstack-nova02:10
*** Sukhdev_ has quit IRC02:10
*** takashin has joined #openstack-nova02:12
*** thorst has joined #openstack-nova02:15
*** jdillaman has quit IRC02:19
*** adrian_otto has quit IRC02:23
*** diga has quit IRC02:25
*** adrian_otto has joined #openstack-nova02:25
*** timello has quit IRC02:26
*** panbalag has joined #openstack-nova02:28
*** huyang_ has quit IRC02:28
*** thorst has quit IRC02:35
*** hongbin has joined #openstack-nova02:36
*** kaisers has quit IRC02:41
*** tuanluong has joined #openstack-nova02:44
*** Shunli has joined #openstack-nova02:46
*** adrian_otto has quit IRC02:47
*** harlowja has joined #openstack-nova02:50
*** panbalag has left #openstack-nova02:50
*** jwcroppe has quit IRC02:50
*** jwcroppe has joined #openstack-nova02:51
*** kaisers has joined #openstack-nova02:54
*** panbalag has joined #openstack-nova02:55
*** nicolasbock has quit IRC02:55
*** panbalag has left #openstack-nova02:56
*** crushil has joined #openstack-nova02:58
*** panbalag has joined #openstack-nova02:58
*** panbalag has left #openstack-nova02:59
*** tbachman_ has quit IRC03:06
*** links has joined #openstack-nova03:08
*** jwcroppe_ has joined #openstack-nova03:11
*** jwcroppe has quit IRC03:13
*** lyan has joined #openstack-nova03:15
*** f10d4 has quit IRC03:18
*** f10d4 has joined #openstack-nova03:18
*** Shunli has quit IRC03:20
*** lyan has quit IRC03:31
*** amotoki has joined #openstack-nova03:34
*** bkopilov has joined #openstack-nova03:39
*** dtp has joined #openstack-nova03:45
*** amotoki has quit IRC03:50
*** trinaths has joined #openstack-nova03:51
*** hongbin has quit IRC03:53
*** hongbin has joined #openstack-nova03:53
*** harlowja has quit IRC03:56
*** adrian_otto has joined #openstack-nova03:57
*** gouthamr has quit IRC03:57
*** gouthamr has joined #openstack-nova03:58
*** Sukhdev has joined #openstack-nova03:59
*** amotoki has joined #openstack-nova04:01
*** armax has joined #openstack-nova04:05
*** sree has joined #openstack-nova04:07
*** hongbin has quit IRC04:07
*** harlowja has joined #openstack-nova04:07
*** gouthamr has quit IRC04:09
*** nmathew has joined #openstack-nova04:18
*** suresh12 has joined #openstack-nova04:19
*** amotoki has quit IRC04:19
*** vks1 has joined #openstack-nova04:21
*** esberglu has joined #openstack-nova04:21
*** suresh12 has quit IRC04:24
*** psachin has joined #openstack-nova04:24
*** esberglu has quit IRC04:26
*** amotoki has joined #openstack-nova04:28
*** thorst has joined #openstack-nova04:32
*** harlowja has quit IRC04:33
*** yamahata has joined #openstack-nova04:34
*** thorst has quit IRC04:37
*** bmace has quit IRC04:45
*** bmace has joined #openstack-nova04:45
*** rcernin has joined #openstack-nova04:45
*** dimtruck is now known as zz_dimtruck04:48
vks1ConfigFileValueError: Value for option instances is not valid: invalid literal for int() with base 10 . Getting this error. I have set nova.conf like this:04:48
vks1[quota]04:48
vks1instances=-104:48
vks1#cores=5004:48
vks1ram=-104:48
vks1gigabytes=-104:48
*** Jack_Iv has joined #openstack-nova04:56
*** suresh12 has joined #openstack-nova04:57
*** Jack_Iv_ has joined #openstack-nova04:57
*** adrian_otto has quit IRC05:00
*** Jack_Iv has quit IRC05:01
*** nmathew- has joined #openstack-nova05:04
*** kaisers_ has joined #openstack-nova05:05
*** vishwana_ has joined #openstack-nova05:05
*** toabctl has quit IRC05:06
*** alezil_ has joined #openstack-nova05:06
*** sballe__ has joined #openstack-nova05:07
*** khappone_ has joined #openstack-nova05:07
*** betherly_ has joined #openstack-nova05:07
*** ratailor has joined #openstack-nova05:09
*** Jack_Iv_ has quit IRC05:09
*** tuanluong_ has joined #openstack-nova05:09
*** rcernin has quit IRC05:09
*** szaher_ has joined #openstack-nova05:10
*** guchihiro has joined #openstack-nova05:10
*** toabctl has joined #openstack-nova05:10
*** Jack_Iv has joined #openstack-nova05:10
*** rcernin has joined #openstack-nova05:11
*** harlowja has joined #openstack-nova05:11
*** crushil has quit IRC05:12
*** rodrigod` has joined #openstack-nova05:12
*** McNinja_ has joined #openstack-nova05:12
*** owalsh_ has joined #openstack-nova05:12
*** MasterofJOKers_ has joined #openstack-nova05:13
*** patriciadomin_ has joined #openstack-nova05:13
*** NightKhaos_ has joined #openstack-nova05:13
*** nmathew has quit IRC05:14
*** f10d4 has quit IRC05:14
*** kaisers has quit IRC05:14
*** tuanluong has quit IRC05:14
*** sridharg has quit IRC05:14
*** szaher has quit IRC05:14
*** Dinesh_Bhor has quit IRC05:14
*** edleafe has quit IRC05:14
*** vishwanathj has quit IRC05:14
*** owalsh has quit IRC05:14
*** khappone has quit IRC05:14
*** betherly has quit IRC05:14
*** rodrigods has quit IRC05:14
*** purplerbot has quit IRC05:14
*** MasterofJOKers has quit IRC05:14
*** McNinja has quit IRC05:14
*** zhenguo has quit IRC05:14
*** patriciadomin has quit IRC05:14
*** NightKhaos has quit IRC05:14
*** thomasem has quit IRC05:14
*** alezil has quit IRC05:14
*** sballe_ has quit IRC05:14
*** MasterofJOKers_ is now known as MasterofJOKers05:14
*** McNinja_ is now known as McNinja05:14
*** NightKhaos_ is now known as NightKhaos05:14
*** edleafe has joined #openstack-nova05:15
*** adisky_ has joined #openstack-nova05:15
*** jamielennox is now known as jamielennox|away05:15
*** Jack_Iv has quit IRC05:15
*** alezil_ is now known as alezil05:15
*** thomasem has joined #openstack-nova05:15
*** diga has joined #openstack-nova05:15
*** esberglu has joined #openstack-nova05:16
*** betherly_ is now known as betherly05:16
*** sballe__ is now known as sballe_05:16
*** f10d4 has joined #openstack-nova05:16
*** udesale has joined #openstack-nova05:17
*** esberglu has quit IRC05:20
*** sridharg has joined #openstack-nova05:21
*** Dinesh_Bhor has joined #openstack-nova05:21
*** amotoki has quit IRC05:26
*** prateek has joined #openstack-nova05:26
*** Jack_Iv has joined #openstack-nova05:29
*** dtp has quit IRC05:29
*** amotoki has joined #openstack-nova05:30
*** mdnadeem has joined #openstack-nova05:31
*** raj_singh has quit IRC05:31
*** raj_singh_ has joined #openstack-nova05:31
*** thorst has joined #openstack-nova05:33
*** madgoat has joined #openstack-nova05:37
*** Sukhdev has quit IRC05:37
*** madgoat has left #openstack-nova05:37
*** sree has quit IRC05:37
*** jamielennox|away is now known as jamielennox05:37
*** thorst has quit IRC05:38
*** sree has joined #openstack-nova05:38
*** tuanluong_ has quit IRC05:38
*** nkrinner_afk is now known as nkrinner05:39
*** Jack_Iv_ has joined #openstack-nova05:39
*** lpetrut has joined #openstack-nova05:39
*** lpetrut has quit IRC05:40
*** udesale__ has joined #openstack-nova05:42
*** sree has quit IRC05:42
*** udesale has quit IRC05:43
*** Jack_Iv has quit IRC05:43
*** sridharg has quit IRC05:46
*** mtreinish has quit IRC05:49
*** mtreinish has joined #openstack-nova05:50
*** mtreinish has quit IRC05:52
*** carthaca_ has joined #openstack-nova05:56
*** mtreinish has joined #openstack-nova05:56
*** iceyao has quit IRC06:00
*** iceyao_ has joined #openstack-nova06:00
*** jaosorior_away is now known as jaosorior06:01
*** harlowja has quit IRC06:02
*** andreas_s has joined #openstack-nova06:03
*** tuanluong has joined #openstack-nova06:06
*** Oku_OS-away is now known as Oku_OS06:08
*** udesale__ has quit IRC06:08
*** esberglu has joined #openstack-nova06:10
*** esberglu has quit IRC06:15
*** voelzmo has joined #openstack-nova06:19
*** voelzmo has quit IRC06:24
openstackgerritGhanshyam Mann proposed openstack/nova master: api-ref: fix os-extended-volumes:volumes_attached in servers responses  https://review.openstack.org/44980906:25
openstackgerritGhanshyam Mann proposed openstack/nova master: ix api-ref for create servers response  https://review.openstack.org/45167306:25
*** tesseract has joined #openstack-nova06:26
openstackgerritGhanshyam Mann proposed openstack/nova master: Fix api-ref for create servers response  https://review.openstack.org/45167306:27
gmannoomichi: updated https://review.openstack.org/#/c/451673/06:27
*** voelzmo has joined #openstack-nova06:27
*** iceyao_ has quit IRC06:32
*** thorst has joined #openstack-nova06:34
*** thorst has quit IRC06:38
openstackgerritDan Peschman proposed openstack/nova master: Add uuid to Service model  https://review.openstack.org/45302506:39
*** jpena|away is now known as jpena06:39
*** claudiub has quit IRC06:40
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Add a removeFloatingIp example  https://review.openstack.org/45302606:42
*** suresh12 has quit IRC06:44
openstackgerritTakashi NATSUME proposed openstack/nova-specs master: List/show all server migration types  https://review.openstack.org/40723706:45
openstackgerritTakashi NATSUME proposed openstack/nova-specs master: Specify keymap on server boot  https://review.openstack.org/44883006:45
openstackgerritTakashi NATSUME proposed openstack/nova-specs master: Abort Cold Migration  https://review.openstack.org/33473206:45
*** rmart04 has joined #openstack-nova06:52
*** abhishek_k has quit IRC06:54
*** satyar has joined #openstack-nova06:56
*** rmart04 has quit IRC06:57
*** sridharg has joined #openstack-nova06:58
openstackgerritmelanie witt proposed openstack/nova-specs master: Add project/user association to placement  https://review.openstack.org/45303006:58
*** amotoki has quit IRC07:00
*** iceyao has joined #openstack-nova07:02
*** amotoki has joined #openstack-nova07:03
*** Jack_Iv_ has quit IRC07:04
*** Jack_Iv has joined #openstack-nova07:04
*** Jack_Iv has quit IRC07:05
*** Jack_Iv has joined #openstack-nova07:05
*** Jack_Iv_ has joined #openstack-nova07:06
*** aarefiev_afk is now known as aarefiev07:07
openstackgerritSergey Nikitin proposed openstack/nova-specs master: TinyFix: Changed type of CPU ID from 'String' to 'Integer' in diagnostics spec  https://review.openstack.org/44585507:09
*** Jack_Iv has quit IRC07:10
*** phuongnh has quit IRC07:11
*** tuanluong has quit IRC07:11
snikitin_johnthetubaguy, jaypipes: Hi guys! You approved my little fix in diagnostics spec but I had to reupload it because of pep8 error. Could you please fast reapprove it? https://review.openstack.org/#/c/44585507:13
*** zhenguo has joined #openstack-nova07:15
*** Jack_Iv has joined #openstack-nova07:16
*** markus_z has joined #openstack-nova07:17
openstackgerritSihan Wang proposed openstack/nova master: Show quota detail when inject file quota exceeds  https://review.openstack.org/45304007:17
*** Jack_Iv_ has quit IRC07:18
*** pcaruana has joined #openstack-nova07:19
openstackgerritmelanie witt proposed openstack/nova-specs master: Convert consoles code to use objects framework  https://review.openstack.org/45304107:23
*** avolkov has joined #openstack-nova07:26
openstackgerritGhanshyam Mann proposed openstack/nova master: Add api sample tests for security group rules  https://review.openstack.org/45205507:27
*** udesale has joined #openstack-nova07:27
openstackgerritGhanshyam Mann proposed openstack/nova master: Add api sample tests for security group rules  https://review.openstack.org/45205507:28
*** prateek_ has joined #openstack-nova07:31
*** prateek_ has quit IRC07:32
*** prateek_ has joined #openstack-nova07:32
*** prateek has quit IRC07:33
*** thorst has joined #openstack-nova07:34
*** amotoki has quit IRC07:35
*** karimb has joined #openstack-nova07:36
*** amotoki has joined #openstack-nova07:36
*** shaner has quit IRC07:38
*** takashin has quit IRC07:38
*** shaner has joined #openstack-nova07:39
*** thorst has quit IRC07:39
*** Jack_Iv has quit IRC07:44
*** armax has quit IRC07:44
*** lpetrut has joined #openstack-nova07:45
*** jamielennox is now known as jamielennox|away07:45
*** udesale__ has joined #openstack-nova07:48
*** prateek has joined #openstack-nova07:49
*** prateek_ has quit IRC07:49
*** udesale has quit IRC07:50
*** amoralej|off is now known as amoralej07:53
*** yamahata has quit IRC07:58
*** lucas-afk is now known as lucasagomes07:59
*** esberglu has joined #openstack-nova07:59
*** zzzeek has quit IRC08:00
*** zzzeek has joined #openstack-nova08:00
*** ltomasbo|away is now known as ltomasbo08:01
*** lpetrut has quit IRC08:01
*** esberglu has quit IRC08:04
*** nmathew has joined #openstack-nova08:11
*** nmathew- has quit IRC08:12
*** ralonsoh has joined #openstack-nova08:14
lyarwoodmdbooth: https://review.openstack.org/#/c/452938/ - hackaround for an encrypted nfs volume corruption bug if you get time today08:22
*** prateek_ has joined #openstack-nova08:27
*** Jack_Iv has joined #openstack-nova08:28
*** Jack_Iv has quit IRC08:28
* johnthetubaguy wishes everyone a happy specs review day08:29
johnthetubaguysfinucan: do you have context on this, I have some dumb questions: https://review.openstack.org/#/c/36114008:30
*** prateek has quit IRC08:30
*** prateek_ has quit IRC08:31
sfinucanjohnthetubaguy: looking08:33
sfinucanjohnthetubaguy: Sure do. What's up?08:33
johnthetubaguysfinucan: so when I read the problem, I assumed I would see the reverse solution, let me try sketch that out08:34
johnthetubaguysfinucan: PCI whitelist tells Nova to only prefer NUMA affinity, because all the PCI devices are only on one NUMA node08:35
johnthetubaguythat way the user doesn't need to worry themselves08:35
*** thorst has joined #openstack-nova08:35
johnthetubaguysfinucan: I am guessing there is a use case that doesn't work for, but I am not seeing it myself08:36
sfinucanjohnthetubaguy: Is that a statement or a question? :)08:36
sfinucanthe PCI whitelist bit, that is08:36
*** guchihiro has quit IRC08:37
johnthetubaguysfinucan: bit of both really, lol08:37
johnthetubaguysnikitin_ I think this is your spec I am look at, if you are about ^08:37
johnthetubaguysfinucan: also, I wasn't sure why an image property was a good idea for this one, anyways I left some comments08:38
sfinucanHmm, so I don't get your question, but I can give you my tl;dr on that spec, if it would help08:38
*** derekh has joined #openstack-nova08:40
sfinucanIn short, some people want to be able to use PCI devices even if they don't have NUMA affinity08:40
*** cdent has joined #openstack-nova08:41
sfinucanbut we can't force that on everyone. The current behaviour is to fail if we can't get NUMA affinitized PCI devices and that behaviour should be retained08:41
*** purplerbot has joined #openstack-nova08:42
sfinucanjohnthetubaguy: Hence, the need for configurable policies. I _think_ what you're saying is why not soften the requirements for everyone. That'd be great, until people start complaining about why the performance of their VMs has dropped (by 10-15%, based on data I've seen in the past) :)08:43
johnthetubaguysfinucan: no, no08:43
johnthetubaguysfinucan: I mean why configure it on the flavor, when its really a host property08:44
*** suresh12 has joined #openstack-nova08:45
*** prateek has joined #openstack-nova08:47
*** suresh12 has quit IRC08:49
sfinucanjohnthetubaguy: Is it though?08:49
snikitin_johnthetubaguy, it's configured in flavor because it's influence on VM performance. For example you want to boot a high performance VM. You have a lot of hosts with different NUMA nodes and PCI devises. `strict` policy is guarantee you that scheduler will choose host with direct NUMA - PCI affinity. and then strict policy is guarantee you that from many PCI-NUMA combinations on current host nova compute will choose NUMA node and PCI device with08:49
snikitin_derect affinity08:49
johnthetubaguysnikitin_: yeah, I think the mixed set of hosts is the main reason flavor wins08:50
sfinucanIt seems very workload specific. Some workloads will be impacted by the affinitization (or lack thereof)08:50
johnthetubaguysnikitin_: sfinucan: the spec doesn't seems to cover scheduler filter or weights changes, I guess thats true right now, as its all picked on the host?08:51
sfinucanjohnthetubaguy: I can't say off the top of my head, but I think snikitin_ has WIP code up that might provide guidance on implementation08:51
johnthetubaguysfinucan: if you want the host to have SRIOV connections, and its only got NICs on one NUMA node, it feels like a host property08:52
johnthetubaguysfinucan: it just the spec normally would cover those details, and I don't see it mentioned really08:52
*** kevinz has joined #openstack-nova08:52
openstackgerritSergey Nikitin proposed openstack/nova master: Added PIC NUMA policies  https://review.openstack.org/39052008:52
snikitin_johnthetubaguy, here is PoC https://review.openstack.org/#/c/390520/08:52
sfinucanjohnthetubaguy: I don't think the spec is focussed on exposing any additional properties of SR-IOV devices. It would only manifest itself with scheduling08:53
sfinucanIf we wanted to expose the NUMA affinity etc. globally, resource providers would be the way forward. Different issue though08:53
*** thorst has quit IRC08:55
johnthetubaguysfinucan: snikitin_: yeah, makes sense it doesn't impact the scheduler as such, because we just don't expose this stuff right now08:55
sfinucanAt the moment, scheduling works by identifying hosts with enough free CPUs and SR-IOV devices (no knowledge of NUMA yet)08:55
snikitin_johnthetubaguy: I don't changed numa_topology filter or weight code because both filter and nova compute use method 'fit_numa_topology' (or similar) to figure out if a VM can be booted on some host or not08:55
sfinucanOnce done, it'll try to fit the instance vCPUs onto the host pCPUs. If that's successful, it tries to get a free SR-IOV device and associate that with the guest08:56
johnthetubaguysfinucan: totally, that all makes sense08:56
johnthetubaguysnikitin_: sfinucan: I wasn't sure why we need the image property as well as the flavor thing, is that just for completness?08:57
snikitin_yes08:57
sfinucanjohnthetubaguy: Sweet. So it's just the very last step that we're touching08:57
sfinucanyup - that was my suggestion08:57
*** priteau has joined #openstack-nova08:57
*** carthaca_ has quit IRC08:58
*** carthaca_ has joined #openstack-nova08:58
openstackgerritJianghua Wang proposed openstack/nova-specs master: Support VGPU  https://review.openstack.org/45012209:00
openstackgerritSylvain Bauza proposed openstack/nova-specs master: Placement doing claims  https://review.openstack.org/43742409:02
*** kevinz has quit IRC09:03
*** haplo37_ has quit IRC09:04
*** haplo37_ has joined #openstack-nova09:04
*** kevinz has joined #openstack-nova09:04
mdboothjohnthetubaguy: Is there a master list of priority specs?09:04
johnthetubaguymdbooth: not sure beyond what is in here: https://etherpad.openstack.org/p/pike-nova-priorities-tracking09:05
*** slunkad has joined #openstack-nova09:05
mdboothjohnthetubaguy: I meant specifically for the spec review09:06
mdboothday09:06
johnthetubaguynot that I know of09:06
*** nmathew has quit IRC09:08
openstackgerritJianghua Wang proposed openstack/nova-specs master: Support VGPU  https://review.openstack.org/45012209:08
mdboothjohnthetubaguy: Do you have a strategy for finding important specs to review today?09:08
johnthetubaguycurrently got a gerrit dash up with all the open reviews, looking for the interesting looking ones, particularly ones with no votes or all positive votes09:09
* mdbooth will go with that09:09
*** tuanluong has joined #openstack-nova09:12
*** jschlueter has left #openstack-nova09:12
openstackgerritSergey Nikitin proposed openstack/nova master: Added PIC NUMA policies  https://review.openstack.org/39052009:13
*** edmondsw has joined #openstack-nova09:14
*** Jack_Iv has joined #openstack-nova09:15
*** Jack_Iv_ has joined #openstack-nova09:16
*** gszasz has joined #openstack-nova09:16
*** ltomasbo is now known as ltomasbo|away09:17
*** edmondsw has quit IRC09:18
*** szaher_ has quit IRC09:19
*** szaher has joined #openstack-nova09:19
*** Jack_Iv has quit IRC09:19
*** ratailor_ has joined #openstack-nova09:25
*** ratailor_ has quit IRC09:25
*** ratailor is now known as ratailor_09:26
*** ltomasbo|away is now known as ltomasbo09:26
*** ratailor_ is now known as Guest656509:27
openstackgerritBalazs Gibizer proposed openstack/nova master: Add snapshot id to the snapshot notifications  https://review.openstack.org/45307709:27
openstackgerritBalazs Gibizer proposed openstack/nova master: Add snapshot id to the snapshot notifications  https://review.openstack.org/45307709:29
*** mvk has quit IRC09:31
*** karimb_ has joined #openstack-nova09:35
*** nmathew has joined #openstack-nova09:38
*** karimb has quit IRC09:39
*** mnestratov has quit IRC09:45
*** esberglu has joined #openstack-nova09:48
*** thorst has joined #openstack-nova09:52
*** cdent has quit IRC09:52
*** esberglu has quit IRC09:52
openstackgerritSilvan Kaiser proposed openstack/nova master: Switch Nova Quobyte volume driver to mount via systemd-run  https://review.openstack.org/43234409:53
*** thorst has quit IRC09:56
*** sree has joined #openstack-nova09:58
*** sree has quit IRC09:58
*** sree has joined #openstack-nova09:58
openstackgerritJianghua Wang proposed openstack/nova-specs master: Support VGPU  https://review.openstack.org/45012209:59
*** sree has quit IRC09:59
*** abalutoiu__ has joined #openstack-nova10:00
*** sree has joined #openstack-nova10:00
*** mvk has joined #openstack-nova10:00
*** NikhilS has quit IRC10:01
*** NikhilS has joined #openstack-nova10:01
*** NikhilS has quit IRC10:02
*** tbachman has joined #openstack-nova10:03
*** abalutoiu_ has quit IRC10:03
*** jahsis has joined #openstack-nova10:04
*** sree has quit IRC10:04
*** sambetts|afk is now known as sambetts10:04
openstackgerritMarkMielke proposed openstack/nova master: Resource tracker should use Block Device Mappings  https://review.openstack.org/43009110:05
*** sdague has joined #openstack-nova10:08
*** priteau has quit IRC10:11
*** iceyao has quit IRC10:11
*** iceyao has joined #openstack-nova10:13
*** satyar has quit IRC10:14
*** bhagyashris has left #openstack-nova10:14
*** bhagyashris has joined #openstack-nova10:14
*** avolkov has quit IRC10:17
*** tovin07_ has quit IRC10:18
*** tuanluong has quit IRC10:20
*** iceyao has quit IRC10:20
johnthetubaguysfinucan: doing some cleanups, I am guessing you are not still pushing this one forward, or did we merge that somewhere else? https://review.openstack.org/#/c/406081/10:22
openstackgerritAndrey Volkov proposed openstack/nova master: [placement] Add api-ref for GET RP inventories  https://review.openstack.org/44976510:23
openstackgerritAndrey Volkov proposed openstack/nova master: [placement] Add api-ref for DELETE RP inventories  https://review.openstack.org/45270810:23
openstackgerritAndrey Volkov proposed openstack/nova master: [placement] Add api-ref for PUT RP inventories  https://review.openstack.org/45270710:23
sfinucanjohnthetubaguy: So that ties into the PCI spec you were reviewing earlier10:23
sfinucanI thought image metadata was used to allow you to package an application up such that you could drop it into any cloud and it would just work10:24
sfinucan...assuming the cloud supported the required features10:25
johnthetubaguysfinucan: just clicked abandon on it as its been left unloved for 4 months, thats all10:25
sfinucanjohnthetubaguy: Yeah, that's fair :) I'm just curious what you think image metadata is for10:26
sfinucanThe above is why I said the PCI policies spec should have an image metadata aspect. Strict NUMA affinity could be a required attribute for a workload/application10:27
johnthetubaguysfinucan: its used for a heap of aweful things right now, and we don't define the contract anywhere, so I just hate it really10:27
*** lpetrut has joined #openstack-nova10:27
johnthetubaguysfinucan: the use I like is specifying things that image requires in order to work correctly10:28
*** Jack_Iv_ has quit IRC10:29
johnthetubaguysfinucan: but less is more when it comes to APIs, so if its something only the admin wants to control, I prefer not adding image metadata. For people who care we force them to add flavor extra specs now, rather than there being no way to change the defaults, possibly for zero gain.10:29
*** priteau has joined #openstack-nova10:30
sfinucanjohnthetubaguy: Right. I think something like CPU thread or PCI policies falls into that category (the image would boot, but the combined performance impact could mean the application is not fit for purpose and therefore "broken")10:30
*** Jack_Iv has joined #openstack-nova10:30
sfinucanHmm, yeah - that's the other perspective10:30
*** udesale__ has quit IRC10:30
sfinucanLong story short, that spec was applying the above idea to emulator thread policies. I don't care enough about it to pursue it though, heh10:31
*** cdent has joined #openstack-nova10:31
*** nicolasbock has joined #openstack-nova10:33
*** Jack_Iv has quit IRC10:35
*** lpetrut has quit IRC10:37
* cdent puts on his spectacles10:37
*** lpetrut has joined #openstack-nova10:38
*** lpetrut has quit IRC10:38
openstackgerritStephen Finucane proposed openstack/nova master: doc: Rewrap 'code-review' at ¬79 characters  https://review.openstack.org/38496010:39
*** owalsh_ is now known as owalsh10:39
*** tbachman has quit IRC10:42
*** mnestratov has joined #openstack-nova10:43
*** avolkov has joined #openstack-nova10:43
*** Jack_Iv has joined #openstack-nova10:47
*** trinaths has left #openstack-nova10:49
*** diga has quit IRC10:53
*** lucasagomes is now known as lucas-hungry10:56
*** Jack_Iv_ has joined #openstack-nova10:59
*** Jack_Iv_ has quit IRC10:59
*** Jack_Iv_ has joined #openstack-nova10:59
*** Jack_Iv has quit IRC11:02
*** claudiub has joined #openstack-nova11:03
*** jamielennox|away is now known as jamielennox11:03
kashyapsfinucan: Why rewrap?11:07
kashyapIt's at 72 now?11:08
sfinucankashyap: I think I had a change after it at one point?11:08
kashyapSomething like that.  FWIW, it looks okay to me11:08
kashyapI think I vaguely recall some list discussion11:08
sfinucanIt was in merge conflict so I just fixed it :)11:08
kashyapAh, okay :-)11:09
*** ltomasbo is now known as ltomasbo|away11:10
*** bkopilov has quit IRC11:12
*** artom_ has joined #openstack-nova11:16
*** artom_ has quit IRC11:18
*** lpetrut has joined #openstack-nova11:18
*** artom has joined #openstack-nova11:19
*** artom has quit IRC11:20
*** artom has joined #openstack-nova11:20
*** artom__ has quit IRC11:20
*** dave-mccowan has joined #openstack-nova11:20
*** artom_ has joined #openstack-nova11:22
*** artom has quit IRC11:22
*** thorst has joined #openstack-nova11:30
*** lpetrut has quit IRC11:31
*** rmart04 has joined #openstack-nova11:34
*** mdnadeem has quit IRC11:36
*** timello has joined #openstack-nova11:36
*** kornica is now known as kornicameister11:37
*** artom_ has quit IRC11:40
*** garyk2 has joined #openstack-nova11:40
*** artom_ has joined #openstack-nova11:40
*** garyk1 has quit IRC11:41
*** artom__ has joined #openstack-nova11:44
*** artom_ has quit IRC11:44
*** dane-fichter has joined #openstack-nova11:47
*** dane-fichter has quit IRC11:48
*** artom_ has joined #openstack-nova11:48
openstackgerritLee Yarwood proposed openstack/nova-specs master: Libvirt: Enable QEMU native LUKs handling  https://review.openstack.org/43707011:48
lyarwoodmdbooth, kashyap ^ if you have spec review time today, I'm not 100% sure that we will have the required versions of QEMU and libvirt in the gate for Pike tbh11:49
kashyaplyarwood: I did notice it, actually11:49
kashyaplyarwood: Yes, we don't have the reqiured versions11:49
*** baoli has joined #openstack-nova11:50
*** baoli has quit IRC11:50
lyarwoodkashyap: right, but 17.04 will, I just don't think it's going to be used in the gate as it isn't LTS11:50
kashyaplyarwood: We should really get that in-progress (over a year) DevStack plugin that lets us use QEMU / libvirt from Git (and newest releases / RCs) with Nova11:50
lyarwoodkashyap: link? I don't think I've seen that11:50
*** baoli has joined #openstack-nova11:50
kashyaplyarwood: https://review.openstack.org/#/c/108714/11:51
lyarwoodkashyap: thanks!11:51
kashyaplyarwood: Err, scratch that -- that's the OLD one that was subimtted directly as part of DevStack11:51
*** mdnadeem has joined #openstack-nova11:51
kashyapBut the agreed decision was to make it a plugin11:51
lyarwoodkk11:52
*** artom__ has quit IRC11:52
*** smatzek has joined #openstack-nova11:52
*** jpena is now known as jpena|lunch11:54
*** artom_ has quit IRC11:54
*** Jack_Iv_ has quit IRC11:54
*** Jack_Iv has joined #openstack-nova11:54
openstackgerritLee Yarwood proposed openstack/nova-specs master: Libvirt: Enable QEMU native LUKs handling  https://review.openstack.org/43707011:55
*** artom has joined #openstack-nova11:56
mdboothlyarwood: Will try to look today11:56
lyarwoodmdbooth: thanks11:56
*** artom has quit IRC11:58
*** voelzmo has quit IRC11:58
*** artom has joined #openstack-nova11:58
*** artom has quit IRC12:00
*** artom has joined #openstack-nova12:00
*** rodrigod` is now known as rodrigods12:01
*** rodrigods has joined #openstack-nova12:01
*** rodrigods has quit IRC12:01
*** voelzmo has joined #openstack-nova12:01
*** rodrigods has joined #openstack-nova12:02
*** lucas-hungry is now known as lucasagomes12:02
*** ltomasbo|away is now known as ltomasbo12:02
*** rodrigods has quit IRC12:03
*** rodrigods has joined #openstack-nova12:03
*** catintheroof has joined #openstack-nova12:05
lyarwoodkashyap: thanks for the link in the review btw12:05
lyarwoodkashyap: I'll check that out after lunch12:05
*** edmondsw has joined #openstack-nova12:06
kashyaplyarwood: Np.  I'll be looking at that plugin again today, been meaning to but couldn't get around12:06
*** tbachman has joined #openstack-nova12:06
jaypipessnikitin_: done12:07
*** amoralej is now known as amoralej|lunch12:08
snikitin_jaypipes, thanks!12:08
*** karimb_ has quit IRC12:09
*** Guest6565 has quit IRC12:11
*** artom has quit IRC12:12
openstackgerritSilvan Kaiser proposed openstack/nova master: Removes getfattr from Quobyte Nova driver  https://review.openstack.org/42864612:12
*** artom has joined #openstack-nova12:12
openstackgerritSilvan Kaiser proposed openstack/nova master: Removes getfattr from Quobyte Nova driver  https://review.openstack.org/42864612:15
*** zz_dimtruck is now known as dimtruck12:16
*** artom has quit IRC12:16
*** artom has joined #openstack-nova12:16
*** artom has quit IRC12:18
*** artom has joined #openstack-nova12:18
*** karimb has joined #openstack-nova12:20
*** jdillaman has joined #openstack-nova12:21
*** tbachman has quit IRC12:21
*** tbachman has joined #openstack-nova12:25
*** rfolco has joined #openstack-nova12:26
*** mdnadeem has quit IRC12:27
*** rfolco_ has joined #openstack-nova12:28
bauzasjaypipes: you could be interested in https://review.openstack.org/#/c/446446/12:28
bauzasjohnthetubaguy: too ^12:29
*** carthaca_ has quit IRC12:29
*** carthaca_ has joined #openstack-nova12:29
*** sapcc-bot has quit IRC12:30
*** carthaca_ has quit IRC12:30
*** sapcc-bot has joined #openstack-nova12:31
*** rfolco has quit IRC12:31
*** esberglu has joined #openstack-nova12:31
*** peter-hamilton has joined #openstack-nova12:31
johnthetubaguybauzas: hopefully will get there, mostly just cleaning up the queue this morning12:31
*** jianghuaw has joined #openstack-nova12:32
bauzasjohnthetubaguy: where are we discussing in the PTG etherpad about https://review.openstack.org/#/c/381912/10/specs/pike/approved/strict_isolation_of_group_of_hosts_for_image_and_flavor.rst ?12:32
bauzasjohnthetubaguy: I don't remember that12:32
johnthetubaguybauzas: search for the patch number, you should find it12:32
* bauzas facepalms12:32
bauzasjohnthetubaguy: FWIW, it's an old discussion12:33
*** nkorabli has joined #openstack-nova12:34
*** jianghuaw__ has quit IRC12:34
*** baoli has quit IRC12:35
*** ralonsoh has quit IRC12:36
*** esberglu has quit IRC12:36
*** vks1 has quit IRC12:38
snikitin_jaypipes: I don't know why bot after your reapprove gate jobs weren't started. https://review.openstack.org/#/c/445855/ maybe try again with +212:38
*** sapcc-bot has quit IRC12:39
snikitin_?12:39
*** gouthamr has joined #openstack-nova12:39
*** baoli has joined #openstack-nova12:39
*** dimtruck is now known as zz_dimtruck12:40
*** tpatzig_ has joined #openstack-nova12:40
*** david_1 has joined #openstack-nova12:40
*** sapcc-bot has joined #openstack-nova12:40
*** carthaca_ has joined #openstack-nova12:40
*** dgonzalez_ has joined #openstack-nova12:40
*** mkoderer_ has joined #openstack-nova12:40
*** mkoderer_ has quit IRC12:40
*** sapcc-bot has quit IRC12:41
*** mkoderer_ has joined #openstack-nova12:41
*** sapcc-bot has joined #openstack-nova12:41
*** voelzmo has quit IRC12:41
sdaguesnikitin_: it needs both a +2 and a +W12:41
*** david_1 has quit IRC12:42
*** tpatzig_ has quit IRC12:42
snikitin_sdague, thanks!12:42
*** dgonzalez_ has quit IRC12:42
*** carthaca_ has quit IRC12:42
*** mkoderer_ has quit IRC12:42
*** sapcc-bot has quit IRC12:43
*** Jack_Iv has quit IRC12:43
*** sapcc-bot has joined #openstack-nova12:43
*** lyan has joined #openstack-nova12:43
*** Jack_Iv has joined #openstack-nova12:43
*** voelzmo has joined #openstack-nova12:43
*** mdnadeem has joined #openstack-nova12:45
*** voelzmo has quit IRC12:46
*** liverpooler has joined #openstack-nova12:46
*** sapcc-bot has quit IRC12:47
*** sapcc-bot has joined #openstack-nova12:47
*** sapcc-bot1 has joined #openstack-nova12:48
*** voelzmo has joined #openstack-nova12:49
*** sapcc-bot1 has quit IRC12:49
*** sapcc-bot has quit IRC12:49
*** sapcc-bot1 has joined #openstack-nova12:49
*** jpena|lunch is now known as jpena12:50
*** suresh12 has joined #openstack-nova12:50
*** sapcc-bot1 has quit IRC12:50
*** sapcc-bot has joined #openstack-nova12:51
*** Jack_Iv has quit IRC12:51
*** suresh12 has quit IRC12:52
*** suresh12 has joined #openstack-nova12:52
*** sapcc-bot has quit IRC12:52
*** jwcroppe_ has quit IRC12:52
*** Jack_Iv has joined #openstack-nova12:52
*** IRCFrEAK has joined #openstack-nova12:53
*** IRCFrEAK has quit IRC12:53
*** Jack_Iv has quit IRC12:53
*** Jack_Iv has joined #openstack-nova12:53
*** esberglu has joined #openstack-nova12:57
*** nkorabli has quit IRC12:57
johnthetubaguybauzas: sfinucan: can I ask you about this one: https://review.openstack.org/#/c/43878712:59
sfinucanjohnthetubaguy: Hit me12:59
johnthetubaguybauzas: sfinucan: why can't we use the existing image property, basically?12:59
* bauzas looking13:00
sfinucanjohnthetubaguy: I think the existing property refers to a different attribute of the emulated VGA dev13:00
johnthetubaguyit seems to be video ram vs vga ram, they seem like the same thing to me13:00
bauzasjohnthetubaguy: AFAICU, that seems to be a separate property13:01
bauzaslooking at https://libvirt.org/formatdomain.html13:01
sfinucanjohnthetubaguy: That should be in the spec. If you haven't done it already, there should probably be a comment to the same13:01
johnthetubaguybut why are they different? what does it mean?13:01
sfinucanThey are different properties though. Lemme find the QEMU docs13:01
sfinucanjohnthetubaguy:13:02
sfinucanjohnthetubaguy: https://www.ovirt.org/documentation/draft/video-ram/13:02
sfinucanvgamem is allocated within ram. Minimum ram size, as enforced by QEMU regardless the command line settings, is 2 * vgamem. vram is allocated separately.13:02
*** awaugama has joined #openstack-nova13:02
bauzasjohnthetubaguy: https://libvirt.org/formatdomain.html#elementsVideo13:02
bauzaswhat sfinucan said13:02
*** Jack_Iv has quit IRC13:02
bauzas"Attribute ram (           since 1.0.2) specifies the size of the primary bar, while the           attribute vram specifies the secondary bar size.           If ram or vram are not supplied a default           value is used. The ram should also be rounded to power of           two as vram. There is also optional attribute           vgamem (since 1.2.11) to set           the size of VGA framebuffer for fallback mode of QXL device13:03
bauzashonestly, it's a very specific libvirt thing13:03
sfinucanfwiw, it's just another libvirt knob13:03
sfinucanbauzas: jinx :)13:03
bauzasI'm not really happy with that, hence my comment saying to maybe wait for custom RCs :)13:03
sfinucanbauzas: well, technically QEMU - libvirt just wraps it13:03
*** gouthamr has quit IRC13:04
*** links has quit IRC13:04
bauzasjohnthetubaguy: sfinucan: just -1d it again13:06
*** belmoreira has joined #openstack-nova13:07
openstackgerritArtom Lifshitz proposed openstack/nova-specs master: SPICE native client support  https://review.openstack.org/44204013:08
*** bkopilov has joined #openstack-nova13:09
johnthetubaguybauzas: don't feel we are being great at giving suggestions how to fix the spec right now though13:09
*** artom has quit IRC13:10
*** artom has joined #openstack-nova13:10
*** mdrabe has joined #openstack-nova13:11
*** Jack_Iv has joined #openstack-nova13:11
*** zul has quit IRC13:12
*** jwcroppe has joined #openstack-nova13:12
*** eharney has joined #openstack-nova13:12
*** Jack_Iv has quit IRC13:12
*** amoralej|lunch is now known as amoralej13:14
bauzasjohnthetubaguy: I tried to explain my preferrence about providing custom resource classes against very specific image props13:14
*** xyang1 has joined #openstack-nova13:14
*** tbachman has quit IRC13:14
*** Jack_Iv has joined #openstack-nova13:15
*** amotoki has quit IRC13:15
*** sapcc-bot has joined #openstack-nova13:15
*** sapcc-bot has quit IRC13:15
openstackgerritSergey Nikitin proposed openstack/nova master: Added PCI NUMA policies  https://review.openstack.org/39052013:16
*** sapcc-bot has joined #openstack-nova13:16
*** gouthamr has joined #openstack-nova13:17
*** efried has joined #openstack-nova13:18
*** cdent has quit IRC13:18
*** sapcc-bot has quit IRC13:19
*** sapcc-bot has joined #openstack-nova13:19
*** sapcc-bot has quit IRC13:20
*** sapcc-bot has joined #openstack-nova13:21
*** annegentle has joined #openstack-nova13:21
*** prateek_ has joined #openstack-nova13:22
*** aysyd has joined #openstack-nova13:23
*** liverpooler has quit IRC13:24
*** sapcc-bot has quit IRC13:24
*** prateek has quit IRC13:24
*** liverpooler has joined #openstack-nova13:24
*** sapcc-bot has joined #openstack-nova13:24
*** sapcc-bot has quit IRC13:25
*** sapcc-bot has joined #openstack-nova13:25
*** sapcc-bot has quit IRC13:26
*** annegentle has quit IRC13:26
*** prateek_ has quit IRC13:27
*** mriedem has joined #openstack-nova13:27
mriedemis everyone excited for a fun spec review day?!13:28
* artom got his spec updated just in time13:29
artomDoc's appointment this morning, but will try to participate this afternoon13:29
peter-hamiltonmriedem: indeed!13:29
mriedemi see johnthetubaguy has been having fun13:29
*** cleong has joined #openstack-nova13:30
johnthetubaguyyeah, I abandoned a bunch of left alone specs13:30
johnthetubaguyonly three pages of joy now13:30
mriedemawesome13:30
*** zul has joined #openstack-nova13:32
*** dikonoor has joined #openstack-nova13:32
*** crushil has joined #openstack-nova13:33
*** liverpooler has quit IRC13:34
*** liverpooler has joined #openstack-nova13:34
*** jaosorior is now known as jaosorior_away13:36
*** litao has joined #openstack-nova13:36
*** awaugama has quit IRC13:37
*** sree has joined #openstack-nova13:39
openstackgerritMaciej Szankin proposed openstack/nova-specs master: Add remove-nova-cert spec  https://review.openstack.org/44888213:39
*** mlavalle has joined #openstack-nova13:44
openstackgerritStephen Finucane proposed openstack/nova master: nova-manage: Deprecate 'agent' commands  https://review.openstack.org/45079513:45
openstackgerritStephen Finucane proposed openstack/nova master: nova-manage: Deprecate 'shell' commands  https://review.openstack.org/43228013:45
openstackgerritStephen Finucane proposed openstack/nova master: nova-manage: Deprecate 'project', 'account' commands  https://review.openstack.org/45317413:45
openstackgerritStephen Finucane proposed openstack/nova master: nova-manage: Deprecate 'host' commands  https://review.openstack.org/45317513:45
openstackgerritStephen Finucane proposed openstack/nova master: nova-manage: Deprecate 'log' commands  https://review.openstack.org/45317613:45
*** sree has quit IRC13:46
bauzasmriedem: I guess you don't know https://en.wikipedia.org/wiki/L%C3%A9onard_%28comics%29 ?13:48
mriedemnope13:48
bauzasmriedem: because the disciple always says "I serve science and it's my joy"13:49
*** amotoki has joined #openstack-nova13:50
*** dane-fichter has joined #openstack-nova13:50
*** kevinz has quit IRC13:50
*** liangy has joined #openstack-nova13:51
dane-fichterpeter-hamilton: anything relevant so far?13:52
*** nmathew has quit IRC13:53
peter-hamiltondane-fichter: not yet :)13:53
dane-fichterpeter-hamilton: cool. got caught in traffic13:53
*** lyan has quit IRC13:53
*** aysyd has quit IRC13:53
*** felipemonteiro has joined #openstack-nova13:54
mriedempeter-hamilton: dane-fichter: you guys might want to review https://review.openstack.org/#/c/44888213:54
mriedemfor dropping the nova-cert service13:54
peter-hamiltonmriedem: looking now13:54
dane-fichtermriedem: we'll take a look, thanks13:54
*** cdent has joined #openstack-nova13:56
*** hoangcx has joined #openstack-nova13:56
tdurakovhi, folks, there will be no live-migration meeting this week13:58
bhagyashrisjohnthetubaguy: Hi, Could you please review patch https://review.openstack.org/#/c/409644/ ? if you have free time.13:58
*** amotoki has quit IRC13:59
*** jwcroppe has quit IRC14:00
sdaguejohnthetubaguy: why did you think 400 instead of 404 - https://review.openstack.org/#/c/448882 ?14:01
*** sree has joined #openstack-nova14:01
johnthetubaguysdague: didn't consider 404 honestly14:01
johnthetubaguysdague: I was seeing this as the implementation removed, not the API changed14:02
*** jwcroppe has joined #openstack-nova14:02
sdaguewell, we could always be tricksie and use 410 then14:03
sdaguebut I though that 404 is what the whole system returns if you go fetch /foobar14:03
*** sree has quit IRC14:06
johnthetubaguysdague: oh, 410 = gone, I had not come across that. I guess it depends if we want to pretend if the old API never existed or not. 410 would help know you got the correct URL, as you always used to, its just the server that has change and no longer wants to server up that API14:06
*** mdnadeem has quit IRC14:07
*** lyan_ has joined #openstack-nova14:07
*** namnh has joined #openstack-nova14:07
sdaguejohnthetubaguy: yeh, though my hesitation on 410 is that no tool is every designed to understand it :)14:08
johnthetubaguysdague: yeah, thats good and bad in equal measure I guess14:08
sdagueyep14:09
sdaguebut, more importantly, I think it requires us to have a stub hanging around14:09
*** ekuris has quit IRC14:09
sdaguevs. just deleting the handler14:09
sdagueand, I'd rather just delete the handler14:09
*** ekuris has joined #openstack-nova14:09
*** liangy has quit IRC14:09
*** dharinic has joined #openstack-nova14:10
*** armax has joined #openstack-nova14:11
*** satyar has joined #openstack-nova14:12
*** mlakat has quit IRC14:13
*** ekuris has quit IRC14:13
*** garyk2 has quit IRC14:14
*** garyk has joined #openstack-nova14:14
*** tbachman has joined #openstack-nova14:15
*** jdillaman has quit IRC14:15
*** amotoki has joined #openstack-nova14:17
cdentsdague, johnthetubaguy I reckon deleting the handler has most win (because of getting to remove cleanly)14:17
*** sree has joined #openstack-nova14:17
mriedemdo i need a spec to propose deleting the os-pci api code even though it's never been enabled or exposed?14:17
cdenthowever 410 would also be fine. Not that many tools actually "understand" response codes. They just react to them.14:18
cdentmriedem I think you have to ask mriedem about that14:19
mriedemdamn14:19
cdentand then collapse in on yourself14:19
*** tommylikehu_ has joined #openstack-nova14:19
cdentmriedem speaking of needing specs: https://review.openstack.org/#/c/448791/ needs one, I guess?14:20
mriedemprobably yeah14:20
mriedemi don't want us to get lax on api impacts for placement14:21
cdentfair14:21
* cdent adds to list14:21
mriedemclarkb: with the UCA change in devstack we get libvirt 2.5 right? do you know if we also are going to get an updated qemu? and if so, which version?14:22
*** lyan_ has quit IRC14:22
*** sree_ has joined #openstack-nova14:22
sdaguemriedem: we will14:23
*** sree_ is now known as Guest1532014:23
mriedemjust wondering if it's new enough to cover what's in https://review.openstack.org/#/c/437070/14:23
mriedem^ requires qemu 2.614:23
*** sree has quit IRC14:24
sdaguemriedem: https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/ocata-staging/+index?batch=75&direction=backwards&start=15014:26
sdagueguessing, I think that would be 2.814:26
*** tommylikehu_ has quit IRC14:26
*** jdillaman has joined #openstack-nova14:28
*** awaugama has joined #openstack-nova14:28
*** eharney has quit IRC14:31
mriedemlyarwood: this introduced a bug https://review.openstack.org/#/c/393901/14:32
mriedemencryptor may not be defined when logged14:32
*** crushil has quit IRC14:32
*** ralonsoh has joined #openstack-nova14:32
*** lyan_ has joined #openstack-nova14:33
lyarwoodmriedem: bug #? The os-brick differs there for some reason..14:35
*** READ10 has joined #openstack-nova14:35
mriedemlyarwood: no bug yet, i can open one14:35
lyarwoodmriedem: thanks, I'll get it backported, btw I'm looking to drop all of this code in Pike via https://review.openstack.org/#/c/391597/14:36
*** zz_dimtruck is now known as dimtruck14:37
mriedemheh that's not really a bug14:37
*** mdrabe has quit IRC14:37
*** crushil has joined #openstack-nova14:37
*** hongbin has joined #openstack-nova14:37
lyarwoodmriedem: ah just code review? I assumed it came from a customer, just reading the scollback it looks like you are reviewing the QEMU LUKS spec right?14:38
mriedemyes14:38
lyarwoodkk, don't worry about the bug then14:38
mriedemalready written14:39
mriedemi meant your os-brick encryptors change was not a bug14:39
mriedemto make nova use os-brick encryptors code14:39
mriedemis not a bug14:39
mriedemthe NameError is definitely a bug :)14:39
mriedemhttps://bugs.launchpad.net/nova/+bug/167971714:39
openstackLaunchpad bug 1679717 in OpenStack Compute (nova) "Potential for NameError when logging volume encryptor" [Undecided,New]14:39
lyarwoodah14:39
*** mriedem has left #openstack-nova14:40
*** tjones has joined #openstack-nova14:40
*** mriedem has joined #openstack-nova14:40
*** vks1 has joined #openstack-nova14:41
*** mdrabe has joined #openstack-nova14:43
*** huyang_ has joined #openstack-nova14:44
*** huyang_ has quit IRC14:45
*** abalutoiu has joined #openstack-nova14:46
*** eharney has joined #openstack-nova14:46
mriedemlyarwood: your spec reminds me that the cinder API reference doesn't even mention the encryption provider stuff in the volume type api docs14:47
openstackgerritJeremy Stanley proposed openstack/nova master: Switch from pip_missing_reqs to pip_check_reqs  https://review.openstack.org/45320814:47
*** cdent has quit IRC14:47
*** jahsis has quit IRC14:47
*** abalutoiu__ has quit IRC14:48
*** erhudy has joined #openstack-nova14:48
*** dikonoor has quit IRC14:48
*** armax has quit IRC14:51
namnhdansmith: Hi mr Smith, are you free, could I ask you a question about rolling upgrade?14:51
dansmithnamnh: just ask and someone here will answer if we know14:52
lyarwoodmriedem: yeah isn't it just stashed in the type as in extra_specs? ./me doesn't have an env to check14:53
*** yingjun has joined #openstack-nova14:53
*** crushil has quit IRC14:53
*** yingjun has quit IRC14:53
lyarwoodtype in extra_specs*14:53
namnhdansmith: According to this link [1], we have to stop and start all Nova's serices except compute at the same time.14:53
openstackgerritPushkar Umaranikar proposed openstack/nova-specs master: Stop using Neutron admin token  https://review.openstack.org/43989014:53
namnh[1] https://docs.openstack.org/developer/nova/upgrade.html#rolling-upgrade-process14:54
namnhdansmith: But IMO, there is another way to upgrade is that I will upgrade the services except compute sequentially by pinning version each services like this file [2], at this time we have a new code with the value of "pin version" is old release, after that I will unpin version by restart all services at the same time. If we do this way, we only have downtime when unpining version. How do you think?14:54
namnh[2] https://github.com/openstack/nova/blob/master/nova/conf/upgrade_levels.py14:54
dansmithnamnh: as we said yesterday, that only works for compute14:55
dansmithnamnh: the other services talk directly to the database, which doesn't honor the upgrade level (those are only for rpc)14:55
dansmithnamnh: compute is not allowed to talk directly to the database, which is why it can be old, but the others cannoy14:55
dansmith*cannot14:55
*** annegentle has joined #openstack-nova14:56
*** armax has joined #openstack-nova14:56
*** crushil has joined #openstack-nova14:57
*** bhagyashris has quit IRC14:59
*** jpena is now known as jpena|away15:00
*** ratailor has joined #openstack-nova15:00
namnhdansmith: but if I upgrade one conductor (N ->O), I will pin version is that: conductor=newton. That mean although conductor at new release, but it will continue talk with other services due to pin version.15:00
namnhdansmith: I understand this file [1] configuration to do this. [1] https://github.com/openstack/nova/blob/master/nova/conf/upgrade_levels.py15:01
namnhdansmith: we can pin version for each service15:02
*** hoangcx has quit IRC15:03
*** lucasxu has joined #openstack-nova15:04
*** pumarani_ has joined #openstack-nova15:04
*** vks1 has quit IRC15:04
*** timello has quit IRC15:04
bauzasdansmith: mriedem: so I thought about the claims spec and I pushed my thoughts in the spec https://review.openstack.org/#/c/437424/15:04
bauzasdansmith: mriedem: tl;dr I think there are 2 things15:05
*** yamahata has joined #openstack-nova15:05
bauzas1/ rescheduling is a cellsv2 problem, not really related to my spec, so we should discuss that separately15:05
*** jwcroppe has quit IRC15:05
bauzasbecause rescheduling (even without scheduler claims) is not possible in a cellsv2 world15:05
*** Oku_OS is now known as Oku_OS-away15:06
bauzas2/ I think it would be a still good behaviour if computes delete allocations directly by calling placemnt API, given it would be quicker than waiting for the scheduler during the reschedule15:06
*** jwcroppe has joined #openstack-nova15:07
namnhhieulq: ping15:08
fricklerfrom a deployment perspective, is there any sense in providing the placement API to customers? or would one rather create an internal endpoint only?15:08
fricklerI'm assuming the latter and then it might make sense to change the default of placement.os_interface from public to internal, too15:10
pumarani_sdague, checking your comment on https://review.openstack.org/#/c/439890/. I understand your concern of getting neutron changes in place first.15:10
pumarani_sdague, we have already added RFE in neutron https://review.openstack.org/#/c/439890/15:10
pumarani_i mean https://bugs.launchpad.net/neutron/+bug/167434915:11
openstackLaunchpad bug 1674349 in neutron "[RFE] Introduce a new rule with service user role in Neutron policy" [Wishlist,Triaged] - Assigned to Akihiro Motoki (amotoki)15:11
*** yamahata has quit IRC15:12
*** Guest52040 has joined #openstack-nova15:13
*** armax has quit IRC15:13
*** nkrinner is now known as nkrinner_afk15:14
*** annegentle has quit IRC15:15
*** cdent has joined #openstack-nova15:16
*** baoli has quit IRC15:18
*** raj_sing- has joined #openstack-nova15:19
sdaguepumarani_: ok, that's a wishlist bug, does that mean it's commited to be accepted?15:19
sdaguealso, where is implementation code for it15:19
fricklersdague: mriedem: this has a nicer (imho) list of all the versions in Ocata UCA: http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/ocata_versions.html15:19
*** ralonsoh_ has joined #openstack-nova15:19
sdaguefrickler: ah, cool, I was looking for something like that15:20
*** raj_singh_ has quit IRC15:20
mriedemlyarwood: no it's in the volume encryption model in the cinder db15:20
*** vks1 has joined #openstack-nova15:20
sdaguepumarani_: I guess, it's really unclear to me what the neutron status is, and as such I'd really feel a lot better about this depending on merged neutron code.15:21
*** jdillaman has quit IRC15:21
mdboothlyarwood: Are you wondering where the provider string comes from?15:22
*** Jack_Iv_ has joined #openstack-nova15:22
mriedembauzas: if we can't reschedule, why do we care about how fast the allocations are deleted?15:22
*** Jack_Iv__ has joined #openstack-nova15:22
*** joanna__ has joined #openstack-nova15:22
mriedemthat raises the question of when the allocations are deleted, but i think that's just left unchanged, when we delete the instance we remove the allocations via RT in the comptue host15:23
mriedem*compute15:23
bauzasmriedem: it's a separate problem, hence me saying if reschedules are possible, then I'd prefer to delete the allocations sooner than later15:23
mdboothmriedem: Do you have a spec to delete bdm v1, btw?15:23
mriedemmdbooth: i don't15:23
mriedembauzas: also, have we taken into account local deletes in the API?15:23
*** ralonsoh has quit IRC15:23
bauzasmriedem: I'm just putting a big hypothesis in my spec that is, reschedules are possible15:23
mriedemthe compute api would have to delete the allocations there if the compute is dead15:23
mdboothmriedem: Why does it linger, btw?15:23
*** Jack_Iv__ has quit IRC15:24
mriedemmdbooth: no good reason probably15:24
*** belmoreira has quit IRC15:24
*** Jack_Iv has quit IRC15:24
*** Guest15320 has quit IRC15:24
mdboothIt's a prime candidate for simplification.15:24
bauzasmriedem: well, that's possibly a good point, if the compute is dead, then the allocation would still be created15:24
*** Jack_Iv has joined #openstack-nova15:24
*** sree has joined #openstack-nova15:24
bauzasmriedem: so we could possibly clean up "dead" allocations15:24
openstackgerritMarkus Zoeller (markus_z) proposed openstack/nova master: The API defines PUT and POST as HTTP methods which need a request body. It is allowed, that this request body might be of zero length. What was missing is, that the "content-length" of the request also might be None.  https://review.openstack.org/45322015:25
bauzasmriedem: that said, the ComputeFilter verifies whether the service is still up15:25
*** Jack_Iv_ has quit IRC15:25
*** Jack_Iv has quit IRC15:25
*** ralonsoh_ is now known as ralonsoh15:25
pumarani_sdague, yes. With neutron changes getting merged, we can also have some code samples on it. we are following up on neutron RFE.15:25
*** Jack_Iv has joined #openstack-nova15:25
bauzasmriedem: so the real problem is rather, say, a full compute MQ with bad performance15:25
bauzasmriedem: then we would have created an allocation for something not really created15:26
bauzaseither way, I need to think more of that15:26
openstackgerritMarkus Zoeller (markus_z) proposed openstack/nova master: API: accept None as content-length in HTTP requests  https://review.openstack.org/45322015:26
sdaguemriedem: in our "spec review sprint" today, are there particular specs you want eyes on instead of just scatter shotting?15:26
*** raj_sing- is now known as raj_singh15:27
openstackgerritPeter Hamilton proposed openstack/nova-specs master: Add support for certificate validation  https://review.openstack.org/35715115:29
*** sree has quit IRC15:29
mriedemlyarwood: https://bugs.launchpad.net/cinder/+bug/167973615:31
openstackLaunchpad bug 1679736 in Cinder "VolumeTypeEncryption API extension is not documented in api-ref site" [Undecided,New]15:31
*** peter-hamilton_ has joined #openstack-nova15:31
mriedembauzas: i'm talking about after you've landed an instance on a host, so after scheduling, and the compute is down and you delete the instance15:31
*** peter-hamilton has quit IRC15:31
mriedemsince we can't remove the allocation via RT on the compute host, where do we deallocate for that resource provider for a local delete?15:31
mriedemhell, is that just a latent bug we already have with placement?15:31
mriedemjaypipes: dansmith: ^?15:32
bauzasmriedem: well, me shrugs15:32
bauzasI guess yes15:32
mriedembauzas: i don't know what "then we would have created an allocation for something not really created" means15:32
mriedemsdague: full monty15:32
* jaypipes reads back15:33
mriedembauzas: for the comptue isn't down, but the instance is shelved-offloaded,15:33
bauzasmriedem: I was thinking of the scheduler saying "okay, this one" then posting the allocations, then the boot requests goes trampled by the RPC bus15:33
mriedemi guess when we shelve offload, do we deallocate?15:33
* cdent tries to catch up too15:33
cdentI think there's some misconceptions going on here15:33
mordredcdent: people have the wrong idea about something? bah15:34
jaypipesmriedem: yeah, it's a latent bug I think. we don't currently deallocate orphaned instances like we should.15:34
mriedemlyarwood: i think we should add a microversion to cinder v3 to fix some of the volume type encryption api stuff, like remove the need for the full classname in the provider entry, just say 'luks' or 'cryptsetup'15:34
cdentyes, known bug: a dead compute node's allocations persist15:35
mriedemlyarwood: and as part of that microversion change in cinder v3, we enforce the actual providers using schema validation, rather than let it be free-form like it is today15:35
mriedemcdent: jaypipes: how about shelve offload?15:35
cdentthere's also this: https://bugs.launchpad.net/nova/+bug/166131215:36
openstackLaunchpad bug 1661312 in OpenStack Compute (nova) "Evacuation will corrupt instance allocations" [Undecided,New]15:36
mriedembecause when we unshelve, the instance could end up on a different host15:36
jaypipesmriedem: no idea. would need to check. not sure if the compute manager calls an RT method on shelve_offload().15:36
mriedemand if it's on a different host, we're then counting allocatoins twice for the same instnace15:36
*** pumarani_ has quit IRC15:37
cdentsince allocations are keyed by consumer id, and we set them (as in fully replace them) the situation is a bit cleaner than it might initially appear15:38
mriedembut when we do claims in the scheduler,15:38
mriedemaren't we aggregating the total allocations for a given resource provider?15:39
mriedemand if we don't remove the allocations for a shelved offloaded consumer on that compute resource provider, it's a lie about actual resource allocation right?15:39
cdentif we are puting an allocation, it will be for the instance uuid, no matter what it uses15:39
*** peter-hamilton_ is now known as peter-hamilton15:39
jaypipesmriedem: no.15:39
mriedemi guess when we do claims we're looking at inventory?15:40
*** iceyao has joined #openstack-nova15:40
*** gszasz has quit IRC15:40
mriedemif i have an inventory of 5 apples, and your instance claims 3 apples, i have 2 apples left for sally to claim, right?15:40
jaypipesmriedem: the "claim" is merely the transactional writing of allocation records against one or more resource providers for a single consumer ID.15:40
bauzasmriedem: I think all the move operations need to update the allocations indeed15:41
jaypipesmriedem: yes, that is a check that occurs entirely within the POST /allocations context in the placement API though.15:41
bauzasI need a second pass of thoughts15:41
mriedemjaypipes: don't we POST allocations to a specific resource provider though?15:41
cdentmriedem: no15:42
jaypipesmriedem: you will get a 409 if, say, Alice gets an apple before Sally's attempt to get 2 apples.15:42
jaypipesmriedem: no, allocations are multi-provider.15:42
cdentmriedem: or rather, not quite15:42
gibimriedem: hi! I saw your ping from yesterday about the snapshot notification and I had some free time to put a patch togheter for that issue https://review.openstack.org/#/c/453077/15:42
mriedemresource_provider_uuid = allocation['resource_provider']['uuid']15:42
jaypipesmriedem: for instance, a compute host provider and a shared storage pool provider might be involved in the same POST /allocations for a consumer (instance UUID)15:42
mriedembut the allocation is still tied to a resource provider15:43
mriedemone or more15:43
jaypipesmriedem: the allocation record is, yes. but the entire "claim" is a *set* of allocation records for a single consumer (the instance)15:43
mriedemthe scheduler is asking placement for the list of available resource providers given some vcpu/ram/disk constraints, right?15:43
jaypipesyep15:43
mriedemand then takes that list, gets the compute nodes from the db, and filters them15:43
jaypipesyep15:44
mriedemso then i have maybe 3 available hosts, i pick one, and make my claim15:44
mriedemwhich is a POST allocation on that resource provider, yes?15:44
jaypipesno15:44
jaypipes:)15:44
*** lucasxu has quit IRC15:44
jaypipesit would be a POST /allocations and the compute node resource provider would be one of the resource providers involved in the allocation request.15:44
jaypipesmriedem: again, the reason this is like that is because you can claim resources against >1 provider in a single request.15:45
mriedemi think i'm trying to say the same thing15:45
mriedembut in the less formal way15:45
mriedemme ugg, me want 2 apples, you mug have 3 apples, me claim 2 of your 3 apples, yes?15:45
jaypipesyes15:46
mriedemi get the multiple provider thing, that's fine, i need some compute resources, i need some shared storage resources from another provider, whatever15:46
cdent(just to be pedantic the currently available method is PUT /allocations/{consumer_uuid} and I think we can continue using that one for the time being)15:46
mriedemok, so i think we've established that the scheduler has 'claimed' resources on a provider, or set of providers, by putting an allocation for a given instance (consumer) on those providers,15:47
mriedemand then sends the build request to that host15:47
mriedemto build the instance15:47
mriedemsince we can't reschedule, i guess i won't ask about that15:48
*** Jack_Iv has quit IRC15:48
mriedemso when we shelve offload an instance, do we deallocate for that consumer on it's resource providers15:48
mriedemor when we delete the instance, and the compute host is down so we can't rpc cast to the compute to do the delete, do we deallocate from the api15:48
mriedemi think the answer to both is no15:48
jaypipesyeah, I suspect you are correct about that. but would be easy enough to fix in a bug report.15:49
mriedemi may be wrong about the shelve offload case, because i remember alaski pointing out a super gross tight coupling of instance vm_state checking in the RT15:50
mriedemyup ALLOW_RESOURCE_REMOVAL = [DELETED, SHELVED_OFFLOADED]15:50
mriedemRT._update_usage_from_instance15:50
mriedemchecks that15:50
*** chyka has joined #openstack-nova15:50
jaypipesok15:50
*** artom has quit IRC15:51
mriedemwhich passes sign=-1 to update_instance_allocation to call _delete_allocation_for_instance15:51
mriedemcool15:51
mriedemwe still fail the local delete case probably15:51
mriedemwhich is maybe related to dansmith's bug about evacuate15:51
*** rmart04 has quit IRC15:52
*** jlvillal_pto is now known as jlvillal15:54
*** andreas_s has quit IRC15:54
*** rfolco_ has quit IRC15:56
*** artom has joined #openstack-nova15:57
*** hieulq_ has joined #openstack-nova15:57
*** hieulq__ has joined #openstack-nova15:58
*** namnh has quit IRC15:58
*** eharney has quit IRC15:59
*** markus_z has quit IRC16:00
*** lucasagomes is now known as lucas-afk16:00
dansmithsorry I was on a call, and have only skimmed the scrollback16:01
mriedemdansmith: in https://bugs.launchpad.net/nova/+bug/1661312 where does step 4 happen?16:01
openstackLaunchpad bug 1661312 in OpenStack Compute (nova) "Evacuation will corrupt instance allocations" [Undecided,New]16:01
mriedemdansmith: jaypipes: cdent: created https://bugs.launchpad.net/nova/+bug/167975016:01
openstackLaunchpad bug 1679750 in OpenStack Compute (nova) "Allocations are not cleaned up in placement for instance 'local delete' case" [Undecided,New]16:01
cdentjaypipes, bauzas, mriedem I left a longer comment on the spec to remind us of some of these things16:01
dansmithjaypipes: if we end up off the compute node due to shelve or evacuate, won't we heal our way to deleting the allocations after a bit?16:01
*** pcaruana has quit IRC16:01
dansmithjaypipes: also for local delete, I would think16:01
cdentthanks mriedem16:01
jaypipesdansmith: need to look into it. we *may* but wasn't 100% sure.16:01
dansmithjaypipes: I would think we do16:02
dansmithjaypipes: it might take a bit, but.. should happen I think16:02
*** hieulq_ has quit IRC16:02
*** efoley has joined #openstack-nova16:02
cdentthe periodic job in the RT is always trying to heal if it sees a gap16:02
dansmithcdent: right16:02
cdentso the problem comes up when there is no RT16:02
cdents/the/a/16:02
*** voelzmo has quit IRC16:03
dansmithyou mean in a scheduler-claims world?16:04
cdentdansmith: no, in the world where we want the representation of available resources to be correct16:05
cdentit doesn't always have practical impact if a compute nodes is down but in the placement db but it does mean that our global total of eg vcpus is wrong16:06
cdentit would be nice that when a compute node went down , it was removed from the placement db16:07
cdentbut since they self register16:07
cdentWe don't currently have anything in place to clean up when they die, do we?16:07
dansmithI dunno about that.. for instances that aren't evacuated, those are still valid allocations, yes?16:07
dansmithif you think about when we do quota by counting things in placement,16:08
cdentI was thinking more in the sense of full on node crash16:08
dansmithone compute node going offline shouldn't free up quota for you and then get you in the red once it comes back16:08
dansmitheven if the compute node is off and cold, if there are unevacuated (or undeleted) instances there, the allocations should stay, IMHO16:08
mriedemdansmith: i agree with that16:08
cdentthe quota case nicely complicates things16:09
dansmithi.e. I wouldn't think placement should know about liveness16:09
mriedemhttps://bugs.launchpad.net/nova/+bug/1679750 is about when you delete an instance on a dead node16:09
openstackLaunchpad bug 1679750 in OpenStack Compute (nova) "Allocations are not cleaned up in placement for instance 'local delete' case" [Undecided,New]16:09
*** nic has joined #openstack-nova16:09
dansmithif nova has an instance, then placement has a record of allocations.. nothing more than that16:09
cdentbecause if we are using allocations for usage, is a cold node supposed to count against my quota? that's not my (the user's) fault and I want to run some instances16:09
*** Jack_Iv has joined #openstack-nova16:09
cdents/usage/quota measurment/16:09
dansmithcdent: it should IMHO yeah16:09
dansmithcdent: you're free to delete the instance and get the quota back16:10
dansmiththe flip side is,16:10
dansmithif a compute node goes down, you get more quota and boot a thing,16:10
dansmithwhen the compute node comes back, should the provider be free to nuke the instance that was running on that node since you'd now be over quota?16:10
cdenthmmm. yeah. weird.16:10
cdentblech16:10
mriedemi think when i get some time i'll write a functional test for the local delete /allocations bug16:10
mriedemback to spec review16:11
*** karimb has quit IRC16:12
*** derekh has quit IRC16:13
*** eharney has joined #openstack-nova16:16
openstackgerritArtom Lifshitz proposed openstack/nova-specs master: SPICE native client support  https://review.openstack.org/44204016:19
*** hieulq__ has quit IRC16:21
*** hieulq__ has joined #openstack-nova16:22
openstackgerritBalazs Gibizer proposed openstack/nova-specs master: Show persisted scheduler hints in server details  https://review.openstack.org/44058016:22
*** aarefiev is now known as aarefiev_afk16:23
*** sridharg has quit IRC16:23
*** READ10 has quit IRC16:24
*** hieulq__ has quit IRC16:25
gibimriedem, sdague, cdent, jaypipes, johnthetubaguy: hi! I updated the spec https://review.openstack.org/#/c/44058016:25
*** Swami has joined #openstack-nova16:25
gibimriedem, sdague, cdent, jaypipes, johnthetubaguy: I tried to answer all the concerns comments16:26
jaypipesgibi: thx Balasz!16:26
cdentgibi++16:26
*** rfolco has joined #openstack-nova16:27
*** Jack_Iv has quit IRC16:27
mriedemmgagne: thanks for this https://review.openstack.org/#/c/337819/16:28
mriedemmgagne: not many people take the time to update spec docs after the fact16:28
*** dtp has joined #openstack-nova16:28
mgagnemriedem: hmm, didn't get notification for that one, checking16:29
johnthetubaguycdent: you are right about limiting the crust at ingress, I think that was the question for me, should we do that first.16:29
*** litao has quit IRC16:29
johnthetubaguymriedem: ++ on the thank you and your comments there, it came up the other day in a bug I think16:30
mgagnecool, glad to see it got merged =)16:31
*** lyan_ is now known as lyan16:31
*** psachin has quit IRC16:32
*** suresh12 has quit IRC16:35
*** suresh12 has joined #openstack-nova16:35
*** annegentle has joined #openstack-nova16:36
*** lucasxu has joined #openstack-nova16:38
*** iceyao has quit IRC16:39
*** mtanino has joined #openstack-nova16:39
*** Apoorva has joined #openstack-nova16:39
*** suresh12 has quit IRC16:39
*** Apoorva has quit IRC16:40
*** Apoorva has joined #openstack-nova16:40
*** gouthamr has quit IRC16:41
*** ltomasbo is now known as ltomasbo|away16:41
*** gouthamr has joined #openstack-nova16:45
*** Jack_Iv has joined #openstack-nova16:45
*** Hosam has joined #openstack-nova16:49
*** Jack_Iv has quit IRC16:50
*** ratailor has quit IRC16:50
*** READ10 has joined #openstack-nova16:56
*** nkorabli has joined #openstack-nova16:57
openstackgerritLee Yarwood proposed openstack/nova master: encryptors: Always default to the NoOpEncrytor  https://review.openstack.org/45326517:03
*** jdillaman has joined #openstack-nova17:04
*** tesseract has quit IRC17:04
*** armax has joined #openstack-nova17:08
*** Jack_Iv has joined #openstack-nova17:09
*** Jack_Iv has quit IRC17:15
*** mvk has quit IRC17:15
*** tbachman has quit IRC17:16
*** timello has joined #openstack-nova17:16
*** vks1 has quit IRC17:16
*** armax has quit IRC17:18
*** amoralej is now known as amoralej|off17:20
*** tbachman has joined #openstack-nova17:22
*** baoli has joined #openstack-nova17:25
mriedemmelwitt: on https://review.openstack.org/#/c/453041/ i know it's just a re-proposal, but most of what that spec is talking about is the old justification for doing it, i.e. rpc versioning and the like. the reason you're re-proposing it is a bit different, for cells v2. i'd like to see something in there about why this is something we want for cells v2 - what cells v2 problem does it solve, etc?17:26
*** sambetts is now known as sambetts|afk17:27
openstackgerritLee Yarwood proposed openstack/nova-specs master: Libvirt: Native LUKS file and host device decryption by QEMU  https://review.openstack.org/43707017:27
melwittmriedem: okay. so add that and remove Previously-approved?17:27
*** armax has joined #openstack-nova17:27
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend  https://review.openstack.org/45327217:27
mriedemmelwitt: previously-approved is fine17:28
mriedemi'm just looking for something about cells v2 in the problem description17:28
melwittk17:28
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend  https://review.openstack.org/45327217:28
mriedemmaybe that's L53... "Because the new tokens will go in the database we need to consider17:28
mriedemcells v2."17:28
*** Guest52040 has quit IRC17:28
* mriedem reads on17:28
mriedemmelwitt: so maybe that paragraph answers it17:29
mriedemthe url contains the instance uuid17:29
mriedemweren't we going to use that to lookup which cell the token was in?17:29
*** voelzmo has joined #openstack-nova17:30
melwittyeah, I'm trying to see if that change happened already yet (looking at the old merged vs abandoned patches)17:32
melwittokay, so that change didn't make it https://review.openstack.org/#/c/325382/17:33
*** lucasxu has quit IRC17:33
*** lucasxu has joined #openstack-nova17:34
*** jvgrant_ has quit IRC17:35
*** jvgrant has joined #openstack-nova17:35
*** voelzmo has quit IRC17:36
mriedemdo we have to worry about old connection urls that don't have the instance uuid so we can't do the lookup for the cell?17:37
*** dillaman has joined #openstack-nova17:39
openstackgerritGábor Antal proposed openstack/nova master: Transform instance.volume_attach notification  https://review.openstack.org/40199217:39
*** voelzmo has joined #openstack-nova17:40
*** lucasxu has quit IRC17:40
*** lucasxu has joined #openstack-nova17:41
*** eharney has quit IRC17:41
*** annegentle has quit IRC17:42
*** Hosam has quit IRC17:43
melwittmriedem: so it looks like the idea during the transition period is to have both the consoleauth service running and have new tokens stored in cell databases. so old connection urls will be served by the consoleauth service, which has the tokens globally in memcached17:44
openstackgerritGábor Antal proposed openstack/nova master: Transform instance.volume_attach notification  https://review.openstack.org/40199217:44
*** annegentle has joined #openstack-nova17:46
openstackgerritGábor Antal proposed openstack/nova master: Transform instance.volume_attach notification  https://review.openstack.org/40199217:47
*** mlavalle has quit IRC17:49
melwittmriedem: and then I think through normal token expiration, eventually all of the old memcached tokens won't be used anymore, and when that happens it would be safe to stop running the consoleauth service since no outstanding connection urls will be without the server uuid17:49
macszbugs team meeting (#openstack-meeting-4)  in 10 minutes, if anyone is interested17:52
*** eharney has joined #openstack-nova17:55
*** prateek has joined #openstack-nova17:56
openstackgerritDan Peschman proposed openstack/nova master: Add uuid to Service model  https://review.openstack.org/45302518:00
*** mvk has joined #openstack-nova18:01
*** tuan_luong has joined #openstack-nova18:02
*** tuanla_ has joined #openstack-nova18:02
*** ralonsoh has quit IRC18:04
mriedemmelwitt: ok is that all in the spec? i didn't read the whole thing b/c i'm lazy18:05
mriedemah reading your reply18:05
*** dillaman has quit IRC18:05
oomichigmann: thanks, LGTM now18:06
*** dillaman has joined #openstack-nova18:06
melwittmriedem: it is, but it's not as detailed as my comment. I sort of derived it from looking at the abandoned patches plus the spec, since I'm not so familiar with consoles. the spec language appears to assume more knowledge18:07
mriedemyeah same here18:07
*** efoley has quit IRC18:08
mriedemyou need a phd like paul murray18:09
mriedemanyway, approved18:09
melwittheh, yeah18:09
melwittcool, thanks!18:09
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend  https://review.openstack.org/45327218:10
*** mdavidson has joined #openstack-nova18:11
*** dillaman has quit IRC18:12
*** felipemonteiro has quit IRC18:13
*** armax has quit IRC18:14
*** ijw_ has joined #openstack-nova18:14
*** felipemonteiro has joined #openstack-nova18:19
*** Sukhdev has joined #openstack-nova18:20
*** suresh12 has joined #openstack-nova18:21
*** sree has joined #openstack-nova18:22
*** suresh12 has quit IRC18:25
*** jamesdenton has joined #openstack-nova18:26
*** dillaman has joined #openstack-nova18:26
*** Apoorva_ has joined #openstack-nova18:27
openstackgerritArtom Lifshitz proposed openstack/nova-specs master: SPICE native client support  https://review.openstack.org/44204018:29
*** Apoorva has quit IRC18:30
*** mdrabe has quit IRC18:30
*** tuanla_ has quit IRC18:31
*** tuan_luong has quit IRC18:31
*** crushil has quit IRC18:32
*** MikeG451 has quit IRC18:33
*** amotoki has quit IRC18:34
*** Jack_Iv has joined #openstack-nova18:34
*** voelzmo has quit IRC18:35
*** Jack_Iv_ has joined #openstack-nova18:35
*** jamesden_ has joined #openstack-nova18:35
*** jamesdenton has quit IRC18:36
*** Jack_Iv has quit IRC18:36
*** Jack_Iv has joined #openstack-nova18:37
*** Jack_Iv_ has quit IRC18:37
*** Jack_Iv_ has joined #openstack-nova18:38
*** Jack_Iv has quit IRC18:40
mriedemcfriesen: in https://specs.openstack.org/openstack/nova-specs/specs/pike/approved/instance-flavor-api.html how are we representing a flavor that doesn't have any extra specs? are you omitting it from the response, or returning an empty list, or None?18:41
*** nkorabli has quit IRC18:41
*** timello has quit IRC18:41
*** artom has quit IRC18:42
*** artom has joined #openstack-nova18:42
openstackgerritmelanie witt proposed openstack/nova-specs master: Add project/user association to placement  https://review.openstack.org/45303018:43
*** MikeG451 has joined #openstack-nova18:44
*** ekuris has joined #openstack-nova18:44
mriedemlooks like it will be {}18:45
mriedemper the api sample18:45
*** cdent has quit IRC18:46
*** suresh12 has joined #openstack-nova18:47
*** joanna__ has quit IRC18:47
*** jwcroppe has quit IRC18:47
*** eharney has quit IRC18:47
*** jwcroppe has joined #openstack-nova18:48
*** artom has quit IRC18:50
*** artom has joined #openstack-nova18:50
*** mdrabe has joined #openstack-nova18:50
*** Jack_Iv has joined #openstack-nova18:50
*** satyar has quit IRC18:51
*** Jack_Iv_ has quit IRC18:51
*** jwcroppe has quit IRC18:52
*** avolkov has quit IRC18:55
*** mlavalle has joined #openstack-nova18:55
*** mkoderer has quit IRC18:57
*** suresh12 has quit IRC18:57
*** suresh12 has joined #openstack-nova18:58
*** mnestratov has quit IRC18:59
*** jamesden_ has quit IRC18:59
*** READ10 has quit IRC19:00
*** jamesdenton has joined #openstack-nova19:00
*** eharney has joined #openstack-nova19:00
*** mdrabe has quit IRC19:02
*** suresh12 has quit IRC19:02
*** mdrabe has joined #openstack-nova19:04
*** Jack_Iv_ has joined #openstack-nova19:05
*** dimtruck is now known as zz_dimtruck19:05
mriedemmelwitt: ever noticed that for project_id and user_id in the nova data model we allow 255?19:07
mriedembut keystone only allows 6419:07
*** sree has quit IRC19:07
*** lucasxu has quit IRC19:07
*** Jack_Iv__ has joined #openstack-nova19:08
*** lucasxu has joined #openstack-nova19:08
*** sree has joined #openstack-nova19:08
melwittmriedem: no, I didn't know we allow 25519:09
*** Jack_Iv has quit IRC19:09
mriedemok questions in https://review.openstack.org/#/c/453030/19:11
*** Jack_Iv_ has quit IRC19:11
*** owalsh_ has joined #openstack-nova19:12
*** sree has quit IRC19:12
melwittcool, thanks19:13
*** baoli has quit IRC19:14
*** owalsh has quit IRC19:15
*** voelzmo has joined #openstack-nova19:17
*** crushil has joined #openstack-nova19:18
*** voelzmo has quit IRC19:19
openstackgerritEric Fried proposed openstack/nova master: WIP: PowerVM Driver: config drive  https://review.openstack.org/40940419:20
*** harlowja has joined #openstack-nova19:24
*** owalsh_ is now known as owalsh19:26
*** voelzmo has joined #openstack-nova19:27
*** Jack_Iv__ has quit IRC19:28
*** Jack_Iv has joined #openstack-nova19:28
openstackgerritEric Fried proposed openstack/nova master: PowerVM Driver: SSP emphemeral disk support  https://review.openstack.org/44318919:29
*** READ10 has joined #openstack-nova19:31
mriedemf yeah down to just 1.5 pages of open spec reviews19:32
*** Jack_Iv has quit IRC19:32
*** baoli has joined #openstack-nova19:32
*** Jack_Iv has joined #openstack-nova19:35
*** prateek has quit IRC19:36
*** Jack_Iv has quit IRC19:36
*** krtaylor has quit IRC19:45
*** voelzmo has quit IRC19:46
*** awaugama has quit IRC19:47
*** ducttape_ has joined #openstack-nova19:48
*** suresh12 has joined #openstack-nova19:52
*** cdent has joined #openstack-nova19:58
*** ediardo has quit IRC20:00
mriedemsdague: this is an easy one to go through https://review.openstack.org/#/c/384261/ - if you agree with my comments, i can update it quick20:00
*** ediardo has joined #openstack-nova20:01
sdaguemriedem: after the TC meeting I'll try to look20:01
mriedemack20:01
*** dave-mccowan has quit IRC20:03
*** nkorabli has joined #openstack-nova20:05
*** nkorabli has quit IRC20:05
*** mnestratov has joined #openstack-nova20:06
*** Sukhdev has quit IRC20:15
*** voelzmo has joined #openstack-nova20:18
*** Apoorva_ has quit IRC20:19
*** Apoorva has joined #openstack-nova20:19
*** gouthamr has quit IRC20:20
openstackgerritmelanie witt proposed openstack/nova-specs master: Add project/user association to placement  https://review.openstack.org/45303020:23
*** voelzmo has quit IRC20:23
openstackgerritJohn Garbutt proposed openstack/nova-specs master: Add additional-default-policy-roles spec  https://review.openstack.org/42787220:23
*** ducttape_ has quit IRC20:24
*** suresh12 has quit IRC20:30
*** cleong has quit IRC20:30
*** armax has joined #openstack-nova20:30
*** suresh12 has joined #openstack-nova20:30
*** ducttape_ has joined #openstack-nova20:34
*** suresh12 has quit IRC20:35
*** thorst has quit IRC20:35
*** smatzek has quit IRC20:37
*** gouthamr has joined #openstack-nova20:38
*** mdrabe has quit IRC20:40
*** mdrabe has joined #openstack-nova20:48
*** jamesdenton has quit IRC20:50
*** zz_dimtruck is now known as dimtruck20:53
*** rcernin has quit IRC20:55
*** krtaylor has joined #openstack-nova20:59
*** jamesdenton has joined #openstack-nova21:00
*** marst has quit IRC21:00
*** marst has joined #openstack-nova21:01
*** Apoorva_ has joined #openstack-nova21:06
*** thorst has joined #openstack-nova21:07
mriedemrandom filter question,21:07
mriedemi'm sure we have something that handles this,21:07
sdaguemriedem: https://review.openstack.org/#/c/384261/6/specs/pike/approved/deprecate-multinic-proxy-api.rst ... yeh, I think your comments are fine there21:08
mriedembut if i have a set of host aggregates with a certain storage backend that has restrictions on it, and i want my flavors tied to that, i can do it with extra specs so the flavors are tied to those host aggregates, but how to i keep other flavors that don't have the extra spec from landing on those hosts?21:08
mriedemwhich filter does that?21:08
*** Apoorva_ has quit IRC21:09
* mriedem spins the wheel of scheduler filters21:09
mriedemsdague: ok i'll update it21:09
mriedemsdague: although at this point in the day i suppose you're done21:09
*** Apoorva_ has joined #openstack-nova21:09
mriedemi can let alex_xu update it21:09
*** Apoorva has quit IRC21:10
melwittmriedem: I thought it would be AggregateInstanceExtraSpecsFilter21:10
sdaguemriedem: either way, the fam is out at the store, so I have a few minutes until they get back21:10
*** marst has quit IRC21:10
mriedemmelwitt: yeah but AggregateInstanceExtraSpecsFilter returns True if the flavor doesn't have extra specs too21:11
melwitthm, I was going off the docstring "Check that the extra specs associated with the instance type match the metadata provided by aggregates.  If not present return False."21:11
mriedemmelwitt: i think that's if the extra spec key is not in the aggregate metadata21:12
mriedemif not aggregate_vals:21:12
*** suresh12 has joined #openstack-nova21:12
melwittright, doesn't that mean if no match, host_passes is False? but I do see it returns True if extra_specs is entirely empty21:13
*** artom has quit IRC21:13
*** artom has joined #openstack-nova21:14
mriedemyeah21:14
mriedemso if the flavor has extra specs but they aren't in the aggregate meta, then host does not pass21:14
mriedemif the flavor doesn't have extra specs at all, then host passes21:14
mriedemthat's the case i'm wondering about21:14
melwittyeah, and I remember the latter was a relatively new addition. "relatively new" meaning I remember when it got added21:15
melwittlemme see21:15
mriedemso the only way to really restrict everything would be to put extra specs on all of your flavors21:15
mriedemi think21:15
*** awaugama has joined #openstack-nova21:16
*** dave-mccowan has joined #openstack-nova21:16
melwitthttps://review.openstack.org/#/c/241016/ was where it got added21:17
*** READ10 has quit IRC21:17
mriedemcrazy yahoo people21:17
melwittyeah, I think you're right. I'm trying to see if the review and/or bug mention how that's supposed to be okay21:17
melwittheh21:18
*** vladikr has quit IRC21:18
*** dane-fichter has quit IRC21:19
melwittI guess, if the flavor has no extra_specs at all, it's like saying "this is okay anywhere"21:20
openstackgerritMatt Riedemann proposed openstack/nova master: nova-net: remove get_instance_nw_info from API subclass  https://review.openstack.org/45333621:20
mriedemyeah21:20
melwittlike, this flavor is okay to be anywhere because it has no special requirements21:20
mriedemeven if it might land on a host that can't support it21:20
mriedemthe flavor might not have requirements, but the host might21:20
melwittwell, if it has support requirements, it would have an extra_specs of some kind, no?21:21
melwittoh21:21
mriedemthis is for the scaleio ephemeral backend spec,21:21
mriedemwhich requires that root_gb on the flavor be in multiples of 821:21
mriedemin a mixed compute environment, you'd have flavors with extra specs that fit that and have an extra spec to hit those scaleio host aggregates,21:21
mriedemi'm trying to figure out how you get non-specific flavors for scaleio to *not* land on those host aggregates21:22
melwittI see21:22
*** cdent has quit IRC21:22
mriedemin reality anyone using this is probably using all scaleio all the time everywhere b/c they are buying a converged architecture product from EMC21:22
mriedemand using anything else voids their support contract with EMC :)21:23
melwitt:)21:23
openstackgerritEmilien Macchi proposed openstack/nova master: Add sem-ver flag so pbr generates correct version  https://review.openstack.org/45333821:23
EmilienMmriedem: ^ is it something you would accept?21:24
mriedemEmilienM: is there supposed to be a code change with that?21:24
EmilienMmriedem: nope21:24
EmilienMmriedem: https://github.com/openstack/ironic/blob/master/doc/source/dev/releasing.rst#things-to-do-before-releasing21:25
EmilienMthe semver thing is just in the commit message21:25
EmilienM"sem-ver: feature" bumps Y21:26
EmilienM"sem-ver: api-break" bumps X21:26
EmilienM(if your version is X.Y)21:26
mriedembut pike is 16.0.021:26
mriedemocata was 15.0.021:26
mriedemnewton is 14.0.021:27
mriedemetc21:27
EmilienMok so we need to bump X I guess21:27
mriedemdidn't this used to all be handled in setup.cfg?21:28
openstackgerritEmilien Macchi proposed openstack/nova master: Add sem-ver flag so pbr generates correct version  https://review.openstack.org/45333821:28
mriedemwe also have tags in the release repo21:28
EmilienMthis thing helps us to update packages without the tag21:28
EmilienMso our tooling can find out there is a new version from pbr21:29
*** Guest63262 has quit IRC21:29
EmilienMafik historically nova was releasing only X.0.Z++21:29
mriedemgenerally yes21:30
mriedemi think we've bumped a minor version on a stable branch when we had to pull in a new dependency21:30
mriedemor bump a minimum dependent package version for a security fix, something like that21:30
mriedemand you're only doing this for nova and ironic?21:31
EmilienMI'm going to do it for all projects21:31
*** edmondsw has quit IRC21:31
EmilienMso tripleo CI can start testing upgrades21:32
EmilienMI need to leave irc now, feel free to comment or push over the patch21:32
EmilienMI'll catch-up later21:32
*** rfolco has quit IRC21:33
*** edmondsw has joined #openstack-nova21:33
*** Guest63262 has joined #openstack-nova21:33
*** jamesdenton has quit IRC21:34
edleafecharge/.21:34
*** david-lyle has quit IRC21:35
*** peter-hamilton has quit IRC21:35
*** jamesdenton has joined #openstack-nova21:37
*** edmondsw has quit IRC21:38
*** jamesdenton has quit IRC21:39
mriedemso reading https://docs.openstack.org/developer/pbr/#version we do postversioning since we don't have version in setup.cfg,21:40
mriedemwhen pbr walks the git tree it finds the last tag, which is 15.0.221:40
mriedemand gives some dev version after that i assume21:40
mriedemA missing Sem-Ver line is equivalent to Sem-Ver: bugfix. The bugfix symbol causes a patch level increment to the version.21:41
mriedemso i guess you'd get 15.0.3 actually21:41
mriedemand because we're in pike, that's wrong b/c pike should be 16.0.021:41
*** dimtruck is now known as zz_dimtruck21:41
*** annegentle has quit IRC21:43
*** david-lyle has joined #openstack-nova21:43
openstackgerritMatt Riedemann proposed openstack/nova master: docs: update description for AggregateInstanceExtraSpecsFilter  https://review.openstack.org/45334921:44
*** annegentle has joined #openstack-nova21:44
*** annegentle has quit IRC21:45
mriedemmelwitt: so maybe if you have a mixed compute env,21:49
mriedemyou have to put all of the hosts into aggregates,21:49
mriedemone for scaleio-specific, and one for non-scaleio specific,21:49
mriedemand then all of your flavors have to have extra specs that tie them to either of the aggregates21:49
mriedemthat seems like the only way around it21:50
*** artom has quit IRC21:53
*** artom has joined #openstack-nova21:54
*** smatzek has joined #openstack-nova21:58
*** esberglu has quit IRC21:58
*** thorst has quit IRC22:01
*** felipemonteiro has quit IRC22:02
*** Sukhdev has joined #openstack-nova22:03
*** mdrabe has quit IRC22:03
mriedemmelwitt: jaypipes: dansmith: i'm +2 on https://review.openstack.org/#/c/453030/ - the rest api impact section could call out the need for a microversion bump, but that could be done in a follow up, or just implied22:03
dansmithI haven't had a chance to look at it yet22:04
*** Apoorva_ has quit IRC22:04
*** eharney has quit IRC22:04
*** Apoorva has joined #openstack-nova22:04
*** priteau has quit IRC22:04
*** mnestratov has quit IRC22:05
*** zz_dimtruck is now known as dimtruck22:08
edleafecharge/.charge/.22:09
edleafestupid vm windows22:09
*** smatzek has quit IRC22:12
*** esberglu has joined #openstack-nova22:13
openstackgerritSarafraj Singh proposed openstack/nova-specs master: Spec to add per instance timeout for LM  https://review.openstack.org/44280922:17
melwittmriedem: yeah, agreed. the only other thing I thought of is if we added a near copy of the AggregateInstanceExtraSpecsFilter that _doesn't_ do the empty extra_specs pass thing and operators would have to choose either/or, depending on the behavior desired22:19
mriedemdansmith: i could use some input on this remove bdm device from api spec too, since it's getting caught up in some legacy kerfuffle https://review.openstack.org/#/c/452546/22:22
mriedemnet is bfv with image bdm overrides f'cks it all up22:23
*** eharney has joined #openstack-nova22:23
*** baoli has quit IRC22:23
mriedembut, we could remove device from volume attach api i think since that doesn't have the image bdm over bfv mess22:23
dansmithoh I thought this was the one john had commented on,22:23
dansmithbut this is different22:24
mriedemthere was never a spec for this,22:24
mriedemwe've talked about it a billion times22:24
mriedemand i thought someone was going to write a spec, but didn't, so i posted to the ML over the weekend and wrote a spec,22:24
mriedemto which ftersin pointed out this legacy hack for ec222:24
dansmithyeah22:25
mriedemartom: do you know if, off the top of your head, we snapshot a volume backed instance that has bdm tags, do the bdm tags also go into the block_device_mapping_v2 image metadata?22:25
mriedemso that when you boot a new server from that snapshot image, it does bfv with a tagged bdm?22:25
*** lucasxu has quit IRC22:27
dansmithguh what a mess22:30
mriedemheh yeah totally22:31
dansmithso I was thinking what mdbooth said before I got down and saw his comment,22:31
dansmithbut your reply doesn't make sense to me22:32
dansmithI think his point is to just leave device_name in the api, but make it clear in all the docs that it is in no way related to the block device name in the guest22:32
dansmithmeaning, change the docs and examples to something like "disk1" and such22:32
mriedemi meant rather than correlate on device_name, we correlate on tag22:34
mriedemwe do actually set a device_name in the bdm based on what libvirt calculates it to be22:35
dansmithwe overwrite what the user gave us?22:35
mriedemso i think having something in the api that says this volume is attached at /dev/vdb but it's actually not, is part of the problem, and why we wanted to remove it22:35
mriedemdansmith: yes22:35
mriedemthe libvirt driver completely ignores what the user specified22:35
mriedemsince liberty22:35
*** awaugama has quit IRC22:35
mriedemas noted in the spec22:35
dansmithbut libvirt doesn't know what it is in the guest22:36
*** eharney has quit IRC22:36
dansmithit knows that it thinks it will be vdb in the guest based on where it got attached, but the guest chooses that22:36
mriedemthen why do we even call https://review.openstack.org/#/c/189632/10/nova/virt/libvirt/driver.py@6802 ?22:36
mriedemi guess because we need to have *something* in the bdm table b/c it's used for a shitty primary key22:37
dansmithto populate that field with something semi recognizeable, I guess22:37
dansmithbut it's definitely not the right thing even in that case22:37
mriedemok22:38
mriedemso we could just throw a uuid in bdm.device_name22:38
dansmithas you say we _could_ do away with all of this and use the tag for sure22:38
mriedemand it wouldn't matter22:38
dansmithright, we could22:38
dansmithbut the least amount of change would be to just be more ambiguous about what "device name" is I think22:39
dansmithalthough we should ask a xenapi person,22:39
dansmithas in xen it does actually match22:39
dansmithor can, or did, or whatever22:39
*** nic has left #openstack-nova22:39
*** nic has joined #openstack-nova22:39
dansmithand libvirt with xen may try to make it match, I have no idea22:39
mriedemthe least amount of change will be for me to just abandon the spec :)22:40
dansmithhah22:40
mriedemif the only thing we care about is this dumb image bdm override use case, wouldn't it be incrementally better to at least remove device from the attach volume api?22:40
*** tommylikehu_ has joined #openstack-nova22:40
mriedemor is that not even worth it?22:40
dansmithit didn't seem clear to me that this wasn't also a problem for ec2 in that api,22:41
dansmithbut I have a hard time understanding his words22:41
dansmithbut yeah, if he doesn't care about that, it'd be worth doing I think22:42
mriedemyeah i have a hard time following what the ec2api is doing or not22:42
mriedemi do'nt know if it's merging the bdms before we hit the compute api or what22:42
dansmithyeah I dunno22:42
mriedemand i'll be god damned if i'm going to go code spelunking22:42
*** hoonetorg has quit IRC22:43
*** hoonetorg has joined #openstack-nova22:44
*** esberglu has quit IRC22:45
*** hoonetorg has quit IRC22:47
*** Guest63262 has quit IRC22:48
mriedemartom: found the answer to my question, we don't include bdm tags in snapshots22:51
mriedemhttps://github.com/openstack/nova/blob/master/nova/block_device.py#L29022:51
mriedemwe'd have to add it to copy_from_template22:51
mriedemwould one expect a new server created from the image snapshot with the volume snapshot bdm to have the original bdm tag? i don't know. does anyone care? probably not.22:52
*** catintheroof has quit IRC22:57
*** tommylikehu_ has quit IRC22:57
*** hoonetorg has joined #openstack-nova22:58
*** Guest63262 has joined #openstack-nova22:59
*** thorst has joined #openstack-nova23:01
*** lyan has quit IRC23:06
*** thorst has quit IRC23:06
openstackgerritSujitha proposed openstack/nova master: Add sync_instances action in os-cells API  https://review.openstack.org/45336623:06
*** suresh12 has quit IRC23:21
artommriedem, always happy to have things work out in my absence;)23:28
*** chyka has quit IRC23:29
*** dillaman has quit IRC23:30
*** mlavalle has quit IRC23:32
*** dimtruck is now known as zz_dimtruck23:35
*** suresh12 has joined #openstack-nova23:36
openstackgerritSujitha proposed openstack/nova master: Add BDM to InstancePayload  https://review.openstack.org/44877923:37
*** mtanino has quit IRC23:39
*** zz_dimtruck is now known as dimtruck23:46
*** ducttape_ has quit IRC23:46
*** ducttape_ has joined #openstack-nova23:46
*** dillaman has joined #openstack-nova23:47
*** ducttape_ has quit IRC23:48
*** ducttape_ has joined #openstack-nova23:48
*** jianghuaw has quit IRC23:48
*** Swami has quit IRC23:49
*** _ducttape_ has joined #openstack-nova23:50
*** ducttape_ has quit IRC23:50

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