Tuesday, 2017-02-28

dansmithnow, he made it sound like they _do_ have a block device even in the containery thing00:00
mikalWe talked through a user space fat implementation they could use instead00:00
mikalAnd they shook their fists at us for being big meanies00:00
*** aslezil has quit IRC00:00
*** dimtruck has quit IRC00:00
mikalI have no comment on if the block thing is still true00:00
mikalSimply don't know00:00
*** scottda has quit IRC00:00
*** betherly has quit IRC00:00
*** spotz has quit IRC00:00
*** McNinja has quit IRC00:00
*** leifz has quit IRC00:00
dansmithmikal: can you make sure that all gets reflected in the current patches? I'll circle back and admit I didn't have that context while we were discussing it and I was not coming up with any reasons to block it00:01
dansmith(which is why we wanted to re-get your context post-ptg)00:01
*** geekinutah has quit IRC00:01
*** comstud has quit IRC00:01
mikalSure. Its not going to happen today though. I'll try and get it done by the end of the week.00:01
*** patrickeast has quit IRC00:02
*** fnordahl has quit IRC00:02
*** melwitt has quit IRC00:02
mikalI'm currently trying to remember why a directory on the host OS was better than a ext4 filesystem00:02
mikalAnd its not coming to me instantly00:02
*** nikhil|afk has quit IRC00:02
*** toan has quit IRC00:02
*** Hazelesque has quit IRC00:02
dansmithwell, it is the same behavior for lxc and parallels, and doesn't require needing to know what filesystem is there00:02
mikalI do recall someone else wanting directories, it might have been LXC00:03
*** nikhil|afk has joined #openstack-nova00:03
mikalI'm a bit fuzzy on the details00:03
mikalThat said, it didn't merge00:03
tonybdansmith: I don't see any open reviews, just the old 2015 blueprint00:03
mikalSo how does LXC do config drives at the moment?00:03
dansmithtonyb: they had a patch I think00:03
dansmithmikal: it doesn't AFAIK00:03
mikalOh, ok00:03
*** jwcroppe has quit IRC00:04
dansmithactually,00:04
*** owalsh_ is now known as owalsh00:04
dansmithtonyb: maybe I'm thinking of the other libvirt image type thing00:04
*** Hazelesque has joined #openstack-nova00:04
*** owalsh is now known as owalsh-afk00:04
dansmithI think we're to expect them to have a spec though, IIRC00:04
tonybdansmith: Yeah could be ... I can't see an configdrive patch and we discussed them at the same time late on Friday soe memory==fuzzy00:05
dansmithyeah00:05
*** scottda has joined #openstack-nova00:05
*** nic has quit IRC00:05
*** hongbin has quit IRC00:05
dansmithtonyb: he should be around during your day today I think, so maybe ping him00:05
mikalWas there any discussion of vendordata? I kind of consider it complete at this point, but I don't know if people showed up with pitchforks with further complaints.00:05
*** geekinutah has joined #openstack-nova00:06
*** patrickeast has joined #openstack-nova00:06
tonybmikal: not near me00:06
dansmithmikal: we declared it a success given the lack of any pitchforks (or other representation)00:06
*** yingjun has joined #openstack-nova00:06
mikaldansmith: good. I shall pretend it never happened then.00:07
*** aslezil_ has joined #openstack-nova00:07
dansmithwell you might miss out on eventual praise if you do00:07
mikaldansmith: oh no, I shall tell random people on the street of my exploits00:07
*** toan has joined #openstack-nova00:07
dansmithheh00:07
tonybdansmith: he'll have a minion pass on the praise in mime00:08
mikaldansmith: and it will go on my application form for Fellow. "I invented the shit out of config drive v2, and the vendordata re-write!"00:08
dansmithheh00:08
cburgesslol00:08
mikalBoth fundamental internet technologies00:08
*** dimtruck has joined #openstack-nova00:08
mikalActually, a tshirt that said "I invented the shit out of config drive v2" would probably be a thing I'd wear00:08
*** McNinja has joined #openstack-nova00:09
*** melwitt has joined #openstack-nova00:09
*** leifz has joined #openstack-nova00:09
*** comstud has joined #openstack-nova00:09
*** spotz has joined #openstack-nova00:09
dansmithand most people would not know it's not that impressive, so, sounds like a good idea00:09
*** melwitt is now known as Guest6807600:09
mikalI would like to note we intended to have deleted config drive by now00:10
mikalBut yet, here we are00:10
mikalIts the gift that keeps on giving00:10
*** diga has joined #openstack-nova00:10
*** betherly has joined #openstack-nova00:11
*** fnordahl has joined #openstack-nova00:11
*** jamesdenton has joined #openstack-nova00:11
tonybmikal: we shoudl just fix the metadata service so configdrive isn't needed00:12
*** iceyao has joined #openstack-nova00:12
cburgessYeah I don't see how we can ever get rid of it at this poing given we can't do metadata over IPv600:12
tonybmikal: how hard can it be ;P00:12
cburgessand yeah metadata service is... umm... horrible00:12
tonybcburgess: it's only code from being less horrible00:12
*** Guest68076 is now known as melwitt00:12
mikalcburgess: that's probably what I'd do next if I had any time00:12
openstackgerritJohn Griffith proposed openstack/nova master: Add Cinder V3 Detach calls  https://review.openstack.org/43875000:12
mikalBut instead, I write project plans00:13
cburgesstonyb mikal Yeah I wish I had the time to fix metadata as well. Its caused us a lot of scaling problems00:13
*** kaisers has quit IRC00:13
mikalcburgess: you just need better users...00:13
cburgessmikal Don't get me started00:13
cburgessSomewhere.. someone on the internet created a chef plugin of some type that spams the hell out of metatata with request from every conciviable cloud format every seconds.00:14
cburgessI have users making 350+ metadata requests a second.00:14
cburgessIts... insane00:14
dansmithcburgess: yeah, it's super good for that00:15
dansmithcburgess: users love hitting it hard00:15
mikalcburgess: you're really going to hate vendordata then00:15
mikalCause we fan out that request to N other services00:15
*** darrenc has quit IRC00:16
*** iceyao has quit IRC00:16
cburgessdansmith Is that supposed to be in the sarcasm font?00:16
dansmithcburgess: no00:16
dansmithcburgess: I have 'em too00:16
cburgessmikal I still have to configure that though right?00:16
dansmithcburgess: run puppet every minute and slam the metadata server00:16
mikalcburgess: yes, its opt in00:16
*** jamielennox|away is now known as jamielennox00:16
mikalcburgess: but if any of those users want windows active directory registration...00:16
cburgessdansmith Ahh ok yeah, its insane to me, and they seem to not understand how its a problem00:16
dansmithyeah00:16
dansmithbut alas00:16
cburgessmikal Hmmm I might need that00:17
mikalcburgess: good news!00:17
mikalcburgess: and by good I mean bad00:17
*** darrenc has joined #openstack-nova00:17
cburgessdansmith Yeah so... like I said.. if I had the time I would propose a re-write of metadata because its horrible.00:17
mikalI could write a project plan for that00:17
mikalI'm getting quite good at them00:17
mikalNot good at getting things resourced00:17
mikalBut I have nice Microsoft Word documents00:17
cburgessLOL00:17
openstackgerritLi Yingjun proposed openstack/nova master: Error message should not include SQL command  https://review.openstack.org/43677300:19
*** sdague has quit IRC00:20
*** ZZelle has quit IRC00:23
*** sapcc-bot has quit IRC00:23
*** sapcc-bot has joined #openstack-nova00:23
*** anthonyper has quit IRC00:28
*** ijw has quit IRC00:29
*** mtanino_ has joined #openstack-nova00:29
*** ijw has joined #openstack-nova00:30
*** ijw has quit IRC00:30
*** mtanino has quit IRC00:30
*** gfhellma_ has quit IRC00:31
*** gfhellma has joined #openstack-nova00:32
*** anthonyper has joined #openstack-nova00:32
*** edmondsw has quit IRC00:33
*** iceyao has joined #openstack-nova00:33
*** edmondsw has joined #openstack-nova00:33
*** hoangcx has joined #openstack-nova00:36
*** jamesdenton has quit IRC00:37
*** iceyao has quit IRC00:38
*** edmondsw has quit IRC00:38
*** gfhellma_ has joined #openstack-nova00:39
*** gfhellma has quit IRC00:40
*** iceyao has joined #openstack-nova00:47
*** yingjun has quit IRC00:49
*** iceyao has quit IRC00:51
*** edmondsw has joined #openstack-nova00:51
*** iceyao has joined #openstack-nova00:54
*** dave-mccowan has joined #openstack-nova00:55
*** gfhellma_ has quit IRC00:56
*** iceyao has quit IRC00:59
*** fragatina has quit IRC01:01
*** nic has joined #openstack-nova01:01
*** phuongnh has joined #openstack-nova01:03
*** sambetts|afk has quit IRC01:04
*** sambetts_ has joined #openstack-nova01:07
*** edmondsw has quit IRC01:08
*** kaisers has joined #openstack-nova01:09
*** kaisers has quit IRC01:14
*** Swami_ has quit IRC01:16
*** raunak has quit IRC01:16
*** bastafidli has joined #openstack-nova01:16
*** thorst has joined #openstack-nova01:26
*** baoli has quit IRC01:28
*** Apoorva_ has joined #openstack-nova01:30
*** dave-mccowan has quit IRC01:30
*** edmondsw has joined #openstack-nova01:31
*** Apoorva has quit IRC01:33
*** Apoorva_ has quit IRC01:34
*** ljxiash has joined #openstack-nova01:36
*** fragatina has joined #openstack-nova01:36
*** dave-mccowan has joined #openstack-nova01:37
*** iceyao has joined #openstack-nova01:38
*** kevinz has joined #openstack-nova01:38
*** namnh has joined #openstack-nova01:39
*** vladikr has quit IRC01:46
*** sam_nowitzki has joined #openstack-nova01:47
*** adrian_otto has quit IRC01:51
*** yuntongjin has joined #openstack-nova01:57
*** dave-mccowan has quit IRC01:59
*** edmondsw has quit IRC02:00
*** baoli has joined #openstack-nova02:02
*** McNinja has quit IRC02:05
*** gcb has joined #openstack-nova02:06
*** eliqiao has quit IRC02:07
*** kaisers has joined #openstack-nova02:10
*** McNinja has joined #openstack-nova02:11
*** unicell has quit IRC02:14
*** mtanino_ has quit IRC02:17
*** eliqiao has joined #openstack-nova02:19
*** bkopilov has quit IRC02:27
*** kaisers has quit IRC02:28
*** baoli has quit IRC02:32
*** diga has quit IRC02:37
*** takashin has joined #openstack-nova02:42
*** thorst has quit IRC02:44
*** thorst has joined #openstack-nova02:44
*** nic has quit IRC02:45
*** thorst has quit IRC02:49
*** gongysh has joined #openstack-nova02:56
*** hongbin has joined #openstack-nova02:59
*** hongbin has quit IRC03:00
*** hongbin has joined #openstack-nova03:01
*** ljxiash has quit IRC03:11
*** dimtruck is now known as zz_dimtruck03:12
*** ljxiash has joined #openstack-nova03:12
*** zz_dimtruck is now known as dimtruck03:13
*** ljxiash has quit IRC03:16
*** ljxiash has joined #openstack-nova03:19
*** kaisers has joined #openstack-nova03:30
openstackgerritLi Yingjun proposed openstack/nova-specs master: Spec for support set vgamem for video  https://review.openstack.org/43878703:31
*** raunak has joined #openstack-nova03:34
*** zhenguo has joined #openstack-nova03:37
*** thorst has joined #openstack-nova03:45
*** mdnadeem has joined #openstack-nova03:46
*** bkopilov has joined #openstack-nova03:48
*** thorst has quit IRC03:50
openstackgerritLi Yingjun proposed openstack/nova master: libvirt: Enable custom video vgamem setting  https://review.openstack.org/41119103:51
*** baoli has joined #openstack-nova03:51
*** lucasxu has joined #openstack-nova03:53
*** gouthamr has quit IRC03:54
*** nmathew has joined #openstack-nova03:56
*** yamahata_ has quit IRC03:57
*** Dinesh_Bhor has joined #openstack-nova03:59
*** fragatin_ has joined #openstack-nova03:59
*** fragati__ has joined #openstack-nova04:01
*** yuntongjin has quit IRC04:02
*** fragatina has quit IRC04:03
*** fragatin_ has quit IRC04:04
*** tojuvone has quit IRC04:04
*** liusheng has quit IRC04:05
*** fragati__ has quit IRC04:05
*** liusheng has joined #openstack-nova04:07
*** gongysh has quit IRC04:12
openstackgerritHuan Xie proposed openstack/nova master: Make xenserver driver compatible with assert_can_migrate  https://review.openstack.org/43879204:12
*** kaisers has quit IRC04:12
*** hongbin has quit IRC04:17
*** kaisers has joined #openstack-nova04:20
*** kaisers has quit IRC04:22
*** gcb has quit IRC04:22
*** crushil has quit IRC04:22
*** psachin has joined #openstack-nova04:23
*** tlian has quit IRC04:29
*** gcb has joined #openstack-nova04:34
*** adisky_ has joined #openstack-nova04:37
*** tiendc has joined #openstack-nova04:38
*** sudipto has joined #openstack-nova04:40
*** sudipto_ has joined #openstack-nova04:40
*** sudipto_ has quit IRC04:41
*** sudipto has quit IRC04:41
*** sudipto has joined #openstack-nova04:43
*** sudipto_ has joined #openstack-nova04:43
*** Jeffrey4l__ has quit IRC04:49
*** trinaths has joined #openstack-nova04:50
*** Jeffrey4l__ has joined #openstack-nova04:52
*** kaisers has joined #openstack-nova04:52
*** baoli has quit IRC04:54
*** crushil has joined #openstack-nova04:54
*** sreeram_v has joined #openstack-nova04:54
*** lucasxu has quit IRC04:54
*** trinaths1 has joined #openstack-nova04:57
*** trinaths has quit IRC04:57
*** unicell has joined #openstack-nova04:58
*** sudipto_ has quit IRC04:58
*** sudipto has quit IRC04:59
*** sridharg has joined #openstack-nova05:00
*** ayogi has joined #openstack-nova05:06
*** udesale has joined #openstack-nova05:19
*** karthiks has joined #openstack-nova05:20
*** fragatina has joined #openstack-nova05:20
*** fragatina has quit IRC05:21
*** fragatina has joined #openstack-nova05:21
*** yamamoto has quit IRC05:24
*** trinaths1 has quit IRC05:26
*** trinaths has joined #openstack-nova05:26
*** diga has joined #openstack-nova05:29
*** udesale__ has joined #openstack-nova05:33
*** prateek has joined #openstack-nova05:34
*** udesale has quit IRC05:35
*** armax has quit IRC05:36
*** yuntongjin has joined #openstack-nova05:39
*** jaosorior has joined #openstack-nova05:41
*** larainema has quit IRC05:42
*** kaisers has quit IRC05:48
*** hshiina has joined #openstack-nova05:52
*** unicell1 has joined #openstack-nova05:56
*** unicell has quit IRC05:56
*** phuongnh has quit IRC05:59
*** phuongnh has joined #openstack-nova05:59
*** salv-orlando has joined #openstack-nova06:03
*** yamamoto has joined #openstack-nova06:04
*** phuongnh has quit IRC06:10
*** Jeffrey4l__ is now known as Jeffrey4l06:10
*** yamamoto has quit IRC06:10
*** phuongnh has joined #openstack-nova06:11
*** yamamoto has joined #openstack-nova06:11
*** fragatina has quit IRC06:12
*** tuanluong has joined #openstack-nova06:13
*** sacharya has quit IRC06:13
*** tojuvone has joined #openstack-nova06:14
*** sacharya has joined #openstack-nova06:14
*** ratailor has joined #openstack-nova06:17
*** salv-orl_ has joined #openstack-nova06:18
*** sacharya has quit IRC06:19
*** salv-orl_ has quit IRC06:20
*** salv-orl_ has joined #openstack-nova06:20
*** yamamoto has quit IRC06:21
*** salv-orlando has quit IRC06:21
*** nkrinner_afk is now known as nkrinner06:24
*** hieulq_ has joined #openstack-nova06:26
*** gk-1wm-su has joined #openstack-nova06:26
*** gk-1wm-su has left #openstack-nova06:26
*** tovin07_ has joined #openstack-nova06:27
*** masuberu has quit IRC06:27
*** artom has quit IRC06:28
*** yamamoto has joined #openstack-nova06:29
*** abhishekk has joined #openstack-nova06:29
*** satyar has joined #openstack-nova06:30
*** yamamoto has quit IRC06:30
*** ratailor has quit IRC06:35
*** udesale__ has quit IRC06:35
*** yamahata_ has joined #openstack-nova06:35
*** kaisers has joined #openstack-nova06:41
*** artom has joined #openstack-nova06:42
*** raunak has quit IRC06:45
*** mjura has joined #openstack-nova06:46
*** ratailor has joined #openstack-nova06:46
*** thorst has joined #openstack-nova06:46
*** yamamoto has joined #openstack-nova06:47
*** yamamoto has quit IRC06:47
*** sudipto_ has joined #openstack-nova06:48
*** sudipto has joined #openstack-nova06:48
*** thorst has quit IRC06:51
*** tojuvone has quit IRC06:56
*** tojuvone has joined #openstack-nova06:56
*** ljxiash has quit IRC07:00
*** ljxiash has joined #openstack-nova07:00
*** ygl has joined #openstack-nova07:03
*** ygl has left #openstack-nova07:03
*** ljxiash has quit IRC07:05
*** karthiks has quit IRC07:05
*** ljxiash has joined #openstack-nova07:06
*** ljxiash has quit IRC07:07
*** ljxiash has joined #openstack-nova07:07
*** ijw has joined #openstack-nova07:07
*** Oku_OS-away is now known as Oku_OS07:08
*** artom has quit IRC07:09
*** yamamoto has joined #openstack-nova07:10
*** rcernin has joined #openstack-nova07:11
*** ijw has quit IRC07:12
*** zsli has joined #openstack-nova07:13
*** yamamoto has quit IRC07:13
*** andreas_s has joined #openstack-nova07:13
*** Kevin_Zheng_ has joined #openstack-nova07:14
*** sacharya has joined #openstack-nova07:15
*** Kevin_Zheng_ is now known as Kevin_Zheng07:17
*** karthiks has joined #openstack-nova07:18
*** hieulq_ has quit IRC07:23
openstackgerritSivasathurappan Radhakrishnan proposed openstack/nova master: Remove mox from nova.tests.unit.virt.xenapi.test_xenapi[1]  https://review.openstack.org/43882507:26
*** lpetrut has joined #openstack-nova07:28
openstackgerritSivasathurappan Radhakrishnan proposed openstack/nova master: Remove mox from nova/tests/unit/virt/xenapi/test_xenapi.py[1]  https://review.openstack.org/43882507:28
*** tesseract has joined #openstack-nova07:34
*** markus_z has joined #openstack-nova07:34
*** gmann has quit IRC07:35
*** crushil has quit IRC07:36
*** lpetrut has quit IRC07:36
*** gmann has joined #openstack-nova07:37
openstackgerritTakashi NATSUME proposed openstack/nova-specs master: List/show all server migration types  https://review.openstack.org/40723707:38
*** jpena|away is now known as jpena07:41
*** kaisers_ has joined #openstack-nova07:45
*** carthaca_ has joined #openstack-nova07:46
*** jpena is now known as jpena|away07:54
*** leifz has quit IRC07:54
*** yuntongjin has quit IRC07:55
*** leifz has joined #openstack-nova07:56
*** tovin07_ has quit IRC07:57
Dinesh_BhorHi all, I have fresh OpenStack installed on Ubuntu 14.04 but I am unable to boot vm. Logs in n-cpu says that:  "InternalError: Nova requires libvirt version 1.2.9 or greater."07:59
*** jpena|away is now known as jpena08:01
Dinesh_BhorI tried to update libvirt version but it only installs 1.2.2. I have ubuntu 14.04 LTS.08:01
Dinesh_BhorI found some bug here: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/153246008:02
openstackLaunchpad bug 1532460 in libvirt (Ubuntu) "Please upgrade to allow virsh blockcommit in Ubuntu 14. libvirt-1.2.9 (and above)" [Undecided,Fix released]08:02
*** acabot has joined #openstack-nova08:03
*** kaisers_ has quit IRC08:07
*** ljxiash has quit IRC08:08
*** gongysh has joined #openstack-nova08:08
*** yuntongjin has joined #openstack-nova08:08
*** ljxiash has joined #openstack-nova08:08
*** ljxiash has quit IRC08:12
*** yamamoto has joined #openstack-nova08:13
*** pcaruana has joined #openstack-nova08:17
*** markus_z has quit IRC08:17
*** yamamoto has quit IRC08:19
*** kaisers_ has joined #openstack-nova08:19
*** sreeram__ has joined #openstack-nova08:21
*** ltomasbo|away is now known as ltomasbo08:21
*** sreera___ has joined #openstack-nova08:22
*** romainh has joined #openstack-nova08:22
*** masber has joined #openstack-nova08:24
*** sreeram_v has quit IRC08:25
*** sreeram__ has quit IRC08:26
*** moshele has joined #openstack-nova08:29
*** diga has quit IRC08:29
*** sreera___ has quit IRC08:31
*** yingjun has joined #openstack-nova08:33
*** romainh1 has joined #openstack-nova08:33
*** romainh1 has quit IRC08:34
*** romainh1 has joined #openstack-nova08:34
*** markus_z has joined #openstack-nova08:34
*** romainh has quit IRC08:35
*** sreeram_v has joined #openstack-nova08:36
*** diga has joined #openstack-nova08:41
gmannalex_xu:  mriedem: this looks good but new error code bug me - https://review.openstack.org/#/c/429476/408:43
*** kornica has quit IRC08:46
*** zsli has quit IRC08:47
*** karimb has joined #openstack-nova08:48
*** zsli has joined #openstack-nova08:48
*** ljxiash has joined #openstack-nova08:48
*** owalsh-afk is now known as owalsh08:57
*** vsaienk0 has joined #openstack-nova09:00
*** zzzeek has quit IRC09:00
*** Jeffrey4l has quit IRC09:00
*** Jeffrey4l has joined #openstack-nova09:00
vsaienk0Hello nova team I'm wondered why multinode tempest test is skipped on grenade multinode in base tests? http://logs.openstack.org/76/429476/4/check/gate-grenade-dsvm-neutron-multinode-ubuntu-xenial/f6613ff/logs/grenade.sh.txt.gz#_2017-02-26_23_56_30_14609:00
*** aarefiev_afk is now known as aarefiev09:02
vsaienk0I meant is it expected behavior?09:05
fricklercan someone explain the difference between default_availability_zone and default_schedule_zone? both descriptions look roughly the same to me here: https://docs.openstack.org/draft/config-reference/compute/config-options.html#id309:08
*** zzzeek has joined #openstack-nova09:12
*** yamamoto has joined #openstack-nova09:15
*** yamamoto has quit IRC09:16
*** yamamoto has joined #openstack-nova09:16
*** udesale has joined #openstack-nova09:17
*** trinaths has left #openstack-nova09:20
*** fandi has joined #openstack-nova09:20
*** zioproto has joined #openstack-nova09:23
*** tiendc has quit IRC09:25
openstackgerritGao Yuan proposed openstack/nova master: Stop using mox stubs in nova.tests.unit.api.openstack.compute.test_serversV21  https://review.openstack.org/43887309:25
*** kaisers_ has quit IRC09:25
*** dimtruck is now known as zz_dimtruck09:28
*** zsli has quit IRC09:36
*** derekh has joined #openstack-nova09:37
johnthetubaguyfrickler: I did look into all that AZ stuff when we tidied up the descriptions, but you are right, its not very clear from that09:38
fricklerjohnthetubaguy: I just opened https://bugs.launchpad.net/openstack-manuals/+bug/1668542 because looking at the code I became even more confused09:39
openstackLaunchpad bug 1668542 in openstack-manuals "nova.conf - az configuration options in Configuration Reference" [Undecided,New]09:39
*** jaosorior has quit IRC09:39
johnthetubaguyfrickler: that probably needs to be a nova bug, the text lives in nova09:39
fricklerjohnthetubaguy: added. probably the "open bug" link on the bug page could need amending then, too09:40
*** jaosorior has joined #openstack-nova09:40
fricklers/bug page/doc page/09:40
johnthetubaguyfrickler: yeah, it probably does, not sure if you can change that per page, probably worth a manuals bug for that!09:42
johnthetubaguyfrickler: ah, so one is about where the host lives by default, and one is about where instances go, I think...09:44
*** yamahata_ has quit IRC09:45
*** gongysh has quit IRC09:46
fricklerjohnthetubaguy: yes, that is my interpretation, but would be nice to get it confirmed, then I could make a patch for the docs09:50
*** lucas-afk is now known as lucasagomes09:50
fricklerjohnthetubaguy: hmm, the source for the page seems to be ./doc/config-reference/source/compute/config-options.rst in openstack-manuals, though09:52
johnthetubaguyfrickler: that thing is auto-generated by a script, so its a two part ifx09:57
johnthetubaguyfix09:57
*** yuntongjin has quit IRC09:57
openstackgerritJohn Garbutt proposed openstack/nova master: Fix default_availability_zone docs  https://review.openstack.org/43888709:58
johnthetubaguyfrickler: does that patch look like it makes it cleaer?09:59
johnthetubaguyhmm, not sure my wording is brilliant, but suggestions welcome10:00
*** gcb has quit IRC10:00
*** artom has joined #openstack-nova10:01
openstackgerritJohn Garbutt proposed openstack/nova-specs master: WIP: Backlog spec on preemptible instances  https://review.openstack.org/43864010:01
*** artom has quit IRC10:01
*** artom has joined #openstack-nova10:02
*** GnomeKing has joined #openstack-nova10:02
*** sapcc-bot has quit IRC10:03
fricklerjohnthetubaguy: ah, nice, I was just about to do a patch for doc/config-reference/source/tables/nova-availabilityzones.rst , will that get synced from the data in nova? or should I do my patch in parallel anyway?10:04
*** sapcc-bot has joined #openstack-nova10:04
johnthetubaguyfrickler: I think the sync is manual, there is a readme on how to do that in that repo somewhere10:04
johnthetubaguyfrickler: but I think you could checkout my patch on your system, inside the docs build system, to pull in the change10:04
johnthetubaguyfrickler: maybe its easier just to patch it directly for now! yeah, do it in parallel, and have a depends-on header pointing to my patch I think10:05
* johnthetubaguy feels like this should have come up before, but I don't remember it happening before10:05
fricklerjohnthetubaguy: will do after you replied to my small comments ;)10:06
* johnthetubaguy looks...10:07
bauzasmorning folks10:08
*** jed56 has joined #openstack-nova10:09
bauzasjohnthetubaguy: frickler: context around AZs ?10:09
*** hoangcx has quit IRC10:10
bauzasjohnthetubaguy: frickler: just in case you need more knowledge, there are kludges with those opts https://docs.openstack.org/developer/nova/aggregates.html#availability-zones-azs10:10
bauzassee the warning section ^10:10
johnthetubaguyyeah, its the config doc that is confusing10:10
openstackgerritJohn Garbutt proposed openstack/nova master: Fix default_availability_zone docs  https://review.openstack.org/43888710:10
johnthetubaguybauzas: its very tempting to just deprecate that one10:11
* bauzas looks at the change10:11
bauzasah, gotcha10:11
johnthetubaguyfrickler: bauzas makes a good point though, the AZ stuff was never really "finished" its all a bit broken honestly. Now placement API work should mean we can look at fixing some of that all soo10:11
johnthetubaguyn10:11
bauzasso, lemme clarify some tribal knowledge10:12
johnthetubaguybauzas: sure10:12
bauzasfirst, we have a weird concept of a "default" AZ10:13
bauzasie. controlplane services have AZs too10:13
bauzaswhile we can't actually schedule them as a target :)10:13
*** fandi has quit IRC10:13
bauzassecondly, we differenciate hosts vs. instances when they have no AZs10:14
bauzasinstead of saying "I don't care at all about AZs so the AZ field should be blank"10:15
bauzaswe then have 2 opts that are different:10:15
bauzasif you don't care about AZs for your instance, then you need to set it blank10:15
bauzasbut if you don't care about AZs for your hosts, then you need to set it as "nova"10:15
bauzasso much fun around10:15
bauzasanyway, given that, fixing AZs a long way towards, and I don't want us to diverge from the placement effort10:16
bauzassomehow, that has to be a trait10:16
johnthetubaguybauzas: yeah, in summary, its nuts10:17
*** sambetts_ is now known as sambetts10:17
bauzasyeah, I'm personnally in favor of deprecating the whole concept of AZs and just leave it at the API level10:17
bauzasinstead, computes have location traits10:17
johnthetubaguyso... once we get the cinder "AZ" and routed networks sorted, it gets interesting again10:17
bauzasand instances could request affinity based on those location traits10:17
johnthetubaguyah, generic location traits are my preference, but AZ is just one of those10:18
bauzaslong-term anyway10:18
johnthetubaguythere was a great spec on that from randall nortman, somewhere10:18
bauzasso in the meantime, what we can fix is docs10:18
bauzasbut there could be room for some slight improvement tho10:18
johnthetubaguychanging up server groups to deal with generic location specifiers, and multiple of them10:18
bauzasyeah I remember that one10:18
johnthetubaguythats the one our users really want10:19
bauzasI know10:19
johnthetubaguycool, just making that the explicit goal I guess10:19
johnthetubaguywe might want to make that a backlog spec actually10:19
bauzastbh, affinity based on location specifiers is an old old story I have in my pipe10:20
openstackgerritLee Yarwood proposed openstack/nova master: objects: Add attachment_id to BlockDeviceMapping  https://review.openstack.org/43766510:20
openstackgerritLee Yarwood proposed openstack/nova master: db: Add attachment_id to block_device_mapping  https://review.openstack.org/43759710:20
johnthetubaguylyarwood: is that the first steps of the Cinder thing?10:20
bauzasanyway, let's move on10:20
lyarwoodjohnthetubaguy: yeah I guess, I had the bdm uuid changes still in my backlog so thought I'd just do the same again for attachment_id10:21
johnthetubaguylyarwood: ah, good idea10:21
bauzaswow, Gerrit is in a bad shape10:21
*** kaisers_ has joined #openstack-nova10:21
johnthetubaguylyarwood: I have this one that could do with some eyes: https://review.openstack.org/#/c/373203/10:21
johnthetubaguyI mean you could just poke your eyes yourself, but I have a lovely spec to do that for you10:21
johnthetubaguybauzas: so I thought my internet was just slow, but you might be right10:22
bauzasHTTP502 killed me10:22
bauzasso, no, this is not internet :p10:22
johnthetubaguyoh, its tipped over into death land then10:22
lyarwoodjohnthetubaguy: haha yeah, I'll go over the spec again this morning10:22
johnthetubaguylyarwood: awesome, thank you10:22
johnthetubaguyI have a feeling I forgot some details from the discussion10:22
bauzasjohnthetubaguy: I actually wonder if we couldn't just try to fix default_availability_zone as wezll10:23
johnthetubaguybauzas: ?10:23
bauzasjohnthetubaguy: having it set to none by default would just fix a looooooot of problems10:23
bauzass/problems/misunderstandings10:23
bauzasjohnthetubaguy: and we could then deprecate default_schedule_zon10:24
johnthetubaguyat this point most folks are used to seeing the Nova AZ default I guess, I could go either way10:24
johnthetubaguyhmm, I duno, some folks want to send all builds into a certain zone at times, I think thats why HP public cloud added that10:24
bauzasjohnthetubaguy: lemme rephrase, if we could have default_availability_zone having None as default and having default_schedule_zone be deprecated, that would be a nice improvement10:24
johnthetubaguyah, I just mixed them up10:25
bauzasjohnthetubaguy: you mean, HPE wanted to default add the AZ without asking the user to do this ?10:25
johnthetubaguyyeah, maybe, duno if that breaks things, like existing deployments10:25
bauzasthat's probably then a good reason for *not10:25
bauzas*not* deprecating it10:25
*** sandanar has joined #openstack-nova10:26
*** kevinz has quit IRC10:26
johnthetubaguybauzas: its just a scheduling decision, if the user didn't specify it, it probably should be a scheduler filter switch really10:26
johnthetubaguyits all a bit of a hack right now10:26
bauzasjohnthetubaguy: that conf opt is more than that10:26
*** kaisers_ has quit IRC10:26
bauzasjohnthetubaguy: if you set default_schedule_zone to something else10:26
johnthetubaguyif it is, then the docs are wrong10:26
bauzasjohnthetubaguy: then your instance will be constrainted forever to that AZ10:27
bauzasjohnthetubaguy: yeah, I'm about to review that patch10:27
johnthetubaguyyep, anywhere you land its meant to stay there forever, I thought10:27
fricklerso let me just add our deployment scenario for reference: we have three AZs of compute nodes with local storage and do maintainance on them in turn for a single AZ at a time.10:27
bauzasjohnthetubaguy: yup, because instance.az should never be modified10:27
johnthetubaguyright, so its just a scheduling decision10:28
fricklercustomers that want HA for their service will need to deploy three instances, one per AZ10:28
johnthetubaguyfrickler: totally, that makes sense10:28
*** ljxiash has quit IRC10:28
bauzasjohnthetubaguy: in terms of placement, you're right10:28
openstackgerritGao Yuan proposed openstack/nova master: Stop using mox stubs in nova.tests.unit.api.openstack.compute.test_serversV21  https://review.openstack.org/43887310:28
*** yingjun has quit IRC10:28
*** sacharya has quit IRC10:29
bauzasjohnthetubaguy: that conf opt default instances to be placed on a specific AZ, that's what it means10:29
johnthetubaguyfrickler: the server groups stuff, once its fixed up, is how you can do that in a better way, but we got loads of placement work before we get there10:29
johnthetubaguybauzas: yep, I thats what I was trying to say, anyways10:29
bauzas(but there are ways to migrate your server out of that AZ :D)10:29
* johnthetubaguy nods10:29
fricklernow we still would like to have "don't care" instances scheduled to any of the AZs. which seems difficult, at least in the dashboard10:29
johnthetubaguyfrickler: ah, that should be the default, the dashboard may have broken that10:30
fricklerany my idea was to set default_schedule_zone differently on three API servers that are accessed round robin10:30
johnthetubaguyfrickler: like "nova boot myserver image_7" should do that10:30
bauzasfrickler: that's a separate usecase10:30
*** jsheeren has joined #openstack-nova10:31
johnthetubaguyfrickler: so I have a feeling we spoke about this a few months back, and I got confused then too10:31
bauzasfrickler: setting default_schedule_zone to None (well, to that ugly empty string rather) means "I don't care about AZs"10:31
jsheerenhi all, i looking at curl calls and filtering results on listing the servers10:31
johnthetubaguyfrickler: I thought default_schedule_zone = None does what you want10:31
bauzasbut it doesn't force the instance to stick with that AZ10:31
johnthetubaguybauzas: it should do I thought10:32
bauzasfrickler: for your usecase, you could just use a scheduling filter tho10:32
jsheerenwith a curl to "https://<api>:8774/v2.1/<tenant>/servers/detail"  i can get all the servers for that tenant10:32
jsheerenif i use "https://<api>:8774/v2.1/<tenant>/servers/detail?name=blah" i can filter to show only the blah instance10:32
bauzasjohnthetubaguy: nope, if you wanna RR between AZs, you need to set default_schedule_zone differently between your API workers10:33
jsheerenbut when i try to filter on metadata, it just returns all the servers instead of filtering on the metadata10:33
johnthetubaguyjsheeren: loads of details on here: https://developer.openstack.org/api-ref/compute/10:33
johnthetubaguyjsheeren: I don't think you can filter by everything (its a performance thing), and in some cases its a policy thing10:33
johnthetubaguybauzas: whaaaat?10:34
bauzasfrickler: see what I said above ^10:34
jsheerenfilter on metadata using: "https://<api>:8774/v2.1/<tenant>/servers/detail?metadata=%7b%22foo%22:%22bar%22%7d"10:34
*** gszasz has joined #openstack-nova10:34
bauzasjohnthetubaguy: yup10:34
bauzasjohnthetubaguy: lemme clarify10:34
*** sreeram_v has quit IRC10:35
jsheerenjohnthetubaguy: aha,gonna check the policy first; i read through the developer api-ref doc a few times now :)10:35
*** avolkov has joined #openstack-nova10:35
bauzasjohnthetubaguy: again, default_schedule_zone is just a terrible thing for saying what should be the default if the user hasn't specific --az in their boot command10:35
*** yamamoto has quit IRC10:35
johnthetubaguyjsheeren: all the available filters are listed in the docs now (thats a recent change): https://developer.openstack.org/api-ref/compute/?expanded=list-servers-detail#list-servers10:36
jsheerencompute policy: "compute:get_instance_metadata": "rule:admin_or_owner"    i would assume i can see the metadata, which i can, cause it's in the full detail10:36
bauzasthe semantics of the empty string meaning the exact same thing as if the user hasn't specify --az : ie. the instance won't be AZ-constrained10:36
johnthetubaguyjsheeren: you can see it, but not query based on it10:36
*** satyar has quit IRC10:36
johnthetubaguyjsheeren: not 100% sure, you can query based on server tags though10:36
fricklerbauzas: I will look into writing a custom filter, thx10:37
johnthetubaguybauzas: right, but None means just pick any, which appears to be the request?10:37
johnthetubaguybauzas: I am clearly missing something10:37
bauzasjohnthetubaguy: None means "leave that field unset"10:37
johnthetubaguybauzas: right, but doesn't it get set when it lands on a compute node10:38
bauzasjohnthetubaguy: I mean, None means "leave the Instance object having the AZ field unset"10:38
bauzasexactly10:38
bauzasif the Instance object doesn't have an AZ information, it will never stick to the AZ the host where it was placed belongs to10:38
jsheerenjohnthetubaguy: https://github.com/openstack/nova/blob/stable/mitaka/nova/compute/api.py#L211210:38
jsheerenmetadata is listed in the filter_mapping10:39
bauzasthere are 2 colocality informations : one for the instance and one for the host10:39
bauzasan host can belong to an AZ10:40
bauzasand one instance can belong to an host10:40
*** laci has joined #openstack-nova10:40
lacihi!10:40
bauzasso, this is transitive10:40
*** laci has left #openstack-nova10:41
bauzasone instance can be in one AZ by the transitivity of the relationship AZ -> host -> instance10:41
*** markus_z has quit IRC10:41
*** phuongnh has quit IRC10:41
bauzasthat's the default10:41
bauzasbut you can give a specific colocality information on one instance if you specify which AZ it should belong to10:42
*** mvk has quit IRC10:42
bauzasin that case, we would force to honor the transitivity by making sure we pick hosts only belonging to the same AZ10:42
johnthetubaguybauzas: was looking in the code, I was expecting AZ to get set to the host value when we set the host on the instance, somewhere near here: https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L57910:43
johnthetubaguybauzas: I can't find the right place though right now10:43
bauzasjohnthetubaguy: I would violently -1 it if I was seeing that code10:43
*** udesale has quit IRC10:43
*** namnh has quit IRC10:43
johnthetubaguybauzas: I guess I don't get why10:43
bauzasjohnthetubaguy: because the AZ information attached to the instance is what the user expressed10:43
johnthetubaguythats in the build request10:43
bauzasnot the result of the placement decision we made10:44
bauzaswell10:44
johnthetubaguyyeah, that sounds wrong to me10:44
bauzasfirst, build request is only temporary10:44
johnthetubaguyyeah, I was meaning the other one10:44
bauzassecondly, I agree, it's rather RequestSpec10:44
johnthetubaguyyeah, request spec, my bad10:44
bauzasbut I wrote that object later10:44
bauzasso10:44
bauzasa move could be to totally remove the instance AZfield10:45
bauzasAZ field10:45
bauzasI mean, deprecate it at the object level, and wait for a major version bump to remove it10:45
johnthetubaguyinstance.host tells you the current host, instance.az feels like it should be similar10:45
johnthetubaguybut thats just me10:45
johnthetubaguyanyways, I think I get enough for the docs patch now10:46
jsheerenjohnthetubaguy: tags look like an option, but we're still on mitaka .. :(10:46
bauzasjohnthetubaguy: no, that's then duplicate information10:46
bauzasjohnthetubaguy: I by far prefer to only keep instance.host and leave the transitivity to determine an instance AZ10:46
johnthetubaguybauzas: it is duplicating host, but its kinda useful, its the AZ cached at the time the instance landed on the host10:46
johnthetubaguyjust like flavor10:46
bauzasthere are a full list of bugs related to the fact we badly manage that relationship10:47
johnthetubaguybut anyways, I clearly see this differently, needs a spec to sort that out10:47
*** ijw has joined #openstack-nova10:47
*** ijw has quit IRC10:47
bauzaswell, you're kinda busy this cycle, so I could give an hand10:47
johnthetubaguywe should record, where we first landed, and what the user requested, I believe10:47
johnthetubaguybauzas: I have no time to sort that out this cycle, if you have cycles feel free10:48
bauzasbut honestly, touching AZs is like trying to unfuse a bomb10:48
* johnthetubaguy nods10:48
bauzascertainly not a thing for people willing to contribute at first hand, unfortunately :(10:48
johnthetubaguybauzas: maybe a backlog spec to capture the thoughts?10:48
*** thorst has joined #openstack-nova10:48
bauzassorting all that out took me like 5 cycles10:48
bauzasI could do that10:49
*** yamamoto has joined #openstack-nova10:49
bauzasI'm pretty free this cycle since I really wanted to make reviews10:49
johnthetubaguybauzas: include the use cases frickler talks about, its easier than the harder server groups one, and its what folks want10:49
* bauzas noting it10:49
bauzasthe fact that one would want to RR between AZs ?10:49
johnthetubaguyyeah, just want to capture these requests, I know my product org asked me some questions on that10:49
johnthetubaguyRR?10:49
johnthetubaguyround robin10:50
bauzasround-robin, my bad10:50
johnthetubaguyyeah, not sure its round robin you want10:50
johnthetubaguyyou want to balance load between them all10:50
bauzaswell, it's a placement question for sure10:50
*** sreeram_v has joined #openstack-nova10:50
bauzasbecause RR is one way to spread your load10:50
johnthetubaguylike if AZ_3 fills up, send more builds to the other two, if folks don't have a preference10:50
bauzasyeah10:51
johnthetubaguythats what people *really* want10:51
johnthetubaguyfrickler10:51
johnthetubaguyoops10:51
johnthetubaguyfrickler please do correct me if I am wrong ^10:51
bauzasto me, the default_schedule_zone flag would rather be "stick_with_the_AZ_I'm_scheduled_for_all_my_lifecycle" and a boolean as value10:52
fricklerwell that is one use case. but thinking about it, the other one would be: create three instances in three different AZs10:52
bauzasthat's a scheduling thing10:52
johnthetubaguyyeah, thats the server groups one10:52
bauzasyou could have different placement strategies10:52
bauzasusing weighters or other things10:52
johnthetubaguyif you just create one instance, and you don't care were it goes, try get an even load between all AZs so the folks targeting to a specific AZ are able to get there10:53
*** esberglu has joined #openstack-nova10:53
johnthetubaguybauzas: there is a clear 80% default here I think10:53
bauzasso, my thoughts are10:53
*** thorst has quit IRC10:53
johnthetubaguybauzas: lets get them in the spec, I need to get on with other things10:53
bauzasfirst boot schedule is a placement decision10:53
*** sam_nowitzki has quit IRC10:53
bauzasbut a move operation is depending on that first placement decision or not10:53
bauzasyeah, lemme try to capture all the best I can10:53
johnthetubaguyping me for a review, I am interested it getting that all down on paper10:54
*** sreeram_v has quit IRC10:55
*** yamamoto has quit IRC10:55
sfinucanjohnthetubaguy: I think I have all comments on https://review.openstack.org/#/c/364468/ addressed now10:56
bauzasjohnthetubaguy: sure thing10:56
*** sreeram_v has joined #openstack-nova10:57
jsheerenjohnthetubaguy: small update on filtering on metadata.  if you are an admin user, you can use the filter  detail?metadata=<urlencoded-metadata-json>  but not as a regular user10:57
jsheerenso, this is a policy issue then?10:57
*** esberglu has quit IRC10:57
*** salv-orl_ has quit IRC10:57
johnthetubaguyjsheeren: possibly, its a really nasty DB query, so you probably don't want to allow that10:58
jsheerenjohnthetubaguy: in the policy.json everything with metadata in the string has admin_or_owner so i'm confused11:00
jsheerengoing to look at the code again .. :-)11:00
akijakhi, I've found a bug in nova concerning rebuilding and 'hw_disk_bus' image property (https://bugs.launchpad.net/nova/+bug/1667667), I'm looking for someone who could give me some directions how to fix that :) can you help?11:01
openstackLaunchpad bug 1667667 in OpenStack Compute (nova) "Rebuilding instance ignores image's property hw_disk_bus" [Low,Confirmed]11:01
*** iceyao has quit IRC11:03
*** sreeram_v has quit IRC11:03
jsheerenhttps://github.com/openstack/nova/blob/stable/mitaka/nova/compute/api.py#L3304 check_policy(context, 'get_all_instance_%s' % metadata_type,instance) .. but in the policy: "compute:get_all_instance_metadata": "rule:admin_or_owner"11:03
*** sreeram_v has joined #openstack-nova11:04
*** salv-orlando has joined #openstack-nova11:05
*** sdague has joined #openstack-nova11:06
*** prateek_ has joined #openstack-nova11:07
*** sreeram_v has quit IRC11:08
*** nicolasbock has joined #openstack-nova11:09
*** mvk has joined #openstack-nova11:14
*** prateek has quit IRC11:14
*** sreeram_v has joined #openstack-nova11:15
*** prateek has joined #openstack-nova11:15
*** sreeram_v has quit IRC11:19
*** kaisers_ has joined #openstack-nova11:22
*** ratailor has quit IRC11:25
*** sudipto has quit IRC11:32
*** sudipto_ has quit IRC11:32
johnthetubaguybauzas: can you take over that patch and fix up the comments how you think makes sense: https://review.openstack.org/#/c/43888711:36
openstackgerritjichenjc proposed openstack/nova master: api-ref: Body verification for os-hypervisors.inc  https://review.openstack.org/38369111:36
*** yamamoto has joined #openstack-nova11:38
*** sreeram_v has joined #openstack-nova11:38
*** sridharg has quit IRC11:39
*** kaisers_ has quit IRC11:41
*** nmathew has quit IRC11:41
*** tojuvone has quit IRC11:41
*** tojuvone has joined #openstack-nova11:41
*** karthiks has quit IRC11:47
*** yamamoto has quit IRC11:49
*** sean-k-m1 is now known as sean-k-mooney11:49
*** tbachman has quit IRC11:51
*** yassine has quit IRC11:52
andymccrare the [placement_database] specifics configured in nova.conf working? I'm noticing that although everything is working and no errors/issues are caused the database specified is empty - wondering if thats a configuration issue my side11:52
*** yassine has joined #openstack-nova11:53
*** betherly has quit IRC11:53
johnthetubaguyandymccr: hmm, thats a bit surprizing for sure11:54
*** diga has quit IRC11:54
*** markus_z has joined #openstack-nova11:54
openstackgerritjichenjc proposed openstack/nova master: Prevent delete cell0 in nova-manage command  https://review.openstack.org/43347611:54
*** betherly has joined #openstack-nova11:55
andymccrjohnthetubaguy: there is a probably high chance its a config issue my side :) but then i almost expect errors somewhere - so thought it'd be worth checking before i release11:55
*** jsheeren has left #openstack-nova11:57
*** jsheeren has quit IRC11:57
fricklerandymccr: https://review.openstack.org/362766 does still seem pending. did you check the api-db?11:57
*** artom has quit IRC11:58
*** artom has joined #openstack-nova11:59
*** salv-orlando has quit IRC12:01
andymccrfrickler: ahh ok thanks! so the separation of the database hasn't merged yet - i figured it must be using the nova_api one since it was working and not creating errors.12:01
*** ildikov has quit IRC12:01
andymccrbut good to know i havent misconfigured it (yet) :)12:02
*** tojuvone has quit IRC12:02
*** tojuvone has joined #openstack-nova12:03
*** ildikov has joined #openstack-nova12:03
*** smatzek has joined #openstack-nova12:04
sean-k-mooneysfinucan: free to pop into the neutron channel for a sec12:04
*** karthiks has joined #openstack-nova12:04
*** johnthetubaguy has quit IRC12:04
*** smatzek_ has joined #openstack-nova12:05
*** smatzek has quit IRC12:05
sean-k-mooneysfinucan: kevinbenton:  has a patch for port filtering for os-vif that relates to the security behavior we were disscussing last week12:05
sean-k-mooneyhttps://review.openstack.org/#/c/438272/212:05
fricklerandymccr: still the current situation seems pretty broken, https://review.openstack.org/#/c/349021/13/releasenotes/notes/placement-database-5aa94ece29eab820.yaml is in place and if people follow that advice, their setup is broken. guess you could open a bug for that12:07
*** bkopilov has quit IRC12:07
openstackgerritJohn Garbutt proposed openstack/nova-specs master: Add use-local-scheduler spec  https://review.openstack.org/43893612:08
openstackgerritKevin Benton proposed openstack/os-vif master: Don't install iptables rules if neutron is filtering  https://review.openstack.org/43827212:09
*** fungi has quit IRC12:11
*** tuanluong has quit IRC12:12
*** bvanhav_ has joined #openstack-nova12:13
*** aysyd has joined #openstack-nova12:14
*** johnthetubaguy has joined #openstack-nova12:14
andymccrfrickler: hmm that placement sync bit has been removed12:14
* johnthetubaguy hmm, got disconnected there12:16
johnthetubaguyandymccr: frickler was right, we send stuff to the API db12:16
johnthetubaguyandymccr: if you configure the compute nodes to have the api-db point to the placement API, you might get what you want12:16
johnthetubaguyits not officially supported right now, but thats probably what you want12:16
johnthetubaguyoops12:16
johnthetubaguyI mean placement-api conf has api-db point to placement-db12:16
johnthetubaguyandymccr: ^12:16
*** bvanhav_ is now known as bvanhav12:16
*** iceyao has joined #openstack-nova12:16
johnthetubaguythats assuming all the tables are created in there now12:16
johnthetubaguybut doing api-db sync on a node that has api pointing to placement12:16
johnthetubaguyapi-db pointing, that is12:17
*** fungi has joined #openstack-nova12:17
*** bvanhav has quit IRC12:19
*** bvanhav_ has joined #openstack-nova12:20
andymccrjohnthetubaguy: not really looking to work around it until its ready i guess :) hoping there is a decent migration path though so its unobtrusive - just wanted to make sure i wasnt doing something bogus since the configuration is still in the sample conf with an explanation and recommendation that it is used.12:20
openstackgerritJohn Garbutt proposed openstack/nova-specs master: Add use-local-scheduler spec  https://review.openstack.org/43893612:20
johnthetubaguyandymccr: its worth avoiding the migration path12:20
*** iceyao has quit IRC12:21
johnthetubaguyandymccr: but we sure will have to write one12:21
johnthetubaguyandymccr: BTW do you like the idea in this spec: https://review.openstack.org/438936 Basically give you less services you need to install and run12:21
* johnthetubaguy goes for some lunch12:22
andymccrjohnthetubaguy: reading - from our perspective fewer containers == better, if they aren't required it definitely makes sense to me12:23
johnthetubaguyandymccr: cool, yeah, placement has changed the need for the separate process12:24
*** sreeram_v has quit IRC12:26
*** irenab_ has joined #openstack-nova12:26
*** ayogi has quit IRC12:30
*** ijw has joined #openstack-nova12:31
*** yamamoto has joined #openstack-nova12:34
*** yamamoto has quit IRC12:35
*** yamamoto has joined #openstack-nova12:35
*** larainema has joined #openstack-nova12:35
*** amotoki has joined #openstack-nova12:35
*** ijw has quit IRC12:36
*** kaisers_ has joined #openstack-nova12:37
*** Dinesh_Bhor has quit IRC12:39
*** lpetrut has joined #openstack-nova12:42
*** salv-orlando has joined #openstack-nova12:42
*** thorst has joined #openstack-nova12:47
*** iceyao has joined #openstack-nova12:47
*** ljxiash has joined #openstack-nova12:48
*** breton has joined #openstack-nova12:51
bretonhi12:51
bretonis it a known problem that having role admin in any project i can edit flavors for all users?12:52
*** kaisers_ has quit IRC12:52
*** kaisers_ has joined #openstack-nova12:53
*** markmcclain has quit IRC12:53
*** yamamoto has quit IRC12:54
*** romainh1 has quit IRC12:55
*** romainh has joined #openstack-nova12:56
fricklerbreton: admin anywhere is admin everywhere, yes12:56
bretonok, 968696 then12:57
frickleryes, was about to paste that bug link ;)12:58
*** Hosam has joined #openstack-nova12:59
alex_xujohnthetubaguy: sdague, just checked, there isn't any API work in the priority tasks, but i guess there still have some work can be tracked by the API team? so probably we can talk about that in the tomorrow api meeting12:59
*** takashin has left #openstack-nova13:00
*** markmcclain has joined #openstack-nova13:00
*** jwcroppe has joined #openstack-nova13:02
*** tbachman has joined #openstack-nova13:02
*** yingjun has joined #openstack-nova13:02
*** kaisers_ has quit IRC13:03
*** tblakes has joined #openstack-nova13:04
*** kaisers_ has joined #openstack-nova13:04
*** satyar has joined #openstack-nova13:04
*** _samdeep has joined #openstack-nova13:05
*** edmondsw has joined #openstack-nova13:05
_samdeepHi All13:07
-openstackstatus- NOTICE: restarting gerrit to address performance problems13:07
*** ChanServ changes topic to "restarting gerrit to address performance problems"13:07
_samdeepI want to fetch instance properties inside a filter13:07
_samdeepbut I am unable to get it using13:09
_samdeepobjects.Instance.get_by_uuid(spec_obj.obj_context, spec_obj.instance_uuid)13:09
_samdeepany idea how to get these details?13:09
*** jpena is now known as jpena|lunch13:09
*** Hosam_ has joined #openstack-nova13:10
johnthetubaguyalex_xu: wasn't the policy docs included?13:11
*** edand has joined #openstack-nova13:11
johnthetubaguyalex_xu: but yeah, we can keep meeting to keep the other stuff moving anywys13:11
*** yamamoto has joined #openstack-nova13:11
*** kylek3h has joined #openstack-nova13:12
*** jaypipes has joined #openstack-nova13:13
*** Hosam has quit IRC13:14
*** iceyao has quit IRC13:15
*** hshiina has quit IRC13:15
alex_xujohnthetubaguy: yeah, anyway if you and sdague have any plan or something you want me help on, let us talk that in the meeting13:16
johnthetubaguyalex_xu: there was the API concepts guide that needed finishing, and a few other loose ends13:16
johnthetubaguyalex_xu: we should go through that as a team at the next meeting I guess13:17
*** yamamoto has quit IRC13:17
alex_xujohnthetubaguy: yea13:17
*** sudipto_ has joined #openstack-nova13:17
*** sudipto has joined #openstack-nova13:17
sdaguealex_xu: yeh, I think the thing is that when we got there most of the mindset had been around policy and the limits setting api going into keystone13:17
sdagueI honestly think that limits in keystone would be something that we should keep api team focus on this cycle13:18
alex_xusdague: what is limits in keystone, i probably didn't follow that in the ptg13:18
openstackgerritJohn Garbutt proposed openstack/nova master: Add device_id when creating ports  https://review.openstack.org/43154513:19
sdaguethe new idea on how hierarchical quotas is going to work is that we're going to store limits in keystone13:19
openstackgerritJohn Garbutt proposed openstack/nova master: Stop leaking ports on port_create timeout  https://review.openstack.org/34718313:19
*** irenab_ has quit IRC13:19
sdagueso the entire hierarchy is efficiently mapped there13:19
sdaguebrb13:19
alex_xuah, i probably have some memory about that13:20
alex_xuI remember we said keystone need to tell nova about the hierarchy13:20
*** lucasagomes is now known as lucas-hungry13:21
alex_xuanyway i will grab the etherpad to get more context before meeting13:21
*** irenab_ has joined #openstack-nova13:21
*** iceyao has joined #openstack-nova13:23
*** dave-mccowan has joined #openstack-nova13:25
*** Hosam_ has quit IRC13:26
openstackgerritJohn Garbutt proposed openstack/nova-specs master: Add prep-for-network-aware-scheduling-pike spec  https://review.openstack.org/43248913:26
*** jaypipes has quit IRC13:28
*** bvanhav__ has joined #openstack-nova13:31
*** bvanhav_ has quit IRC13:32
openstackgerritStephen Finucane proposed openstack/nova master: Stop using mox in compute/test_hypervisors.py  https://review.openstack.org/32681413:32
*** bastafidli has quit IRC13:32
*** amoralej is now known as amoralej|lunch13:32
*** Hosam has joined #openstack-nova13:33
-openstackstatus- NOTICE: ok gerrit is back to normal13:36
*** ChanServ changes topic to "ok gerrit is back to normal"13:36
*** sudipto_ has quit IRC13:36
*** sudipto has quit IRC13:36
*** Hosam has quit IRC13:38
*** mdrabe has joined #openstack-nova13:38
zioprotojohnthetubaguy, I am about to build ubuntu packages on top of commit 2e05c82b807624b8420df4c94d68b75563b230d2 . Is that a good candidate for new stable/mitaka tag ?13:39
*** jaypipes has joined #openstack-nova13:40
johnthetubaguyzioproto: unsure, I would ask lyarwood about that13:40
*** tojuvone has quit IRC13:41
*** salv-orlando has quit IRC13:42
*** edmondsw_ has joined #openstack-nova13:42
*** ChanServ changes topic to "This channel is for Nova development. For support of Nova deployments, please use #openstack. Please see: https://wiki.openstack.org/wiki/Nova/Ocata_Release_Schedule"13:43
zioprotolyarwood, ping me when you are here :)13:43
-openstackstatus- NOTICE: gerrit is back to normal and I don't know how to use the openstackstaus bot13:43
lyarwoodzioproto: https://review.openstack.org/#/c/438570/ but I'd wait until the tag lands13:43
*** edmonds__ has joined #openstack-nova13:43
sfinucanmacsz: I wonder if it's time to look at switching back to nose, now that it supports parallel testing? :P https://review.openstack.org/#/c/43511113:44
zioprotogreat that is the correct commit13:44
*** tojuvone has joined #openstack-nova13:45
lyarwoodzioproto: right but I'd wait until the tag lands in the repo to build, we've already respun that to include an additional commit in the last 24 hours13:45
lyarwoodzioproto: it shouldn't be long until that lands tbh13:45
*** edmondsw has quit IRC13:46
*** hoangcx has joined #openstack-nova13:46
*** kaisers_ has quit IRC13:47
*** edmondsw_ has quit IRC13:47
zioprotothanks13:48
*** yassine has quit IRC13:49
*** gouthamr has joined #openstack-nova13:50
*** zhurong has joined #openstack-nova13:52
*** yassine has joined #openstack-nova13:52
*** baoli has joined #openstack-nova13:52
*** diana_clarke has left #openstack-nova13:52
*** xyang1 has joined #openstack-nova13:54
*** baoli_ has joined #openstack-nova13:54
*** esberglu has joined #openstack-nova13:54
bauzasjohnthetubaguy: I do wonder, do we need to change some modules if we're just changing where a conf opt is set ?13:55
bauzasjohnthetubaguy: like the one you made about moving default_schedule_az13:55
johnthetubaguybauzas: its still looked up by doing CONF.xxx_xxx13:55
bauzasyeah I know13:55
johnthetubaguybauzas: if the tests pass we should be fine13:55
bauzasbut I do wonder if we weren't explicitely saying "this or that"'13:56
bauzasoh wait13:56
bauzasthat's a global opt13:56
johnthetubaguyits not moving group, right13:56
johnthetubaguyits just in the default group13:56
bauzaswe're only do that for groups13:56
bauzasyeah13:56
bauzasnevermind then13:56
*** Oku_OS has quit IRC13:56
*** mlavalle has joined #openstack-nova13:56
bauzasjohnthetubaguy: FWIW, saw your spec about local scheduler, will review it soon13:57
lyarwoodhmmm is gerrit still messed up for anyone?13:57
* lyarwood f5's a few times13:57
johnthetubaguymine seems OK now, but its worth a shift-F5 maybe?13:58
johnthetubaguybauzas: that the one we discussed at the PTG13:58
*** baoli has quit IRC13:58
*** liangy has joined #openstack-nova13:58
bauzasjohnthetubaguy: yeah I remember13:58
johnthetubaguyalthough I don't remember quite when we covered it13:58
lyarwoodah there we go13:58
bauzastbh, sometimes my French tricks me during summits13:59
bauzasbut I was pretty following that convo13:59
*** edmondsw has joined #openstack-nova13:59
bauzass/summits/f2f13:59
*** edmonds__ has quit IRC13:59
*** mlavalle has quit IRC14:00
*** mlavalle has joined #openstack-nova14:00
*** jaypipes has quit IRC14:01
*** openstackgerrit has quit IRC14:03
*** bkopilov has joined #openstack-nova14:03
*** mriedem has joined #openstack-nova14:07
*** bastafidli has joined #openstack-nova14:07
*** openstackgerrit has joined #openstack-nova14:08
*** vladikr has joined #openstack-nova14:08
openstackgerritMatthew Booth proposed openstack/nova master: libvirt: Fix races with nfs volume mount/umount  https://review.openstack.org/38385914:08
openstackgerritMatthew Booth proposed openstack/nova master: libvirt: Pass instance to connect_volume and disconnect_volume  https://review.openstack.org/43897014:08
*** Oku_OS has joined #openstack-nova14:09
*** fyxim has quit IRC14:09
*** vladikr has quit IRC14:09
*** vladikr has joined #openstack-nova14:10
*** jpena|lunch is now known as jpena14:10
*** fyxim has joined #openstack-nova14:12
*** yamamoto has joined #openstack-nova14:13
*** kfarr has joined #openstack-nova14:13
*** iceyao has quit IRC14:14
*** lucas-hungry is now known as lucasagomes14:15
*** jaypipes has joined #openstack-nova14:16
*** crushil has joined #openstack-nova14:18
*** yamamoto has quit IRC14:18
*** lpetrut has quit IRC14:19
*** ljxiash has quit IRC14:20
mriedemmdbooth: so you plumbed an instance through for mount/unmount but i don't see where you are using the instance counting to tell when it's OK to unmount the volume in the case of multi-attach?14:20
mdboothmriedem: In the next patch. I explain in the commit message.14:21
mdboothmriedem: I could squish them together if you like, but as I explained in the commit message I think it's clearer this way.14:21
mriedemnext patch being https://review.openstack.org/#/c/383859/ ?14:22
mdboothJust makes it a bit easier to read imho, because this is a mechanical change which touches a bunch of files.14:22
mriedembecause as i commented in that change, i don't see where you're looking at the set of attachments for the same volume to see when it's fully gone14:22
mriedemalso,14:22
mriedemthis is jumping the gun a bit14:22
*** sudipto_ has joined #openstack-nova14:22
*** sudipto has joined #openstack-nova14:22
mdboothmriedem: Yeah, that one14:22
mdboothmriedem: Originally I thought so, which is why I removed it promptly when it turned out it was problematic.14:23
mriedemi think the plan was,14:23
mdboothHowever, I keep hearing multi-attach noises, and this change allows it to work with multi-attach14:23
mdboothI don't want my code to be a barrier to that14:23
mriedemwe don't even call disconnect_volume on the volume driver if cinder is reporting more than one attachment for the same volume/host14:23
lyarwoodyeah that's the plan in the cinderv3 spec14:24
mriedemthat's in johnthetubaguy's spec somewhere14:24
* mriedem digs14:24
*** mdnadeem has quit IRC14:24
mdboothSurely that's wrong, because it depends entirely on the volume driver implementation?14:24
mdboothIf it's a direct attachment to the instance rather than eg a host mount, that's not going to work correctly14:25
lyarwoodhttps://review.openstack.org/#/c/373203/15/specs/pike/approved/cinder-new-attach-apis.rst@19614:25
*** jamesdenton has joined #openstack-nova14:25
*** zz_dimtruck is now known as dimtruck14:25
mdboothYeah, I don't think you can do that at the api level. It's a driver thing.14:26
johnthetubaguyI am curious, reading the scroll back14:26
*** sacharya has joined #openstack-nova14:26
lyarwoodmdbooth: IIRC cinderv3 should tell us if the connection is shared or not directly from the volume driver14:26
johnthetubaguyso its the cinder driver that tells the cinder API what should happen14:26
*** tlian has joined #openstack-nova14:26
johnthetubaguywe pass the cinder driver details from os-brick in the connector14:26
mdboothlyarwood: But it can't tell you if the driver needs to perform a global action or not14:26
johnthetubaguycinder folks seemed to think that could be specific enough for our needs14:26
mdboothe.g. connecting a gluster volume directly to a domain via a monitor call14:26
mdboothvs mounting a gluster volume on the host and passing a file to the domain14:27
mdboothThe gluster driver supports both of those things currently, and only it knows which of them it's doing14:27
johnthetubaguyso the cinder backend needs to tell cinder API what happens, if that needs to know which one we are doing, it needs to go into the connector, I assume?14:28
mdboothSo no higher level can decide whether or not to call disconnect14:28
lyarwoodah it's not configured locally on the host is it?14:28
johnthetubaguythere is no higher level deciding here14:28
johnthetubaguyits the driver14:28
lyarwoodconnection_info isn't telling it which one to do?14:28
mdboothlyarwood: No14:28
johnthetubaguyso it needs to add that now14:28
lyarwoodyeah14:28
johnthetubaguyand default to a global lock if that might be possibe14:28
mdboothIt literally can't14:28
johnthetubaguyand it doesn't know which14:28
mdboothAnd it's none of its business anyway14:29
johnthetubaguyit is now14:29
mdboothIn the gluster case it's based on the qemu and libvirt versions on the host14:29
mdboothcinder doesn't know that14:29
johnthetubaguyso what we are saying, I think, is the cinder driver, on the cinder side, needs to tell us if we need the lock or not14:29
mriedemwe can tell cinder via the connector dict14:29
smcginnisThere is no gluster driver, but anyway...14:29
mdboothAs it happens we can safely remove it, but it's still an example of how cinder cannot know this14:29
johnthetubaguyto make that possible cinder always stores the connector I think14:30
mdboothIt's a host-side driver implementation detail14:30
mdboothAll cinder knows is that there will be a connection from the host14:30
smcginnisI'm trying to read the scrollback, but not sure what the issue is here.14:30
johnthetubaguymy preference is to always call os-brick, and tell it what we know14:30
*** sacharya has quit IRC14:30
mdboothIt's not cinder's business where that comes from14:30
johnthetubaguywould that make things happier?14:30
mdboothjohnthetubaguy: Yup. That's also entirely consistent with my patch.14:31
*** smatzek_ has quit IRC14:31
johnthetubaguymdbooth: I am totally fine with that approach, but I guess we will have to version that somehow, but thats fine14:31
mdboothjohnthetubaguy: version what?14:31
johnthetubaguydeciding if we always call detach14:32
*** jdandrea has joined #openstack-nova14:32
mriedemmdbooth: the nfs volume driver in nova today doesn't call os-brick right14:32
mriedem?14:32
johnthetubaguyalthough maybe thats what we always do today anyways?14:32
mriedemjohnthetubaguy: we always call disconnect_volume on the volume driver today14:32
mdboothmriedem: No, it doesn't. None of the fs backed drivers do, I think.14:32
lyarwoodyeah correct14:32
mriedemjohnthetubaguy: then the nfs vol driver just handles a "device is busy" error and ignores it on umount14:32
johnthetubaguymriedem: ah, fair enough14:33
mdboothmriedem: ... which is broken for a few reasons.14:33
mriedemmdbooth's patch https://review.openstack.org/#/c/383859/ is adding ref counting14:33
mriedemso we don't blindly do that14:33
johnthetubaguyso all this shared connection stuff is the very last bit of the cinder API changes14:33
mdboothYeah14:33
mdboothWell "ref counting"14:33
johnthetubaguyif we don't need it, thats cool14:33
mdboothBecause our connect and disconnect calls don't actually match up in practise14:34
*** bastafidli has quit IRC14:34
jdandreaCan someone please clarify? From Placement API doc: "The placement service tracks the inventory and usage of each provider." Does the Placement service *perform* placement, or is it a means to that end, or is it something else?14:34
mriedem"ref counting" is how i'm summarizing with wavy high-level hands a 1200 LOC patch :)14:34
*** bastafidli has joined #openstack-nova14:34
mdboothIt's not that big, is it?14:34
* mdbooth checks14:34
mriedemmdbooth: massive14:34
mdboothEurgh, it bloody is14:34
mriedemjdandrea: nova-scheduler performs the actual placement,14:35
mriedemthe placement service is the means to the end14:35
mdboothAnyway, have a look at how big glusterfs is using it :)14:35
jdandreamriedem Thank you! My brain was running in circles, confused as to why it isn't called an Inventory API, f'rinstance.14:35
mdboothIt's all about error handling, and it can be reused without modification by all the other filesystem drivers14:35
mriedemjdandrea: the placement service holds the global view on resources in the deployment, and nova-scheduler asks it which resource providers it knows about can fit a given instance build/move request14:35
jdandreamriedem *nodnod* got it14:36
mdboothmriedem: Look at this: https://review.openstack.org/#/c/423402/14:36
jdandreaAppreciatd!14:36
jdandrea(and also appreciated)14:36
mdboothI can do that to ever other filesystem driver14:36
jdandrea:)14:36
mriedemmdbooth: still https://review.openstack.org/#/c/383859/19/nova/virt/libvirt/volume/mount.py@19214:37
mriedemwhat am i missing there?14:37
mdboothmriedem: It's aset14:37
mdbootha set14:37
mdboothSo you can add (vol_a, instance_a) and (vol_a, instance_b)14:37
mdboothand they're different things14:38
*** amoralej|lunch is now known as amoralej14:38
mdboothWhen you remove (vol_a, instance_b), the mountpoint is still in use14:38
mdboothThere's a test for it14:38
mriedemah because self.attachments is still len == 114:38
mdboothYeah14:38
mdboothmriedem: Anyway, don't look at this as a 1200 line nfs driver patch. It's a 1200 line driver for every filesystem volume driver with really good error handling and really good tests.14:40
*** tlian has quit IRC14:40
mriedemyeah i know - you also told me how really good it was right before rc1 and i found an issue in there, so the size and complexity does matter :)14:40
mriedemnot trying to knock it, but you know14:40
mriedemi was just trying to sort out why the multiattach stuff was playing into it since the new bottom patch in the series is new14:41
johnthetubaguymdbooth: is there are reason not to use the usual oslo.concurrency lock thing instead of using threading directly?14:41
mdboothjohnthetubaguy: Probably. Do you have a specific?14:41
johnthetubaguymdbooth: well I was just expecting to see us generate a string, and use that for the lock, in your locking patch14:42
*** Matias has quit IRC14:42
*** kaisers_ has joined #openstack-nova14:43
mdboothjohnthetubaguy: I think my solution is much simpler. I don't think oslo.concurrency locks were really designed for this.14:43
*** yingjun has quit IRC14:43
johnthetubaguymdbooth: https://review.openstack.org/#/c/383859/19/nova/virt/libvirt/volume/mount.py@183 and https://review.openstack.org/#/c/383859/19/nova/virt/libvirt/volume/mount.py@295 and https://review.openstack.org/#/c/383859/19/nova/virt/libvirt/volume/mount.py@6214:44
johnthetubaguymdbooth: its just not following the pattern I was expecting that we know is eventlet friendly14:44
mdboothjohnthetubaguy: I don't think you can do conditions with oslo.concurrency for eg, can you?14:44
*** READ10 has joined #openstack-nova14:44
*** Matias has joined #openstack-nova14:44
mdboothjohnthetubaguy: This is all eventletised, as I have discovered14:44
mdboothIt's monkey patched14:44
johnthetubaguyyeah, I figured it had to be14:45
mdboothI was going to use evently primitives explicitly, in fact I think I had one version where I did that14:45
mdboothBut iirc the api is a bit crippled compared to the python threading api14:45
*** sridharg has joined #openstack-nova14:45
johnthetubaguyjust I know getting this stuff "correct" is surpizingly hard, I was kinda expecting us to use some more higher level construct, but I am probably missing something14:45
*** thorst is now known as thorst_afk14:46
openstackgerritStephen Finucane proposed openstack/nova master: Remove mox in nova/tests/unit/compute/test_shelve.py (3)  https://review.openstack.org/34264814:47
johnthetubaguymdbooth: its probably the need for notify_all that rings alarm bells, I remember that being tricky to get correct14:47
mriedemdansmith: melwitt: sdague: btw, i enjoyed some wonderful high fiber whole grain cereal this morning14:47
johnthetubaguymdbooth: we could just use a regular lock to protect the counts, and if we did, I am not sure what we would loose14:47
mdboothjohnthetubaguy: Not really, if you ensure all your waits are guarded.14:47
dansmithmriedem: sounds like my morning 18 minutes from now14:48
*** kaisers_ has quit IRC14:48
mdboothjohnthetubaguy: You'd lose condition.wait(), which is a really useful construct14:49
*** lpetrut has joined #openstack-nova14:49
johnthetubaguymdbooth: but why not guard the count with a regular lock? with eventlet I can't see there being much of a gain between the two, and one is more obviously "OK ish"14:49
johnthetubaguyI am probably missing something big14:49
*** yingjun has joined #openstack-nova14:49
mdboothjohnthetubaguy: Yeah, so I want to wait until the in-use count reaches zero.14:50
mdboothI take the lock14:50
mdboothIt's not zero14:50
mdboothWhat do I do?14:50
mdboothThis is exactly what the Condition api is for14:51
johnthetubaguymdbooth: ah, so its because you want to wait rather than just sleep or something dumb like that, thats what I was missing14:51
*** burt has joined #openstack-nova14:51
mdboothYeah, otherwise you have to drop the lock and poll14:51
*** felipemonteiro_ has joined #openstack-nova14:52
*** felipemonteiro has joined #openstack-nova14:52
mdboothThat uses more resources, and it's more complicated14:52
mdboothAnd there's an existing API which designed for exactly this14:52
johnthetubaguymdbooth: we could just do callbacks on triggers I guess?14:52
mdboothThat's not sounding simpler :)14:52
mdboothCondition gives us: wait until X is true14:53
openstackgerritJay Pipes proposed openstack/nova master: placement: ironic inventory reporting  https://review.openstack.org/43760214:53
mdboothjohnthetubaguy: I also wrote a slightly funky test library for this, btw14:54
sdaguemriedem: thank you for sharing14:54
mdboothIt's in that patch, but it's entirely generic14:55
mdboothIt allows you to insert arbitrary wait points in test code so you can force race conditions14:55
*** smatzek_ has joined #openstack-nova14:57
*** hongbin has joined #openstack-nova15:02
openstackgerritSylvain Bauza proposed openstack/nova master: Fix default_availability_zone docs  https://review.openstack.org/43888715:03
sfinucanmdbooth: The fact that your Red Hat email isn't also mdbooth annoys me15:03
sfinucanmriedem: That run_tests patch you requested is here https://review.openstack.org/#/c/43794715:04
johnthetubaguymdbooth: maybe the bit I am not getting is why you have to reset the state when you loose connection to libvirt?15:05
*** andreas_s has quit IRC15:07
*** hemna is now known as guest_66615:08
*** guest_666 is now known as hemna15:08
*** zhurong has quit IRC15:10
*** hoangcx has quit IRC15:13
mdboothjohnthetubaguy: That was originally danpb's suggestion. It's a robustness measure.15:14
mdboothjohnthetubaguy: We need to tie initialisation to host_up anyway, because initialisation uses the libvirt connection.15:14
*** yamamoto has joined #openstack-nova15:15
johnthetubaguyyeah, host up makes sense15:15
mdboothSo re-initialising it after host_down is no great complication.15:15
johnthetubaguyjust seems odd to drop it15:15
*** lucasxu has joined #openstack-nova15:15
mdboothjohnthetubaguy: Well, if libvirt went down we don't really know what happened.15:15
mdboothThat doesn't really complicate the code all that much, anyway, as it's separate in the manager15:16
bauzasjaypipes: around ?15:17
bauzasjaypipes: I have a question for you before +Wign https://review.openstack.org/#/c/376198/1115:17
mdboothThe code is especially paranoid as it's reference counting. We want to do our best to be correct, even if operators are doing unexpected things underneath us, or things are crashing.15:18
*** larainema has quit IRC15:18
bauzasjaypipes: ie. we set the collation to latin1 encoding, I guess it's for memory reasons, right?15:18
bauzasI just wonder if that's really worth it in case we would need to add another column needing utf8 encoding, like a description TEXT field15:19
*** larainema has joined #openstack-nova15:19
*** yamamoto has quit IRC15:19
jaypipesbauzas: gimme a bit.. back to back meetings15:20
bauzasheh, no worries15:20
*** liangy has quit IRC15:20
mriedembauzas: before you go approving that code,15:21
mriedemhttps://blueprints.launchpad.net/openstack/?searchtext=resource-provider-traits15:21
mriedemcan we get the bp actually approved?15:21
bauzasoh very good point15:21
*** liangy has joined #openstack-nova15:21
bauzaswas there a spec reproposed ?15:21
mriedemhttps://review.openstack.org/#/c/345138/15:22
bauzasthere it is https://review.openstack.org/#/c/345138/15:22
bauzasyeah15:22
bauzashere is the thing, given it would take more time for that as we haven't previously approved the spec15:23
bauzasmriedem: I would then wonder if it would be worth decoupling that spec into 2 pieces15:23
mriedemi haven't read the spec,15:23
spotzHey nova, anyone about who could review the doc we're working on for the placement API and cells and give feedback? We can't build instances so we're missing something https://review.openstack.org/#/c/438328/15:23
bauzasmriedem: one would be the the basement piece we agreed as the top prio15:23
mriedemif it's the full hog of traits, then yeah probably15:23
bauzasmriedem: the other would be exposing it thru the API15:23
mriedemsince we just need the piece to fix can_host15:23
mriedemspotz: have you seen the docs in the nova devref?15:24
mriedemhttps://docs.openstack.org/developer/nova/cells.html15:24
mriedemhttps://docs.openstack.org/developer/nova/placement.html15:24
*** tovin07_ has joined #openstack-nova15:24
dansmithspotz: also, kinda need to know the error you're hitting to know what you're missing15:24
*** marst has joined #openstack-nova15:25
spotzdansmith: I'm getting the very unhelpful No valid hosts, I'm not sure what Brian got last night though15:27
*** sacharya has joined #openstack-nova15:27
dansmithspotz: got host_mappings in the apidb?15:27
*** sacharya has quit IRC15:27
*** sacharya has joined #openstack-nova15:28
spotzdansmith. Let me bring up the VM and double check15:28
spotzdansmith: Nice call, table is empty15:30
dansmithspotz: nova-manage cell_v2 discover_hosts15:30
dansmith-v15:30
*** karthiks has quit IRC15:31
*** sneti_ has joined #openstack-nova15:31
*** sneti_ has quit IRC15:31
spotzdansmith: Nada, not even with debug  nova-manage --debug cell_v2 discover_hosts15:32
dansmithspotz: got hosts actually registering with their cell db?15:32
dansmithspotz: compute_nodes and services tables in the cell1 db15:32
*** owalsh has quit IRC15:33
*** owalsh_ has joined #openstack-nova15:33
*** mtanino has joined #openstack-nova15:33
*** satyar has quit IRC15:35
spotzdansmith: I thought so, but let me go back to the DB vs output from list_cells15:35
dansmithspotz: -v should show you something at least I thought15:36
dansmithspotz: like "checking cell foo"15:36
*** sandanar has quit IRC15:36
dansmithyeah, confirmed15:36
spotzdansmith: I have a nova_cell0 DB no cell1 DB15:37
dansmithspotz: well that's a real problem :P15:37
spotzdansmith: So our create_cell didn't work?15:37
dansmithspotz: create_cell just tells nova where the db is for a given cell15:38
dansmithspotz: you should have an apidb, a cell0 db, and a cell1 db15:38
spotzdansmith: Ok so we're definitely missing steps, I do get this for list_cells though  cell1 | 143df967-eb22-4d2c-baff-bfc2538816fd |15:38
dansmithyeah, but that doesn't mean anything if you don't have a db to back it up15:38
dansmithspotz: have you looked through our devref docs mriedem pointed to?15:38
*** jgriffith has quit IRC15:39
*** jgriffith has joined #openstack-nova15:39
spotzdansmith: yeah that's where the steps came from15:39
dansmithspotz: okay I see, you're doing both of those mappings with the same config, which means they probably point to the same place?15:40
dansmithspotz: an unfortunate side-effect of the config file method for getting to this point :/15:40
macszsfinucan: lol what about no :D15:41
dansmithspotz: can you pastebin your cel_mappings table?15:41
spotzdansmith: sure hang on15:41
macszsfinucan: and also from nose's docs: "nose itself supports python 3, but many 3rd-party plugins do not!"15:41
*** psachin has quit IRC15:41
*** yamahata_ has joined #openstack-nova15:41
sfinucanmacsz: Who says we need plugins, eh? ;)15:41
* sfinucan is pretty sure a few OpenStack projects use nose. Swift, perhaps?15:42
* sfinucan is also not 100% serious. That's a lot of work :P15:42
*** adrian_otto has joined #openstack-nova15:42
spotzdansmith: https://gist.github.com/spotz/42b9d15f01607345874226873564457815:42
dansmithspotz: oh, no you do have a cell1 db15:43
dansmithspotz: in that db (nova) do you have services and compute_nodes?15:43
*** ediardo has quit IRC15:44
*** karthiks has joined #openstack-nova15:44
macszsfinucan: I have had enough of beers last week, so i can invest my friday's evenings to convert tox to nose, if you want it :P15:45
sfinucanmacsz: *testrepository to nose15:45
sfinucantox would stay15:45
spotzdansmith: added as a comment on the gist15:45
macszsfinucan: ah, sorry, was focused on typing "beer"15:45
*** liangy has quit IRC15:46
sfinucanIma take a look and see if it would even be possible. The testrepository library annoys me in many ways15:46
sfinucanmacsz: :D15:46
*** ediardo has joined #openstack-nova15:46
dansmithspotz: cool, so can you show me the exact result of "nova-manage cell_v2 discover_hosts -v" ?15:46
spotzdansmith: it didn't like -v as a switch when I tried earlier15:46
spotz--debug gave no results to screen15:47
spotzmoved it but no help15:47
*** armax has joined #openstack-nova15:47
spotzroot@controller:~# nova-manage -v cell_v2 discover_hosts15:47
spotzOption "verbose" from group "DEFAULT" is deprecated for removal.  Its value may be silently ignored in the future.15:47
*** kaisers_ has joined #openstack-nova15:48
dansmithspotz: -v goes after discover_hosts15:48
spotzdansmith: that's no joy nova-manage: error: unrecognized arguments: -v15:48
dansmithspotz: sorry it's --verbose15:49
spotzthat worked adding as a comment15:49
dansmithspotz: right so I think it worked before when you did --debug15:50
macszsfinucan: yeah... and I hate my change with "rm" as well, but I am so fed up with doing it manually, and I could not see the use for having this file around either way...15:50
dansmithspotz: it just didn't say anything because you didn't have --verbose15:50
dansmithspotz: that "checking" means the mapping is there now15:50
dansmithspotz: so you should have that host_mapping in the api db and maybe even be able to create instances15:50
spotzdansmith: 2017-02-28 15:31:57 | NULL       |  1 |       2 | compute |15:51
dansmithspotz: I need more context, can you paste the full thing in the gist?15:51
spotzdansmith: I wonder why it didn't work before though, I've run the command before15:51
*** pkholkin has quit IRC15:51
dansmithspotz: it needs to run after the host shows up in the cell db, so if you run it before you start the service it won't find it, of course15:52
spotzdansmith: It was up but I'll make sure we make a note for that15:52
*** ijw has joined #openstack-nova15:54
spotzdansmith: no joy on the instance, checking logs to see if it's something new15:54
*** unicell has joined #openstack-nova15:54
spotzdansmith: still no valid hosts in the nova-conductor.log though I do think we made progress:)15:55
*** unicell1 has quit IRC15:55
dansmithspotz: well paste some logs15:56
*** unicell has quit IRC15:56
*** owalsh_ is now known as owalsh15:57
spotzdansmith: api, scheduler and conductor logs up15:59
*** ociuhandu has joined #openstack-nova15:59
mriedemspotz: where?16:00
spotzmriedem: https://gist.github.com/spotz/42b9d15f01607345874226873564457816:00
spotzlooks like placement-api not found from compute side, gonna peek at apache16:01
dansmithspotz: would be a lot easier to read those as a new gist in fixed-width font, fwiw16:01
dansmithdamn docs people and their variable-width nonsense :P16:01
spotzdansmith: Ha I'm not really a docs person:)16:01
*** salv-orlando has joined #openstack-nova16:01
dansmithheh16:01
mriedemis the nova-compute service reporting as up?16:02
mriedemnova service-list16:02
spotzmriedem: Yep reporting as up16:02
mriedemhmm, but yeah16:02
mriedem2017-02-28 09:58:07.852 1621 WARNING nova.scheduler.client.report  [req-62fa3550-e8f7-4111-a297-6b24b20a7e1f - - - - -] The placement API  endpoint not found. Placement is optional in Newton, but required in  Ocata. Please enable the placement service before upgrading.16:02
mriedemis the placement endpoint in "openstack endpoint list"?16:02
spotzmriedem: Brian noted an apache issue last night but he's doing rhel install. Public, internal and admin present16:03
mriedemmy guess is, the compute node isn't reporting into placement, so when the scheduler asks placement for somewhere to build an instance, it says it doesn't know about anything and we get NoValidHost16:03
*** jaosorior has quit IRC16:03
mriedemare the credentials correct in the [placement] section of nova.conf on the compute node?16:04
spotzmriedem: Yep16:04
spotzI can paste them if you want16:04
*** ociuhandu has quit IRC16:05
mriedemdid you configure the compute before or after placement was running?16:07
mriedemi.e. do you need to restart the nova-compute service?16:07
spotzI did just notice os_region was there twice, once as the default openstack and the one I set to RegionOne16:07
spotzmriedem: I've restarted compute several times since config. New error Quota exceeded for instances: Requested 1, but already used 10 of 10 instances (HTTP 403) (Request-ID: req-6fedaf70-89b9-4bc4-a978-9ab04090767f)16:08
*** rcernin has quit IRC16:08
mriedemso you've already got 10 dead instances in ERROR state right?16:08
mriedemnova list would show 10 ERROR instances16:08
mriedemdelete those16:09
spotzmriedem: I've been clearing them out16:09
akijakhi, I've found a bug in nova concerning rebuilding and 'hw_disk_bus' image property (https://bugs.launchpad.net/nova/+bug/1667667), I'm looking for someone who could give me some directions how to fix that :) can you help?16:09
openstackLaunchpad bug 1667667 in OpenStack Compute (nova) "Rebuilding instance ignores image's property hw_disk_bus" [Low,Confirmed]16:09
spotzyeah just 2 in error currently16:09
*** markus_z has quit IRC16:10
efriedHowdy folks, is there a Pike equivalent of https://etherpad.openstack.org/p/ocata-nova-priorities-tracking ?  I.e. somewhere I can put up-to-date status & review priorities for the PowerVM driver "subteam"?16:11
lyarwoodakijak: hey, have you looked at https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2679 and how we are passing image_meta around?16:11
mriedemefried: i can create one16:11
efriedmriedem Thanks.  And wipe the agenda for Thursday's meeting?16:11
mriedemefried: it's only tuesday!16:11
mriedemi get to the thurs meeting agenda by about wed night16:12
efriedHeh.  Didn't know how much lead time we were supposed to have ;-)16:12
mriedemefried: if you need to change something in the meeting agenda, you can do that now16:12
*** _samdeep has quit IRC16:12
efriedrgr16:12
*** kaisers_ has quit IRC16:14
*** yingjun has quit IRC16:14
spotzmriedem: 0 instances in Error, same result16:14
*** lpetrut has quit IRC16:14
dansmithmriedem: so I noticed some weird quota behavior when I was trying to get my multicell patch working16:15
dansmithspotz: what is the [database]/connection set to in the nova conf that you're using for your apis?16:15
dansmithand conductors16:15
dansmithmaybe we're reserving in cell016:16
*** yamamoto has joined #openstack-nova16:16
mriedemi assume it's mysql+pymysql://nova:linuxacademy123@controller/nova16:17
mriedemfrom https://gist.github.com/spotz/42b9d15f01607345874226873564457816:17
*** Oku_OS is now known as Oku_OS-away16:17
dansmithactually, it has to be or other things won't work because ocata16:18
spotzmriedem: Yep16:18
spotzI know the basic config docs that are there minus placement-api and cells work as I also built a newton cluster and it's happy16:19
spotzWe're missing something, whether it's a step or something out of order16:19
*** liangy has joined #openstack-nova16:19
*** yamamoto has quit IRC16:21
efriedmriedem: I can start populating https://etherpad.openstack.org/p/pike-nova-priorities-tracking with the structure of its ocata predecessor if you like.16:23
efriedYou have more important (or at least more urgent) things to do ;-)16:23
mriedemefried: yes please16:24
*** mdrabe_ has joined #openstack-nova16:24
mriedemi'm doing 3 things at once16:24
*** Matias has quit IRC16:25
*** nkrinner is now known as nkrinner_afk16:26
mriedemspotz: can you make a curl request to the placement endpoint using the same creds as are in the nova.conf on the compute?16:26
spotzmriedem: Yep hang on16:27
*** mdrabe has quit IRC16:27
mriedemto /resource_providers would be enough16:27
*** bvanhav_ has joined #openstack-nova16:27
*** Matias has joined #openstack-nova16:27
*** bvanhav_ is now known as bvanhav16:28
*** tovin07_ has left #openstack-nova16:28
*** baoli_ has quit IRC16:28
*** bvanhav__ has quit IRC16:28
*** baoli has joined #openstack-nova16:29
*** sridharg has quit IRC16:31
*** salv-orlando has quit IRC16:32
*** prateek has quit IRC16:32
*** tbachman has quit IRC16:33
*** tbachman has joined #openstack-nova16:34
*** artom has quit IRC16:34
*** pcaruana has quit IRC16:34
*** lpetrut has joined #openstack-nova16:34
*** edand has quit IRC16:35
spotzmriedem: Bad Request but it could have been my curl16:36
*** artom has joined #openstack-nova16:36
*** baoli has quit IRC16:37
*** artom has quit IRC16:37
*** prateek_ has quit IRC16:38
*** jaypipes has quit IRC16:40
*** Jeffrey4l has quit IRC16:41
*** Jeffrey4l has joined #openstack-nova16:42
*** salv-orlando has joined #openstack-nova16:44
spotzmriedem: Yeah everytime I try to curl I'm getting the 400, I'm assuming you wanted me to just get like tokens?16:49
mriedemspotz: just get the /resource_providers16:50
mriedemyou'll need a token16:50
mdboothmriedem: https://review.openstack.org/#/c/395709/16:51
mriedemmdbooth: you don't need that16:52
mdboothNothing unexpected in the logs, either16:52
mriedemwe run the nfs job in the nova experimental queue16:52
mdboothmriedem: You mean the check experimental job?16:52
mdboothYeah, we run a bunch of other stuff in there too, though16:52
mriedem"check experimental" runs the set of experimental jobs on your nova change16:52
mriedemdirectly16:52
mdboothThat one only runs the nfs job, so it's kinda nice16:52
*** nic has joined #openstack-nova16:52
*** igordcar1 has quit IRC16:54
*** ijw_ has joined #openstack-nova16:54
*** igordcard has joined #openstack-nova16:54
mdboothmriedem: check experimental is a bit of a nose bleed. How much of it is intended to be red vs green?16:54
mriedemi need to remove some of it16:55
mriedemala https://review.openstack.org/#/c/415033/16:55
mriedembut time is an issue16:55
mdboothmriedem: The nfs job it ran passed16:56
mdboothmriedem: Incidentally, would it be practical to do 'check16:57
mdboothgate-tempest-dsvm-full-devstack-plugin-nfs-nv', and have it run just that job?16:57
mriedemspotz: http://paste.openstack.org/show/600806/16:57
mriedem^ is from my devstack, with curl to placement16:57
*** ijw has quit IRC16:57
mriedemmdbooth: that's not a thing16:57
mdboothOr have a much wider array of 'interest areas' maybe, like 'check nfs', or 'check storage'16:57
mdboothmriedem: Right, but is there any reason it's not a thing?16:58
mriedemsomeone would have to do it16:58
mdboothSure. Would it be a useful thing?16:58
mriedemidk16:58
mdboothFor eg, in this case we've run gate-tempest-dsvm-lxc-ubuntu-xenial, and it failed, but I don't really care.16:59
mriedemwhat would have been useful was if the hilton didn't f up charging me for last week so my internal expense reporting tool took over an hour to trick to make up for a separate .05 charge16:59
mriedemrecheck hilton16:59
mdboothlol16:59
mriedemspotz: i get the token via: OS_TOKEN=$(openstack token issue -c id -f value)17:00
mdboothI'm pretty sure that the scope of expense reporting tools vastly exceeds anything we have to deal with :)17:00
*** zioproto has quit IRC17:00
*** gfhellma has joined #openstack-nova17:01
spotzmriedem: Still getting no json object17:01
mriedemspotz: but a 200 or an error?17:02
*** gfhellma has quit IRC17:02
*** mvk has quit IRC17:02
*** gfhellma has joined #openstack-nova17:02
spotzmriedem: 200, I think it's me I suck at curl17:03
mriedemand the creds you're using for that token are the same as what's in nova.conf on the compute?17:03
spotzmriedem: Yeah I set up an rc and did an openstack token issue17:04
*** nicolasbock has quit IRC17:04
spotzOr I could be doing things ass backwards17:05
mriedemare you still seeing warnings in the nova-compute logs about not being able to connect to placement?17:05
*** crushil has quit IRC17:05
*** ijw has joined #openstack-nova17:06
spotzmriedem: Nope17:06
*** gcb has joined #openstack-nova17:06
*** browne has joined #openstack-nova17:07
*** irenab_ has quit IRC17:07
*** tbachman has quit IRC17:08
*** nicolasbock has joined #openstack-nova17:08
*** moshele has quit IRC17:09
*** tesseract has quit IRC17:09
mriedembut there are no resource providers coming back...17:09
*** ijw_ has quit IRC17:09
mriedemsomething is janked there then17:10
mriedembecause the compute is running a periodic task every minute that will update it's info in the placement api17:10
*** Swami has joined #openstack-nova17:10
mriedemif it can't, you should be seeing a warning every 10 minutes or so in the compute logs17:10
*** kaisers_ has joined #openstack-nova17:10
*** raunak has joined #openstack-nova17:11
spotznova-compute.log is now lines of 017-02-28 11:05:39.099 2618 INFO nova.compute.resource_tracker [req-8025f2c1-a990-4383-ab04-46e929ffce39 - - - - -] Final resource view: name=compute phys_ram=7983MB used_ram=512MB phys_disk=5GB used_disk=0GB total_vcpus=1 used_vcpus=0 pci_stats=[]17:11
mriedemthat's not it17:11
cfriesenwith the change to make live migration checks async in Newton, did horizon get updated to properly report any errors in the checks?17:11
mriedemcfriesen: it's a microversion so horizon would have to be opting in17:11
mriedemand if so,17:11
mriedemthey have to adjust for the behavior change17:11
openstackgerritJohn Griffith proposed openstack/nova master: Add attachment_uuid to BDM table  https://review.openstack.org/43874417:12
openstackgerritJohn Griffith proposed openstack/nova master: Add Cinder V3 Detach calls  https://review.openstack.org/43875017:13
openstackgerritSTEW TY proposed openstack/nova master: Complete verification of servers-action-fixed-ip.inc  https://review.openstack.org/33860617:14
mriedemsfinucan: mdbooth: you were asking why lyarwood was adding an attachment_id to the bdm table17:14
mriedemhttps://review.openstack.org/#/c/373203/17:14
mriedemis why17:14
mriedemyou should read it since we need more eyes on it17:14
mriedemdansmith: what do you think, should we shit or get off this pot? https://review.openstack.org/#/c/242602/17:15
dansmithmriedem: lol17:15
mriedemwe have no immediate need for it right now that i'm aware of17:16
mdboothmriedem: Coincidentally just reading that17:16
mriedembut it's always something that comes up as "if we only had a uuid on the bdm"17:16
dansmithmriedem: I don't care.. seems like a good thing, and people seem to occasionally need it17:16
*** jaypipes has joined #openstack-nova17:16
dansmithbut yeah if no need then whatever17:16
mdboothlyarwood: You still need a commit message btw :P17:16
dansmithI can abandon if it's bothering you17:16
mriedemit's not bothering me17:16
* lyarwood will add more context to that later17:16
mriedembut lyarwood is building on it17:16
lyarwoodmdbooth: meh, can't you read my mind?17:16
mdboothlyarwood: Not until you push it to gerrit :)17:17
mriedemlyarwood: consequently, what state is https://review.openstack.org/#/c/290793/ in now?17:17
*** yamamoto has joined #openstack-nova17:18
*** nic has left #openstack-nova17:18
*** nic has joined #openstack-nova17:19
lyarwoodmriedem: rotting on the floor, I had an open question around how to actually use the new UUIDs to avoid this iirc17:19
jgriffithomg that change is everywhere :)17:19
mriedemspotz: looking for the errors from here https://github.com/openstack/nova/blob/45cb83829e5b16dbacb7c71b7a49060c75cad986/nova/scheduler/client/report.py#L5117:19
mriedemthat will log the warning every 10 tries, so 10 minutes https://github.com/openstack/nova/blob/45cb83829e5b16dbacb7c71b7a49060c75cad986/nova/scheduler/client/report.py#L4317:20
mriedemearlier you said you hit this https://github.com/openstack/nova/blob/45cb83829e5b16dbacb7c71b7a49060c75cad986/nova/scheduler/client/report.py#L5917:20
*** dtp has joined #openstack-nova17:20
mriedemspotz: can you share the nova.conf from your compute node?17:20
cfriesenquestion about aborting live migration...where are users supposed to find the appropriate migration id?  I don't see it returned in the response to the live-migrate request or instance-action.  Are they supposed to parse the output of migration-list?17:21
mriedemnova migration-list or something17:21
*** armax has quit IRC17:21
spotzmriedem: Yep, its just the one built through the install guide, nothing prorietary let me get it for you17:21
mriedemsdague: i still owe you that nickel, i totally forgot to pay up in person17:23
mriedemcfriesen: https://docs.openstack.org/cli-reference/nova.html#nova-migration-list17:23
*** yamahata_ has quit IRC17:23
mriedemthat api currently filters so that only live migration records are returned17:23
sfinucantonyb: Just FYI, https://review.openstack.org/#/c/438510/ merged so the next pbr release should be coming shortly (I hope)17:23
*** yamamoto has quit IRC17:23
mriedemcfriesen: see https://review.openstack.org/#/c/407237/17:24
spotzmriedem: It's gthe latest comment but it decided it needed a BIG font for some reason17:25
*** lpetrut has quit IRC17:25
*** lpetrut has joined #openstack-nova17:26
mriedemspotz: ?17:26
mriedemcomment where?17:26
spotzmriedem: here new gist https://gist.github.com/spotz/4550ffcd9568d608bf6f483ef5feebab17:26
mriedemefried: https://etherpad.openstack.org/p/pike-nova-priorities-tracking looks grand, thanks17:26
*** thorst_afk is now known as thorst17:27
efriedmriedem Thanks, still working on it.17:27
mriedemspotz: and a gist for the rc you used to make the curl request to the placement endpoint?17:28
*** ijw has quit IRC17:28
*** jdandrea has quit IRC17:28
*** karimb has quit IRC17:28
openstackgerritSTEW TY proposed openstack/nova master: Complete verification of servers-action-fixed-ip.inc  https://review.openstack.org/33860617:29
*** ltomasbo is now known as ltomasbo|away17:29
spotzmriedem: https://gist.github.com/spotz/779bd1045c0422b6dd1cc6640dd1178717:30
*** gcb has quit IRC17:30
*** ZZelle has joined #openstack-nova17:31
mriedemthat all looks fine17:31
spotzmriedem: It's gotta be something stupid just not sure what17:34
spotzI do appreciate all the help today mriedem and dansmith!17:34
mriedemyeah i don't really understand it, if the creds are ok for you to make a curl request, then nova-compute should be reporting into the placement api17:35
mriedemand the curl request you made should return something17:35
mriedemand there are no errors or warnings in the nova-compute logs...17:35
*** claudiub has quit IRC17:36
*** ijw has joined #openstack-nova17:36
spotzmriedem: yeah it's not making much sense and the more I tinker I worry I'm losing track of what I changed. Between Brian and I testing each version of the doc we'll get it just not as quickly as I was hoping17:36
mriedemdo you see this debug message in the n-cpu logs? https://github.com/openstack/nova/blob/45cb83829e5b16dbacb7c71b7a49060c75cad986/nova/scheduler/client/report.py#L58217:37
mriedeme.g. http://logs.openstack.org/59/383859/19/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/4377f7d/logs/screen-n-cpu.txt.gz#_2017-02-28_14_35_05_21017:37
spotzmriedem: Nope, just 2017-02-28 11:37:29.369 2204 INFO nova.scheduler.host_manager [req-b549cd44-392e-4992-a88e-31f7180a3451 - - - - -] Successfully synced instances from host 'compute'.17:38
*** antwash has joined #openstack-nova17:38
spotzAnd one retry filter a while ago17:39
*** jpena is now known as jpena|away17:39
cfriesenmriedem: thanks, I knew about that command.  The inconvenience is that there's no way to list the currently active migration for a server, so the user has to list all the migrations, then find the currently active one for the server of interest.17:39
*** sudipto_ has quit IRC17:39
*** sudipto has quit IRC17:39
cfriesenmriedem: why doesn't the live migration request return the migration ID?  (or the "nova instance-action" command?)17:40
antwashjohnthetubaguy, sdague : hey there! I have something for you to look at https://review.openstack.org/#/c/439070/ -- marked as WIP until feedback is received.17:40
antwash^^ when yo have time17:40
*** ijw has quit IRC17:41
*** edand has joined #openstack-nova17:41
spotzmriedem: Thanks again for the help, need to afk17:42
mriedemcfriesen: i don't think we have a migration id before we return from the live migration request17:44
mriedemcfriesen: would have to look to confirm17:44
mriedemthe instance-action is not specific to live migration17:44
mriedemso it wouldn't have a migration id in it17:44
*** derekh has quit IRC17:44
mriedemyou'd have to extend instance actions if you wanted to store extra meta per action17:44
*** Apoorva has joined #openstack-nova17:45
efriedmriedem Think I'm done; added announcement & link on meeting agenda.17:47
mriedemcfriesen: so we should be pulling migrations per server /servers/{uuid}/migrations17:47
mriedemcfriesen: would have to look at what nova migration-list does, because i thought it would take a server uuid17:48
*** annegentle has joined #openstack-nova17:48
mriedemah17:48
mriedemhttps://docs.openstack.org/cli-reference/nova.html#nova-server-migration-list17:48
mriedemcfriesen: ^17:48
mriedemthat will return the list of live migrations for the given server17:49
mriedemif you have a high enough api to provide that microversion17:49
*** pkholkin has joined #openstack-nova17:49
openstackgerritDan Smith proposed openstack/nova master: Target cell in conductor cold migrate  https://review.openstack.org/43802217:52
openstackgerritDan Smith proposed openstack/nova master: Change MQ targeting to honor only what is in the context  https://review.openstack.org/43802317:52
openstackgerritDan Smith proposed openstack/nova master: Add cell field to Destination object  https://review.openstack.org/43802417:52
openstackgerritDan Smith proposed openstack/nova master: WIP: Make conductor ask scheduler to limit migrates to same cell  https://review.openstack.org/43802517:52
dansmithno whammies no whammies no whammies17:53
*** crushil has joined #openstack-nova17:54
*** slaweq_ has quit IRC17:55
*** fragatina has joined #openstack-nova17:55
*** slaweq_ has joined #openstack-nova17:56
*** fragatina has quit IRC17:57
*** fragatina has joined #openstack-nova17:58
*** kaisers_ has quit IRC17:58
*** kfarr has quit IRC17:59
cfriesenmriedem: okay, server-migration-list is useful.  still requires parsing though.  would it maybe make sense to have a "--active" flag on that to return just the in-progress migration for that server?18:00
cfriesenor do we just make client code sort the response by ID and pick the latest to try to get the active one?18:02
*** moshele has joined #openstack-nova18:02
mriedemcfriesen: it might be nice to add a status filter query parameter to the /servers/id/migrations REST API18:03
mriedemwe could validate that with json schema now18:03
mriedemcfriesen: but it does look like you could filter client side18:04
mriedemwe print out the migration status18:04
*** lucasagomes is now known as lucas-afk18:05
cfriesenmriedem: hmm...in newton at least it appears that "server-migration-list" doesn't show completed migrations18:07
*** bastafidli has quit IRC18:08
*** bastafidli has joined #openstack-nova18:08
*** romainh1 has joined #openstack-nova18:09
*** romainh1 has quit IRC18:09
mriedemcfriesen: that's because it's calling objects.MigrationList.get_in_progress_by_instance18:10
mriedemwhere in-progress is one of18:11
mriedem'queued', 'preparing',18:11
mriedem                                                'running',18:11
mriedem                                                'post-migrating']18:11
mriedemwhy we only return in progress migrations, idk18:11
mriedemi think because that api was added for being able to cancel a live migration18:11
mriedemwhich you can only do if it's running18:11
mriedemtdurakov might remember more18:11
*** romainh has quit IRC18:12
mriedemcfriesen: so before you ask "why only in progress live migrations?" i think that's the original idea of why, but "can we return all, not just in progress?" - i'd think sure18:12
mriedemi believe the os-migrations API returns all migrations18:13
mriedemimo it's a pretty clunky gd API and is tailor made just for canceling a live migration18:13
mriedemwhich seemed to be too short sighted18:13
cfriesenmriedem: hmm...the API docs do specify that it's in-progress live migrations, but the CLI docs don't specify that it's only for in-progress migrations.18:14
*** bvanhav_ has joined #openstack-nova18:15
tdurakovIt was done to return adress live-mig abort functionality18:15
*** bvanhav has quit IRC18:16
cfriesentdurakov: okay, thanks.  I agree it's a bit clunky, but it does at least let you get the info needed to abort.18:17
*** salv-orl_ has joined #openstack-nova18:17
cfriesenmriedem: tdurakov: is it just me that thinks "nova server-migration-list" is a wierd command for something that should only ever have a single result?18:18
*** yamamoto has joined #openstack-nova18:19
*** salv-orlando has quit IRC18:20
*** dtp has quit IRC18:20
mriedemcfriesen: i believe i wrote the api ref docs because they didn't exist18:21
mriedemand i was sorting this all out about 5 months ago18:21
tdurakovMigration list is awful...18:21
mriedemcfriesen: you could push a patch to update the cli help18:23
mriedemto make it more clear18:23
*** yamamoto has quit IRC18:25
*** unicell has joined #openstack-nova18:25
*** tbachman has joined #openstack-nova18:26
*** dtp has joined #openstack-nova18:28
*** bvanhav_ has quit IRC18:29
*** bvanhav_ has joined #openstack-nova18:29
*** dharinic is now known as dharinic|lunch18:31
*** krtaylor has quit IRC18:32
*** gfhellma_ has joined #openstack-nova18:33
*** sambetts is now known as sambetts|afk18:33
*** lucasxu has quit IRC18:34
*** lpetrut has quit IRC18:35
*** gfhellma has quit IRC18:35
*** karimb has joined #openstack-nova18:35
*** mlavalle has quit IRC18:35
*** karimb has quit IRC18:35
*** bvanhav_ is now known as bvanhav18:38
*** artom has joined #openstack-nova18:39
*** thumpba has quit IRC18:40
*** jed56 has quit IRC18:40
*** baoli has joined #openstack-nova18:41
*** liangy has quit IRC18:43
*** salv-orl_ has quit IRC18:45
*** tbachman has quit IRC18:46
*** tbachman has joined #openstack-nova18:48
*** moshele has quit IRC18:48
*** bkopilov has quit IRC18:49
*** yamahata has joined #openstack-nova18:49
*** ijw has joined #openstack-nova18:51
*** gfhellma__ has joined #openstack-nova18:54
*** kaisers_ has joined #openstack-nova18:54
*** irenab_ has joined #openstack-nova18:55
*** bastafidli has quit IRC18:57
*** ijw has quit IRC18:57
*** gfhellma_ has quit IRC18:58
*** adisky_ has quit IRC18:59
*** gfhellma__ has quit IRC19:00
*** baoli has quit IRC19:00
*** baoli has joined #openstack-nova19:01
*** baoli has quit IRC19:01
*** bastafidli has joined #openstack-nova19:03
*** dtp has quit IRC19:04
*** bkopilov has joined #openstack-nova19:05
*** lucasxu has joined #openstack-nova19:06
*** gfhellma has joined #openstack-nova19:07
*** lucasxu has quit IRC19:08
*** thumpba has joined #openstack-nova19:10
*** thumpba has quit IRC19:10
*** baoli has joined #openstack-nova19:11
*** salv-orlando has joined #openstack-nova19:12
*** amoralej is now known as amoralej|off19:13
*** dharinic|lunch is now known as dharinic19:14
*** krtaylor has joined #openstack-nova19:15
*** edand has quit IRC19:15
*** gszasz has quit IRC19:16
*** fragatina has quit IRC19:17
*** kaisers_ has quit IRC19:18
*** krtaylor has quit IRC19:18
openstackgerritMonty Taylor proposed openstack/nova master: WIP Clean up and consolidate client creation  https://review.openstack.org/43851219:19
openstackgerritMonty Taylor proposed openstack/nova master: Be a little more explicit about checking ok status  https://review.openstack.org/43912119:19
*** krtaylor has joined #openstack-nova19:19
*** lpetrut has joined #openstack-nova19:19
*** kaisers_ has joined #openstack-nova19:21
*** yamamoto has joined #openstack-nova19:21
*** armax has joined #openstack-nova19:23
*** krtaylor has quit IRC19:23
*** Apoorva has quit IRC19:24
*** Apoorva has joined #openstack-nova19:25
*** liangy has joined #openstack-nova19:26
*** yamamoto has quit IRC19:27
openstackgerritSujitha proposed openstack/nova master: Remove mox from nova/tests/unit/db/test_db_api.py  https://review.openstack.org/43455719:32
*** krtaylor has joined #openstack-nova19:36
*** krtaylor has quit IRC19:39
*** READ10 has quit IRC19:39
*** krtaylor has joined #openstack-nova19:39
*** krtaylor has quit IRC19:42
*** fragatina has joined #openstack-nova19:42
*** baoli has quit IRC19:42
*** baoli has joined #openstack-nova19:43
*** krtaylor has joined #openstack-nova19:44
*** lucasxu has joined #openstack-nova19:45
*** tbachman_ has joined #openstack-nova19:45
tdurakovmriedem: I wonder what if we just merge these 2 comands from the client side, I mean ,nova migration-list and nove server-migration-list19:45
*** tbachman has quit IRC19:46
*** tbachman_ is now known as tbachman19:46
*** krtaylor has quit IRC19:46
mriedemtdurakov: as in like nova migration-list --server <optional server id> which toggles the behavior, i.e. which REST API to call?19:47
*** fragatina has quit IRC19:47
tdurakovafair there is no --server param in nova migration list19:48
mriedemthere isn't19:48
mriedembut that's how i'd unify the CLIs19:48
tdurakovyeah19:48
*** krtaylor has joined #openstack-nova19:48
tdurakovsounds good!19:48
tdurakovonce takashi implement the spec, it will be more useful19:49
*** krtaylor has quit IRC19:50
*** fragatina has joined #openstack-nova19:50
*** fragatina has quit IRC19:50
mriedemit is a bit odd, the os-migrations API behaves differently depending on if you're using >=2.2319:51
*** fragatina has joined #openstack-nova19:51
mriedem2.23+ will add links to servers for in-progress live migrations19:52
mriedem2.23+ will always return the migration_type19:52
mriedemand os-migrations doesn't filter on just live migrations19:52
mriedemso it can also return cold migrations and evacuations19:52
openstackgerritDan Smith proposed openstack/nova master: WIP: Make conductor ask scheduler to limit migrates to same cell  https://review.openstack.org/43802519:53
mriedem/servers/uuid/migrations will only return in-progress live migrations19:53
mriedemwe are definitely missing some behavioral details in the api-ref for os-migrations https://developer.openstack.org/api-ref/compute/?expanded=list-migrations-detail#list-migrations19:53
*** tbachman has quit IRC19:54
*** ijw has joined #openstack-nova19:55
tdurakovright, but the problem with the link, that is passed after 2.23 is already there19:55
*** baoli has quit IRC19:56
mriedemi'm not sure i understand your point19:56
mriedemos-migrations will return the links for 2.23+, and we also have /servers/id/migrations at 2.2319:56
mriedemso yes it's redundant19:56
mriedemi believe that's why os-migrations is marked as "frozen"19:56
mriedemalthough the APIs do behave differently19:57
mriedemso it's kind of odd that os-migrations is frozen19:57
mriedemit seems to be frozen for a very specific case, which is the in-progress live migration case so you can cancel those things19:57
*** tbachman has joined #openstack-nova19:57
tdurakovmy current understanding of the problem: I'd like to see /servers/uuid/migrations become more useful(not only live-migrations) and maybe not only active, based on that I think it's worth to have a mechanism to filter migrations not only by  instnace, but host and cell as well19:57
mriedembut if i'm an admin and i just want to see any migration, including completed ones, i can't use /servers/id/migrations19:57
mriedemi don't even see where os-migrations filters by cell19:58
tdurakovmriedem: http://paste.openstack.org/show/600833/19:59
mriedemtdurakov: in general yes, i think if /servers/id/migrations replaces os-migrations, then the former needs to be built up to serve the needs that the latter already provideds19:59
mriedem*provided19:59
*** ijw has quit IRC19:59
tdurakovis doc help doc misleading?19:59
mriedemi think so19:59
mriedemi don't see anything in the db api code about filtering migrations by cell name19:59
* mriedem looks at the client code20:00
tdurakovat the same point it would be weird to filter out migration by host at the uri: /servers/id/migrations because it's about servers, righht?20:01
mriedemyeah cell_name is passed as a query parameter20:01
mriedemcorrect20:01
mriedemso the GET query parameters are passed way down to migration_get_all_by_filters in the db api20:01
mriedemand cell_name isn't a thing that gets filtered on20:01
mriedemso the CLI code is lying to us20:01
mriedem:)20:01
mriedemcell_name is not even in the migrations table20:02
mriedemso i don't know who thought that up20:02
*** baoli has joined #openstack-nova20:03
*** bastafidli has quit IRC20:04
mriedemhttps://github.com/openstack/python-novaclient/commit/3c2a817efcb6954f3c8246c32ce997b9e3a4d00020:07
mriedemcell_name was just always there20:07
mriedemcrazy ass rax20:07
mriedemi'll remove that from novaclient20:07
*** belmoreira has joined #openstack-nova20:08
*** mlavalle has joined #openstack-nova20:09
mriedemthis will allow me to procrastinate on recapping the resource provider talk from the PTG, which i didn't follow most of i don't think20:11
mriedemsomething something traits ironic inventory success glory fame20:11
mriedemjaypipes: ^ is that the summary from the PTG?20:11
*** mrhillsman has quit IRC20:13
mriedemsdague: i suppose to be a nice guy, i should deprecate a completely worthless and unused CLI arg/python API binding option in novaclient for a release before removing it right?20:13
mriedemeven though it's never ever worked20:13
*** baoli has quit IRC20:15
tdurakovmriedem: patch is in progress20:15
*** baoli has joined #openstack-nova20:15
mriedemtdurakov: are you deprecating or removing?20:15
mriedemalso https://bugs.launchpad.net/python-novaclient/+bug/166874320:15
openstackLaunchpad bug 1668743 in python-novaclient "nova migration-list --cell_name does not actually do anything" [Undecided,New] - Assigned to Matt Riedemann (mriedem)20:15
tdurakovno reason procrastinating on resource provider20:15
*** harlowja has quit IRC20:15
*** tbachman has quit IRC20:15
*** harlowja has joined #openstack-nova20:16
*** adrian_otto has quit IRC20:16
*** tbachman has joined #openstack-nova20:18
*** READ10 has joined #openstack-nova20:18
*** nic has quit IRC20:19
*** mrhillsman has joined #openstack-nova20:20
*** yamamoto has joined #openstack-nova20:23
*** yamamoto has quit IRC20:23
*** baoli has quit IRC20:25
*** baoli has joined #openstack-nova20:25
jaypipesmriedem: kind of, though I'm actually writing an email summarizing resource providers/placement stuff at the PTG. do you want me to continue that?20:27
mriedemjaypipes: that would be tops20:28
jaypipesmriedem: so, continue this email then? :)20:29
openstackgerritTimofey Durakov proposed openstack/python-novaclient master: remove cell_name parameter from nova migration-list  https://review.openstack.org/43914120:29
tdurakovmriedem: if you still want to procrastinate^20:29
mriedemjaypipes: yes please20:30
*** baoli has quit IRC20:30
mriedemcontrary to popular belief i don't love doing the recap emails20:30
*** kaisers_ has quit IRC20:32
*** salv-orlando has quit IRC20:32
*** liverpooler has joined #openstack-nova20:34
*** bastafidli has joined #openstack-nova20:34
tdurakovmriedem: what's the proper way deprecating params in nova-client?20:35
mriedemtdurakov: there is a DeprecatedAction class20:35
mriedemit's used elsewhere20:35
tdurakovmriedem: ok, will submit new deprecation one20:36
tdurakovbut will remove that in a next release:-p20:36
*** mvk has joined #openstack-nova20:37
*** kfarr has joined #openstack-nova20:41
*** bvanhav has quit IRC20:42
*** tbachman has quit IRC20:43
*** baoli has joined #openstack-nova20:43
*** liverpooler has quit IRC20:43
*** liverpooler has joined #openstack-nova20:44
openstackgerritTimofey Durakov proposed openstack/python-novaclient master: Deperecate cell_name cli arg for migration-list  https://review.openstack.org/43914720:50
tdurakovmriedem: ^20:50
*** mrda has left #openstack-nova20:51
*** tbachman has joined #openstack-nova20:51
mriedemsfinucan: you've been deprecating nova-network related options, why not also firewall_driver?20:53
*** aslezil_ has quit IRC20:53
mriedemonce nova-network is gone, there is only one impl for firewall_driver which is the noop one20:53
*** aslezil_ has joined #openstack-nova20:53
*** yamamoto has joined #openstack-nova20:54
*** aslezil_ has quit IRC20:55
*** aslezil_ has joined #openstack-nova20:55
*** ijw has joined #openstack-nova20:56
*** lpetrut has quit IRC20:56
*** aslezil_ has quit IRC20:56
*** aslezil_ has joined #openstack-nova20:57
*** baoli has quit IRC20:58
*** yamamoto has quit IRC20:59
*** ijw has quit IRC21:01
*** Apoorva_ has joined #openstack-nova21:01
*** kaisers_ has joined #openstack-nova21:02
*** baoli has joined #openstack-nova21:03
*** sdague has quit IRC21:03
*** moshele has joined #openstack-nova21:05
*** Apoorva has quit IRC21:05
*** lpetrut has joined #openstack-nova21:05
tonybsfinucan: \o/21:05
*** abhishek_k has joined #openstack-nova21:08
*** abhishekk has quit IRC21:11
*** armax has quit IRC21:12
*** adrian_otto has joined #openstack-nova21:13
*** dave-mccowan has quit IRC21:13
*** READ10 has quit IRC21:15
*** READ10 has joined #openstack-nova21:17
*** yamamoto has joined #openstack-nova21:17
*** belmoreira has quit IRC21:18
*** belmoreira has joined #openstack-nova21:20
*** yamamoto has quit IRC21:21
*** crushil has quit IRC21:24
*** moshele has quit IRC21:25
*** mjura has quit IRC21:25
*** aysyd has quit IRC21:25
*** artom has quit IRC21:27
*** kfarr has quit IRC21:27
*** belmoreira has quit IRC21:27
*** jwcroppe has quit IRC21:28
*** smatzek_ has quit IRC21:28
*** jwcroppe has joined #openstack-nova21:28
*** ociuhandu has joined #openstack-nova21:31
*** artom has joined #openstack-nova21:32
*** artom has quit IRC21:32
*** jwcroppe_ has joined #openstack-nova21:32
*** artom has joined #openstack-nova21:33
*** jwcroppe has quit IRC21:33
dansmithmriedem: so on the traits thing,21:33
*** acabot has quit IRC21:33
dansmithmriedem: I would hate to see us delay merging the mechanical stuff because we're obsessing over the stuff in the spec which is a little higher level than what we need right away21:34
dansmithobviously I don't want to have two specs, but I wonder if we could move the -2 up a couple patches without risking too much?21:34
*** slaweq__ has joined #openstack-nova21:34
dansmithI haven't looked over the comments on the spec, I just see that there are some21:35
*** slaweq_ has quit IRC21:35
*** Jeffrey4l has quit IRC21:35
*** yassine has quit IRC21:36
mriedemdo we have any api db blocker migrations we need to do first or anything?21:38
dansmithI don't think so21:38
*** crushil has joined #openstack-nova21:38
dansmiththat said, I'm looking at the set of patches and I'm not sure where I'd re-place the -2 without just delaying at a different spot21:38
dansmithso maybe it's not worth it21:39
*** ijw has joined #openstack-nova21:39
*** salv-orlando has joined #openstack-nova21:39
mriedemunicode traits huh21:40
mriedempile of poo can be a trait21:40
*** thorst has quit IRC21:41
*** thorst has joined #openstack-nova21:42
*** gouthamr has quit IRC21:44
*** yassine has joined #openstack-nova21:45
mriedemdo we have a resource tracker patch ready to set the trait that depends on this data model change?21:46
*** thorst has quit IRC21:46
mriedemi don't see anything in RT building on this yet21:46
*** acabot has joined #openstack-nova21:46
*** lucasxu has quit IRC21:46
*** Jeffrey4l has joined #openstack-nova21:48
*** unicell has quit IRC21:49
dansmithmriedem: the only RT intersection is reporting the compute-node trait on startup/RP creation or something21:49
*** lucasxu has joined #openstack-nova21:49
*** Apoorva_ has quit IRC21:50
mriedemyeah, and then the scheduler passing that into the resource provider GET query with the filter param right?21:50
mriedemand something something aggregates fits in there too21:50
*** Apoorva has joined #openstack-nova21:50
mriedemso,21:50
mriedemthe immediate need for this is for scheduling with shared storage pools and aggregate resource providers right?21:51
mriedemwe have a separate bp for that - we could just tie this into that work and decouple the data model change from the REST API/scheduling fallout that will probably come from the traits spec21:51
mriedemif that makes sense21:51
*** ijw has quit IRC21:52
dansmithscheduler asks for that trait to placement, but yeah21:52
*** ijw has joined #openstack-nova21:52
dansmiththe immediate need is that we can't start reporting any shared pool resources (regardless of if we use them) until we can distinguish them from compute nodes21:52
mriedemyeah, so let's do the traits data model change under https://blueprints.launchpad.net/nova/+spec/shared-resources-pike21:52
mriedemis that a fair compromise?21:53
dansmithis that a paperwork hack?21:53
dansmithI don't care how you justify it :P21:53
*** unicell has joined #openstack-nova21:53
*** annegentle has quit IRC21:54
mriedemit's a papercut21:54
dansmith*rimshot*21:55
*** yamahata has quit IRC21:55
mriedemjaypipes: oh sql wizard of yore, can you answer my question in https://review.openstack.org/#/c/376198/11/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/041_resource_provider_traits.py@57 ?21:55
*** ijw has quit IRC21:56
mriedemcburgess: L33 here https://etherpad.openstack.org/p/nova-ptg-pike-cinder21:57
cburgessmriedem Yes what?21:57
mriedemcburgess: what was the outcome of that? wasn't it "roll this into johnthetubaguy's spec"?21:57
cburgessYes it was21:57
*** tblakes has quit IRC21:57
mriedemhot21:57
mriedemdamn21:57
cburgessmriedem See my comments on https://review.openstack.org/#/c/373203/1421:58
cburgessI need to re-review that though now.21:58
mriedemthus concludes my nova/cinder recap email, yay21:59
cburgessmriedem I'll review rev 15 of that spec today and update with any comments I have as it related to our spec that needs to be merged into this one.22:00
*** dtp has joined #openstack-nova22:00
mriedemsuper22:00
*** Apoorva_ has joined #openstack-nova22:05
*** armax has joined #openstack-nova22:06
*** Apoorva has quit IRC22:08
*** krtaylor has joined #openstack-nova22:08
cburgessmriedem Comments added. We still need to account for the changes that will impact BFV in the spec22:09
*** ducttape_ has joined #openstack-nova22:10
*** claudiub has joined #openstack-nova22:12
*** yamamoto has joined #openstack-nova22:12
openstackgerritMatt Riedemann proposed openstack/nova master: Default firewall_driver to nova.virt.firewall.NoopFirewallDriver  https://review.openstack.org/43918722:12
*** tbachman has quit IRC22:13
*** baoli has quit IRC22:13
*** baoli has joined #openstack-nova22:13
*** baoli has quit IRC22:14
*** edmondsw has quit IRC22:17
*** bastafidli has quit IRC22:22
*** baoli has joined #openstack-nova22:24
*** gouthamr has joined #openstack-nova22:30
*** mnestratov|2 has joined #openstack-nova22:33
*** annegentle has joined #openstack-nova22:34
jaypipesmriedem: answered. sorry for delay.22:36
*** raunak has quit IRC22:36
*** mnestratov has quit IRC22:36
jaypipesmriedem: I blame cburgess.22:36
cburgessjaypipes Wait what did I do this time?22:36
mriedemjaypipes: i'm not sure i understand your response22:37
mriedemresource_provider_traits doesn't have a unique constraint defined, but it has 2 primary keys22:37
*** raunak has joined #openstack-nova22:37
*** amotoki has quit IRC22:37
mriedemdo we not need a unique constraint because of those 2 primary keys?22:37
*** mnestratov|2 has quit IRC22:38
cburgessA primary key is already unique. Why would you need to unique them again?22:38
jaypipescburgess: everything. you did everything.22:38
mriedemit's the combo, but i think i'm just over thinking it22:38
jaypipesmriedem: the primary key is unique and already contains trait and provider id, yes.22:38
*** antwash has left #openstack-nova22:38
cburgessjaypipes I'm glad someone has finally realized that.22:39
jaypipesmriedem: and the uniqueness isn't dependent on the order. In other words, the constraint of uniqueness over (trait, provider) applies implicitly to (provider, trait)22:39
*** amotoki has joined #openstack-nova22:42
mriedemand we're doing a mapping table b/c you can have M:M22:42
mriedemunlike inventories/resource_classes22:42
mriedema single inventory has a single resource class22:43
mriedembut a resource provider can have multiple traits22:43
mriedemand a trait can be used by multiple resource providers22:43
mriedemused/exposed whatever22:43
mriedemalright22:43
*** baoli has quit IRC22:43
*** lpetrut has quit IRC22:44
openstackgerritMatt Riedemann proposed openstack/nova master: [placement] Add Traits related table to the api database  https://review.openstack.org/37619822:44
mriedemjaypipes: dansmith: ok +2 on https://review.openstack.org/#/c/376198/ now22:45
*** tjones has joined #openstack-nova22:45
*** tjones has left #openstack-nova22:46
*** amotoki has quit IRC22:46
*** crushil has quit IRC22:48
*** burt has quit IRC22:49
jaypipesmriedem: yup, zactly correct.22:49
*** adrian_otto has quit IRC22:50
jaypipesmriedem: and thanks for adding that blueprint to get this going.22:50
*** salv-orlando has quit IRC22:50
dansmithjaypipes: left the +W for you22:50
*** salv-orlando has joined #openstack-nova22:50
mriedemok hosers i'll talk to you tomorrow22:51
*** mriedem is now known as mriedem_away22:51
dansmithmelwitt: *gasp* https://review.openstack.org/#/c/438025/22:52
dansmithlooks like the gate is too busy to run my devstack patch against that, but at least it's passing the regular setup22:52
*** ijw has joined #openstack-nova22:53
jaypipesWallaby'd.22:53
*** edmondsw has joined #openstack-nova22:58
*** ijw has quit IRC22:58
masberhi23:00
*** esberglu has quit IRC23:00
dansmithinfra says nodepool is jammed up, fyi to anyone waiting23:00
*** edmondsw has quit IRC23:01
masberanybody knows why when I do "nova image-create --poll  ..." the image size is 0?23:01
*** edmondsw has joined #openstack-nova23:01
masberI am following this document --> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/5/html/End_User_Guide/cli_migrate_instances.html#create_snapshot23:01
masberand this one --> https://docs.openstack.org/user-guide/cli-use-snapshots-to-migrate-instances.html23:02
dansmithmasber: that first document is about icehouse, which is ancient. nova image routines are deprecated, and this is not a support channel (please see topic)23:02
*** esberglu has joined #openstack-nova23:02
*** jwcroppe_ has quit IRC23:03
*** felipemonteiro_ has quit IRC23:03
*** felipemonteiro has quit IRC23:03
*** armax has quit IRC23:03
*** esberglu has quit IRC23:07
*** baoli has joined #openstack-nova23:07
*** jamesdenton has quit IRC23:08
masberdansmith, sorry, I couldn't get help on #openstack channel23:11
masberso i was wondering if I could get some ideas from here as the people is specialised on nova...23:11
*** tbachman has joined #openstack-nova23:11
masberapologise again23:12
*** lucasxu has quit IRC23:15
*** Apoorva_ has quit IRC23:17
*** Apoorva has joined #openstack-nova23:17
*** edmondsw has quit IRC23:18
*** edmondsw has joined #openstack-nova23:19
*** crushil has joined #openstack-nova23:20
*** baoli has quit IRC23:22
*** ducttape_ has quit IRC23:23
*** jwcroppe has joined #openstack-nova23:25
*** tbachman_ has joined #openstack-nova23:27
*** tbachman has quit IRC23:30
*** tbachman_ is now known as tbachman23:30
*** Fdaisuke has joined #openstack-nova23:33
*** tbachman has quit IRC23:35
*** tbachman has joined #openstack-nova23:41
*** marst has quit IRC23:42
*** liangy has quit IRC23:45
*** edmondsw has quit IRC23:45
*** edmondsw has joined #openstack-nova23:46
melwittdansmith: woot \o/23:46
*** yamahata has joined #openstack-nova23:47
*** sacharya has quit IRC23:47
*** tbachman has quit IRC23:48
*** edmondsw has quit IRC23:50
*** amotoki has joined #openstack-nova23:53
*** jwcroppe has quit IRC23:53
openstackgerritJay Pipes proposed openstack/nova master: placement: ironic inventory reporting  https://review.openstack.org/43760223:53
*** crushil has quit IRC23:53
jaypipesdansmith: ok dokey :) ^^ hopefully I got it right this time.23:54
*** ijw has joined #openstack-nova23:54
jaypipesheading back to hotel from office... biab.23:54
*** annegentle has quit IRC23:55
*** dave-mccowan has joined #openstack-nova23:57
cburgessjaypipes Yick another week of travel right after PTG?23:58
*** ijw has quit IRC23:59

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