Tuesday, 2017-04-11

*** gcb has quit IRC00:03
*** awaugama has joined #openstack-nova00:07
*** artom has quit IRC00:10
*** artom has joined #openstack-nova00:11
*** artom has quit IRC00:12
*** mvk has quit IRC00:12
*** artom has joined #openstack-nova00:12
openstackgerritDan Peschman proposed openstack/nova master: Add uuid to Service model  https://review.openstack.org/45302500:13
*** crushil has quit IRC00:17
*** catintheroof has quit IRC00:19
*** amotoki has joined #openstack-nova00:20
*** MasterOfBugs has quit IRC00:22
*** pramodrj07 has quit IRC00:23
*** mtanino_ has joined #openstack-nova00:23
*** mvk has joined #openstack-nova00:25
*** mtanino has quit IRC00:25
*** iceyao has joined #openstack-nova00:26
*** cdelatte has joined #openstack-nova00:30
*** cdelatte has quit IRC00:30
*** mvk has quit IRC00:34
*** mvk has joined #openstack-nova00:34
*** hongbin has quit IRC00:36
*** phuongnh has joined #openstack-nova00:42
*** yamahata has joined #openstack-nova00:43
*** dtp has quit IRC00:44
*** crushil has joined #openstack-nova00:47
*** baoli has joined #openstack-nova00:48
*** baoli has quit IRC00:49
*** ssurana has quit IRC00:50
*** baoli has joined #openstack-nova00:50
*** mvk has quit IRC00:51
*** kaisers has joined #openstack-nova00:52
*** zhurong has joined #openstack-nova00:54
*** kaisers has quit IRC00:57
*** mdrabe has quit IRC00:57
*** Apoorva_ has joined #openstack-nova01:02
*** cNilesh has joined #openstack-nova01:02
*** cNilesh has quit IRC01:03
*** cNilesh has joined #openstack-nova01:03
*** mvk has joined #openstack-nova01:03
*** gyee has quit IRC01:04
*** Apoorva has quit IRC01:06
*** Apoorva_ has quit IRC01:06
*** mvk has quit IRC01:10
*** mvk has joined #openstack-nova01:10
*** gcb has joined #openstack-nova01:16
*** tovin07_ has joined #openstack-nova01:20
*** thorst has quit IRC01:30
*** thorst has joined #openstack-nova01:30
*** Sukhdev has quit IRC01:33
*** thorst has quit IRC01:34
*** NikhilS has joined #openstack-nova01:35
*** edmondsw has joined #openstack-nova01:39
*** edmondsw has quit IRC01:43
*** awaugama has quit IRC01:54
*** dixiaoli has joined #openstack-nova01:54
*** dixiaoli has quit IRC01:58
*** esberglu has joined #openstack-nova01:58
*** nic has quit IRC02:00
*** dixiaoli has joined #openstack-nova02:02
*** esberglu has quit IRC02:03
*** yonglihe has joined #openstack-nova02:03
openstackgerritAlex Xu proposed openstack/nova-specs master: Deprecate multinic proxy API  https://review.openstack.org/38426102:06
alex_xumriedem: ^ updated02:06
*** nic has joined #openstack-nova02:09
*** mtanino_ has quit IRC02:11
openstackgerritAlex Xu proposed openstack/nova master: placement: Add Traits API to placement service  https://review.openstack.org/37620002:12
*** nic has quit IRC02:12
*** tuanluong has joined #openstack-nova02:15
*** catintheroof has joined #openstack-nova02:16
*** kevinz has joined #openstack-nova02:26
*** hongbin has joined #openstack-nova02:26
*** thorst has joined #openstack-nova02:31
*** fragatina has joined #openstack-nova02:34
*** catintheroof has quit IRC02:34
*** diga has joined #openstack-nova02:34
*** catintheroof has joined #openstack-nova02:35
*** fragatin_ has quit IRC02:37
*** iceyao has quit IRC02:37
*** fragatina has quit IRC02:38
*** catintheroof has quit IRC02:40
openstackgerritSpencer Yu proposed openstack/python-novaclient master: Nova client should retry with Retry-After value  https://review.openstack.org/44776602:40
*** fragatina has joined #openstack-nova02:41
*** fragatina has quit IRC02:42
*** diga has quit IRC02:48
*** diga has joined #openstack-nova02:49
*** thorst has quit IRC02:51
*** iceyao has joined #openstack-nova02:55
*** Shunli has joined #openstack-nova02:55
*** iceyao has quit IRC02:59
*** armax has joined #openstack-nova03:00
*** dixiaoli has quit IRC03:00
*** dixiaoli has joined #openstack-nova03:01
*** iceyao has joined #openstack-nova03:03
*** diga has quit IRC03:03
*** diga has joined #openstack-nova03:10
*** nicolasbock has quit IRC03:10
*** chyka has quit IRC03:14
mriedemalex_xu: thanks, a couple of small things were missed03:18
mriedembut overall should be easy to fix and then i'm +203:18
openstackgerritGhanshyam Mann proposed openstack/nova master: Fix api-ref for create servers response  https://review.openstack.org/45167303:20
mriedemtommylikehu: re https://review.openstack.org/#/c/453272/3/specs/pike/approved/nova-support-attached-volume-extend.rst@26 nova does not yet support volume multiattach upstream03:25
mriedemso a VM is correct there03:25
*** sridharg has joined #openstack-nova03:26
*** amotoki has quit IRC03:26
tommylikehumriedem: thanks03:27
*** crushil has quit IRC03:32
*** dimtruck is now known as zz_dimtruck03:38
*** tbachman has quit IRC03:38
openstackgerritBob Ball proposed openstack/nova master: XenAPI: device tagging  https://review.openstack.org/33378103:39
*** amotoki has joined #openstack-nova03:40
mriedemtommylikehu: mgagne: comments inline https://review.openstack.org/#/c/453272/303:41
*** esberglu has joined #openstack-nova03:47
*** iceyao has quit IRC03:49
*** amotoki has quit IRC03:50
*** gouthamr has quit IRC03:51
*** esberglu has quit IRC03:52
*** kaisers has joined #openstack-nova03:54
tommylikehumriedem: great, thanks!03:55
*** mriedem has quit IRC03:56
*** amotoki has joined #openstack-nova03:58
*** diga has quit IRC03:58
*** kaisers has quit IRC03:58
*** vks1 has joined #openstack-nova04:00
*** kaisers has joined #openstack-nova04:00
*** kaisers has quit IRC04:03
*** abhi89 has joined #openstack-nova04:03
*** kaisers has joined #openstack-nova04:04
*** chyka has joined #openstack-nova04:06
*** Dinesh_Bhor has quit IRC04:07
*** fragatina has joined #openstack-nova04:09
*** yamamoto_ has quit IRC04:09
*** kaisers has quit IRC04:09
*** markvoelker has quit IRC04:09
*** yamamoto has joined #openstack-nova04:09
*** chyka has quit IRC04:11
*** hongbin has quit IRC04:12
*** awaugama has joined #openstack-nova04:12
*** fragatina has quit IRC04:13
*** iceyao has joined #openstack-nova04:13
*** amotoki has quit IRC04:13
*** Sukhdev has joined #openstack-nova04:14
*** baoli has quit IRC04:14
*** trinaths has joined #openstack-nova04:16
*** yamahata has quit IRC04:17
*** dixiaoli has quit IRC04:17
*** dixiaoli has joined #openstack-nova04:19
*** dixiaoli has quit IRC04:23
*** dharinic has quit IRC04:27
*** vks1 has quit IRC04:28
*** amotoki has joined #openstack-nova04:29
*** psachin has joined #openstack-nova04:31
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend  https://review.openstack.org/45327204:35
*** fragatina has joined #openstack-nova04:37
*** diga has joined #openstack-nova04:37
*** fragatina has quit IRC04:37
*** fragatina has joined #openstack-nova04:38
*** vks1 has joined #openstack-nova04:42
*** diga has quit IRC04:44
*** ayogi has joined #openstack-nova04:46
*** thorst has joined #openstack-nova04:48
*** thorst has quit IRC04:52
*** iceyao has quit IRC04:57
*** awaugama has quit IRC05:02
*** kaisers has joined #openstack-nova05:05
*** kaisers has quit IRC05:09
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend  https://review.openstack.org/45327205:10
*** Dinesh_Bhor has joined #openstack-nova05:11
*** Sukhdev has quit IRC05:12
*** iceyao has joined #openstack-nova05:15
*** rcernin has joined #openstack-nova05:15
*** Jack_Iv has joined #openstack-nova05:16
*** iceyao has quit IRC05:20
*** udesale has joined #openstack-nova05:20
*** prateek has joined #openstack-nova05:20
*** Jack_Iv has quit IRC05:21
*** dixiaoli has joined #openstack-nova05:26
*** mdnadeem has joined #openstack-nova05:26
*** prateek has quit IRC05:29
*** prateek has joined #openstack-nova05:29
*** abhi89 has quit IRC05:29
*** abhi89 has joined #openstack-nova05:30
*** tuanluong has quit IRC05:33
*** psachin has quit IRC05:34
*** esberglu has joined #openstack-nova05:37
*** esberglu has quit IRC05:41
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend  https://review.openstack.org/45327205:42
*** adisky_ has joined #openstack-nova05:44
*** fragatina has quit IRC05:44
*** spotz is now known as spotz_zzz05:46
*** thorst has joined #openstack-nova05:48
*** spotz_zzz is now known as spotz05:48
openstackgerritAlex Xu proposed openstack/nova-specs master: Deprecate multinic proxy API  https://review.openstack.org/38426105:51
*** sridharg has quit IRC05:51
*** Jack_Iv has joined #openstack-nova05:52
*** thorst has quit IRC05:53
*** jaosorior_away is now known as jaosorior05:55
*** tuanluong has joined #openstack-nova05:58
*** chyka has joined #openstack-nova06:01
*** iceyao has joined #openstack-nova06:01
*** markus_z has joined #openstack-nova06:04
*** chyka has quit IRC06:05
*** kaisers has joined #openstack-nova06:06
openstackgerritLei Zhang proposed openstack/nova master: Add sync traits command for placement  https://review.openstack.org/45012506:07
*** vks1 has quit IRC06:08
*** nirendra has joined #openstack-nova06:12
*** nirendra has left #openstack-nova06:13
*** mkoderer_ has joined #openstack-nova06:13
*** Oku_OS-away is now known as Oku_OS06:13
*** nirendra has joined #openstack-nova06:14
*** mkoderer_ has quit IRC06:15
*** satyar has joined #openstack-nova06:15
nirendraHi, Nova placement API checks for max_units which is local_gb for the host. This makes allocation_ratio useless. So if I'm trying to create a VM with 80GB root disk and disk_allocation_ratio as 100, it fails for a host which does not have 80GB local storage06:16
nirendraIs this a known bug? I couldn't find one in Launchpad06:16
*** andreas_s has joined #openstack-nova06:18
*** iceyao has quit IRC06:23
*** Jack_Iv has quit IRC06:24
*** Jack_Iv has joined #openstack-nova06:24
*** voelzmo has joined #openstack-nova06:26
*** vks1 has joined #openstack-nova06:27
*** Jack_Iv has quit IRC06:29
*** avolkov has joined #openstack-nova06:30
*** psachin has joined #openstack-nova06:31
*** Jack_Iv has joined #openstack-nova06:32
*** ltomasbo|away is now known as ltomasbo06:41
*** nirendra has quit IRC06:41
*** trinaths has quit IRC06:41
*** tesseract has joined #openstack-nova06:47
*** iceyao has joined #openstack-nova06:47
*** thorst has joined #openstack-nova06:49
*** mgagne has quit IRC06:52
*** iceyao has quit IRC06:52
*** Jack_Iv has quit IRC06:53
*** Jack_Iv has joined #openstack-nova06:54
*** thorst has quit IRC06:54
*** Jack_Iv has quit IRC06:55
*** Jack_Iv has joined #openstack-nova06:56
*** Jack_Iv has quit IRC06:56
*** Jack_Iv has joined #openstack-nova06:56
*** chyka has joined #openstack-nova07:01
*** sridharg has joined #openstack-nova07:05
*** chyka has quit IRC07:06
*** pcaruana has joined #openstack-nova07:06
*** garyk1 has quit IRC07:10
openstackgerritYuYang proposed openstack/nova master: VMware:fix get VM root device conditional verify  https://review.openstack.org/45444107:16
*** karimb has joined #openstack-nova07:17
*** xinliang has quit IRC07:19
*** Jack_Iv has quit IRC07:19
*** Jack_Iv_ has joined #openstack-nova07:20
*** Jack_Iv_ has quit IRC07:20
openstackgerritYuYang proposed openstack/nova master: VMware:fix get VM root device conditional verify  https://review.openstack.org/45444107:20
*** Jack_Iv has joined #openstack-nova07:20
*** Jack_Iv has quit IRC07:21
*** Jack_Iv has joined #openstack-nova07:21
*** chenying has joined #openstack-nova07:22
*** garyk has joined #openstack-nova07:23
*** hieulq has quit IRC07:27
*** garyk has quit IRC07:27
*** hieulq has joined #openstack-nova07:27
*** hieulq has quit IRC07:29
*** hieulq has joined #openstack-nova07:29
*** hieulq has quit IRC07:29
*** garyk has joined #openstack-nova07:29
*** hieulq has joined #openstack-nova07:29
*** hieulq is now known as Guest3322007:30
*** hieulq_ has joined #openstack-nova07:30
*** trinaths has joined #openstack-nova07:30
*** garyk has quit IRC07:30
*** hieulq_ has quit IRC07:30
*** hferenc has quit IRC07:31
*** xinliang has joined #openstack-nova07:32
*** garyk has joined #openstack-nova07:33
*** hferenc has joined #openstack-nova07:33
*** garyk has quit IRC07:33
*** Jack_Iv has quit IRC07:36
*** Jack_Iv has joined #openstack-nova07:37
*** karimb has quit IRC07:39
*** hieulq_ has joined #openstack-nova07:41
*** aarefiev_afk is now known as aarefiev07:41
*** Jack_Iv has quit IRC07:41
*** mlakat has quit IRC07:46
*** rpodolyaka_afk is now known as rpodolyaka07:47
*** alexpilotti has quit IRC07:47
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (1/4)  https://review.openstack.org/45556307:49
*** thorst has joined #openstack-nova07:50
*** mlakat has joined #openstack-nova07:51
*** frickler has quit IRC07:51
openstackgerritZhenyu Zheng proposed openstack/nova master: Fix HTTP 500 raised for getColsolelog for stopped instance  https://review.openstack.org/45518307:52
*** frickler has joined #openstack-nova07:52
*** derekh has joined #openstack-nova07:54
*** Jack_Iv has joined #openstack-nova07:54
*** hieulq_ has quit IRC07:54
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (2/4)  https://review.openstack.org/45556807:55
*** hieulq_ has joined #openstack-nova07:56
*** zzzeek has quit IRC08:00
*** zzzeek has joined #openstack-nova08:00
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (3/4)  https://review.openstack.org/45557008:00
*** hieulq_ has quit IRC08:01
*** chyka has joined #openstack-nova08:02
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (4/4)  https://review.openstack.org/45557308:04
*** lucas-afk is now known as lucasagomes08:06
*** chyka has quit IRC08:07
*** takashin has left #openstack-nova08:09
*** thorst has quit IRC08:09
*** karimb has joined #openstack-nova08:11
*** efoley_ has joined #openstack-nova08:18
*** ralonsoh has joined #openstack-nova08:20
*** efoley__ has joined #openstack-nova08:21
*** Kevin_Zheng has quit IRC08:23
*** efoley_ has quit IRC08:24
*** priteau has joined #openstack-nova08:27
*** haplo37_ has quit IRC08:30
*** gszasz has joined #openstack-nova08:38
*** haplo37 has quit IRC08:40
*** rmart04 has joined #openstack-nova08:43
*** Jack_Iv has quit IRC08:46
*** Jack_Iv has joined #openstack-nova08:49
*** Jack_Iv has quit IRC08:49
*** Jack_Iv has joined #openstack-nova08:49
*** iceyao has joined #openstack-nova08:50
*** kaisers has quit IRC08:50
*** karimb has quit IRC08:53
*** haplo37 has joined #openstack-nova08:54
*** iceyao has quit IRC08:54
*** haplo37_ has joined #openstack-nova08:54
*** voelzmo has quit IRC09:00
*** voelzmo has joined #openstack-nova09:02
*** cdent has joined #openstack-nova09:02
d9kwhen instance is destroyed neutron deletes ipsets while nova is modifying iptables and https://ptpb.pw/16S8 happens, acquiring neutron-ipset lock in (network/linux_net.py) IptablesManager._apply seems to fix the problem09:03
*** openstackgerrit has quit IRC09:03
*** karimb has joined #openstack-nova09:03
*** lpetrut has joined #openstack-nova09:04
*** ociuhandu has quit IRC09:05
*** thorst has joined #openstack-nova09:06
*** abalutoiu has quit IRC09:08
*** thorst has quit IRC09:11
*** jsheeren has joined #openstack-nova09:14
*** esberglu has joined #openstack-nova09:14
jsheerenhi, question: is it possible to limit image A to be only able to use flavor X and Y, image B only flavor Z?09:15
*** esberglu has quit IRC09:19
*** abhi89 has quit IRC09:19
*** abhi89 has joined #openstack-nova09:20
*** sambetts|afk is now known as sambetts09:26
*** prabhuraj has joined #openstack-nova09:27
prabhurajHi team, Someone could review the following changes :09:28
prabhurajhttps://review.openstack.org/#/c/397471/09:28
prabhurajhttps://review.openstack.org/#/c/397459/09:29
*** BobBall has joined #openstack-nova09:37
BobBallHowdy - Trying to use device tagging I'm getting an "Invalid input for field/attribute networks" - nova cli says I need to use ",tag=<value>" but schema validation fails if I add it.  Openstack cli doesn't seem to support tags (According to help text anyway)...09:40
BobBallCan someone remind me how to use tagging?09:40
johnthetubaguyopenstack cli doesn't support microversions yet09:41
johnthetubaguyafaik09:41
johnthetubaguydid you try with nova client?09:42
BobBallYes - that's what failed the schema validation when running it09:42
BobBallhttp://paste.openstack.org/show/606121/ - I'm clearly using the wrong syntax09:44
*** naichuans has joined #openstack-nova09:44
BobBall(or device tagging is broken...)09:45
*** kaisers has joined #openstack-nova09:46
*** belmoreira has joined #openstack-nova09:47
abhi89johnthetubaguy: can you please review https://review.openstack.org/#/c/455118/209:49
*** prabhuraj has quit IRC09:49
*** ishant has joined #openstack-nova09:54
*** tovin07_ has quit IRC09:55
*** ociuhandu has joined #openstack-nova09:57
*** tbachman has joined #openstack-nova09:57
johnthetubaguyBobBall: that doesn't seem good09:58
BobBallOK - so the nova client does not now support nova microversion 2.42 - for some reason 7.1.0 was installed09:58
BobBallit's just weird that novaclient 7.1.0 lists tag in the help text but doesn't support the microversion which introduced the API09:59
johnthetubaguyBobBall: try do the full debug and see what version is requested09:59
johnthetubaguyyeah, thats... inconsistent09:59
johnthetubaguyprobably only got some of the patches landed09:59
BobBallnova client is requesting 2.41 - which doesn't support tagging... *jumps with joy*09:59
johnthetubaguyBobBall: did you try explicitly request the new version, it might be we couldn't raise the maximum at that point09:59
BobBallYes - python-novaclient says it's not supported.10:00
johnthetubaguynot 100% sure thats a thing10:00
johnthetubaguyha10:00
johnthetubaguyabhi89: I think this might be the code you need to change for your bug: https://github.com/openstack/nova/blob/3092d2adcb6bab0bf39b01ea0561ec7e6a3990fd/nova/compute/manager.py#L158510:00
*** karimb has quit IRC10:01
Dinesh_Bhorsfinucan: Hi, addressed your review comments. Already got one +2 please take a look at it whenever you are free: https://review.openstack.org/#/c/364687/10:01
sfinucanDinesh_Bhor: Will do10:01
Dinesh_Bhorsfinucan: thanks10:01
*** tuanluong_ has joined #openstack-nova10:02
*** tuanluong has quit IRC10:05
ishantHi All, I am creating instance and it always sets availability_zone as None even though default_availability_zone value is 'nova'10:05
ishantbeacuse of this port device_owner is always set as compute:None10:06
BobBallEven the latest python-novaclient does not support the required API micro version!!! http://git.openstack.org/cgit/openstack/python-novaclient/tree/novaclient/__init__.py10:06
BobBallIn other words, I think no one can use python-novaclient to specify device tagging at all.10:06
*** NikhilS has quit IRC10:07
*** karimb has joined #openstack-nova10:09
*** zhurong has quit IRC10:10
*** zhurong has joined #openstack-nova10:11
*** chyka has joined #openstack-nova10:14
sfinucanralonsoh: You around. Question on https://review.openstack.org/#/c/444415 for you10:15
*** cNilesh has quit IRC10:16
ralonsohsfinucan: hi!10:16
sfinucanralonsoh: How come we're using the 'extra_info' column in that review rather than adding a new capabilities column?10:18
sfinucanI didn't even question it until you said that nothing else was using the column now. If it was important enough to move out the other stuff, why re-add new stufF?10:18
ralonsohsfinucan: that is the easy way, to add a new field10:19
*** chyka has quit IRC10:19
ralonsohsfinucan: instead of this, we decided not to modify the DB schema and add this information into extra_info10:20
*** zsli_ has joined #openstack-nova10:20
ralonsohsfinucan: extra_info is initially a bucket for "other" information, not so relevant10:20
sfinucanralonsoh: OK. What's the long term strategy then? Drop that entire table in favour of resource providers?10:22
*** openstackgerrit has joined #openstack-nova10:22
openstackgerritStephen Finucane proposed openstack/nova master: Add description to policies in hypervisors.py  https://review.openstack.org/45129410:22
ralonsohsfinucan: yes, move every item (network:capabilities, etc) to resource providers10:22
ralonsohsfinucan: this migration will modify a small part of this feature10:23
ralonsohsfinucan: and should be fast to implement10:23
*** Shunli has quit IRC10:23
openstackgerritSylvain Bauza proposed openstack/nova-specs master: Proposed block accepting AZ renames  https://review.openstack.org/44644610:24
sfinucanralonsoh: Oh yeah - I agree with doing it this way. Just making sure I've the big picture right in my head first :)10:24
abhi89johnthetubaguy: at https://github.com/openstack/nova/blob/5a6d4e089dca2515c0f7e083a8b903ac7a166773/nova/volume/cinder.py#L202, after catching the OverLimit exception, we are raising OverQuota exception with overs='volumes'. But here the overs could have been volumes, gigabytes or per_volume_gigabytes. In each case there would be different error messages specific to the quota exceeded10:24
ralonsohsfinucan: sure! this is the last working point of the spec, but I'll do it10:24
*** nicolasbock has joined #openstack-nova10:24
johnthetubaguyabhi89: I agree with you, it just the fix is in a different place to your current patch10:25
sfinucanralonsoh: Ok, thanks for the info. I'm going to add a few points about including context comments (so people can understand what's going on) but that looks good to me otherwise10:25
ralonsohsfinucan: thanks!10:25
*** trinaths has left #openstack-nova10:27
*** satyar has quit IRC10:27
BobBalljohnthetubaguy / artom: Found the problem - it's relating to Ia0869dc6f7f5bd347ccbd0930d1d668d37695a22 (device tag disappearing) - because nova re-added the device tag in the 2.42 version but novaclient doesn't support that version, we have no way of using device tagging currently.10:28
jsheerenanyone know if it is possible to limit image A to be only able to use flavor X and Y, image B only flavor Z?10:28
johnthetubaguyBobBall: oh I forgot about that being for tags10:28
BobBallNot sure what the fix is currently -I did try hacking novaclient but it still can't cope with device tags for block devices...10:29
johnthetubaguyjsheeren: there are various image properties that can help for specific requirements, not sure there is a blanket only flavor X thing.10:29
johnthetubaguyBobBall: can't you raise the max supported API version up to 2.42?10:29
*** haplo37_ has quit IRC10:31
BobBallworks for nics but not for block devices (volume_id is not recognised)10:32
johnthetubaguyBobBall: I am curious what the API tests are doing, I don't remember the context around that stuff10:35
*** Drankis has joined #openstack-nova10:35
BobBall:P10:36
*** kevinz has quit IRC10:39
*** haplo37_ has joined #openstack-nova10:40
*** sdague has joined #openstack-nova10:42
*** kaisers has quit IRC10:48
*** Jack_Iv has quit IRC10:48
*** Jack_Iv has joined #openstack-nova11:02
*** phuongnh has quit IRC11:03
*** Jack_Iv has quit IRC11:04
*** Jack_Iv has joined #openstack-nova11:05
*** smatzek has joined #openstack-nova11:07
*** thorst has joined #openstack-nova11:08
*** alexpilotti has joined #openstack-nova11:12
*** alexpilotti has quit IRC11:12
*** prateek_ has joined #openstack-nova11:13
*** thorst has quit IRC11:13
*** prateek has quit IRC11:15
*** karimb has quit IRC11:15
*** zsli_ has quit IRC11:16
*** tbachman has quit IRC11:16
*** lucasagomes is now known as lucas-bbl11:20
*** dixiaoli has quit IRC11:21
*** dixiaoli has joined #openstack-nova11:21
*** prateek__ has joined #openstack-nova11:23
sfinucanvladikr, sahid: Could you guys take a look at some point, please? https://review.openstack.org/#/q/topic:bump-min-libvirt+status:open11:24
*** dixiaoli has quit IRC11:25
*** prateek_ has quit IRC11:26
*** alexpilotti has joined #openstack-nova11:26
*** Guest49144 has quit IRC11:30
*** ekhugen has quit IRC11:30
*** ekhugen_alt has quit IRC11:32
jsheerenjohnthetubaguy: thanks11:32
*** patriciadomin has quit IRC11:32
openstackgerritSergey Nikitin proposed openstack/nova master: Added PCI NUMA policies  https://review.openstack.org/39052011:32
vladikrsfinucan, sure. will drop off my kids to school and then11:33
*** egarbade has joined #openstack-nova11:36
*** patriciadomin has joined #openstack-nova11:37
*** egarbade is now known as Guest2619511:37
*** ekhugen has joined #openstack-nova11:37
*** ekhugen_alt has joined #openstack-nova11:37
*** venki has quit IRC11:40
*** venki has joined #openstack-nova11:41
artomBobBall, if you pin the version to 2.32 it should work for both nic and bdm tags11:43
artomUntil we merge the 2.42 novaclient change11:43
*** kaisers has joined #openstack-nova11:43
*** zz_dimtruck is now known as dimtruck11:43
*** dillaman has quit IRC11:43
*** karimb has joined #openstack-nova11:45
*** baoli has joined #openstack-nova11:47
*** thorst has joined #openstack-nova11:47
gaurangthi, I'm facing issue in the nova instance creation and it is failing with following error in nova-compute.log11:48
gaurangtFailed to create resource provider record in placement API for UUID11:48
gaurangtThe requested URL /placement/resource_providers was not found on this server11:48
gaurangtI actually added the <Directory> section in nova-placement-api.conf, but still the same issue.11:49
*** mvk has quit IRC11:49
*** Jack_Iv has quit IRC11:49
*** Jack_Iv has joined #openstack-nova11:49
gaurangtany idea what might be going wrong here?11:50
gaurangt nova-placement-api.conf looks like this -  http://paste.openstack.org/show/606143/11:50
cdentgaurangt: "/nova-placement-api" should be "/placement" in both places it shows up11:51
cdentactually the Alias is wrong in other ways too, just a sec11:51
*** baoli has quit IRC11:52
cdentgaurangt: we're you following some docs to set this up?11:53
gaurangtcdent, yes, I'm following the official OpenStack guide11:53
gaurangthttps://docs.openstack.org/ocata/install-guide-rdo/nova-controller-install.html11:53
*** Jack_Iv has quit IRC11:55
*** Jack_Iv has joined #openstack-nova11:55
cdentgaurangt: it looks like the rdo packages may be configuring apache somewhat incorrectly11:55
gaurangtcdent, oh11:56
cdentchanges the <Location ..> entry to be <Location /placement> and reload apache and see what happens11:56
gaurangtcdent, what should be the workaround here?11:56
cdentwhat I just said11:56
*** markvoelker has joined #openstack-nova11:56
gaurangtwhat about this - Alias /nova-placement-api /usr/bin/nova-placement-api?11:56
gaurangtjust above the <Location..>11:56
*** dillaman has joined #openstack-nova11:57
cdentthere too: Alias /placement /usr/bin/nova-placement-api11:57
gaurangtcdent, hmm ok11:58
gaurangtany nova service needs to be restarted?11:59
cdentno just apache11:59
gaurangtok11:59
gaurangtah, now it says - You don't have permission to access /placement/resource_providers11:59
*** karimb has quit IRC12:01
gaurangtcdent, anything still wrong?12:02
*** chyka has joined #openstack-nova12:03
*** tbachman has joined #openstack-nova12:03
*** markvoelker has quit IRC12:03
cdentmove that <Directory> section outside of the VirtualHost12:06
cdentgaurangt: ^12:06
*** nkorabli has joined #openstack-nova12:06
gaurangtcdent, ok12:06
*** chyka has quit IRC12:07
*** tuanluong_ has quit IRC12:08
*** vks1 has quit IRC12:08
*** rmart04 has quit IRC12:09
cdentgaurangt: once you get this figured out, I'd suggest you submit a bug to the rdo packagers. It seems like there might some confusion between what's being set the apache configuration and what's being set in the service catalog. Either the packages or the docs are wrong12:10
*** amotoki has quit IRC12:11
*** edmondsw has joined #openstack-nova12:12
gaurangtcdent, thanks it worked12:13
*** venki has quit IRC12:13
cdentgaurangt: ah, good, glad to hear it12:13
gaurangtcdent, I will submit a bug now12:13
cdentawesome!12:13
gaurangtcdent, thanks for the help !12:13
*** venki has joined #openstack-nova12:13
*** gouthamr has joined #openstack-nova12:14
*** iceyao has joined #openstack-nova12:15
*** lucas-bbl is now known as lucasagomes12:16
*** vladikr has quit IRC12:17
*** breton has quit IRC12:17
*** breton has joined #openstack-nova12:18
*** iceyao has quit IRC12:20
*** iceyao has joined #openstack-nova12:20
*** amotoki has joined #openstack-nova12:23
*** Jack_Iv has quit IRC12:24
*** Madasi has quit IRC12:24
*** Jack_Iv has joined #openstack-nova12:26
*** jsheeren has quit IRC12:26
*** hshiina has joined #openstack-nova12:27
*** Jack_Iv has quit IRC12:30
*** egonzalez has joined #openstack-nova12:31
*** iceyao has quit IRC12:31
*** iceyao has joined #openstack-nova12:32
*** ayogi has quit IRC12:32
*** cmurphy has left #openstack-nova12:35
*** prateek__ has quit IRC12:35
*** amotoki has quit IRC12:39
*** venki has left #openstack-nova12:40
*** vks1 has joined #openstack-nova12:41
*** iceyao_ has joined #openstack-nova12:42
*** Jack_Iv has joined #openstack-nova12:42
*** amotoki has joined #openstack-nova12:43
*** cleong has joined #openstack-nova12:44
*** scottda has joined #openstack-nova12:45
*** iceyao has quit IRC12:45
*** vks1 has quit IRC12:45
*** garyk has joined #openstack-nova12:45
*** amotoki has quit IRC12:49
egonzalezHi, it's been a recent change in master who change the behaviour in nova service-list? in current master output is empty with no service registered12:50
*** zhurong has quit IRC12:54
*** vladikr has joined #openstack-nova12:54
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (4/4)  https://review.openstack.org/45557312:59
*** Jack_Iv has quit IRC13:00
*** vks1 has joined #openstack-nova13:00
*** Jack_Iv has joined #openstack-nova13:00
*** esberglu has joined #openstack-nova13:00
*** iceyao_ has quit IRC13:00
*** chyka has joined #openstack-nova13:03
*** mriedem has joined #openstack-nova13:04
*** satyar has joined #openstack-nova13:05
*** jsheeren has joined #openstack-nova13:06
jsheerenhi again, i'm back with my question about pinning an image to a flavor13:07
jsheerenwe can set the min-disk and min-ram on the image, is there something similar with os_distro or os_type?13:07
*** mdrabe has joined #openstack-nova13:07
*** chyka has quit IRC13:08
*** bpoulos has joined #openstack-nova13:10
*** jaypipes has joined #openstack-nova13:10
*** mdrabe has quit IRC13:11
BobBallartom: Thanks but I don't think it will - nova client is rejecting the volume_id based on internal code, not checking the nova API version13:11
*** amotoki has joined #openstack-nova13:12
*** lyan has joined #openstack-nova13:13
*** jsheeren has quit IRC13:13
*** karimb has joined #openstack-nova13:13
*** garyk has quit IRC13:13
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Example verification for servers-actions.inc  https://review.openstack.org/45456513:13
*** peter-hamilton has joined #openstack-nova13:14
peter-hamiltonjohnthetubaguy: do you have a minute to discuss cert validation?13:15
*** rfolco has joined #openstack-nova13:15
*** garyk1 has joined #openstack-nova13:15
*** liverpooler has joined #openstack-nova13:18
*** Jack_Iv has quit IRC13:18
*** gabor_antal has quit IRC13:19
*** abhi89 has quit IRC13:20
*** abhishek has joined #openstack-nova13:20
*** gabor_antal has joined #openstack-nova13:20
*** dane-fichter has joined #openstack-nova13:22
*** Dinesh_Bhor has quit IRC13:22
*** bhagyashris has quit IRC13:22
andymccrcdent: are you about?13:23
cdentandymccr: hi, yes13:23
andymccrcdent: hey :) if you have a second - is there a reason why CONTENT_LENGTH has to be set to an int? https://github.com/openstack/nova/commit/6dd047a3307a1056077608fd5bc2d1c3b328533813:23
*** Dinesh_Bhor has joined #openstack-nova13:24
andymccrim having issues in that content_length is present, but empty so its failing with a valueError: https://bugs.launchpad.net/nova/+bug/168184313:24
openstackLaunchpad bug 1681843 in OpenStack Compute (nova) "Nova-placement returns "ValueError: invalid literal for int() with base 10: ''"" [Undecided,New]13:24
andymccri figure the easiest fix is just to remove the int() (which works) but wanted to make sure im not overlooking anything13:24
*** erlon has joined #openstack-nova13:24
*** bhagyashris has joined #openstack-nova13:25
*** iceyao has joined #openstack-nova13:25
cdentandymccr: need to catch up and get my brain right, just a sec13:25
andymccrcdent: no problem. lemme know if i can explain anything better/further13:25
peter-hamiltonjaypipes: do you have a sec to discuss cert validation?13:25
jaypipespeter-hamilton: here on IRC? or in a hangout or something?13:26
peter-hamiltonjaypipes: here's fine, just some quick questions13:26
jaypipespeter-hamilton: go for it.13:26
*** jianghuaw has joined #openstack-nova13:26
peter-hamiltonjaypipes: are you ok with adding two conf options, (1) to enable/disable cert validation, and (2) to provide a default list of trusted cert IDs13:27
peter-hamiltonjaypipes: the goal would be to smooth the migration path and user experience13:27
peter-hamiltonjaypipes: these were recommended by johnthetubaguy13:27
jaypipespeter-hamilton: if that smooths the integration path, I'm all for it.'13:27
peter-hamiltonjaypipes: cool, i'm folding those in13:28
jaypipesrock on brother.13:28
*** READ10 has joined #openstack-nova13:29
*** iceyao has quit IRC13:29
*** Jack_Iv has joined #openstack-nova13:30
openstackgerritAndy McCrae proposed openstack/nova master: Don't force CONTENT_LENGTH to be an int()  https://review.openstack.org/45571013:30
cdentandymccr: hmmm. that's icky behavior by nginx. what that check is trying to do is detect that there is a body with some length, without actually looking at the body, and then complain if there's no content-type header13:31
cdentso if nginx is sending both, but with empty values, neither line is correct13:31
andymccrcdent: agreed, although im confused as to why we need to force it to be an int? if there are no integer comparisons after that13:32
cdentandymccr: probably because i was being overzealous: the spec says that if the header is present it's value is made up of DIGITS13:33
*** mvk has joined #openstack-nova13:33
andymccrahh13:33
*** smatzek has quit IRC13:33
andymccrcdent: any issue with removing the int? alternatively, we could get it, check it's not None and then make sure it's an int?13:33
andymccr(or something slightly more efficient i assume)13:34
cdentso yeah, your fix is probably okay, but if you're in there, addressing nginx'isms then you probably need to fix the content-type thing too13:34
*** al498u has joined #openstack-nova13:34
*** eharney has joined #openstack-nova13:34
*** Jack_Iv has quit IRC13:35
cdenta) drop the int b) if not environ.get('CONTENT_TYPE', ''):13:35
cdentandymccr: that would get the correct behavior wouldn't it?13:35
*** Jack_Iv has joined #openstack-nova13:36
andymccrcdent: hmm thinking.13:36
andymccrcdent: how it is now worked on content_type, because i guess it is defined, so they're both defined (but empty) - trying to think if there is another use case (that isnt this) where that would cause an issue13:37
mriedemjaypipes: johnthetubaguy: sdague: at some point i need to talk with you about the os-interface response body and how we want that to look13:37
cdentandymccr: the thing we are trying to prevent here is an empty content-type13:37
cdentand I was thinking that the environ would only have the key if the header was present13:38
andymccrcdent: so when CONTENT_LENGTH is not empty, make sure CONTENT_TYPE is also not empty13:38
cdentyes13:38
andymccrohh i see what you mean13:38
andymccrok lemme fix!13:38
*** udesale has quit IRC13:40
cdentandymccr: thank you!13:40
*** ecelik has joined #openstack-nova13:40
*** ecelik has left #openstack-nova13:40
*** diana_clarke has joined #openstack-nova13:41
fricklerdid nova stop writing libvirt.xml into the instance-dir with ocata? or do I just need a specific option for it?13:42
*** Jack_Iv has quit IRC13:44
*** Jack_Iv has joined #openstack-nova13:45
*** mlavalle has joined #openstack-nova13:48
*** Jack_Iv has quit IRC13:48
*** Jack_Iv has joined #openstack-nova13:48
openstackgerritAndy McCrae proposed openstack/nova master: Don't force CONTENT_LENGTH to be an int()  https://review.openstack.org/45571013:49
*** crushil has joined #openstack-nova13:50
*** Jack_Iv has quit IRC13:50
*** Jack_Iv has joined #openstack-nova13:51
*** Jack_Iv has quit IRC13:52
*** Jack_Iv has joined #openstack-nova13:52
*** dimtruck is now known as zz_dimtruck13:53
*** lpetrut has quit IRC13:53
*** Jack_Iv has quit IRC13:54
*** Jack_Iv has joined #openstack-nova13:54
*** awaugama has joined #openstack-nova13:55
sdaguemriedem: I was looking through that this morning13:58
jaypipesmriedem: sure, just gimme a few. need to restart my workstation..13:58
*** jaypipes has quit IRC13:58
sdaguemriedem: I guess the question is, what do we think people need to do with this?13:58
*** Jack_Iv has quit IRC13:58
mriedemsdague: alex_xu: just left replies in https://review.openstack.org/#/c/455023/14:00
mriedemsdague: to list ports attached to their server14:00
*** kaisers has quit IRC14:00
mriedemsdague: same reason we have os-volume_attachments14:00
sdagueso that they can go operate on those ports in neutron?14:00
mriedemor detach a port from the server in the same api14:00
sdaguelike after they get that, what do they do with it next?14:00
*** jaypipes has joined #openstack-nova14:01
mriedemGET /os-interface - nothing attached, POST /os-interface/port_id - attach a port, GET /os-interface, see my port is attached, DELETE /os-interface/port_id - detach the port14:01
*** Jack_Iv has joined #openstack-nova14:01
jaypipesmriedem: ok, back...14:01
mriedemjaypipes: replied to comments inline14:01
johnthetubaguypeter-hamilton: thanks for taking a look at those14:01
peter-hamiltonjohnthetubaguy: not a problem14:02
mriedemalex_xu: pointed out duplication with the /ips API such that we could drop the fixed_ips and mac_addr part of os-interface14:02
*** p01nt3r75 has joined #openstack-nova14:02
peter-hamiltonjohnthetubaguy: can you provide more info on versionedobjects?14:02
mriedemwe could drop port_state since it doesn't really make sense14:02
mriedemor help14:02
peter-hamiltonjohnthetubaguy: i'm not that familiar with them14:02
mriedempeter-hamilton: https://github.com/openstack/oslo.versionedobjects14:02
sdague /ips is all super weird, and that's all in the main server doc iirc14:02
peter-hamiltonmriedem: thanks!14:02
*** smatzek has joined #openstack-nova14:02
johnthetubaguypeter-hamilton: sure thing, the rest of those instance extra entries are basically serialised versioned objects, helps with upgrades, etc, long term14:02
mriedemsdague: it is, in fact, more of /ips is in the main server doc than it is in /ips14:03
mriedemsdague: details wise14:03
peter-hamiltonjohnthetubaguy: ok, so it would just match the current convention for InstanceExtras14:03
johnthetubaguypeter-hamilton: yeah14:03
mriedempeter-hamilton: the nova objects are in https://github.com/openstack/nova/tree/master/nova/objects14:03
peter-hamiltonjohnthetubaguy: thanks14:03
mriedeminstance_extra stuff is used in https://github.com/openstack/nova/blob/master/nova/objects/instance.py14:03
*** garyk1 has quit IRC14:03
*** Jack_Iv has quit IRC14:04
peter-hamiltonjohnthetubaguy: i'm fine with making that a versionedobject then14:04
mriedemhttps://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L37214:04
peter-hamiltonjohnthetubaguy: i'm working through some updates to the spec now14:04
*** Jack_Iv has joined #openstack-nova14:04
johnthetubaguypeter-hamilton: the extra bit of detail might be here, in case that helps with context: https://github.com/openstack/nova/blob/master/nova/objects/instance.py#L71814:04
mriedemif we store something in the nova database and it's passed over rpc, it should be a versioned object14:04
peter-hamiltonjohnthetubaguy: thanks, i'll look it over14:04
johnthetubaguypeter-hamilton: sweet, will try hit that as soon as its updated14:04
johnthetubaguy+1 mriedem14:04
*** jaosorior is now known as jaosorior_away14:06
dansmithmriedem: is this docs failure known? http://logs.openstack.org/92/443292/15/check/gate-nova-docs-ubuntu-xenial/a9a4dc5/console.html14:08
dansmithseems like the kind of thing that would be wide failure14:08
mriedemdansmith: not by me14:08
dansmithokay14:08
mriedemlemme checkade logstash14:09
sdaguemriedem: I don't understand the dropping of mac address, how would you determine what guest interface is what port if you don't have that?14:09
alex_xusdague: good point~14:09
mriedemsdague: I only mentioned that b/c the /ips API also has it14:10
mriedemso maybe we remove mac from /ips and leave in os-interface14:10
sdaguedansmith: it looks like that job ran on python 3.5, which is the issue14:10
dansmithsdague: talking in infra now, it's known14:10
sdaguemriedem: well, if you have > 1 port I'm not sure how ips helps14:10
mriedemyeah http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22AttributeError%3A%20'dict_keys'%20object%20has%20no%20attribute%20'sort'%5C%22&from=7d14:10
dansmithpabelanger said they'd send out a note shortly14:11
*** lpetrut has joined #openstack-nova14:11
openstackgerritGábor Antal proposed openstack/nova master: Add json style checking for sample notifications  https://review.openstack.org/44367714:11
mriedemthe /ips api is also a bit goofed up since it keys off the network label14:11
mriedemso it's less about showing fixed/floating ips for a server and more about showing addresses for a server within a network14:12
*** markvoelker has joined #openstack-nova14:12
*** markvoelker has quit IRC14:12
*** felipemonteiro has joined #openstack-nova14:12
mriedemand of course we have /os-fixed-ips/14:13
mriedembut that's not tied to the server14:13
*** haplo37_ has quit IRC14:13
*** markvoelker has joined #openstack-nova14:13
mriedemand /os-floating-ips but that's not tied to a server either14:13
sdagueok, so, let's not go through everything that's wrong, that will just take us in loops :)14:13
mriedemright,14:13
mriedemso,14:13
sdaguehow compat are you trying to be here?14:14
mriedemcan we agree that at some point in the future, we want to expose bdm and vif tags out of the rest api?14:14
mriedemsince those are a nova-only concept14:14
mriedemwell, i guess you can set tags on ports in neutron too14:15
mriedembut you can't tag volumes in cinder, and they aren't used the same way in nova anyway14:15
sdaguehttps://etherpad.openstack.org/p/nova-os-interfaces - scratch space, because there seem like there are so many options14:16
sdagueyeh, I think tags exposed would be good14:16
*** abalutoiu has joined #openstack-nova14:16
mriedemsdague: my goal is one day expose tags for both bdms and ports in a single microversion, and i planned on exposing vif tags out of the os-interface API14:16
sdaguesure14:16
mriedemi'm totally fine with putting the os-interface response on a diet14:16
mriedemi.e. remove port_status and fixed_ips14:16
mriedemleave port_id, net_id, and mac_addr14:16
sdagueso, the real question I wonder is if we are making enough change to those, if we change the resource url at the same time14:17
mriedemGET /servers/ports?14:17
jaypipesmriedem: honestly, I hate all the existing APIs for dealing with both BDMs and vNICs.14:17
mriedemGET /servers/{server_id}/ports?14:17
sdagueI was going to say interfaces14:17
*** lucasxu has joined #openstack-nova14:17
sdaguejaypipes: ok, well hate only gets so far :)14:17
mriedemjaypipes: yeah, provide your alternatie14:17
mriedem*alternative14:18
jaypipesfine, I will.14:18
mriedembecause i'm about to ragequit on this spec14:18
sdagueit seems like this is the way to understand relationships so you can chain through14:18
sdaguewell, etherpad sketch things first14:18
sdagueis net_id readily available?14:22
sdaguelike how much of this data exists cheaply for us?14:22
*** haplo37_ has joined #openstack-nova14:22
mriedemit's cheap14:23
mriedemit's all in the instance info_cache14:23
openstackgerritAndy McCrae proposed openstack/nova master: Don't force CONTENT_LENGTH to be an int()  https://review.openstack.org/45571014:24
*** abalutoiu_ has joined #openstack-nova14:24
jaypipessdague: honestly, I'm thinking in terms of the end user here. Which end user needs to know the subnet_id or the net_id?14:24
openstackgerritAndy McCrae proposed openstack/nova master: Allow CONTENT_LENGTH to be present but empty  https://review.openstack.org/45571014:25
sdaguejaypipes: if you have multiple networks and some can get out and others cant?14:25
mriedemjaypipes: we agreed to drop fixed_ips from the response, which drops the subnet_id14:25
openstackgerritMario Villaplana proposed openstack/nova master: virt/ironic: Implement rescue and unrescue  https://review.openstack.org/41648714:25
sdaguemaybe mordred's pov would be good14:25
jaypipessdague: it's just downright confusing to the end user, IMHO. I'd rather see an API that exposes things the end user is interested in in relation to the instance itself (not the port object in Neutron, which is what MANO/VNFM users are interested in)14:25
sdagueas he fights with network discovery all the time14:25
mordredI do indeed!14:26
* mordred reads scrollback14:26
-openstackstatus- NOTICE: latest base images have mistakenly put python3 in some places expecting python2 causing widespread failure of docs patches - fixes are underway14:27
sdaguemordred: we're trying to fix the interfaces API in nova, because it remains full of some nova-net gorp. And the real question is what should it return in it's new state14:27
mordredso - as a I read - a few quick thoughts: the addresses dict as it is today is horrible to work with, I'd love something new - I'd also love for port_ids to be returned inside of the server resource for all ips reported14:27
jaypipessdague: what I'm saying is not that network info isn't interesting to some users (it is for VNF managers and orchestrators) but for the most part, none of that is interesting for a normal cloud user. What they want to see is simply the IP[v46] address information, the routes and that's pretty much it.14:27
*** abalutoiu has quit IRC14:27
jaypipeshonestly, the VIF tag stuff should never have been added to Nova. It's a Neutron port profile thing iMHO.14:28
mordredjaypipes: a normal cloud user cannot use a vm in a cloud without knowing a TON of informaiton about the networks and ports14:28
*** lucasxu has quit IRC14:28
alex_xuEmm...thinking of most user should distinguish the interface by ip address, so they have to have two API call to delete a interface14:28
jaypipesmordred: other than routing and addressing information, what information about networks and ports do they need?14:28
mordredthe number of neutron calls I have to do after getting a server from nova to figure out what the hell is going on with it is mind boggling14:28
sdaguealex_xu: which is all well and good until their interface dosen't actually get an IP because of things14:28
mordredjaypipes: well, the port_id for one14:29
dansmithjaypipes: you mean the user-specified tag or the vlan tag?14:29
*** lucasxu has joined #openstack-nova14:29
jaypipesmordred: I'm thinking of myself as a normal cloud user here. In all my time using AWS, I've never needed anything other than routing and address info.14:29
mordredjaypipes: also whether or not the IP came from a network that can route off of the cloud or not14:29
mordredjaypipes: that's because AWS is only one install14:29
jaypipesdansmith: both.14:29
sdaguejaypipes: because they have one very specific way of setting up networking14:29
*** mdnadeem has quit IRC14:29
mordredjaypipes: and they give you your ip in DNS14:29
jaypipessdague: no, they have many actually.14:29
dansmithjaypipes: the user-specified tag seems extremely useful to me14:29
mordredin openstack, your cloud could be doing networking a bilion different ways14:29
mordredand doesn't use dns to return your ip14:29
jaypipesdansmith: sure, on the Neutron *port* object, not on the server instance's information.14:30
dansmithjaypipes: not for public cloud so much, but for just base IaaS where you are trying to arrange your I in a particular way...14:30
mordredjaypipes: I REALLY need the port id on server objects14:30
dansmithjaypipes: but the whole point is to know which interface in the guest is the one you tied to which neutron network14:30
mordredit would save at least 4 additional API calls, including 2 lists14:30
dansmithjaypipes: otherwise it's just ethN and you don't know what to do with it14:30
mordredthat's per server14:30
mordredyah14:30
mordredI have no way of knowing just from an address on the server if it's routable or if it's attached to the server or is NATed14:31
mordredthose are important things to know14:31
mordred"fixed vs. floating" doesn't tell me anytihng by itself14:31
sdaguemordred: so... network_id also valuable in that context? I think that's kind of any outstanding question14:31
mordredsdague: yes14:31
mordredit  is14:31
sdaguehttps://etherpad.openstack.org/p/nova-os-interfaces14:31
sdaguesome sketching14:32
jaypipesmordred: I still don't understand why this is information a user of Nova needs to know (versus just calling Neutron if you're a power user or a VNFM)14:32
mordredbecause if an IP is not floating but is fixed, I need to be able to ask neutron whether or not the network the ip is from is externally routable or not14:32
openstackgerritAndy McCrae proposed openstack/nova master: Allow CONTENT_LENGTH to be present but empty  https://review.openstack.org/45571014:32
mordredjaypipes, sdague: network id would be nice and save me a roundtrip - but port_id is the more important thing14:32
mordredbecause port_id is my foreign key into my neutron resources14:33
jaypipesmordred: you're equating floating IP to "publically routable" but OK... still doesn't answer why the *Nova* API needs to expose this stuff when Neutron's API already does.14:33
sdaguemordred: yeh, port_id seems mandatory14:33
mordredjaypipes: port_id is the essential - I can live wihtout network being on the server14:33
jaypipesmordred: I'm not arguing against port_id being in the return..14:33
mordredawesome14:33
sdaguebut, network_id also doesn't cost us anything14:33
mordredif we can agree on port id, then we're at a good baseline :)14:33
jaypipesmordred: I'm arguing against crap like Neutron's "port_state" which is totally out of sync with the actual state of the VIF on the VM.14:34
sdagueand it would save mordred round trips in real world use cases14:34
jaypipesmordred: which we just dump out into our os-interface/ return.14:34
*** dave-mccowan has joined #openstack-nova14:34
mriedemjaypipes: we also agreed to drop port_state14:34
jaypipesalso, WTF is it os-interface and not os-interfaces/ or, I don't know... just /interfaces. :( guh.14:34
mordredoh- so - I'm saying please add port_id to the server14:34
mordrednot to /servers/{server}/interfaces14:34
mordredadding it to /interfaces doens't save me anything14:35
jaypipesmordred: you mean a list of port_ids I assume?14:35
mordredI want a port id with every ip address in addresses14:35
sdaguemordred: ok, we weren't talking about serviers14:35
mriedemmordred: right which gets us into fixed the addresses monster14:35
mordred(although I really want a new thing that isn't addresses, but I'd take just adding a port_id to addresses)14:35
mriedemwhich we weren't getting into for this spec14:35
mordredgotcha14:35
mordredso - for me, /interfaces is not useful at all14:35
mordredbecause I've got neutron if I want to query that info14:35
jaypipesmordred: EXACTLY.14:36
mordredI want to know how to contact my server without an additional roundtrip14:36
*** eharney has quit IRC14:36
jaypipesmordred: why are we even trying to return any of this other than a list of port_ids (or even hyperlinks to a Neutron URL).14:36
*** eharney has joined #openstack-nova14:36
mordredand the server record as it is today is not sufficient for that14:36
mordredjaypipes: don't return hyperlinks, they're gross14:36
mriedemso GET /ports/?device_id=<server uuid> is preferred?14:37
mordredmriedem: that's what I have to do today14:37
mordredso - let me give a specific use case, that might help14:37
jaypipesmordred: please.14:37
mordredI boot a server and I now want to attach a new floating ip14:37
mordredin order to do that, I need the port id of the fixed ip on the server so that I can pass  it to the neutron create_floating_ip call14:38
mordredbut in order to be able to do that, Ineed to call  GET /ports/?device_id=<server uuid>14:38
*** andreas_s has quit IRC14:38
mordredso I can find the port id14:38
mordredso it's "boot sever, list ports, create fip" - instead of "boot server, create fip"14:38
*** lucasxu has quit IRC14:38
mordred(that's the super basic use case and doesn't get in to "how do I know if I need a FIP or not"14:39
mriedemPOST /servers/{'networks': 'auto-floating'} :)14:39
mriedemget me a network + floating IP14:39
mordredmriedem: I'd still need the port id14:39
mordredOR14:39
jaypipesmordred: if that's the use case, why does any of that information need to be exposed to the end user? I mean, why not just say "hey, boot me a server with external connectivity". oh wait... that's kind of what "get me a network" was supposed to be.14:39
mordredneutron auto-network-and-float would need to grow the abilityto take a server id14:40
mordredjaypipes: yes. cloud.create_server(auto_ip=True) is what I _actually_ want14:40
alex_xumordred: after 'boot server' you can't get the network info, because the port created in nova-compute. So at least you need to 'boot server, show server, create fip'14:40
*** armax has quit IRC14:40
mriedemmordred: i'm not sure why you'd need the port id if nova takes care of this for you at server create14:40
mriedemanyway, we're sort of going off course here14:40
mordredalex_xu: yes - wel -  Ihave to do a poll loop on show server anyway to tell when it's active14:40
mordredmriedem: because nova does not take care of this for me at server create14:41
jaypipesalex_xu: the port doesn't *have* to be created in nova-compute. in fact, for virtually all NFV use cases, the ports are created separately and before any VM is launched.14:41
jaypipesalex_xu: ala service function chaining14:41
mriedemmordred: i know, today it doesn't, i'm talking about requested support14:41
mriedemexpanding get me a network14:41
mordredmriedem: unless nova has grown a "please make me a FIP if I need a fip on this cloud otherwise please do not get me a FIP"14:41
mordredmriedem: dear god in heaven yes that would be a BILLION times better14:41
mordredmriedem: but that logic, I'll warn you, does get rather complex :)14:42
mordredso I'll take port_id in addresses in the meantime :)14:42
mriedemright so we're digressing14:42
alex_xujaypipes: emm..yea, and you creat the port by your own, then you already know the port id14:42
mriedemmordred has pointed out that he doesn't care about or use GET /os-interface/{server_id}14:42
mriedemsorry, GET /servers/{server_id}/os-interface14:43
jaypipesmriedem: is the choice here about whether to reduce os-interface/ to just a list of port_ids or to have it repeat some/all of the informatio nin the instance_info cache?14:43
sdagueor.... delete os-interface entirely14:44
sdagueand put port_id in addresses14:44
*** mdrabe has joined #openstack-nova14:44
jaypipessdague: ++14:44
*** lucasxu has joined #openstack-nova14:44
alex_xusdague: +114:44
mriedemwhere are you going to move the POST and DELETE methods?14:44
alex_xumove to action?14:44
alex_xuour ugly action14:44
sdaguewell...14:44
mriedemand eventually when we want to expose vif tags, those are in 'addresses' as well?14:45
mordredsdague: ++14:46
sdaguemriedem: yeh, probably, they are honestly more useful than a lot of things we have in the server doc14:46
jaypipesmriedem: Neutron ports can be tagged in the port binding details.14:46
openstackgerritRodolfo Alonso Hernandez proposed openstack/nova master: Read NIC features in libvirt  https://review.openstack.org/44441514:46
mriedemjaypipes: we don't use those tags14:46
mriedemjaypipes: not for the 2.32 microversion anyway14:47
jaypipesmriedem: yeah, unfortunately. now we have two places to look for them :(14:47
-openstackstatus- NOTICE: we have rolled back centos-7, fedora-25 and ubuntu-xenial images to the previous days release. Feel free to recheck your jobs now.14:47
alex_xujaypipes: do you mean there is a copy in port binding detail for tag? or the tag in port binding detail is separated thing than nova's one14:48
mriedemand binding:profile in the port is completely free form,14:48
mriedemand a wild west of what could or might not be in there depending on version and backend of the neutron you're talking to14:48
mriedemso that's also a ton of fun14:48
*** baoli has joined #openstack-nova14:49
*** mtanino has joined #openstack-nova14:49
*** adisky_ has quit IRC14:49
mordredmriedem: because I don't follow everything y'all do - "when we want to expose vif tags" - can you point me to something where I can learn what vif tags are and what I might  use them for?14:50
jaypipesalex_xu: what mriedem said. but I will add that *Neutron* is the owner of all information about a port, so regardless of what we think about Neutron's API, it is what is the canonical source of truth for things like os-vif.14:50
mordred++14:51
jaypipesmordred: it's NFV fun.14:51
mriedemmordred: https://docs.openstack.org/developer/nova/api_microversion_history.html#id2914:51
mordredjaypipes: ah. so I do not care aboutthem :)14:51
jaypipesmordred: well, you should.14:51
mordredjaypipes: yah. I was being snarky14:51
*** chyka has joined #openstack-nova14:51
mordredthose seem potentially cool14:52
*** jlvillal_pto is now known as jlvillal14:52
sdaguemriedem / jaypipes so... I guess the one question I still have, which jaypipes and I are cycling on is there is some delay between "attach" and it being attached14:52
mriedemmordred: one example for a bdm tag i think is that, you know how we return a device_name for bdms attached to a server? and that's a total lie? people could think they can correlate that mountpoint in their guest to what the api says volume x is attached to, but that could be totally wrong14:52
sdagueand what are we indicating in that interim14:52
sdagueespecially if there is no port_status14:52
mriedemi believe the bdm tag can actually be used to correlate within the guest a given volume attached to the server14:52
mordredmriedem: that would be neat14:54
*** lucasxu has quit IRC14:54
jaypipessdague: well, the user could easily poll on GET /ports/{port_id} for the attachment state.14:54
sdaguejaypipes: yeh, that's probably reasonable14:54
mriedemsdague: i think ^ is what tempest does14:54
* mordred thinks the server should not be active until the ports are attached14:54
mriedemi added the code to do it i think, will look14:54
sdagueso it only shows up in servers once it's really there14:54
mriedemmordred: we already do that14:55
sdaguemordred: you can add ports later too14:55
*** lucasxu has joined #openstack-nova14:55
mriedemwe wait for the vif plug callback from neutron14:55
jaypipesmordred: we're talking about the live attach/detach of a port.14:55
*** nkorabli has quit IRC14:55
mordredsdague: yes - post-create port attach I think polling the port in neutron for attach state is right - or port not showing up on server until it's attache14:55
mordredeither way14:55
mriedemsdague: https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_attach_interfaces.py#L10014:56
*** marst has quit IRC14:56
*** chyka has quit IRC14:56
mriedemsdague: https://github.com/openstack/tempest/blob/master/tempest/common/waiters.py#L26414:56
*** kaisers has joined #openstack-nova14:56
mriedemso tempest totally relies on the port_state in the os-interface response to see when the port is ACTIVE14:56
mriedemand the attach is done14:56
sdaguemriedem: ok, sure14:57
sdagueso, you down at the bottom of the etherpad14:57
sdagueI think we could get that whole thing with the ports sub resource that jay proposed14:57
mordredmriedem: maybe it's time to switch tempest to poll neutron port state instead?14:57
mriedemmordred: i'm not saying that can't be change14:58
*** hongbin has joined #openstack-nova14:58
mriedemthe test doesn't even run if you're using nova-net https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_attach_interfaces.py#L3514:58
*** belmoreira has quit IRC14:59
mordredmriedem: awesome. so it's only a neutron test anyway :)14:59
sdaguemriedem: sure, but also realize this isn't contract code, it's the incidental code14:59
mriedemmordred: os-interface GET ONLY works for neutron14:59
mriedemit's a NotImplementedError for nova-net14:59
sdagueyeh14:59
mriedemand os-virtual-interfaces ONLY works for nova-net, and is a NotImplementedError for neutron14:59
mordredmriedem: I don't know that I even knew os-interface existed14:59
mriedemhence me wanting to collapse these14:59
sdaguemriedem: anyway, on your level of rage, what about the add ports to server document, provide this new minimalist interface for the port attach/detach/attaching status15:00
jaypipesmriedem, sdague: sounds like we are converging on something here..15:00
johnthetubaguyI always wish the volume attachments and network attachments kinda look/feel similar in the API, not sure I like either right now though15:00
mordredas I say that ...15:00
mriedemjohnthetubaguy: i was trying to get them closer, this gets them much further apart15:00
mordredhttps://developer.openstack.org/api-ref/compute/?expanded=list-port-interfaces-detail is pretty15:00
*** zz_dimtruck is now known as dimtruck15:01
sdaguemordred: you just said that did you no good :P15:01
mriedemsdague: honestly it's a lot more than i was planning to do for this15:01
johnthetubaguymriedem: would we likely take everything there eventually?15:01
sdaguemordred: litterally, that's where we started15:01
mriedemsdague: and if it comes to that, i'm basically going to punt for pike15:01
mriedemand just deprecate os-virtual-interfaces as the easy thing we have to do anyway, we could lump that in with deprecating multinic15:02
sdaguemriedem: that's fine15:02
mriedemjohnthetubaguy: who knwos15:02
mriedemjohnthetubaguy: maybe eventually we do similar for bdms15:02
mordredsdague: well, yah - it doesn't - because it's an extra call - I'm just saying it _is_ nice looking, so whoever wrote it didn't do a bad job or anything15:02
mriedemGET /servers/{server_id}/volumes15:02
mriedemjohnthetubaguy: but in 2 years time when we talk about doing that, we'll have either all moved on or likely changed our minds and come to some other conclusion15:03
johnthetubaguymriedem: it feels like when they seems similar, we are closer to where we want to be15:03
mordredsdague: if the addresses dict was instead list of those, that might be nice15:03
johnthetubaguy+1 for deprecating the broken bits15:03
*** hshiina has quit IRC15:03
mordredalthough I'd have to go poke for a minute to see how much code I could delete if it was15:03
sdagueok, so I think that's where we stand, just deprecate the broken thing15:03
mriedemhow about microversion 2.43: completely rewrite the entire gd compute api?15:03
cdentmriedem++15:03
*** sridhargaddam has joined #openstack-nova15:03
alex_xu:)15:04
*** sridhargaddam has quit IRC15:04
mriedembecause what i always think is an incremental step forward turns into a giant rewrite15:04
* johnthetubaguy does sarcastic nod15:04
sdaguemriedem: yeh, they do have the natural tendancy to grow15:05
sdagueanyway, I think deprecate in a mv is fine15:05
sdaguethat's a small change15:05
*** rcernin has quit IRC15:05
mriedemalex_xu: if we just deprecate os-virtual-interfaces, i think we should combine that in the same microversion as deprecating multinic15:06
*** armax has joined #openstack-nova15:06
mriedemso we don't have 20 separate microversions for just deprecating APIs15:06
alex_xumriedem: i'm ok with that15:06
mriedembecause that gets super annoying15:06
jaypipesya15:06
jaypipeson the MV for 2 deprecations.15:06
*** marst has joined #openstack-nova15:07
alex_xudo you want me merge that two spec? or we just approve the two spec separately, then I can help to code them together?15:07
alex_xuand fyi, one more deprecation spec https://review.openstack.org/386888 :)15:08
mriedemalex_xu: i don't think i ever liked that one15:08
mriedemalex_xu: because of the very odd flow that the user has to do on the neutron side15:09
alex_xumriedem: ok, I probably remember your point15:09
mriedemto hook up a server with a floating ip via neutron15:09
mriedemit's all technically possible using the APIs, but the UX seems pretty terrible15:09
jaypipesmriedem: pls see summary of mine on bottom of etherpad.15:09
mriedemalex_xu: i've abandoned https://review.openstack.org/#/c/455023/ and we can just merge it into https://review.openstack.org/#/c/384261/15:10
mriedemalex_xu: since it's getting late for you, do you want me to just combine those?15:10
mriedemthen i can harass sean or jay or john to approve that today15:10
alex_xumriedem: will appreciate for that15:11
mordredmriedem: the nova fip proxy api should never be used15:11
* johnthetubaguy nods15:11
mordredmriedem: it's racy and impossible to use atomically15:11
mordredits use should be discouraged strongly15:11
johnthetubaguyfip = floating ip?15:11
mordredyah15:11
jaypipesyes15:11
johnthetubaguymriedem: I think you removed that from alex_xu's original deprecation spec right?15:11
jaypipesmordred, mriedem, sdague: does that summary on the etherpad make sense?15:11
*** garyk has joined #openstack-nova15:12
mriedemjohnthetubaguy: originally alex_xu had deprecating floating ip actions and multinic in the same spec, and they were separated yes15:12
*** cNilesh has joined #openstack-nova15:12
johnthetubaguyah, separated, I don't remember finding the other one I guess.15:12
egonzalezHi, it's been a recent change in master who change the behaviour in nova service-list? in current master output is empty with no service registered15:13
mriedemmordred: you should read this then https://review.openstack.org/#/c/386888/415:14
mriedemjaypipes: seems so15:14
johnthetubaguymriedem: do we want to include floating ip in your mega merged deprecated spec?15:15
amotokiI totally agree that nova fip proxy is discouraged. on the other hand, it is sometimes useful i.e. in case of an instance has only one port.15:16
mriedemjohnthetubaguy: when i originally read the spec about deprecating the ability to associate/disassocate floating ips to servers and what you had to do in neutron for that, it seemed really complicated which is why i avoided it15:16
*** Drankis has quit IRC15:16
mriedemif it's really just:15:17
mriedemneutron floatingip-create EXT_NET_ID15:17
*** cNilesh has quit IRC15:17
mriedemneutron floatingip-associate FLOATING_IP_ID VM_PORT_ID15:17
mriedemthen that doesn't seem as bad15:17
amotokiit is about CLI perspective. my comment is not applied to the API perspective and I thought so from when I implemented the neutron proxy...15:17
*** Jack_Iv has quit IRC15:17
johnthetubaguymriedem : I think thats correct15:17
amotokiyeah. I believe OSC can support it15:17
mriedemit could also be,15:18
mordredmriedem: that's the bad version15:18
johnthetubaguymriedem: the network changed event bit was missing out that original spec, not sure if that was also a possible blocker15:18
mordredmriedem: neutron floatingip-create EXT_NET_ID VM_PORT_ID15:18
mriedemwhenever i need to read through the docs on how to associate a floating ip to a server in docs.o.o, i can't figure it out15:18
mordredis actually the good way15:18
mordredit's a single call15:18
johnthetubaguymordred: bad version? I am curious?15:19
johnthetubaguyoh15:19
mriedemjohnthetubaguy: no i remember that part15:19
mriedemmordred: but neutron cli is deprecated :)15:19
sdaguejaypipes: I think that 2 & 3 have to happen at the same time along with droping the os-interface resource15:19
mordredjohnthetubaguy: the reason is that if you have multiple api accessors, and any of them want to attempt to re-use unattached floating ips, they have no way of knowing if a fip that is in the flow of being created/attached is actually up for grabs or not15:19
mordredmriedem: :)15:19
jaypipessdague: os-interface, sure, but not os-virtual-interfaces, right?15:20
mordredif you use the single-api-call create-with-port version in places you know you want to create-and-attach, then it is possible to know that unattached fips are available15:20
sdaguejaypipes: correct15:20
*** baoli_ has joined #openstack-nova15:20
mriedemso "neutron floatingip-create EXT_NET_ID VM_PORT_ID" creates a floating ip on EXT_NET_ID and then associates that to a fixed ip on VM_PORT_ID?15:20
mordredif you do the create/attach dance, you are always racing15:20
johnthetubaguymordred: yeah, make sense15:20
mordredmriedem: yes- but it does it in one step15:20
jaypipessdague: and technically, we could add a ports/ subresource listing before deprecating os-interface.15:20
mordredmriedem: so you never have a fip show up in a non-attached state15:20
sdaguejaypipes: we could, but it would mostly create 1 mv where there was a funny duplication15:21
mordredmriedem: (we used to have to run a fip cleaner thread in nodepool before switching to the single-call neutron api)15:21
jaypipessdague: sure, understood.15:21
johnthetubaguymordred: not sure if the generation id they are adding to ports helps with that, I guess its a pattern they could use elsewhere15:21
*** Jack_Iv has joined #openstack-nova15:21
mordredjohnthetubaguy: I haven't heard about this generation id15:21
jaypipessdague: though we'd need to deprecate os-interface for a while anyway, so there'd still be a duplication period.15:22
*** aarefiev is now known as aarefiev_afk15:22
johnthetubaguymordred: kevinbenton I think knows about that, for atomic port updates15:22
mordredneat. I like atomic things15:22
*** baoli has quit IRC15:22
sdaguejaypipes: we actually don't15:22
jaypipessdague: no?15:22
sdaguejaypipes: no, it's a microversion change15:22
johnthetubaguymordred: I was curious on your comment about server metadata getting out of sync, is that given the clouds you are using? They might not have the bug fix in them15:23
mordredjohnthetubaguy: speaking of kevinbenton ... I just realized that my ssh-hostkey spec should actually be a neutron feature not a nova feature, so I'm going to be bugging kevinbenton about it and not you15:23
rpodolyakamriedem: hey! you asked about https://review.openstack.org/#/c/381912/ yesterday. It's not on the top of my list, but yes, I was hoping either me or snikitin_  will take over it from pkholkin15:23
* johnthetubaguy mordred: I believe this is the one: https://bugs.launchpad.net/neutron/+bug/164291815:23
openstackLaunchpad bug 1642918 in neutron "floating-ip nova notification is broken" [High,Fix released] - Assigned to YAMAMOTO Takashi (yamamoto)15:23
mriedemrpodolyaka: ok15:23
mordredjohnthetubaguy: it's entirely possible, yes - but we have since learned to not trust that data as it's proxy data and just go directly to the source15:23
mordredjohnthetubaguy: AWESOME15:23
sdaguejaypipes: the old version continues to work as well, this is just the new prefered way. The old one isn't going to get dropped any time soon.15:23
johnthetubaguymordred: yeah, that makes sense15:23
alex_xumordred: under 'neutron floatingip-create EXT_NET_ID VM_PORT_ID' is one API or multiple API?15:23
mordredjohnthetubaguy: that does, in fact, sound like the problem we saw :)15:23
*** gcb has quit IRC15:24
mordredalex_xu: well, I honestly don't know about the neutron command line client- but there is a single REST API for create-with-port15:24
mordredone sec, lemme find it for you15:24
amotokialex_xu: it is a single API except name lookup15:24
alex_xumordred: amotoki, ah, that is cool15:24
mriedemalex_xu: mordred: https://developer.openstack.org/api-ref/networking/v2/index.html?expanded=show-port-details-detail,create-floating-ip-detail#create-floating-ip15:25
mriedemPOST /v2.0/floatingips with a port_id in the body15:25
mordredmriedem: yah15:25
mordredthat'sit15:25
mriedem"To associate the floating IP with an internal port, specify the port ID attribute in the request body. If you do not specify a port ID in the request, you can issue a PUT request instead of a POST request."15:25
*** psachin has quit IRC15:25
mordred(this API is 100% of the reason I want port_ids on fixed ips reported in the nova server record, fwiw)15:26
alex_xuamotoki: I remember we can't do that in single API in long time before?15:26
*** lucasxu has quit IRC15:26
mordredsdague, jaypipes: so - don't hate me - but I do actually think net_id and subnet_id are also useful alongside the port_id in the addresses dict - largely because if I only have port_id I'll still have to go do a GET on the port to find out what network it's from so I can match it to cached information I've figured out about which networks are public and which are private15:28
mordredSO15:28
mordredif it's possible to add it when you add port_id without any additional cost - it is very useful (and still isn't duplicating all the additinonal info)15:28
sdaguemordred: so... I think it's pushing it to put all of that in the server doc15:29
sdaguein the subresource, sure15:29
mordredsdague: adding three ids adjacent to the ip is pushing it?15:29
jaypipessdague: yeah, that's what I was referring to... as in "we still will duplicate information for a time being" :)15:30
mordredI mean, you already have the port_id in ram when you're building addresses and just delete it15:30
jaypipesmordred: sure, I hear ya. it's more of an efficiency thing, as we discussed.15:30
sdaguemordred: it's mostly about the constant everyone wants everything they might ever need in the server document15:30
sdagueand we're trying to resist that a bit15:31
mordredsure. but it's not everything they might ever need -it's the two foreign keys you need to know how to take action on the server from a networking perspective.15:31
sdaguemordred: so, I think it's just time to walk away on this one, because the whole thing got dropped from pike about 30 minutes ago when it overran mriedem's rage level15:32
mordredok15:32
mordredI'd _love_ to dig in to find the right thing whenver it's the right time to do that - but I totally grok rage level on this topic15:32
mriedemjohnthetubaguy: alex_xu: so given the above discussion, maybe we do just merge the deprecation of add/removeFloatingIP with add/removeFixedIP (multinic), and also throw os-virtual-interfaces deprecation in there as well15:33
johnthetubaguymriedem: I am very tempted by that15:33
mriedemjohnthetubaguy: don't let me seduce you, you're married proper now15:34
mriedemmordred: sdague: jaypipes: yeah i'm running as far away from fixing bdms and ports in the compute API as i can for pike15:34
mriedembecause both attempts crushed both balls15:34
jaypipesmriedem: fine with me.15:35
jaypipesmriedem: sorry for complaining.15:35
*** eharney_ has joined #openstack-nova15:35
johnthetubaguymriedem: :)15:35
mriedemoh btw https://review.openstack.org/#/c/453272/15:35
mordredmriedem: well, please let me know if/when the topic comes up again. I'm definitely both very interested, very opinionated and often very confused15:35
sdaguemordred: yeh, well the issue is not a lack of opinions for sure....15:36
jaypipesmriedem: apparently, Tommy *doesn't* Like.15:36
* mriedem cues rimshot15:36
*** Jack_Iv has quit IRC15:37
mordredsdague: :)15:37
*** dane-fichter has quit IRC15:37
*** artom has quit IRC15:38
*** artom has joined #openstack-nova15:38
*** crushil has quit IRC15:39
*** eharney has quit IRC15:39
*** eharney_ is now known as eharney15:39
*** artom has quit IRC15:40
*** Jack_Iv has joined #openstack-nova15:40
*** artom has joined #openstack-nova15:40
mriedemjaypipes: since you championed server tags in the comptue api, you might want to chime in on this cinder thread to do similar for volume tags http://lists.openstack.org/pipermail/openstack-dev/2017-March/114618.html15:40
*** Jack_Iv has quit IRC15:40
mriedembecause the reply right now is, 'use searchlight'15:40
jaypipesmriedem: that would mean I want to tell DuncanT that he's wrong again. :)15:41
*** Jack_Iv has joined #openstack-nova15:41
mordredmriedem: are clouds using searchlight yet?15:42
*** chyka has joined #openstack-nova15:42
*** tuan_luong has joined #openstack-nova15:42
*** tuanla_ has joined #openstack-nova15:43
mriedemmordred: no idea15:43
mriedemmordred: searchlight wasn't listed in the oct 2016 user survey report anyway15:45
* mordred likes searchlight as an idea, just hasn't seen uptick enough yet to turn it into the answer for things15:46
mriedemmordred: well let me introduce you to https://specs.openstack.org/openstack/nova-specs/specs/pike/approved/list-instances-using-searchlight.html15:46
mriedemmordred: you're going to end up wasting your entire gd day in this channel15:47
*** Jack_Iv has quit IRC15:48
mordredmriedem: luckily I like all of you people15:48
sdaguemriedem: after a couple of hours yesterday, I did figure out why my flake8 in buffer checking didn't like the order import extension. It's that it's out of the box behavior isn't what we use15:48
sdagueand that if the file being run on it is outside of the tox tree (and there are reasons tools do that) it then behaves differently15:49
mordredmriedem: neat!15:49
sdagueanyway I have a work around, but as this is the second time that flake8-import-order caused an issue, I do kind of wonder if we really want to keep it, https://review.openstack.org/#/c/454853/15:50
mriedemsdague: i have no opinion on it, and haven't had issues with it15:51
*** Jack_Iv has joined #openstack-nova15:51
*** dtp has joined #openstack-nova15:51
sdaguemriedem: it broke the intel ci, again, because it does things by just being installed15:51
mriedembecause it's in nova?15:51
sdaguewell, it used to be in test-requirements15:52
sdaguewhich means it impacted things system wide15:52
mriedemit's not in test-requirements anymore though15:53
sdagueit's not15:53
sdaguenow it's this other problem15:53
amotokialex_xu: sorry for late. IIRC we can do that from the beginning: 'neutron floatingip-create --port-id <port-id> <floating-ip-net>15:53
amotokialex_xu: neutron didn't change the floating IP API from Folsom, but I am not sure the neutron proxy in nova supports all of the API15:55
*** kaisers has quit IRC15:55
sdaguemriedem: at this point it's in the land of "we shouldn't make it any harder to develop than we have to"15:56
DuncanTjaypipes: I've spent enough time telling you over the years that you're wrong, turn about is fair play. I'm often wrong, I just hope I'm right even more often :-)15:56
jaypipes:)15:57
*** trinaths has joined #openstack-nova15:58
mriedemsdague: i've had 0 problem with it15:58
mriedemi don't use tramp over emacs or whatever you said15:59
mriedemso i don't have an opinion15:59
sdaguemriedem: that's fine, I've lost a full day of development15:59
*** jistr is now known as jistr|mtg15:59
sdaguedebugging why this does the wrong thing15:59
mriedemsorry about that. i've lost a full day on abandoned specs.15:59
mriedemit sucks15:59
mriedemi'm not -1 on it16:00
*** karimb has quit IRC16:01
*** Jack_Iv has quit IRC16:01
DuncanTjaypipes: Having caught up with what I said, it seems daft to have two apis (metadata and tags) for the same purpose... I guess if you /really/ want tags, we just make it a convenience API that updates one specific metadata key (tags), rather than having a whole new bunch of stuff in the db... not sure if that will make search prohibatively difficult16:02
DuncanTthough... SQL has in 'in' operator, right?16:02
*** Jack_Iv has joined #openstack-nova16:02
*** voelzmo has quit IRC16:02
jaypipesDuncanT: that's not how the IN operator works in SQL.16:02
*** bpoulos has quit IRC16:03
DuncanTjaypipes: Step 1, fix SQL ;-)16:03
*** voelzmo has joined #openstack-nova16:03
*** Jack_Iv has quit IRC16:03
jaypipesDuncanT: we (in Nova-land) tend to separately define tags as "user-defined simple strings" whereas the metadata key/values can (and often are) added by the system itself and have a particular encoding of information in them.16:04
jaypipesDuncanT: so, tags on a server instance are just that... simple string tags ala the typical Web definition of the term.16:04
*** crushil has joined #openstack-nova16:04
jaypipesDuncanT: and the system never sets tags on anything.16:05
jaypipesDuncanT: only the user.16:05
mriedemthe nova 'system' doesn't set anything on server.metadata16:05
mriedemit uses server.system_metadata16:05
DuncanTjaypipes: metadata in cinder should never be set by anything other than the user... we have admin-metadata for sematically significant things16:05
mriedemthe single-tenant NFV monolith might be the system that uses server.metadata, idk16:05
DuncanTjaypipes: I think there's a historical lack of definition about what the 'metadata' fields are there for16:06
jaypipesmriedem: well, yes, sorry I was referring to the entire concept of key/value metadata. there is server metadata, system metadata on the server, image metadata, "metadetails" on the aggregate, etc.16:06
*** Jack_Iv has joined #openstack-nova16:06
*** armax has quit IRC16:06
mriedemdon't forget about flavor extra specs16:07
*** Jack_Iv has quit IRC16:07
mriedemand resource provider traits16:07
jaypipesmriedem: :) how could I forget about them? :)16:07
DuncanTjaypipes: I don't think the best fix for historical lack of definition is to slap something new on the edge though16:07
*** voelzmo has quit IRC16:07
jaypipesmriedem: one of the reasons we didn't call traits "tags" for resource providers was specifically because it is the system/admin that sets traits on a resource provider, not a user.16:07
DuncanTI think we've only got volume.metadata, volume.admin_metadata, snapshot.metadata and backup.metadata, though I haven't checked carefully16:08
jaypipesDuncanT: like I said, I didn't want to get in a conversation with you about how you're wrong. :P16:08
jaypipesDuncanT: in case it's not clear, you're not wrong at all...16:09
DuncanTjaypipes: You actually had me worried for a moment :-)16:09
sdaguemordred: with your user hat on, you want to check on this one - https://review.openstack.org/#/c/400883/16:09
jaypipesDuncanT: the concept of a simple string tag is actually pretty universal in the web. The fact that OpenStack inherited the AWS EC2 concept of metadata key/value pairs is really just a vestigiality of the early Nova API more than anything else.16:10
*** Jack_Iv has joined #openstack-nova16:10
mriedemheh, i can even apply tags to VSIs in softlayer for gods sake16:10
mriedemand they have the worst api16:10
jaypipesmriedem: sshh, don't tell.16:11
*** jianghuaw has quit IRC16:11
mriedemthey know16:11
mordredsdague: we do not seem to use that informaiton in glean at all16:13
*** Jack_Iv has quit IRC16:13
*** annegentle has joined #openstack-nova16:13
sdaguemordred: ok, great16:13
*** Jack_Iv has joined #openstack-nova16:13
sdagueI just wanted to make sure with a consumer before cutting that off16:13
clarkbsdague: mordred you sure that won't affect the udev rules for glean?16:14
*** Jack_Iv has quit IRC16:14
*** baoli_ has quit IRC16:14
clarkbI guess udev doesn't rely on metadata only what is actualy exposed by kernel16:14
mordredclarkb: I don't see us doing anything with link type in glean at all16:14
clarkbmordred: well glean does things with the link type in udev, but thats provided by linux kernel not metadata16:15
mordredright16:15
mordredI mean doesn't do anything with the link type from config-drive16:15
*** p01nt3r75 has quit IRC16:16
jaypipesmriedem, sdague, johnthetubaguy, dansmith, bauzas: https://review.openstack.org/#/c/376200/ ready for your eyeballs if you have some time today.16:17
*** Jack_Iv has joined #openstack-nova16:17
*** nic has joined #openstack-nova16:17
sdaguejaypipes / cdent what's the status on api-ref for placement?16:19
*** udesale has joined #openstack-nova16:20
cdentsdague: https://review.openstack.org/#/q/topic:cd/placement-api-ref16:20
*** browne has joined #openstack-nova16:20
*** Apoorva has joined #openstack-nova16:21
cdentsdague: avolkov is working on getting the publishing jobs linked up right. the html drafts are created but not linking into the test results yet16:21
sdaguecdent: is the publishing job up for review anywhere?16:21
mriedemmarkus_z: https://bugs.launchpad.net/nova/+bug/168036316:22
openstackLaunchpad bug 1680363 in OpenStack Compute (nova) "Raise Unexpected API Error when get console log from stopped instance" [Undecided,In progress] - Assigned to Zhenyu Zheng (zhengzhenyu)16:22
mriedemmarkus_z: UnboundLocalError on https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L280116:22
sdaguetraits seems big enough I don't want us to be digging too giant of a hole on the docs side, as we know how long it takes to dig out from the past nova experience16:22
cdentsdague: the initial ones have merged, last I talked to avolkov there's more that's WIP, but I don't currently have the details16:23
*** derekh has quit IRC16:23
cdenthttps://review.openstack.org/#/q/project:openstack-infra/project-config+owner:avolkov%2540mirantis.com+status:merged16:24
*** baoli has joined #openstack-nova16:24
sdaguecdent: yeh, doesn't seem like any open patches16:25
*** gyee has joined #openstack-nova16:25
cdentyeah, I think in this case WIP means "on his disk"16:25
sdagueok16:26
*** sridharg has quit IRC16:27
cdentsdague: since we're in the same place at the same time, did you see that I left some notes on the uwsgi etherpad, just some playing around with options https://etherpad.openstack.org/p/devstack-uwsgi ?16:28
sdaguecdent: sure16:28
openstackgerritmelanie witt proposed openstack/nova-specs master: Amend spec for placement project/user association  https://review.openstack.org/45435216:28
*** egonzalez has quit IRC16:29
sdagueso the line 85 bit16:29
cdentit's opened some question on what we're actually trying to accomplish with uwsgi, logs, etc. because, as ever, there are options...16:29
sdaguecan you do that without ports16:29
*** pcaruana has quit IRC16:29
*** Jack_Iv has quit IRC16:30
sdaguewhat I'd really like to do is find a way to not have the custom ports used anywhere16:30
openstackgerritBalazs Gibizer proposed openstack/nova master: Make all timestamps formats equal  https://review.openstack.org/42198116:30
sdaguewhich I think means, 1 http server with a lot of /paths, talking to a bunch of uwsgi processes over the local app socket16:31
*** trinaths has left #openstack-nova16:31
cdentline 85 can do that16:32
sdaguecdent: that I think gets us the most win16:32
cdentis the port issue to make sure that nothing connects to the port (even over localhost) because the first example binds to localhost only, so isn't externally exposed.16:33
*** nkorabli has joined #openstack-nova16:33
*** Jack_Iv has joined #openstack-nova16:33
markus_zmriedem: OK, will review it tomorrow. Thanks for the notice16:33
*** Jack_Iv has quit IRC16:34
mordredsdague: btw - if you get rid of the custom ports, I will buy you a unicornpony16:35
mriedemmarkus_z: nvm it's latent anyway16:35
mriedemmarkus_z: easy fix, it's not a regression16:35
sdaguecdent: I want nothing to connect to it, because we still have collisions if we require them anywhere16:36
*** markus_z has quit IRC16:36
sdaguecdent: I'm starting a new bit at the top about behaviors of the system16:36
cdentsdague: cool, I'll build the example of the l85 version tonight or tomorrow morning, and dump its implications when I do. should be simple-ish16:36
*** Jack_Iv has joined #openstack-nova16:37
*** jistr|mtg is now known as jistr16:37
*** Jack_Iv has quit IRC16:37
*** Jack_Iv has joined #openstack-nova16:38
sdaguecdent: yeh, before you run off, look at my list of behaviors at the top of that etherpad16:39
sdagueand make sure they make sense16:39
*** lpetrut has quit IRC16:39
*** alexpilotti has quit IRC16:39
cdentthey do make sense, thanks for that, will leave some comments16:39
*** alexpilotti has joined #openstack-nova16:40
*** udesale has quit IRC16:40
cdentsdague: one question about logs: coming from a webby background I think in terms of an access log and and error log, as showin in one of the examples lower in the doc. uwsgi can have specific request logs if configured to do so but I'm not sure if those logs can go to systemd in the same was as the error log, does that matter16:41
openstackgerritBalazs Gibizer proposed openstack/nova master: fix null_safe_int when called with 0  https://review.openstack.org/45577816:43
sdaguecdent: we're going to be hooking the journal directly in the oslo.log setup I think16:43
*** Jack_Iv has quit IRC16:43
sdaguei.e. I think we're going to straight bypass that ... but we'll see16:43
cdentokay, but what about request logs (of the access_log vareity). do they matter?16:44
*** alexpilotti has quit IRC16:44
cdentfor me they've always been at least as important as the log messages generated by LOG.*('some message')16:44
openstackgerritmelanie witt proposed openstack/nova-specs master: Amend spec for placement project/user association  https://review.openstack.org/45435216:45
*** lucasagomes is now known as lucas-afk16:45
*** burt has joined #openstack-nova16:46
*** gouthamr has quit IRC16:47
*** crushil has quit IRC16:48
sdaguecdent: honestly, I don't think the access logs are all that useful one way or another, because they are lacking all the identifiable information about request-id / project-id / user-id that let you dig any deeper about what was going on16:49
sdaguemostly only really for high level statistics I think16:49
bauzasp!spy16:49
sdagueat least that's how I react when I look at something like this - http://logs.openstack.org/31/450431/3/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/38bb8c6/logs/apache/tls-proxy_access.txt.gz16:49
cdenthuh, I think they're the least noisy way to answer the question: is the service getting the hits I expect16:49
cdentbut it's not really an issue, that info is a variety of places16:50
*** garyk has quit IRC16:50
*** fragatina has joined #openstack-nova16:51
sdagueyeh, and with the journal, that should be a better way to see it. The logging standards are that those things should be in the INFO block, which should be easy to query.16:52
*** kaisers has joined #openstack-nova16:52
melwitthas anyone seen a docs job failure like this? "WARNING: no "man_pages" config value found; no manual pages will be written"16:52
dansmithmelwitt: my docs job is failing too16:53
*** fragatina has quit IRC16:53
*** fragatina has joined #openstack-nova16:53
*** karimb has joined #openstack-nova16:55
openstackgerritBalazs Gibizer proposed openstack/nova master: fix null_safe_int when called with 0  https://review.openstack.org/45577816:56
*** ralonsoh has quit IRC16:56
*** armax has joined #openstack-nova16:58
jaypipesbauzas: have you checked out https://etherpad.openstack.org/p/new-instance-reservation ?16:59
*** mgagne has joined #openstack-nova17:00
sdaguejaypipes / bauzas / cdent - https://bugs.launchpad.net/nova/+bug/168165817:00
openstacksdague: Error: Could not gather data from Launchpad for bug #1681658 (https://launchpad.net/bugs/1681658). The error has been logged17:00
*** Jack_Iv has joined #openstack-nova17:00
sdagueoh... thank you openstack bot :P17:00
cdentsdague: that's correct behavior: max_unit means you can't have more than max_unit17:01
cdentit's doesn't depend on allocation_ratio17:01
*** alexpilotti has joined #openstack-nova17:01
cdenttotal capacity does17:01
*** Jack_Iv has quit IRC17:02
sdaguecdent: ok, cool, can you update the bug with why it's a Won't Fix then?17:02
cdentsdague: you wanna get that or shall I?17:02
cdentjinxish17:02
cdentyeah, will do17:02
sfinucandansmith, melwitt: It's a broken gate. There was a bot message on infra or docs a while back17:03
dansmithsfinucan: that was for the py3 thing17:04
dansmithwhich was supposedly already fixed17:04
sfinucanOh, wait - different issue17:04
*** amotoki has quit IRC17:04
sfinucanthe no man_pages thing can be fixed by removing same from Sphinx's conf.py or setting 'builders = html' in '[build_sphinx]' of 'setup.cfg'17:05
sfinucanblame pbr being too clever for its own good :(17:06
sfinucanhttps://github.com/openstack-dev/pbr/blob/master/pbr/builddoc.py#L6617:06
dansmithsfinucan: are you saying that something has changed in some package such that we're dead until we start doing that?17:07
sfinucandansmith: Depends on what project the issue is happening in. This isn't nova, is it?17:07
*** abalutoiu_ is now known as abalutoiu17:08
dansmithsfinucan: it's neutron, we're just talking about it in the nova channel17:08
dansmithsfinucan: kidding, yes nova :P17:08
*** Jack_Iv has joined #openstack-nova17:08
dansmithactually, melwitt, mine seems to still be the py3 thing17:08
sdagueyeh, the known broken thing was python3 going on by default17:09
*** Jack_Iv has quit IRC17:09
melwitthmm17:09
dansmithone of my changes is working though so maybe the puppet didn't propagate fully yet17:09
jaypipessdague: done.17:09
*** gouthamr has joined #openstack-nova17:10
sfinucandansmith: Yeah, it shouldn't happen for nova. All 'source/conf.py's (doc, api-ref, api-guide) have 'man_page' removed or set to something17:10
sfinucanHence "this isn't nova" :)17:10
*** ayogi has joined #openstack-nova17:11
melwittsfinucan: my failure is happening in nova-specs17:15
*** sambetts is now known as sambetts|afk17:15
*** efoley__ has quit IRC17:16
melwittI see 'man_pages = []' under doc/source/conf.py17:16
*** tuanla_ has quit IRC17:16
*** tuan_luong has quit IRC17:16
*** crushil has joined #openstack-nova17:16
melwittso it seems like it shouldn't be failing17:16
melwittit's not failing locally, only in the gate17:16
melwittand I rebased it already17:17
melwitt¯\_(ツ)_/¯17:18
jaypipesmelwitt: yeah, I had the same reaction looking at your spec amendment's docs failure :(17:18
*** gszasz has quit IRC17:18
*** mtanino has quit IRC17:21
openstackgerritMario Villaplana proposed openstack/nova master: virt/ironic: Implement rescue and unrescue  https://review.openstack.org/41648717:24
*** mvk has quit IRC17:25
*** tesseract has quit IRC17:26
*** tjones has joined #openstack-nova17:28
*** tjones has left #openstack-nova17:28
*** mlavalle has quit IRC17:31
*** kaisers has quit IRC17:32
*** kaisers has joined #openstack-nova17:32
*** vks1 has quit IRC17:36
cdentsdague: hiccup on mod_proxy_uwsgi: we need this version https://uwsgi-docs.readthedocs.io/en/latest/Changelog-2.0.13.html to get unix socket support, xenial is 2.0.1217:38
cdentdo we have a usual solution to such issues?17:39
*** garyk has joined #openstack-nova17:39
*** ltomasbo is now known as ltomasbo|away17:41
*** MasterOfBugs has joined #openstack-nova17:41
*** pramodrj07 has joined #openstack-nova17:41
clarkbcdent: you can ask ubuntu to backport, but generally if its not a bug I don't think they do. The other option is to get it into cloud archive (and then use cloud archive). Or maybe just use tcp?17:41
cdentclarkb: not using tcp is a design goal17:42
cdentclarkb: https://etherpad.openstack.org/p/devstack-uwsgi17:42
openstackgerritAndy McCrae proposed openstack/nova master: Allow CONTENT_LENGTH to be present but empty  https://review.openstack.org/45571017:42
clarkbcdent: to avoid the port allcoation madness?17:43
cdentin part yeah17:43
clarkbanother option may be to use not apache if another tls terminator has better uwsgi support?17:43
cdentclarkb: yeah, nginx was the original plan, but we're doing discovery on apache options to see about limit the surface of the change17:44
*** ociuhandu has quit IRC17:45
*** armax has quit IRC17:47
*** armax has joined #openstack-nova17:50
sdaguecdent: we have a certain amount of flexibility in making it a reasonable dev environment, even if it means more change. I'm totally find with the nginx cut over at the same time17:55
*** fragatina has quit IRC17:57
*** mvk has joined #openstack-nova17:57
clarkbcan I selfishly ask that https://bugs.launchpad.net/nova/+bug/1676363 and its associated changes get reviews/input/etc? This is the sort of issue in the pike release that will break us (us being infra) when the noav change that precipitated this hits clouds17:58
openstackLaunchpad bug 1676363 in OpenStack Compute (nova) "The network metadata should be more useful" [Medium,In progress] - Assigned to Dr. Jens Rosenboom (j-rosenboom-j)17:58
*** baoli has quit IRC17:59
*** hshiina has joined #openstack-nova17:59
*** baoli has joined #openstack-nova17:59
*** armax has quit IRC18:01
*** hshiina has quit IRC18:03
jaypipesclarkb: looking now.18:05
*** karimb has quit IRC18:06
*** mtanino has joined #openstack-nova18:06
cdentsdague: added some notes on the hackarounds I did to get mox_proxy_uwsgi working, going to switch to some other things for a while: https://etherpad.openstack.org/p/devstack-uwsgi18:16
openstackgerritGábor Antal proposed openstack/nova master: Transform instance.volume_attach.error notification  https://review.openstack.org/45580118:18
*** yamahata has joined #openstack-nova18:18
*** MasterOfBugs has quit IRC18:21
*** pramodrj07 has quit IRC18:21
*** nkorabli has quit IRC18:24
*** abalutoiu has quit IRC18:25
*** nkorabli has joined #openstack-nova18:25
*** tbachman has quit IRC18:25
*** lucasxu has joined #openstack-nova18:25
*** ociuhandu has joined #openstack-nova18:25
*** Jack_Iv has joined #openstack-nova18:26
*** Sukhdev has joined #openstack-nova18:26
*** priteau has quit IRC18:26
*** abalutoiu has joined #openstack-nova18:27
*** nkorabli has quit IRC18:28
*** prabhuraj has joined #openstack-nova18:28
prabhurajHi all, Warm Greetings, someone could review my code https://review.openstack.org/#/c/397471/18:29
prabhurajhttps://review.openstack.org/#/c/397459/18:29
mriedemprabhuraj: wrong channel?18:29
mriedemthose are fuel patches18:29
mriedemthis is nova18:29
*** abalutoiu_ has joined #openstack-nova18:31
*** Apoorva_ has joined #openstack-nova18:31
*** dtp has quit IRC18:32
*** prabhuraj has quit IRC18:33
*** crushil has quit IRC18:33
clarkbjaypipes: tldr on glean was cloud init couldn't configure rax interfaces and monty went off and made a thing that could. But also cloud init has historically made some very bad choices for us so I think mordred was just looking for an excuse at that point. (distro specific users, mounting volumes in places where we did not wnat them mounted are the two big ones that I recall)18:34
*** abalutoiu has quit IRC18:34
*** Apoorva has quit IRC18:34
jaypipesclarkb: hey, cool by me. I wasn't complaining about NIH or anything. was genuinely learning about a new thing :)18:34
clarkbya, just thought I'd explain after seeing your comment :)18:35
*** mgagne_ has joined #openstack-nova18:35
*** mgagne_ is now known as Guest8931718:35
clarkbjaypipes: there are days I am grumpy about it (especially when something breaks due to sillyness in glean) but then there are times when we don't break due to something cloud init would have done when I am happy18:35
clarkb:)18:35
jaypipesno worries clarkb :)18:36
clarkbbut its become quite common with ironic uses I guess because it groks vlans and stuff18:36
jaypipesclarkb: doesn't cloud-init grok vlans as well? I think it does...18:36
clarkbI think it didn't for a long time?18:37
jaypipesclarkb: ok, done with reviews on that series.18:38
jaypipesclarkb: only thing I'd like to see is prefixlen be an int not a string.18:38
clarkbthis is mostly second hand I don't actually do ironic things. VLANs and link aggregation were the two big features they like18:38
jaypipesclarkb: otherwise, looks fine to me.18:38
clarkbjaypipes: awesome thank you for taking a look18:38
jaypipesany time.18:38
jaypipesclarkb: link agg: https://git.launchpad.net/cloud-init/tree/cloudinit/sources/helpers/openstack.py#n590 and vlans: https://git.launchpad.net/cloud-init/tree/cloudinit/sources/helpers/openstack.py#n614 :)18:39
*** ociuhandu has quit IRC18:40
*** ociuhandu has joined #openstack-nova18:41
mordredjaypipes: yah -so - when we started in on glean, cloud-init was on a very explicit freeze not accepting new things becaue they were working on a v218:44
mordredjaypipes: which meant adding support for the network_info.json stuff was a no-go18:44
mordredthey have since unfrozen, which is great for everyone18:45
jaypipescool beans.18:45
*** abhishek has quit IRC18:45
mordredso at this point the main difference is size - glean assumes the only thing you want it to do is get networking set up and inject ssh keys - and that you NEVER want to talk to non-config-drive metadata service18:45
mordredcloud-init is much more flexible and lets you inject arbitrary scripts18:46
mordredwhich some people think is cool18:46
*** Guest89317 has quit IRC18:46
mordredand I support them in that - I, for myself, _never_ want to run scripts via cloud-init because I can run scripts over ssh much more easily and more debuggably :)18:47
dansmithmordred: orly, glean is configdrive-only?18:47
*** kaisers has quit IRC18:47
mordreddansmith: yup18:47
dansmithinteresting18:47
mordredwe have had nothing but terrible experiences with the ec2-style metadata service18:47
mordredcrashing clouds and instances not booting and instances timing out and whatnot18:47
mordredso we avoid it like the plague18:47
mordredconfig-drive is teh ossum18:48
dansmithmordred: yeah, especially when you have puppet running every 15 minutes on every instance against central metadata services18:48
mordreddansmith: yup18:48
dansmithand when I say every fifteen minutes I mean "for 14 minutes total until smoke"18:49
*** baoli has quit IRC18:49
mordreddansmith: since cloud-init does support config-drive, i'd LOVE it if nova just defaulted config-drive to on, removed the option to turn it off, and then removed the ec2 metadata service18:49
dansmithyeah, the only problem is the staticness of it18:50
mordreddansmith: but I suppose that's at odds with my stance about not changing things, so maybe I'm a hypocrit :)18:50
dansmithi.e. volume attach and nic attach18:50
mordredright- so ...18:50
jaypipeslmao18:50
mordrednetwork attach should just work, since clouds should just be offering dhcp, which means there is no need for config-drive to be updated (unless the cloud is broken)18:51
*** mlavalle has joined #openstack-nova18:51
dansmithmordred: unless you want/need metadata about that nic18:51
mordredbut if you're adding a NIC after boot, you're adding the nic, so you as the orchestrator likely already know you're doing it and should be able to direct the instance to do something different,no?18:52
dansmithunless you have an agent that looks for nics with tags of "multipath-to-db" and enslaves them into a bond,18:52
mordredI mean, the only reason we need config-drive for network info anyway is for clouds without dhcp - for the rest I recommend using your orchestration tool to talk to the nova api18:52
dansmithnot necessarily18:52
jaypipesmordred: right, unless you're a VNFM or MANO system that is dynamically swapping metadata about your workload's vNICs at runtime and having the workload reconfigure service function chains.18:52
dansmiththat ^18:53
*** fragatina has joined #openstack-nova18:53
*** kaisers has joined #openstack-nova18:53
*** crushil has joined #openstack-nova18:53
* jaypipes drops NFV into water supply, poisons everyone.18:53
mordredI'm still not sure why that isn't just an API call on the service API - which would of course be hard because we haven't bothered with per-instance credentials :)18:53
dansmithjaypipes: it does kinda sound like a chemical18:53
jaypipesmordred: bingo.18:54
mordredbut ec2 metadata services is a poor workaround for having an agent in an instance just make API calls to the control plane in a sane fashion18:54
jaypipesmordred: also correct.18:54
dansmithso you want the instance to hit the api, find out the ports that are on the instance, and corellate them all by mac address to know what to do with which actual device in the OS?18:55
mordreddansmith: well, the list ports call also lists the mac addresses of the ports18:55
mordredbut yah - I do that for every instance we spin up in nodepool18:56
mordredbecause I have to to figure out if the instance needs a floating ip or not18:56
*** abalutoiu has joined #openstack-nova18:56
mordredso sure!18:56
dansmiththat works if you've got creds in the instance18:57
*** alexpilotti has quit IRC18:57
mordredwe could also just have an API call that gives a rollup report similar to what's in the metadata service - I'm just saying it doesn't need to be a special network port that's only usable to talk to the special service that doesn't scale18:57
*** baoli has joined #openstack-nova18:57
mordredand instead we should focus on getting creds into the instance18:57
*** kaisers has quit IRC18:57
mordredwhich would make many people happy18:57
*** alexpilotti has joined #openstack-nova18:57
dansmithwell, I dunno, given where we are, tags on the devices we add seems like a reasonable thing to me18:58
dansmithespecially given that there are some devices for which there is no service to talk to18:58
dansmithlike a raw pci device18:58
mordredwouldn't that raw pci device be there at boot? or be a thing you added to the vm via nova?18:59
dansmithif cinder gives us the serial number of the block device that we're going to add or something, then I guess we can do the same for cinder,18:59
*** kaisers has joined #openstack-nova18:59
dansmithbut otherwise that's a problem18:59
*** marst has quit IRC18:59
mordredI mean - I hear you18:59
dansmithmordred: what does it matter if it was there at boot?18:59
mordredif it's there at boot, it can have data in config-drive without any issues19:00
*** abalutoiu_ has quit IRC19:00
mordredthe static nature of config-drive and dynamic devices was the issue19:00
*** fragatina has quit IRC19:00
dansmithsure, I thought we were talking about not needing metadata at al19:00
mordredoh golly no19:00
mordredmetadata is great19:00
dansmithcinder doesn't show me a device serial number or aything,19:00
*** karimb has joined #openstack-nova19:00
dansmithso not sure that I can do the same correlation inside the guest for it19:00
mordredwell, mounting volumes is hard no matter what19:00
mordredbecause how they're presented to the guest varies by hypervisor19:01
mordredand the api can lie to you about the device name19:01
dansmithwell, same for nic, except we have an address in the case of ethernet19:01
mordreddansmith: WHAT ABOUT TOKEN RING???19:01
dansmithmordred: indeed, what about token ring indeed,19:01
dansmithbut while you say that,19:01
dansmiththere are definitely requests for weird custom L2 things19:02
mordredoh, I'm sure there are19:02
dansmithat which I laugh, but..19:02
*** alexpilotti has quit IRC19:02
*** garyk1 has joined #openstack-nova19:03
*** ociuhandu has quit IRC19:03
mordredso ... my world view has given up on magical agents sitting inside of guests looking for metadata updates to automagically reconfigure themselves19:03
mordredthat might color my opinion on how these things should work19:03
*** ociuhandu has joined #openstack-nova19:03
dansmithwell, in that case you don't really need instance creds, right?19:03
mordredhaving systems that sit outside of the guests, that konw what's going on and that can reach in and execute commands in the guests works much better in my world so far19:03
mordreddansmith: that is correct, I do not19:04
*** garyk has quit IRC19:04
dansmithanyway, I just think that being consistent about how you plumb things at boot or after boot requires metadata, and I like configdrive for that for all cases other than that it can't be updated after boot19:04
mordredhowever, if instance creds are there, then in-instance things have access to the same power I have while sitting outside of the guest19:04
mordreddansmith: ++19:04
*** gjayavelu has joined #openstack-nova19:04
mordredand I'd like more metadata - especially in cases where our current metadata is missing or lies19:04
mordred"this is the volume you named bob"19:05
openstackgerritChris Dent proposed openstack/nova master: [placement] Idempotent PUT /resource_classes/{name}  https://review.openstack.org/44879119:05
dansmithmordred: right and we have that now, but only at boot for configdrive19:05
*** tbachman has joined #openstack-nova19:05
dansmiththe volume thing I mean19:05
dansmithbecause we can generate that data only in the hypervisor driver19:05
mordreddansmith: we ALSO have the volume thing in libvirt with device names19:05
dansmithand because it's virt-specific, we only show that to the guest not the external API19:05
dansmithmordred: not with volume tags which we now have19:05
dansmithmordred: now you get a metadata blob that says "your vdb IS the volume you tagged as foo"19:06
mordredand that tag does't show up in /dev/disk?19:06
dansmithmeaning /dev/disk/by-tag/?19:06
mordredyah19:07
dansmithsomething in the guest would have to do that for us, of course19:07
*** garyk1 has quit IRC19:07
*** READ10 has quit IRC19:08
mordredwe get labels for normal cinder volumes now though - but I guess a disk can only have one lable and could have many tags19:08
*** lucasxu has quit IRC19:08
dansmithwe get labels if they lay a filesystem down, right?19:08
*** abalutoiu_ has joined #openstack-nova19:08
mordredwe get a by-$something thathas the volume name in somewhere - one sec, lemme find the thing I'm talking about19:08
dansmithI don't think so19:09
*** abalutoiu__ has joined #openstack-nova19:09
dansmiththat would be by-label, and if they put a filesystem in and labeled it19:09
dansmithor are you talking about the virtio-$neutered_uuid ?19:10
*** lucasxu has joined #openstack-nova19:11
mordreddansmith: ok. I think I may just be smoking crack19:12
*** abalutoiu has quit IRC19:12
dansmithI would totally believe that19:12
dansmith:)19:12
*** Jack_Iv has quit IRC19:12
mordreddansmith: it's 19:12 UTC, which everyone knows is crack-o'clock19:12
dansmithobvi19:12
*** abalutoiu_ has quit IRC19:12
*** Jack_Iv has joined #openstack-nova19:13
* dansmith assumes that by crack, mordred means "maple candy from vermont"19:14
mordredof course!19:16
mordreddansmith: is there some other type I should know about?19:16
dansmithmordred: nah, stick to the safe stuff19:16
*** dharinic has joined #openstack-nova19:16
*** mgagne_ has joined #openstack-nova19:18
openstackgerritMatt Riedemann proposed openstack/nova master: Deprecate CONF.api.allow_instance_snapshots  https://review.openstack.org/45510019:18
*** mgagne_ is now known as Guest436619:19
*** dave-mccowan has quit IRC19:21
*** armax has joined #openstack-nova19:22
*** mgagne has quit IRC19:24
*** Guest4366 is now known as mgagne19:25
*** mgagne has quit IRC19:25
*** mgagne has joined #openstack-nova19:25
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend  https://review.openstack.org/45327219:27
*** liusheng has quit IRC19:29
*** liusheng has joined #openstack-nova19:29
*** bmace has quit IRC19:30
*** bmace has joined #openstack-nova19:30
*** tbachman has quit IRC19:31
mgagnegibi: mriedem asked me to ask you about your input/opinion on notification impact on this proposed spec: https://review.openstack.org/#/c/453272/19:35
mgagnegibi: in PS3: "Hmm, this seems like something for which we should send a notification. I don't think we send notifications for any external events that we handle today though. It might be worth talking to gibi about this. I wouldn't block this spec on it, but it seems useful."19:35
*** pramodrj07 has joined #openstack-nova19:36
*** MasterOfBugs has joined #openstack-nova19:36
*** alexpilotti has joined #openstack-nova19:37
cfriesendoes anything test with "force_raw_images" set to false, or with glance image formats other than raw/qcow2 ?19:39
mriedemof course not http://codesearch.openstack.org/?q=force_raw_images&i=nope&repos=nova19:41
*** awaugama has quit IRC19:41
mriedemthat reminds me, i noticed we don't test with that as False once19:41
*** alexpilotti has quit IRC19:41
*** fragatina has joined #openstack-nova19:43
cfriesenit seems to work okay for raw/qcow2, but apparently it doesn't work with a vmdk format image file.  (admittedly a qcow2 image with a vmdk backing file is a bit odd, but we don't do anything to prevent it)19:43
*** dtp has joined #openstack-nova19:45
mriedemcfriesen: did you mean integration test? because we don't even test that with a unit test19:45
mriedemvmdk with libvirt imagebackend?19:45
*** satyar has quit IRC19:45
mriedemvmdk is all vmware19:46
mordredcfriesen: we do vhd uploads in production19:46
mordredbut that's not helpful for gate testing :)19:47
openstackgerritMatt Riedemann proposed openstack/nova master: Add uuid to Service model  https://review.openstack.org/45302519:47
openstackgerritMatt Riedemann proposed openstack/nova master: Add online data migration for populating services.uuid  https://review.openstack.org/45489919:47
openstackgerritJay Pipes proposed openstack/nova master: Read Neutron port 'binding_profile' during boot  https://review.openstack.org/44925719:48
openstackgerritJay Pipes proposed openstack/nova master: Modify PciPassthroughFilter to accept lists  https://review.openstack.org/44494619:49
openstackgerritJay Pipes proposed openstack/nova master: Read Neutron port 'binding_profile' during boot  https://review.openstack.org/44925719:49
mriedemcfriesen: you've got a little unit test failure to fix up in https://review.openstack.org/#/c/447055/19:53
*** smatzek has quit IRC19:53
*** markvoelker has quit IRC19:56
*** kaisers has quit IRC19:57
cfriesenmriedem: okay, will sort it out.  I'm putting out customer fires.19:59
*** cdent has quit IRC20:00
cfriesenmriedem: mordred: apparently libvirt/qemu will boot a vmdk-format glance image.20:00
mriedemhttps://en.wikibooks.org/wiki/QEMU/Images#Image_types20:01
mriedemi don't see ploop in that list20:02
mordredcfriesen: fascinating20:02
*** ayogi has quit IRC20:02
cfriesenI have a report that it boots up, but then fails when we try to live-migrate the instance.20:03
cfriesenI'll raise a bug once we have the info nailed down a bit more securely20:03
mriedemplease include customer credit card numbers in the bug report thanks20:03
cfriesenwouldn't that be nice. :)20:04
cfriesennot actually expecting it to get fixed, but at least someone else can see the bug report and know it's broken. :)20:04
*** eharney has quit IRC20:04
jaypipeswait, mriedem, your customers pay you?20:07
mriedemi don't have customers20:07
*** Jack_Iv has quit IRC20:08
*** Jack_Iv has joined #openstack-nova20:08
*** Jack_Iv has quit IRC20:08
*** Jack_Iv has joined #openstack-nova20:08
d9kis there any code for different components to share locks?, i dont see anything20:08
d9kalso oslo, which uses fasteners does not have any code for shared locks either20:09
*** Jack_Iv has quit IRC20:09
*** Jack_Iv has joined #openstack-nova20:10
d9ki posted earlier about a race nova and neutron introduce with iptables and ipsets, both need to acquire shared locks from each other20:10
sdagued9k: there is no mechanism for that today, is there an open bug on that issue?20:11
*** xyang1 has joined #openstack-nova20:13
*** Jack_Iv has quit IRC20:14
d9kno not yet, acquiring neutron-ipset lock in the iptables-save/restore bit fixes https://ptpb.pw/16S8, but https://ptpb.pw/aukQ needs locks too20:16
*** eharney has joined #openstack-nova20:18
mriedemhttp://forumtopics.openstack.org/cfp/details/1120:19
d9kalso this happens fairly often when running tempest compute.servers20:21
*** kaisers has joined #openstack-nova20:22
*** kaisers has quit IRC20:24
*** kaisers has joined #openstack-nova20:24
*** armax has quit IRC20:26
*** READ10 has joined #openstack-nova20:26
*** tbachman has joined #openstack-nova20:27
*** lucasxu has quit IRC20:27
*** armax has joined #openstack-nova20:27
*** gouthamr has quit IRC20:28
sdagued9k: a bug with details would be good, sounds like you've done a lot of the debugging, and it would be great to get all those details down20:30
*** lucasxu has joined #openstack-nova20:30
*** lucasxu has quit IRC20:34
*** dimtruck is now known as zz_dimtruck20:35
*** lucasxu has joined #openstack-nova20:35
swebsterHas anybody run the latest py27 unit tests on a Centos system?  I'm getting a failure on the nova.tests.unit.objects.test_objects.TestObjectVersions.test_versions test which seems to be related to the recent "Use cursive for signature verification" change: https://review.openstack.org/#/c/351232/.  The test passes on my Ubuntu Xenial box, with cursive versions both at 0.1.2.20:38
*** crushil has quit IRC20:44
mriedemswebster: it's likely something in the cursive library, what is the actual error? (in a paste)20:44
*** karimb has quit IRC20:45
swebstermriedem: Here's a paste of the error(s) seen https://pastebin.com/1rqJaTPs20:46
*** jpena|off has quit IRC20:48
*** dmellado has quit IRC20:48
mriedemmy guess would be something with this https://github.com/openstack/cursive/blob/master/cursive/signature_utils.py#L17720:48
mriedemthat changes what's in REGISTERED_TYPES20:49
mriedemwhich changes our enum list in nova20:49
*** ltomasbo|away has quit IRC20:50
mriedemthis https://github.com/openstack/nova/blob/master/nova/objects/fields.py#L43020:50
mriedemswebster: to find out, import cursive 0.1.2 in centos and xenial and compare signature_utils.SignatureKeyType.REGISTERED_TYPES.keys()20:51
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Deprecate multinic, os-virtual-interfaces, and floating IP action APIs  https://review.openstack.org/38426120:54
mriedemsdague: jaypipes: mordred: alex_xu: johnthetubaguy: ^ there you go20:54
mriedembig bag of deprecation20:54
jaypipesmriedem: cool.20:55
swebstermriedem: Very right.  Centos: ['RSA-PSS', 'ECC_SECP521R1', 'ECC_SECP384R1', 'DSA']. Ubuntu: ['RSA-PSS', 'ECC_SECP521R1', 'ECC_SECT409R1', 'ECC_SECT409K1', 'ECC_SECT571R1', 'ECC_SECP384R1', 'ECC_SECT571K1', 'DSA']20:55
*** armax has quit IRC20:56
mriedemswebster: that's super fun20:56
*** dharinic has quit IRC20:56
mriedemthey used to be hardcoded https://review.openstack.org/#/c/351232/16/nova/objects/fields.py20:56
mriedembefore we were using cursive20:56
mriedemswebster: please report a bug20:57
mriedemhttps://bugs.launchpad.net/nova/20:57
swebstermriedem:  And now it looks like they could be different system to system.  Will do, and thanks20:57
*** dharinic has joined #openstack-nova20:58
mriedemyeah that sucks, and i was afraid of something like that happening20:58
mriedemwe should probably just hard-code the superset20:58
*** ssurana has joined #openstack-nova20:59
*** xyang1 has quit IRC21:00
*** xyang1 has joined #openstack-nova21:00
*** rfolco has quit IRC21:01
mriedemmelwitt: so you hit "sphinx.errors.SphinxWarning: WARNING: no "man_pages" config value found; no manual pages will be written" right?21:01
mriedemdid you just recheck it?21:01
melwittmriedem: cdent rechecked it and it failed again21:02
*** zz_dimtruck is now known as dimtruck21:02
mriedemwell that's just great21:03
mriedemi'm going to go eat my feelings21:03
*** karimb has joined #openstack-nova21:05
*** thorst has quit IRC21:07
*** cleong has quit IRC21:08
*** armax has joined #openstack-nova21:10
*** lucasxu has quit IRC21:12
dansmithlast time I tasted feelings they had a distinct "like butt" quality21:13
*** gouthamr has joined #openstack-nova21:13
dansmithbut, I'm not very adventurous with my mouth21:13
dansmither, tastes21:13
*** jdurgin has quit IRC21:14
*** lucasxu has joined #openstack-nova21:16
*** eharney has quit IRC21:19
*** catintheroof has joined #openstack-nova21:19
*** esberglu has quit IRC21:19
*** esberglu has joined #openstack-nova21:20
*** catintheroof has quit IRC21:21
*** Apoorva_ has quit IRC21:21
*** catintheroof has joined #openstack-nova21:21
*** Apoorva has joined #openstack-nova21:22
*** vladikr has quit IRC21:22
*** abalutoiu_ has joined #openstack-nova21:23
*** esberglu has quit IRC21:24
mriedemthese feelings tasted like pretzels21:25
*** abalutoiu__ has quit IRC21:27
*** READ10 has quit IRC21:30
*** alexpilotti has joined #openstack-nova21:30
*** thorst has joined #openstack-nova21:30
*** edmondsw has quit IRC21:34
*** thorst has quit IRC21:34
*** edmondsw has joined #openstack-nova21:35
*** esberglu has joined #openstack-nova21:35
mriedemok, on to writing a spec to deprecate os-hosts now?!21:36
*** kaisers has quit IRC21:37
*** edmondsw has quit IRC21:39
*** ociuhandu has quit IRC21:43
*** jdurgin has joined #openstack-nova21:44
dansmithmriedem: uuid should be nullable on the model but not on the object right? https://review.openstack.org/#/c/453025/6/nova/objects/service.py21:48
dansmithAFAICT, there's no need for it to actually be None anywhere21:49
dansmithbut if it's nullable everything needs to be defensive21:49
openstackgerritMatt Riedemann proposed openstack/nova master: Add uuid to Service model  https://review.openstack.org/45302521:52
mriedemyes21:52
mriedemyou're right21:52
mriedemcompute nodes uuid is read-only https://github.com/openstack/nova/blob/master/nova/objects/compute_node.py#L5521:52
mriedembut not nullable21:52
mriedemaggregate uuid is nullable=False, but not read-only https://github.com/openstack/nova/blob/master/nova/objects/aggregate.py#L24421:53
*** esberglu has quit IRC21:53
*** ociuhandu has joined #openstack-nova21:53
dansmithyeah21:53
dansmiththere was a reason for the agg one not being read-only21:53
mriedemso should be nullable=False and read_only=True?21:53
dansmithtbh, just make it nullable=False (i.e. don't specify it)21:54
dansmiththe readonly has been problematic recently,21:54
mriedemok21:54
dansmithso I'd leave that off, which is why it is in aggregate21:54
* dansmith runs off for a bit21:55
openstackgerritEric Fried proposed openstack/nova master: PowerVM Driver: spawn/destroy #2: functional  https://review.openstack.org/43859821:57
efriedmriedem ^^ back atcha.21:57
efriedStill a couple uncertainties inline.21:58
*** lucasxu has quit IRC21:58
openstackgerritMatt Riedemann proposed openstack/nova master: Add uuid to Service model  https://review.openstack.org/45302521:59
openstackgerritMatt Riedemann proposed openstack/nova master: Add online data migration for populating services.uuid  https://review.openstack.org/45489921:59
*** jaypipes has quit IRC22:02
*** edmondsw has joined #openstack-nova22:04
*** mdrabe has quit IRC22:04
*** edmondsw has quit IRC22:08
*** tbachman has quit IRC22:12
*** burt has quit IRC22:14
*** dgonzalez has quit IRC22:24
*** xyang1 has quit IRC22:26
*** dgonzalez has joined #openstack-nova22:28
*** ociuhandu has quit IRC22:29
*** mtanino has quit IRC22:30
*** ociuhandu has joined #openstack-nova22:31
*** Guest89312 has quit IRC22:35
mriedemmgagne: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115292.html22:36
mriedembrowne: efried: BobBall: would be good to check out https://review.openstack.org/#/c/453272/ and see if vmware, powervm and xen drivers can support this API eventually22:37
mgagnemriedem: Thanks for starting the conversation and doing proper follow up22:37
mriedemclaudiub: you too but i think hyperv already does22:37
*** kaisers has joined #openstack-nova22:37
mriedemmgagne: does the cinder extend volume api have a confirm / reject state like nova resize does?22:38
*** r-daneel has joined #openstack-nova22:38
mgagnemriedem: cinder doesn't have this confirmation system22:38
mgagnemriedem: as you mention, there are pending questions: capabilities from virt driver. But also error handling in Nova since event system is async, Cinder can't query back for status.22:39
mriedemmgagne: the nova api could fail fast in one case,22:39
mriedemthat the computes aren't new enough22:39
claudiubmriedem: yeah, that's something i was going to comment on.22:40
*** felipemonteiro has quit IRC22:40
mriedemi.e. if we know the instance is running on an ocata compute, we know it's going to fail, and we could fail the request to cinder with a 409 or something22:40
mgagnemriedem: this means a sync call to compute node? or could capabilities be cached somewhere in database?22:40
claudiubit seems that it only talks about iscsi volumes.22:40
mriedemmgagne: we have the nova-compute service version in the database22:40
mriedemmgagne: so we know if the compute host is running ocata or pike code,22:40
claudiubwhile for hyper-v we support iscsi, smb, and fibre channel volumes.22:40
mgagnecool, didn't know about that22:40
mriedemor what the minimum nova-compute is in the deployment22:41
claudiubfor smb, afaik, the hyper-v driver might have to do the volume resize. didn't read the whole spec to see if that's possible in nova22:41
mgagneclaudiub: yes, the proposed implementation is very "optimist" by assuming only libvirt+iscsi exists in its presumed perfect world =)22:41
mriedemclaudiub: yeah good point - mgagne: how do we know which brick connector to get? do we have to get the connection_info dict from cinder for the given volume?22:41
mgagnemriedem: iirc, extend_volume takes connection_info in parameter so I assume it knows that to do with that22:42
mgagnemriedem: I can check, just a bit busy with some openstack upgrade atm =)22:42
mriedemoh, hmm,22:43
mriedemi guess we have the bdm.connection_info22:43
mriedemand can lookup the bdm by instance and volume id22:43
mgagneyes, nova has it afaik in bdm22:43
*** dixiaoli has joined #openstack-nova22:43
*** al498u has quit IRC22:43
claudiubmriedem: anyways. since there's blueprints talk. i was going to propose a sriov + hyperv spec to nova. i finally have some hardware to work / test on. :D it would be a pretty straight-forward implementation IMO, especially since we already support pci passthrough in hyper-v. do I need a spec for that?22:46
mriedemclaudiub: i thought you had a spec for that at one point?22:47
mriedemmaybe it was just a blueprint and a patch that was abandoned?22:47
mriedemclaudiub: i think i'm fine with a specless feature parity blueprint though22:47
claudiubi don't think I had, never had the hardware to test that feature before.22:47
claudiubcool, will submit the blueprint and some POC code by the end of the week.22:48
*** r-daneel has quit IRC22:59
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Nova support for attached volume extend  https://review.openstack.org/45327223:03
*** chyka has quit IRC23:05
*** chyka has joined #openstack-nova23:05
*** lyan has quit IRC23:06
*** sdague has quit IRC23:09
*** tbachman has joined #openstack-nova23:10
*** annegentle has quit IRC23:12
*** artom has quit IRC23:14
*** artom has joined #openstack-nova23:14
*** erlon has quit IRC23:15
*** artom has quit IRC23:16
*** artom has joined #openstack-nova23:16
*** Apoorva_ has joined #openstack-nova23:16
*** Apoorva has quit IRC23:20
*** thorst has joined #openstack-nova23:20
*** baoli has quit IRC23:21
*** thorst has quit IRC23:23
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (1/4)  https://review.openstack.org/45556323:24
*** claudiub has quit IRC23:25
*** catintheroof has quit IRC23:29
*** catintheroof has joined #openstack-nova23:30
*** catintheroof has quit IRC23:30
*** chyka has quit IRC23:30
*** dixiaoli has quit IRC23:36
*** mlavalle has quit IRC23:38
*** crushil has joined #openstack-nova23:38
*** jamielennox is now known as jamielennox|away23:48
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (2/4)  https://review.openstack.org/45556823:48
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (3/4)  https://review.openstack.org/45557023:48
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (4/4)  https://review.openstack.org/45557323:48
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Example verification for servers-actions.inc  https://review.openstack.org/45456523:48
*** baoli has joined #openstack-nova23:49
*** baoli has quit IRC23:49
*** baoli has joined #openstack-nova23:50
*** jamielennox|away is now known as jamielennox23:51
*** thorst has joined #openstack-nova23:53
*** hongbin has quit IRC23:54
*** takashin has joined #openstack-nova23:55

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